You are here

qjackctl -a option

Hi !

I am german. I am no musican. But i like to make noise and not really satisfied by "Magix musikmaker" under windows.

I work on a preconfigured ready to run startscript for Ubuntu Audio Studio. For beginners like me.

I dreamed about some arrangements that work when I start them and give sound, and i can change before i have to spend weeks of trying and investigations and looking for no documentation.

Maybe there will be some more for different example arrangements.

It is something really simple like

/usr/bin/qjackctl -s -p /home/gottfried/Desktop/xxx.xml &
sleep 5
jackeq &
/usr/bin/ams ams --jack --preset /usr/share/doc/ams/demos/example_ams_demo_scope_spectrum_mcpvcf.ams &
/usr/bin/zynaddsubfx &
/usr/bin/hydrogen &
/usr/bin/timemachine -f wav

But the script produces an error like "can not open /home/gottfried/Desktop/xxx.xml use preconfiguration instead" (-a option of qJackctl 0.3.5.1).

it works good - starts a working little soundstudio, if i load the patchfield xxx.xml from my desktop into qjackctl by hand when the script has finished.

This script makes nice backgroundmusic with ams and hydrogen with a little handisch accopany by zynaddsubfx and the possibility to mix all and record it to a wav.

I have to load the patchbay from the identical location then , that works.
But this is not so good for beginners.

did i missunderstand the -a option of qjackctl ? I also used "" and tried several other possibilities.

also jackeq or jackrack do not offer offer commandline parameters for a startscript. You always have to configure it manual from the beginning. Would be fine that would be possible. nothing is documented. impossible?

Forums: 
rncbc's picture

(what was really the question? :)

I guess you want to setup a patchbay definition in a way that all your pieces (client applications) come together when the so-called studio script is done.

Well, the patchbay profile only deals with restoring client/port connections and you have to get it assembled first, saved to a file (.xml) and then activated on qjackctl, that's right. In fact, that's what the qjackctl -a/--active-patchbay=/path/to/file.xml command line option does: it activates the given patchbay definition file, explicitly.

Side-note: the -a option is the command line way of doing this; you can, however, activate a patchbay profile using the GUI exclusively and that setting (as the command line one as well) will get remembered whenever you run qjackctl in the future. Relax.

The time for you to create and edit that particular patchbay definition file is up to you, just take note that it is all doable while in QjackCtl Patchbay window. There you set the connections rules you want to preserve at all times when the profile is active. It might not sound quite a beginner's thing to do, out of the box, because it hardly is :/ You'll have to setup it at least once, and eventually put it right there in the script as you asked (qjackctl -a option, that's right, remember?).

HTH

Hi !

Beg your pardon, Sir !
I did all like you described it before. I assembled and stored the xml in the patchbay window.

But my fault was i left a -q from trying, instead of changing it to an -a in my "studio script" and i did not realize that.

My eyes become old.

Now everything works fine. That's very good !

Thank you !

rncbc's picture

Ah, as a matter of fact, this Sir of yours have aging eyes as well (or should I say, as bad instead?:)

Seeya ;)

Add new comment