I'm cross posting, including this to the JACK mailing list. On Sun, Feb 26, 2012 at 1:09 AM, Jason Jones <poeticintensity(a)gmail.com> wrote: Hey guys.. I recently acquired a RME Raydat interface (works like a *charm*, and I love it!), but ever since I installed it, I'm getting a random error when I try to export my tracks, and it's driving me bonkers. Previously to installing the Raydat card, I had used ardour for approximately 10 years, and have never experienced this problem. The problem is about 75% of the time, when exporting, the GUI will just sit there and do nothing, maintaining the "export" button depressed continually. Within QJackctl's "message" window, I see the following error: JackEngine::XRun: client = ardour was not run: state = 2 JackFreewheelDriver::Process: Process error 00:31:20.920 XRUN callback (1). The remaining 25% of the time it exports just fine, without issue. Needless to say, this is extremely frustrating. Googling the problem returns nothing but the snippet of code which contains the error message itself, which can be found at the link below: http://www.trac.jackaudio.org/browser/jack2/branches/pipelining/common/Jack… Any help would be greatly appreciated. If more info is needed, please let me know what I can get you. Also, thanks to everyone who assured me that the Raydat card works well under Linux. It really does work like a charm. Regards, --Jason www.advancedbudgetstudios.com I've since found that this problem only occurs in Jack2. Jack1 exports 100% of the time just fine, but I've found that Jack2 (aside from the export problem) works much better under high stress. Most of my projects contain a high number of tracks / plugins / etc... Thus, high stress. It'd be very nice to go back to Jack2, but not being able to export pretty much kills any usefulness from it. Any ideas at all? Thanks in advance. --Jason _______________________________________________ Jack-Devel mailing list Jack-Devel(a)lists.jackaudio.org http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org

Can you possibly get a larger error log? 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. It seems like mixbus is simply waiting for some sort of response from jack. Perhaps there's a way to get more verbose logs? Thanks for your response, and patience, Stephane. --Jason

I'm cross posting, including this to the JACK mailing list. On Sun, Feb 26, 2012 at 1:09 AM, Jason Jones wrote: Hey guys.. I recently acquired a RME Raydat interface (works like a *charm*, and I love it!), but ever since I installed it, I'm getting a random error when I try to export my tracks, and it's driving me bonkers. Previously to installing the Raydat card, I had used ardour for approximately 10 years, and have never experienced this problem. The problem is about 75% of the time, when exporting, the GUI will just sit there and do nothing, maintaining the "export" button depressed continually. Within QJackctl's "message" window, I see the following error: JackEngine::XRun: client = ardour was not run: state = 2 JackFreewheelDriver::Process: Process error 00:31:20.920 XRUN callback (1). The remaining 25% of the time it exports just fine, without issue. Needless to say, this is extremely frustrating. Googling the problem returns nothing but the snippet of code which contains the error message itself, which can be found at the link below: http://www.trac.jackaudio.org/browser/jack2/branches/pipelining/common/Jack… Any help would be greatly appreciated. If more info is needed, please let me know what I can get you. Also, thanks to everyone who assured me that the Raydat card works well under Linux. It really does work like a charm. Regards, --Jason www.advancedbudgetstudios.com <http://www.advancedbudgetstudios.com> I've since found that this problem only occurs in Jack2. Jack1 exports 100% of the time just fine, but I've found that Jack2 (aside from the export problem) works much better under high stress. Most of my projects contain a high number of tracks / plugins / etc... Thus, high stress. It'd be very nice to go back to Jack2, but not being able to export pretty much kills any usefulness from it. Any ideas at all? Thanks in advance.

Since issue doesn't occur 100% of the time, maybe it's something specific to projects that have the problem - like a particular plugin or softsynth patch? On 05/05/2012 09:34 AM, Jason Jones wrote: > I'm cross posting, including this to the JACK mailing list. > > On Sun, Feb 26, 2012 at 1:09 AM, Jason Jones wrote: > > Hey guys.. I recently acquired a RME Raydat interface (works like a > *charm*, and I love it!), but ever since I installed it, I'm getting > a random error when I try to export my tracks, and it's driving me > bonkers. > > Previously to installing the Raydat card, I had used ardour for > approximately 10 years, and have never experienced this problem. > > The problem is about 75% of the time, when exporting, the GUI will > just sit there and do nothing, maintaining the "export" button > depressed continually. Within QJackctl's "message" window, I see > the following error: > > JackEngine::XRun: client = ardour was not run: state = 2 > > JackFreewheelDriver::Process: Process error > > 00:31:20.920 XRUN callback (1). > > > The remaining 25% of the time it exports just fine, without issue. > > > Needless to say, this is extremely frustrating. Googling the > problem returns nothing but the snippet of code which contains the > error message itself, which can be found at the link below: > > > http://www.trac.jackaudio.org/browser/jack2/branches/pipelining/common/Jack… > > > Any help would be greatly appreciated. If more info is needed, > please let me know what I can get you. > > > Also, thanks to everyone who assured me that the Raydat card works > well under Linux. It really does work like a charm. > > > Regards, > > --Jason > > www.advancedbudgetstudios.com <http://www.advancedbudgetstudios.com> > > > > I've since found that this problem only occurs in Jack2. Jack1 exports > 100% of the time just fine, but I've found that Jack2 (aside from the > export problem) works much better under high stress. Most of my > projects contain a high number of tracks / plugins / etc... Thus, high > stress. It'd be very nice to go back to Jack2, but not being able to > export pretty much kills any usefulness from it. Any ideas at all? > > Thanks in advance.

I'm cross posting, including this to the JACK mailing list. On Sun, Feb 26, 2012 at 1:09 AM, Jason Jones &lt;poeticintensity(a)gmail.com&gt;wrote;wrote: I've since found that this problem only occurs in Jack2. Jack1 exports 100% of the time just fine, but I've found that Jack2 (aside from the export problem) works much better under high stress. Most of my projects contain a high number of tracks / plugins / etc... Thus, high stress. It'd be very nice to go back to Jack2, but not being able to export pretty much kills any usefulness from it. Any ideas at all? Thanks in advance. --Jason