From: Jim C. <m_...@bu...> - 2012-10-28 18:19:37
|
After finding a bit of time to spend playing with rosegarden, after several months of inactivity, and not really having used it with much dedication for 3 or 4 years, I've forgotten some things, and there are probably new features/behavior that I've not yet learned, so apologies in advance if I start to bombard the group with questions after not having posted much in the past. My first question: How do I disable use of jackd? I'm currently using an external synthesizer as my sound generator and don't need jack. I tried Edit -> Preferences -> General -> Behavior, and I see that "Use jack transport" is unchecked. If this is the right place to disable jack, it's not working, since 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? Thanks. Jim |
From: Jim C. <m_...@bu...> - 2012-10-28 18:40:26
|
I forgot to mention which version I'm using. I've got a recent development version from svn a few days ago. svn info says: Path: . Working Copy Root Path: /home/development/jtc/rosegarden/rosegarden URL: svn://svn.code.sf.net/p/rosegarden/code/trunk/rosegarden Repository Root: svn://svn.code.sf.net/p/rosegarden/code Repository UUID: cf6a83e7-f017-4305-b0b3-678bde24f230 Revision: 13127 Node Kind: directory Schedule: normal Last Changed Author: tedfelix Last Changed Rev: 13127 Last Changed Date: 2012-10-23 18:23:39 -0500 (Tue, 23 Oct 2012) Thanks. On Sun, 28 Oct 2012 13:06:34 -0500 Jim Cochrane <m_...@bu...> wrote: > After finding a bit of time to spend playing with rosegarden, after > several months of inactivity, and not really having used it with much > dedication for 3 or 4 years, I've forgotten some things, and there are > probably new features/behavior that I've not yet learned, so apologies > in advance if I start to bombard the group with questions after not > having posted much in the past. > > My first question: How do I disable use of jackd? I'm currently > using an external synthesizer as my sound generator and don't need > jack. I tried Edit -> Preferences -> General -> Behavior, and I see > that "Use jack transport" is unchecked. If this is the right place > to disable jack, it's not working, since 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? > > > Thanks. > Jim > > ------------------------------------------------------------------------------ > WINDOWS 8 is here. > Millions of people. Your app in 30 days. > Visit The Windows 8 Center at Sourceforge for all your go to > resources. http://windows8center.sourceforge.net/ > join-generation-app-and-make-money-coding-fast/ > _______________________________________________ > Rosegarden-user mailing list > Ros...@li... - use the link below to > unsubscribe > https://lists.sourceforge.net/lists/listinfo/rosegarden-user |
From: D. M. M. <ros...@gm...> - 2012-10-28 22:33:46
|
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. There isn't any neat way to disable this. The workaround is to edit your ~/.jackdrc and just put some garbage in there whenever you don't want JACK to start. For example, you had: /usr/bin/jackd -dalsa -dhw:2 -r48000 -p1024 -n2 -S Change to something like: foo/usr/bin/jackd -dalsa -dhw:2 -r48000 -p1024 -n2 -S Since foo/usr/bin/jackd is an invalid path, it will fail, and no more audio server. 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 they changed, so we have to ask what this setting is when they come along one day complaining that audio is broken, six months after the last time they tinkered around with their settings. I'd really rather not, but I'm not giving a firm no for an answer. -- D. Michael McIntyre |
From: Jim C. <m_...@bu...> - 2012-10-30 04:29:09
|
Hi Michael. Thanks for the response. On Sun, 28 Oct 2012 18:33:39 -0400 "D. Michael McIntyre" <ros...@gm...> 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. > > There isn't any neat way to disable this. The workaround is to edit > your ~/.jackdrc and just put some garbage in there whenever you don't > want JACK to start. I presumed that this would be the case - that there's a reasonable explanation for missing this config. option. So I went ahead with my version of a work-around: I renamed /bin/jackd to /bin/jackd-hidden. Your method is less brutal and more reasonable, though, so I think I'll switch to it. > > For example, you had: > > /usr/bin/jackd -dalsa -dhw:2 -r48000 -p1024 -n2 -S > > Change to something like: > > foo/usr/bin/jackd -dalsa -dhw:2 -r48000 -p1024 -n2 -S > > Since foo/usr/bin/jackd is an invalid path, it will fail, and no more > audio server. > > 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 they changed, so we have to ask what this setting is > when they come along one day complaining that audio is broken, six > months after the last time they tinkered around with their settings. > I'd really rather not, but I'm not giving a firm no for an answer. I won't argue against that. If this was expensive commercial software, I'd feel I have a right to ask; but it's not, and since there appears to be some good work going on to RG these days, I don't want to risk slowing it down for an unnecessary request. Thanks. Jim |
From: John O'H. <res...@jo...> - 2012-10-31 02:40:25
|
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? Regards, -- John |
From: Holger M. <ho...@ma...> - 2012-10-31 06:07:50
|
On Wed, 31 Oct 2012, 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. On my Xubuntu 11.10 I never had a problem. Rosegarden started and endet my jackd. My .jackdrc was "/usr/bin/jackd -dalsa -r44100 -p128 -n2 -Xseq -D -Chw:5,1 -Phw:0,1" But since JACK has so many advantages (e.g. recording flash-sound when running firefox to record streaming-only content in the web) I decided that all applications should be redirected to jack. This works with the following ~./asoundrc or /etc/asound.conf: pcm.!default { type plug slave.pcm "jack" } pcm.jack { type jack playback_ports { 0 system:playback_1 1 system:playback_2 } capture_ports { 0 system:capture_1 1 system:capture_2 } } My jackd is now started by qjackctl that's autonatically started by my session manager. I can now even record the sound that's produced by virtual machines (VirtualBox), eg. browser sounds of a Windows-VM. |
From: S. C. C. <s_c...@ho...> - 2012-10-31 06:44:47
|
KXStudio <http://kxstudio.sourceforge.net/> also sets Jack up as the uber sound driver for the system, which I LOOOVE! I never have to think about whether or not Jack needs to be started, etc., because it's always running. KXStudio also integrates Pulseaudio as just another Jack client. This makes it really easy to capture the sound out of anything that happens to be running on my PC. And everything Just Works(tm). -~Chris On 10/31/2012 01:07 AM, Holger Marzen wrote: > On Wed, 31 Oct 2012, 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. > On my Xubuntu 11.10 I never had a problem. Rosegarden started and endet > my jackd. My .jackdrc was "/usr/bin/jackd -dalsa -r44100 -p128 -n2 -Xseq > -D -Chw:5,1 -Phw:0,1" > > But since JACK has so many advantages (e.g. recording flash-sound when > running firefox to record streaming-only content in the web) I decided > that all applications should be redirected to jack. This works with the > following ~./asoundrc or /etc/asound.conf: > > pcm.!default { > type plug > slave.pcm "jack" > } > > pcm.jack { > type jack > playback_ports { > 0 system:playback_1 > 1 system:playback_2 > } > capture_ports { > 0 system:capture_1 > 1 system:capture_2 > } > } > > My jackd is now started by qjackctl that's autonatically started by my > session manager. > > I can now even record the sound that's produced by virtual machines > (VirtualBox), eg. browser sounds of a Windows-VM. > > ------------------------------------------------------------------------------ > Everyone hates slow websites. So do we. > Make your web apps faster with AppDynamics > Download AppDynamics Lite for free today: > http://p.sf.net/sfu/appdyn_sfd2d_oct > _______________________________________________ > Rosegarden-user mailing list > Ros...@li... - use the link below to unsubscribe > https://lists.sourceforge.net/lists/listinfo/rosegarden-user > > |
From: david <gn...@ha...> - 2012-10-31 08:00:57
|
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???? -- David gn...@ha... authenticity, honesty, community http://clanjones.org/david/ http://dancing-treefrog.deviantart.com/ |
From: John O'H. <res...@jo...> - 2012-11-01 10:58:47
|
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 Testing. -- John |
From: david <gn...@ha...> - 2012-11-02 06:42:02
|
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 > Testing. I've lost track - is this JACK1 or JACK2 being used? I have JACK2. -- David gn...@ha... authenticity, honesty, community http://clanjones.org/david/ http://dancing-treefrog.deviantart.com/ |
From: John O'H. <res...@jo...> - 2012-11-03 01:15:18
|
On 02/11/12 17:41, david wrote: > On 11/01/2012 12:58 AM, John O'Hagan wrote: >> On 31/10/12 19:00, david wrote: [...] >>> 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 >> Testing. > > I've lost track - is this JACK1 or JACK2 being used? I have JACK2. > I have jack2 also. To clarify the garbled mess I wrote above, what I should have said was "I find jackd _doesn't_ shut down when RG does. Some don't have this problem. For those who use jack all the time it doesn't matter." IMHO, whatever the pros and cons of using jack for everything, it would be good if the -T option to jack was behaving as expected, i.e. jack should shut down once no clients remain. However it turns out that this issue isn't restricted to RG: qsynth also leaves jack running after exiting on my system. My ~.jackdrc has: /usr/bin/jackd -dalsa -dhw:0 -r44100 -p256 -n4 What I see in my task manager after running RG and/or qsynth is: jackd -T -ndefault -dalsa -dhw:0 -r44100 -p256 -n4 Notice the extra "-T -ndefault" in front of the option string. Any jack experts out there able to cast some light on this? -- John |