Page 2 of 2

Re: Virtual Midi Port/Cable

Posted: Thu Dec 26, 2019 12:56 am
by Kott
d.healey wrote:
Kott wrote:This is very odd.

Should we cast Rui (rncbc) for help? :)
Yes, but how?
I've send him PM.

Re: Virtual Midi Port/Cable

Posted: Thu Dec 26, 2019 1:09 am
by d.healey
Kott wrote:
d.healey wrote:
Kott wrote:This is very odd.

Should we cast Rui (rncbc) for help? :)
Yes, but how?
I've send him PM.
Cool, thanks!

Re: Virtual Midi Port/Cable

Posted: Thu Dec 26, 2019 9:47 am
by rghvdberg
Which Linux are you running?

Re: Virtual Midi Port/Cable

Posted: Thu Dec 26, 2019 12:58 pm
by rncbc
care to show your QjackCtl Messages output right after you start the JACK server?

remember that the startup/shutdown scripts you set on QjackCtl > Setup > Options > Scripting are only meaningful iif you start the JACK server via QjackCtl on its own premises.

cheers

Re: Virtual Midi Port/Cable

Posted: Thu Dec 26, 2019 1:52 pm
by d.healey
rncbc wrote:care to show your QjackCtl only meaningful iif you start the JACK server via QjackCtl on its own premises.
Ooooh I bet that has something to do with the issue, it was years ago when I setup JACK but I'm pretty sure I have it auto-starting with the system, I'll see what's going on. Thanks for the tip!

Re: Virtual Midi Port/Cable

Posted: Fri Dec 27, 2019 1:54 pm
by d.healey
I can't find anything specific that's starting the JACK server, however I am using the pulse-audio sink which runs on start-up, does this automatically start the JACK server?

Re: Virtual Midi Port/Cable

Posted: Fri Dec 27, 2019 2:35 pm
by Loki Harfagr
d.healey wrote:I can't find anything specific that's starting the JACK server, however I am using the pulse-audio sink which runs on start-up, does this automatically start the JACK server?
You may check it any old time in a console:

Code: Select all

#>: ps -ef | grep -i jack

Re: Virtual Midi Port/Cable

Posted: Fri Dec 27, 2019 3:27 pm
by d.healey
Loki Harfagr wrote:
d.healey wrote:I can't find anything specific that's starting the JACK server, however I am using the pulse-audio sink which runs on start-up, does this automatically start the JACK server?
You may check it any old time in a console:

Code: Select all

#>: ps -ef | grep -i jack
I get this output, but I don't know what it means
dave 2176 1 0 13:45 ? 00:00:44 /usr/bin/jackd -T -ndefault -r -m -dalsa -dhw:MicroII -r48000 -p512 -n2 -Xseq -D -Phw:MicroII,0
dave 7518 7508 0 15:27 pts/0 00:00:00 grep --color=auto -i jack

Re: Virtual Midi Port/Cable

Posted: Fri Dec 27, 2019 4:45 pm
by rncbc
you seem to have some client that managed to auto(magically)started jackd ... and it also seems that it's still up and running... otherwise that "jackd -T .." would be long gone...

anyway...

try this:

1. killall -9 jackd
2. run qjackctl, go to Setup > Misc: turn off "Save JACK audio server configuration to:" if it's set; Quit!
3. on the command line or console:

Code: Select all

echo $(which qjackctl) --start > ~/.jackdrc
chmod a-w ~/.jackdrc
4. now run qjackctl again and setup it as you may like, including adding `a2jmidid -e &` as part of post-startup script;
5. hit Start...

hint: nowadays it is well worth a try to turn on qjackctl > Setup > Misc > JACK D-BUS interface, install pulseaudio-module-jack, then maybe run `pulseaudio -k`just once before hitting (qjackctl >)Start again, but i really don't care whether you want a full desktop audio experience or else ;)

cheers && happy NYE!

Re: Virtual Midi Port/Cable

Posted: Sat Dec 28, 2019 2:07 am
by d.healey
rncbc wrote:you seem to have some client that managed to auto(magically)started jackd ... and it also seems that it's still up and running... otherwise that "jackd -T .." would be long gone...

anyway...

try this:

1. killall -9 jackd
2. run qjackctl, go to Setup > Misc: turn off "Save JACK audio server configuration to:" if it's set; Quit!
3. on the command line or console:

Code: Select all

echo $(which qjackctl) --start > ~/.jackdrc
chmod a-w ~/.jackdrc
4. now run qjackctl again and setup it as you may like, including adding `a2jmidid -e &` as part of post-startup script;
5. hit Start...

