On 11/01/2012 12:58 AM, John O'Hagan wrote:
> On 31/10/12 19:00, david wrote:
>> On 10/30/2012 04:40 PM, John O'Hagan wrote:
>>> On 29/10/12 09:33, D. Michael McIntyre wrote:
>>>> On 10/28/2012 02:06 PM, Jim Cochrane wrote:
>>>>> jackd is started up whenever I start
>>>>> rosegarden, even though this box is unchecked. Is there another spot in
>>>>> the GUI to disable jack that I'm not seeing?
>>>> There is no box for that as such. Rosegarden isn't starting jackd so
>>>> much as the JACK API is starting jackd. I misremember the technical
>>>> details, but basically we made a minor change to use a different API
>>>> call, and now the audio server starts itself when Rosegarden does if
>>>> it's not already running. This is basically a good thing, since it
>>>> starts Rosegarden with all of its features enabled by default.
>>>> I suppose we could consider making some config option that would prevent
>>>> Rosegarden from even attempting to start JACK, but I'd really rather not
>>>> bother unless there is a lot of demand. It's just one more confusing
>>>> configuration option for people to misunderstand, one more thing for
>>>> everybody to have to translate, and one more thing for users to forget
>>> I agree with the approach, but there is an unfortunate consequence in
>>> this case, at least on my Debian XFCE box, RG 12.04: after using
>>> Rosegarden, jackd remains running, and prevents all my normal (ALSA)
>>> applications' audio from working, except the handful which are
>>> automatically jack-aware. This means manually terminating jack, from a
>>> task manager or whatever, after each RG session; users still have to
>>> manage jack, with all the attendant potential for confusion.
>>> I'm not sure why this is happening, as jackd is started with the -T
>>> option, which means it should exit once it has no clients left, and
>>> which is what it used to do when I started jack manually (using
>>> qjackctl) in earlier RG versions which did not start jack automatically.
>>> However, now it keeps running happily after RG exits, even though
>>> qjackctl shows no connections remain. Any ideas why?
>> Hmm, I just started RG 12.04 under Debian Sid XFCE. RG didn't start up
>> jackd. Which is the way I like it. So your RG is starting JACK whether
>> or not you want it started????
> Yes, as the OP stated and D. Michael McIntyre confirmed, that is the way
> it's supposed to work, at least if jackd is installed. Some would prefer
> this didn't happen and need to use tricks to achieve this. Personally I
> like it, but find it shut down when RG does. Some don't have this
> problem For others it seems this is happening already. I'm using Debian
I've lost track - is this JACK1 or JACK2 being used? I have JACK2.
authenticity, honesty, community