Hi,
do you know if there's a way to turn qjackctl on through the console? That
is, the program is already open, but instead of clicking start or stopp, I
wanted to do it with bash commands.
Thanks (again),
João
João Pais wrote:
Hi,
do you know if there's a way to turn qjackctl on through the console? That is, the program is already open, but instead of clicking start or stopp, I wanted to do it with bash commands.
qjackctl uses jackd as a backend, so you can do what you want without accessing qjackctl at all and just using jackd (whether jackd was started by qjackctl or not).
You can manually run jackd with the commands qjackctl would have used by running "sh .jackdrc"
If you start jackd in this way, then qjackctl should see that running jackd instance instead of making a new one.
To stop jackd from the commandline, regardless of how it was started, you can run "killall jackd".
You can use the various jack tools like jack_lsp, jack_connect, jack_disconnect, to do the things you would usually do in qjackctl from the command line (list client ports, connect them to one another, disconnect them from one another).
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Justin Glenn Smith wrote:
João Pais wrote:
Hi,
do you know if there's a way to turn qjackctl on through the console? That is, the program is already open, but instead of clicking start or stopp, I wanted to do it with bash commands.
qjackctl uses jackd as a backend, so you can do what you want without accessing qjackctl at all and just using jackd (whether jackd was started by qjackctl or not).
You can manually run jackd with the commands qjackctl would have used by running "sh .jackdrc"
If you start jackd in this way, then qjackctl should see that running jackd instance instead of making a new one.
To stop jackd from the commandline, regardless of how it was started, you can run "killall jackd".
You can use the various jack tools like jack_lsp, jack_connect, jack_disconnect, to do the things you would usually do in qjackctl from the command line (list client ports, connect them to one another, disconnect them from one another).
dbus-send --system /org/rncbc/qjackctl org.rncbc.qjackctl.start
dbus-send --system /org/rncbc/qjackctl org.rncbc.qjackctl.stop
is equivalent to pressing qjackctl's start&stop buttons.
YMMV. robin
dbus-send --system /org/rncbc/qjackctl org.rncbc.qjackctl.start
dbus-send --system /org/rncbc/qjackctl org.rncbc.qjackctl.stop
is equivalent to pressing qjackctl's start&stop buttons.
hmm, this would be what I want, but it didn't work here (jaunty). any
permissions missing?
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
João Pais wrote:
dbus-send --system /org/rncbc/qjackctl org.rncbc.qjackctl.start
dbus-send --system /org/rncbc/qjackctl org.rncbc.qjackctl.stop
is equivalent to pressing qjackctl's start&stop buttons.
hmm, this would be what I want, but it didn't work here (jaunty). any permissions missing?
You'll need qjackctl >= 0.3.4.11 and "D-bus interface" must be enabled (it it on by default) in Setup->Misc.
No special permissions are required. FWIW, the actual use-case for this feature is to relaunch jack after a suspend/resume cycle.
HTH, robin
qjackctl uses jackd as a backend, so you can do what you want without
accessing qjackctl at all and just using jackd (whether jackd was
started by qjackctl or not).You can manually run jackd with the commands qjackctl would have used by
running "sh .jackdrc"If you start jackd in this way, then qjackctl should see that running
jackd instance instead of making a new one.
I just tried the sh, and there was no reaction from qjackctl. I didn't
test if jack was running, because it would be nice to have to gui working
(just dropped a line about it in another mail in this thread)
You can use the various jack tools like jack_lsp, jack_connect,
jack_disconnect, to do the things you would usually do in qjackctl from
the command line (list client ports, connect them to one another,
disconnect them from one another).
yes, that far I got. I've made a patch to control ardour transport, and
also create jack connections quite fast through Pd. I don't know if it's
not that appealing to anyone, or if no one noticed it, I thought there
would be more reactions to it -
http://lists.puredata.info/pipermail/pd-list/2010-02/075887.html
(some improvements will be made the next version, when there's time for it)
João
Hi João,
Qjackctl will also simply report if JACK has been started or not, and with which settings. I'm not sure why you would need to start and stop JACK many times during a session, but if you wanted to do all this from the command line then wouldn't it be easier to simply use the "jackd" command? JACK could be started with whatever startup flags you wanted that way, or you could use a .jackdrc file in your home directory to save settings.
HTH, D.
João Pais wrote:
Hi,
do you know if there's a way to turn qjackctl on through the console? That is, the program is already open, but instead of clicking start or stopp, I wanted to do it with bash commands.
Thanks (again),
João
Hi,
actually I don't want to start/stop many times. I just have a complex
setup now (jack+jackrack+pd+ardour), and wanted to start them all with one
bash command. the gui of qjackctl would be necessary, for when I have to
create/remove connections (although I can already make jack connections
faster with my pd patch)
João
Qjackctl will also simply report if JACK has been started or not, and
with which settings. I'm not sure why you would need to start and stop
JACK many times during a session, but if you wanted to do all this from
the command line then wouldn't it be easier to simply use the "jackd"
command? JACK could be started with whatever startup flags you wanted
that way, or you could use a .jackdrc file in your home directory to
save settings.HTH, D.
João Pais wrote:
Hi, do you know if there's a way to turn qjackctl on through the console?
That is, the program is already open, but instead of clicking start or
stopp, I wanted to do it with bash commands. Thanks (again), João
On 2010-02-21 00:10, João Pais wrote:
Hi,
actually I don't want to start/stop many times. I just have a complex setup now (jack+jackrack+pd+ardour), and wanted to start them all with one bash command. the gui of qjackctl would be necessary, for when I have to create/remove connections (although I can already make jack connections faster with my pd patch)
i think the problem with "no reaction" on qjackctl side is, that it just doedsn't poll the jack server often enough.
a pretty safe way should be to start jackd before and then start qjackctl (and whatever apps): qjackctl will then be aware of an already running jack process and hook to that.
fgmadsr IOhannes
Hey again,
at the bottom of this page:
http://en.flossmanuals.net/PureData/StartingPD
under "Advanced scripting for starting Pd" is a sample script I wrote to start Jack, start Pd, start SooperLooper and then use aconnect to hook them all together. Would something like this help you?
D.
João Pais wrote:
Hi,
actually I don't want to start/stop many times. I just have a complex setup now (jack+jackrack+pd+ardour), and wanted to start them all with one bash command. the gui of qjackctl would be necessary, for when I have to create/remove connections (although I can already make jack connections faster with my pd patch)
ah yes, thanks. this looks very useful.
pd floss manual? Uau, had never heard of it!
João
Hey again,
at the bottom of this page:
http://en.flossmanuals.net/PureData/StartingPD
under "Advanced scripting for starting Pd" is a sample script I wrote to
start Jack, start Pd, start SooperLooper and then use aconnect to hook
them all together. Would something like this help you?D.
João Pais wrote:
Hi, actually I don't want to start/stop many times. I just have a complex
setup now (jack+jackrack+pd+ardour), and wanted to start them all with
one bash command. the gui of qjackctl would be necessary, for when I
have to create/remove connections (although I can already make jack
connections faster with my pd patch)
-
Derek Holzer -
IOhannes m zmoelnig -
João Pais -
Justin Glenn Smith -
Robin Gareus