hint: nowadays it is well worth a try to turn on qjackctl > Setup > Misc > JACK D-BUS interface, install pulseaudio-module-jack, then maybe run `pulseaudio -k`just once before hitting (qjackctl >)Start again, but i really don't care whether you want a full desktop audio experience or else ;)

cheers && happy NYE!
That didn't seem to help unfortunately - https://pasteboard.co/INh3Mh1.png

Re: Virtual Midi Port/Cable

Posted: Sat Dec 28, 2019 5:17 am
by Kott
That didn't seem to help unfortunately - https://pasteboard.co/INh3Mh1.png
looks like jackd is still running

Re: Virtual Midi Port/Cable

Posted: Sat Dec 28, 2019 8:17 am
by rghvdberg
d.healey wrote:
rncbc wrote:you seem to have some client that managed to auto(magically)started jackd ... and it also seems that it's still up and running... otherwise that "jackd -T .." would be long gone...

anyway...

try this:

1. killall -9 jackd
2. run qjackctl, go to Setup > Misc: turn off "Save JACK audio server configuration to:" if it's set; Quit!
3. on the command line or console:

Code: Select all

echo $(which qjackctl) --start > ~/.jackdrc
chmod a-w ~/.jackdrc
4. now run qjackctl again and setup it as you may like, including adding `a2jmidid -e &` as part of post-startup script;
5. hit Start...

hint: nowadays it is well worth a try to turn on qjackctl > Setup > Misc > JACK D-BUS interface, install pulseaudio-module-jack, then maybe run `pulseaudio -k`just once before hitting (qjackctl >)Start again, but i really don't care whether you want a full desktop audio experience or else ;)

cheers && happy NYE!
That didn't seem to help unfortunately - https://pasteboard.co/INh3Mh1.png
Have you by any chance installed cadence previously?
This could be starting in the background..

Re: Virtual Midi Port/Cable

Posted: Sat Dec 28, 2019 10:48 am
by Loki Harfagr
d.healey wrote:
Loki Harfagr wrote:
d.healey wrote:I can't find anything specific that's starting the JACK server, however I am using the pulse-audio sink which runs on start-up, does this automatically start the JACK server?
You may check it any old time in a console:

Code: Select all

#>: ps -ef | grep -i jack
I get this output, but I don't know what it means
dave 2176 1 0 13:45 ? 00:00:44 /usr/bin/jackd -T -ndefault -r -m -dalsa -dhw:MicroII -r48000 -p512 -n2 -Xseq -D -Phw:MicroII,0
dave 7518 7508 0 15:27 pts/0 00:00:00 grep --color=auto -i jack
This might give you the "faulty parent" name and address ;)

Code: Select all

#>: ps -ef | grep $( ps -C jackd --no-headers -o ppid )

Re: Virtual Midi Port/Cable

Posted: Sat Dec 28, 2019 2:06 pm
by d.healey
rghvdberg wrote: Have you by any chance installed cadence previously?
This could be starting in the background..
No I've never had cadence on this machine.
Loki Harfagr wrote: This might give you the "faulty parent" name and address ;)

Code: Select all

#>: ps -ef | grep $( ps -C jackd --no-headers -o ppid )
I don't know what to do with the output from that command, it just gave me pages of data.

Re: Virtual Midi Port/Cable

Posted: Sat Dec 28, 2019 3:19 pm
by Loki Harfagr
d.healey wrote:
rghvdberg wrote: Have you by any chance installed cadence previously?
This could be starting in the background..
No I've never had cadence on this machine.
Loki Harfagr wrote: This might give you the "faulty parent" name and address ;)

Code: Select all

#>: ps -ef | grep $( ps -C jackd --no-headers -o ppid )
I don't know what to do with the output from that command, it just gave me pages of data.
Ah, OK, then that's certainly the "parent" launched jackd as "detached spawn" thus it is now seen a having process "1" as sole parent and
my commond would actually list most every process having a charcater 1 in its ps output, quite ungraceful, sorry for the blund.

You'd have had a better (more restrained output) with:

Code: Select all

 #>: ps --ppid $( ps -C jackd --no-headers -o ppid )
but since it's a detached process it won't help!

A typical program I know as using jackd this way is Carla, but there might be others. (AFICT Cadence uses jackdbus and not jackd but I may be wrong since I never could understand how to use it/launch/stop/setitup [my bad, just like some folks can/could use an iphone or a Palm and I never ever could])
Anyway...

You may try to force kill the running jacke and immediatly launch the commands @rncbc gave you hoping the respawner hadn't had time to hassle in:

Code: Select all

 #>: killall -KILL jackd ; echo $(which qjackctl) --start > ~/.jackdrc ; chmod a-w ~/.jackdrc ; qjackctl -s