jack2 qjackctl and kxstudio cadence and midi

[blubee]

I am having some trouble with jack2 and my midi keyboard.

It would seem that qjackctl is a better than cadence in some respects but then cadence is a lot nicer in some effects.

When I start my jack session with qjackctl it doesn't do well with pulseaudio and as we know shuts off pulse audio but cadence allows the pulse audio pass through. If it wasn't for this issue I would stick with qjackctl because it's so much better, IMHO.

Why?

qjackctl allows me to run scripts at startup, which allows me to start midi by running this after startup scrip

Code: Select all

a2jmidid -e &

It's audio/midi/alsa tabs are also very useful allowing me to connect almost anything jack related.

For example I can launch zynaddsubfx connect it directly to my midi keyboard and start testing out some ideas.
connect any random pieces of software to others and do really cool stuff but ....

With cadence I much prefer catia view and how it allows me to connect more visually because everything is in one view and I can just drag and drop.

Does qjackctl have a better support like kxstudio catia or is there a better all around tool? I wouldn't even mind using qjackctl but I would really like a better manager to handle jack connections.

Please any assistance?

I might also be just using cadence wrong, I am new to linux music so I might just be dense right now.

[asbak]

When I start my jack session with qjackctl it doesn't do well with pulseaudio and as we know shuts off pulse audio but cadence allows the pulse audio pass through.

It's possible to route pulseaudio through jack while using qjackctl to manage jack. (In other words, both pulseaudio and jack are running, and pulseaudio is routed through jack).
Or you can disable pulseaudio, use qjackctl to manage jack.
Or you can run pulseaudio while jack is not running etc.

You could use jackdbus, or disable it. Cadence requires it so if you plan to use Cadence then it needs to remain enabled. Qjackctl doesn't need jackdbus. (It can use it, or not.)
As falkTX mentioned you can use Catia with qjackctl to manage midi and audio connections, or use the jack_connect command to do the same thing.
Patchage should also work I think. a2jmidid can be run from a terminal.

There are a lot of possibilities. Unfortunately it's not really well explained anywhere that I'm aware of. The individual pieces of information exist but the problem is that one needs to know what to look for and how it relates to other subsystems for things to start making sense, and that takes time to learn.

falkTX would know better but as far as I can tell the relevant configuration files which affect Cadence and jackdbus are here:

/etc/X11/Xsession.d/
/etc/xdg/autostart/
/usr/share/dbus-1/services/org.jackaudio.service

Read through all the scripts and understand what they do before modifying anything, just in case there's some kind of functionality you may require which could be impacted by changes.

Personally I disable cadence and jackdbus related items because it suits my purposes but this isn't for everybody.

[blubee]

Thank you

After reading this post and then spending a lot of time, working with linux audio is a bit different but I like the creativity and freedom.