I've been doing this for 10 years. I've successfully run the M-audio delta 1010LT, the delta 1010, the Echo Audiofire12, and now the Raydat. The only card which has ever exhibited this behavior is the Raydat, so there is a high likelihood it is the Raydat's issue. The drivers which were written for this card are brand-new as of alsa 1.0.25, if I remember correctly. Perhaps I should notify the author (Adrian Knoth) of the driver... <div>
<br></div><div>As for now, I'm making due with Jack2, recording the "export" on to a stereo track, and then exporting the track itself. Seems to work, albeit a bit more slowly...</div><div><br></div><div>Thanks again for the attention.. Hopefully we figure this out, because the Raydat is an amazing card, and works very well with Linux OOTB.</div>
<div><br></div><div>--Jason<br><br><div class="gmail_quote">On Sat, May 5, 2012 at 2:59 PM, Stéphane Letz <span dir="ltr"><<a href="mailto:letz@grame.fr" target="_blank">letz@grame.fr</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Could it be that the RME Raydat interface does not "restart" correctly when the freewheel (export) mode is finished?<br>
<br>
Can you possibly test with another audio card? Or even with the "dummy" driver?<br>
<br>
Stéphane<br>
<br>
<br>
Le 5 mai 2012 à 22:08, Jason Jones a écrit :<br>
<div class="HOEnZb"><div class="h5"><br>
> Can you possibly get a larger error log?<br>
><br>
> Actually, there is no error to be found anywhere, but in the jack messages, and those are the only ones. Neither jack nor mixbus stop working when this error manifests itself. It just sits with the export dialog window open forever.<br>
><br>
> It seems like mixbus is simply waiting for some sort of response from jack.<br>
><br>
> Perhaps there's a way to get more verbose logs?<br>
><br>
> Thanks for your response, and patience, Stephane.<br>
><br>
> --Jason<br>
<br>
</div></div></blockquote></div><br></div>