Re: [Rosegarden-user] Irritation rather than bug

2014-12-17 Thread david
On 12/17/2014 11:50 AM, D. Michael McIntyre wrote: > On 12/17/2014 04:18 PM, Abrolag wrote: > >> Every time Rosegarden shuts down I get this little sequence. > > Been seeing some kind of jack error on Rosegarden exit for about 10 > years now. I reckon we would have fixed it if anybody knew how, an

Re: [Rosegarden-user] Irritation rather than bug

2014-12-17 Thread Abrolag
On Wed, 17 Dec 2014 17:29:19 -0500 Ted Felix wrote: > On 12/17/2014 04:18 PM, Abrolag wrote: > > Every time Rosegarden shuts down I get this little sequence. > > JackEngine::XRun: client = rosegarden was not finished, state = Triggered > >I usually just turn JACK auto-start off in the prefer

Re: [Rosegarden-user] Irritation rather than bug

2014-12-17 Thread Ted Felix
On 12/17/2014 04:18 PM, Abrolag wrote: > Every time Rosegarden shuts down I get this little sequence. > JackEngine::XRun: client = rosegarden was not finished, state = Triggered I usually just turn JACK auto-start off in the preferences: Edit > Preferences > Audio > General > Start JACK Automa

Re: [Rosegarden-user] Irritation rather than bug

2014-12-17 Thread D. Michael McIntyre
On 12/17/2014 04:18 PM, Abrolag wrote: > Every time Rosegarden shuts down I get this little sequence. Been seeing some kind of jack error on Rosegarden exit for about 10 years now. I reckon we would have fixed it if anybody knew how, and all the actual audio developers are loon

[Rosegarden-user] Irritation rather than bug

2014-12-17 Thread Abrolag
Every time Rosegarden shuts down I get this little sequence. ## JackEngine::XRun: client = rosegarden was not finished, state = Triggered JackAudioDriver::ProcessGraphAsyncMaster: Process error 21:15:03.491 XRUN callback (6). JackEngine::XRun: client = rosegarden was not finished, state =