falkTX wrote:alexoest wrote:FalkTX, Grep
I read the release notes and tried to follow them in their description of how to start Jack1. I could start Jack1 from the terminal, but I don't know what the piece "set the jackd binary to "/opt/jack1/bin/jackd"" implies. Where and how do you set that? Is it the text that should be in the server path field?
You can set the jackd binary in QJackCtl settings, at the top, the "Server Path" option.
Set it to "/opt/jack1/bin/jackd" (only works with "jack1 qjackctl").
Then all the other apps must be started using "jack1 <app>" as well.
That way you get Jack1 in KXStudio.
Unfortunately, it doesn't work. When typng "jack1 qjackctl" in the terminal, I get:
Bus::open: Can not get ibus-daemon's address.
IBusInputContext::createInputContext: no connection to ibus-daemon
And then Jack won't start with "/opt/jack1/bin/jackd" in the "server" field. I get this message:
20:36:04.814 Could not connect to JACK server as client. - Overall operation failed. - Unable to connect to server. Please check the messages window for more info.
Cannot connect to server socket err = No such file or directory
Cannot connect to server socket
jack server is not running or cannot be started
When typing jack1 rakarrack in the terminal, rakarrack tries to start, but abandons due to jack not being started.