[ardour-users] exporting tracks?

Wolfgang Woehl tito at rumford.de
Wed Apr 27 06:38:19 PDT 2005

Kevin, ok, you tried a lot of things. Next thing you could try is build 
ardour with "scons DEBUG=1" and run it inside a debugger:

$ cd ardour/gtk_ardour
$ ./ardbg
gdb shows up, at the prompt you say
gdb> run
When the export crashes/comatizes ardour you can try to get a backtrace 
gdb> thread apply all bt
(If ardour doesn't really crash though it's more complicated. You would 
have to set a breakpoint and then apply bt)

Another thing to check would be to look for jackd right after the 
freeze. Is it alive?
In qjackctl -> Setup you can set a (much) longer timeout so that jackd 
waits longer for an app to come back up again.

If the above doesn't help then you should 
/join #ardour on freenode.net to get live and way more competent help 
from las, taybin, sampo_v2 and nick_. Keep a list at hand with exact 
kernel version, jackd version, ardour version etc.

> Each of those cases I've tried with the realcap module loaded

I'm on 2.4.26/caps, no experience with 2.6/realcap module

> long enough -- a minute or two -- while ardour grinds, then the
> exported file seems intact and sounds like what I'd expect.
> I guess my experience isn't exactly "quietly freezing and dying"
> in that ardour didn't die; it slipped into a coma maybe.

It's a productive coma then, isn't it :?

> In the ardour-dev mailing list archives I found a thread titled
> "workaround for the "silent export" bug using beta19?"  This is Paul

That was something else obviously.

> ardour.rc things have mattered in the past for other issues.  I
> can't see how this might be the case now, but here is the config
> for things other than key-bindings in my ardour.rc:

Your rc looks totally ok. Me being a monkey I would try the case with 
vst disabled, but just out of a hunch. I use vst too and have zero 
problems with it.


>   <MIDI-port tag="hw:0" device="/dev/snd/midiC0D0" type="alsa/raw"
> mode="duplex"/> <MIDI-port tag="hw:1" device="/dev/snd/midiC1D1"
> type="alsa/raw" mode="duplex"/> <MIDI-port tag="seq" device="ardour"
> type="alsa/sequencer" mode="duplex"/> <Config>
>     <Option name="minimum-disk-io-bytes" value="262144"/>
>     <Option name="track-buffer-seconds" value="5.000000"/>
>     <Option name="mute-affects-pre-fader" value="yes"/>
>     <Option name="mute-affects-post-fader" value="yes"/>
>     <Option name="mute-affects-control-outs" value="yes"/>
>     <Option name="mute-affects-main-outs" value="yes"/>
>     <Option name="solo-latch" value="yes"/>
>     <Option name="mtc-port" value="hw:0"/>
>     <Option name="mmc-port" value="hw:0"/>
>     <Option name="midi-port" value="hw:0"/>
>     <Option name="jack-time-master" value="no"/>
>     <Option name="trace-midi-input" value="no"/>
>     <Option name="trace-midi-output" value="no"/>
>     <Option name="plugins-stop-with-transport" value="no"/>
>     <Option name="no-sw-monitoring" value="yes"/>
>     <Option name="stop-recording-on-xrun" value="no"/>
>     <Option name="stop-at-session-end" value="no"/>
>     <Option name="auto-xfade" value="yes"/>
>     <Option name="no-new-session-dialog" value="yes"/>
>     <Option name="timecode-source-is-synced" value="yes"/>
>     <Option name="auditioner-left-out" value="alsa_pcm:playback_2"/>
>     <Option name="use-vst" value="yes"/>
>   </Config>

More information about the Ardour-Users mailing list