[Ardour-Users] xruns??? or soemthins else makes my playhead freeze and Ardour crash

Robin Gareus robin at gareus.org
Mon May 21 08:31:27 PDT 2012

Hi Wendy,

On 05/21/2012 04:51 PM, fukked up wrote:
> You have -p twice with different arguments.

That's perfectly OK. It means different things.

> On 21.05.2012 16:00, Wendy Van Wynsberghe wrote:
>> /usr/bin/jackd -p 128 -R -P 60 -T -d alsa -n 2 -r 48000
>> -p 1024 -d hw:0,0
> I don't think this is causing your issues, though.

The '-p' before the driver (-d alsa) sets the "--port-max"

The '-p' after the driver is a backend parameter "--period"

> I wouldn't recommend using a non-rt or realtime kernel with less than -p
> 512 and -n4 but that depends on your hw and further setup.
> I once had huge problems because of pulseaudio.
> To check if it's running, enter in the terminal:
> ps aux | grep pulseaudio
> if it's running,
> create ~/.pulse/client.conf with the following content:
> autospawn = no
> type
> pulseaudio -k
> into the terminal.

more info: http://jackaudio.org/pulseaudio_and_jack

> start jack.
> hth
> /mn0
>> ------> What else can I do to find out what's going on?

Starting jackd from the commandline (or use qjackctl) - take ardour out
of the equation for now.

Play a simple audio. eg 'mplayer -ao jack some_file.wav'

Try jackd in verbose mode: `jackd -v -d alsa` -  it's really verbose but
some hints may be in there.

If the problem persists, send the full output of `jackd -v -d alsa` here
or to the jack-devel mailing-list (or post it somewhere (pastebin) if
it's too large for an email.)

It may be related to pulseaudio and/or the built-in soundcard. Those
HDA-Intel cards are bad bad bad :)


More information about the Ardour-Users mailing list