![]() I could see these drifting out of step with one another which was odd because they are both ‘clocked’ from the same signal. The chipset also has two internal registers that act as pointers to the internal audio buffers for capture and playback. The ICE1712 chipset has a shared interrupt for the capture and playback halves of the card, this is triggered when either half needs ‘attention’ - the driver then has to go and read a register in the chip to find out who caused the interrupt. There are many things you can tweak with regard to PCI settings, that affect the so-called latency (by changing how long a device can grab the PCI bus for etc) but it isn’t quite the same as the time taken for the kernel to process an interrupt from a hardware device which I think is where the problem lies. This sounds like the problem I was having with my ICE1712 chipset - if that is the case, then its really a problem with the chipset design, that gets triggered by an aspect of the kernel behaviour (windows or I think you may be refering to interrupt priority, which although connected with this issue isn’t quite the same. JACK connects to the driver for your soundcard (ALSA, FFADO, or OSS) and finally, the driver (loaded as a kernel module) actually controls the hardware. Ardour doesn’t interface directly with (or care) about your sound card, Ardour just connects to JACK as another client to the JACK audio server. I haven’t got my sound working yet in firefox so I’m guessing there’s some kind of Ubuntu-Studio setup that is defaulting to the onboard sound & causing Ardour want to over ride the Jack settings unless I start Jack I think its quite certain that the problem is not with Ardour (or JACK). I run qjackctl & in settings I set Frames/Period - 128, Sample Rate 44100, Periods/Buffer 2 & that puts my latency at 5.8 msĪrdour automaticaly starts Jack every time at start up so I haven’t figured how to start it without Jack though there probably isn’t a good reason to do it except for testing purposes. The M-audio is the only one that shows up in Alsamixer & I know the M-audio is what Ardour is recording & playing back with. M Audio Audiophile 24/96 at 0xb400, irq 18ġ : EMU10K1 - SB Live! Value Evidently all three sound sources are picked up because cat/proc/asound/cards yields:Ġ : ICE1712 - M Audio Audiophile 24/96 ![]() I’m using an M-audio audiophile 2496, but i also have a soundblaster live card installed & my onboard audio is turned off in the bios. ![]() My guess is that it has something to do with my second sound card or onboard sound that I think runs at 48K So really the only problem I have is when I open Ardour without opening up Jack first.Įvidently when Ardour opens up Jack it defaults to 48K. The good news is that I was only opening up the Jack Control before starting Ardour & not actually starting the Jack server so that’s why I was still getting 48k sample rate/ 21.3 ms.(My Bad) if I start jack first it shows its running at 44100 & then open Ardour everything works great showing 44100/2.9ms & no pops or clicks. Sorry I’ve been away for while but I really appreciate the help & I’ll try to answer a few things.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |