You are not logged in.

#1 2014-06-05 14:06:54

asnakeofjune
Member
Registered: 2014-06-03
Posts: 3

Ardour/Jack problems

Hello,

my first post here. I've searched a lot around the internet to solve my problem but I didn't find any solution.

My issue: Ardour randomly crashes and has a big DSP load while idle.

This is a message I get when I start Ardour from shell:

JackEngine::XRun: client = ardour was not finished, state = Running
JackAudioDriver::ProcessGraphAsyncMaster: Process error

(ardour-3.5.378:23219): GLib-CRITICAL **: Source ID 200 was not found when attempting to remove it

I'm using Ardour from extra repo and till yesterday jack2 from community. Yesterday I tried jack2 from AUR but there is no better performance.
I can't find out where my problem is and I don't know where to look any further.

My system:
HP xw8600 Workstation (2x Xeon 5420 and 8GB RAM)
RME HDSP9652 on PCI-X slot with its own IRQ (52)

Kernel: linux-rt-lts-3.10.39_rt40-1-x86_64 with kernel parameter threadirqs
My installation: I followed the beginners guide, added all of the ProAudio wiki instructions incl. rtirq and cpu scaling governor performance.

I tried very different things with jack: Sometimes 128 frames are working better than 256. It is really confusing. But everytime I have xruns - especially when loading plugins like calf. I'm using calf-git, because calf is outdated.

The DSP load is about 30% when idle and I was lucky to open my recent project without a crash. It has ~30 tracks and ~10 busses - there are nearly no plugins (3 or 4) loaded.

What else can I do? What logs can I check? Is it a hardware problem?
This evening I will try my old RME Digi 9636 card to check if my HDSP is the problem.

Thanks in advance for your help and suggestions.

Regards
Tim

Offline

#2 2014-06-05 14:23:14

emeres
Member
Registered: 2013-10-08
Posts: 1,570

Re: Ardour/Jack problems

How do you set up jack, what start parameters do you use? Do you have xruns without anything using audio just after starting jack? Do simple players cause xruns? Do you use dithering or resampling?

Last edited by emeres (2014-06-05 14:32:10)

Offline

#3 2014-06-05 15:34:36

asnakeofjune
Member
Registered: 2014-06-03
Posts: 3

Re: Ardour/Jack problems

As I'm not completely sure but I think it is:

jackd -S -R -dalsa -dhw:DSP -P80 -r48000 -p256 -n2

I'm not at the machine right now.

When jack is up there are no xruns. Xruns occure esspecially when I start ardour and it load a session with active plugins. I don't remember any xruns when using audacious.

Thanks and regards
Tim

Offline

#4 2014-06-05 21:30:45

emeres
Member
Registered: 2013-10-08
Posts: 1,570

Re: Ardour/Jack problems

That leaves you with a latency of approx. 11 ms. What does speaker-test say about DSPs buffer and period ranges? Try going both directions, increasing to 40 ms and decreasing as low as it gets. Increase the samplerate for that.
So a new empty session does not produce xruns? Only when using plugins, every time like you wrote? Try to isolate the source of the problem. I do not use Ardour yet, only took a glance at it. I did not find many options, probably looking through wiki might turn up something useful.

Offline

#5 2014-06-13 14:33:55

asnakeofjune
Member
Registered: 2014-06-03
Posts: 3

Re: Ardour/Jack problems

Thank you very much for your help. I didn't ever use speaker-test, but I'll give it try.

I loaded my project and deleted all plugins and saved this as a snapshot. There is an idle DSP load at approx 15% at realtime mode with 256/2. No xrun at all. What could be the reason for that load? What should I look at? There must be something else than a plugin.

Offline

#6 2014-06-13 21:52:55

emeres
Member
Registered: 2013-10-08
Posts: 1,570

Re: Ardour/Jack problems

What specific plugins are you using? (name, version) What about cpu load/affinity? Try disabling realtime and check if the load is as high as it was before with plugins loaded.

Offline

Board footer

Powered by FluxBB