[Ardour-users] WAV files, xruns

[Anthony DiSante]

Anthony wrote:
> * Steffen Sauder <steffensauder at gmx.de> [Feb 20 04 08:53]:
> 
>>Anthony DiSante wrote:
>>
>>
>>>A couple questions here.  Before I installed the low latency patches, 
>>>I got
>>>lots of xruns from the ardour process.  They went away after I applied 
>>>the
>>>Morton and Love low-latency patches, but I still get xruns from the jackd
>>>process.  I've got 4 windows open (ardour, ardour mixer, the xterm owning
>>>ardour, and the xterm owning jackd), and just clicking from window to 
>>>window
>>>causes these xruns from jackd, like this:
>>>
>>>**** alsa_pcm: xrun of at least 43.943 msecs
>>>
>>>Should I be concerned about this?  I don't think I've noticed it 
>>>affecting
>>>the recording at all, but then I'm only recording 2 channels, at the 
>>>moment.
> 
> 
> Yes, you should be. It *will* affect recording. Make sure you are running
> as root, lowlatency is enabled, and that jack is using a non-journaling
> filesystem for shm. Make your latency as large as you can tolerate, in
> fact I suggest choosing the -n and -p options as big as the device allows.
> Make sure you don't have an autopoller checking the CD-rom drive.

I'm running as root, lowlatency is enabled, and I don't have any 
automounters for my cdrom drives.

I did do the shmfs thing when installing jack (I have "shmfs on /dev/shm 
type shm"), but that was a while ago.  Is there a way I can make sure jack 
is actually using it?

Also, how do I know what values to choose for -n and -p for my card?

Thanks,
Anthony
http://nodivisions.com/