[ardour-users] Ardour was not fast enough

Mark Knecht markknecht at gmail.com
Sun Jul 17 21:18:03 PDT 2005

OK, so basically you have lots of disk throughput, so if the 'disk
cannot keep up', as the Ardour message goes, it's most likkely a red
herring sort of message. More likely something else is getting in the

Sorry that I've forgotten or didn't read this earlier but you are
using a pretty old version of Fedora Core. Can you post the output of
these commands?

uname -a
cat /proc/asound
cat /proc/interrupts

I may be wrong but you're using a pretty new version of Jack with a
pretty old kernel. I wonder if many folks have tried that combination?

Since you got better xrun results by up-ing the latency that suggests
to me that somehow the realtime aspect of the kernel is not working.
I'd have to go back and look at how that was done on 2.4 kernels, but
I should double check that:

1) When configuring Jack through qjackctl that you ARE enabling
realtime in the config screen

2) That if oyu look at the message screen for QJC you see realtime
getting enabled.

All for now,

On 7/17/05, Devin Venable <dvenable at valornet.com> wrote:
> > Would you please post the results of this command run as root?
> >
> > hdparm -tT /dev/hda
> >
> No problem:
> /dev/hda2:
>  Timing buffer-cache reads:   460 MB in  2.04 seconds = 225.05 MB/sec
>  Timing buffered disk reads:  138 MB in  3.00 seconds =  45.97 MB/sec
> Other hardware info:
> K7VM2 Rev 2.02 motherboard
> Duron 1.4 GHz CPU
> 709 MB RAM
> Maxtor 2F040L0 hard drive
> ES1370 AudioPCI sound card
> Other software info:
> Fedora Core 1 ( Linux version 2.4.26-1.ll.rhfc1.ccrma )
> jackd version 0.99.0
> Ardour/GTK 0.9beta29
>    (built using 0.589.2 with libardour 0.887.1)

More information about the Ardour-Users mailing list