Page 2 of 3

Re: Question regarding new_song template

Posted: 07 May 2020 09:55
by kjetil
And if you see "capture_2" in the Connections window, are you also able to connect to it?

Re: Question regarding new_song template

Posted: 07 May 2020 10:05
by TheYke
Sure, sorry for not being clear ..:
qjackCtl_Connection.png
qjackCtl_Connection.png (113.51 KiB) Viewed 11039 times
.

No actually inside the "connection"-dialog it's just "capture_1".

EDIT: typos

EDIT2: What I meant earlier: in the permanent patchbay (accessible through the button "Steckfeld", I guess "patchbay" in english), "capture_2" is persistent, and there I configured my basic setup for all patchbay-connections regardless of the qjackctl-profile (internal with stereo-input or external with mono input).
qjackctlGUI.png
qjackctlGUI.png (14.6 KiB) Viewed 11037 times

Re: Question regarding new_song template

Posted: 07 May 2020 10:22
by kjetil
Thank you. It helps tracking it down. Qjackctl checks if the returned port name is valid, so I'll do that in Radium as well. It might not be the solution, and if it is, it is a bug in Jack, but we'll see.

Re: Question regarding new_song template

Posted: 07 May 2020 10:36
by TheYke
No problem, thanks a lot for your will to shed light on this, and for all the hard work that goes into such amazing software :)

Re: Question regarding new_song template

Posted: 08 May 2020 08:47
by kjetil
A person on the jack mailing list suggested that you should post the output of running the command "jack_lsp". This would help to determine more what jack system ports you actually have.

Another idea was that the behavior you see could be caused by a bad interaction between radium and the qjackctl patchbay. Can you try to run jackd from the command line without running qjackctl?

Re: Question regarding new_song template

Posted: 08 May 2020 10:03
by TheYke
Hi there again, as for

Code: Select all

jack_lsp

Code: Select all

[fex@manjarome ~]$ jack_lsp
system:capture_1
system:playback_1
system:playback_2
PulseAudio JACK Sink:front-left
PulseAudio JACK Sink:front-right
PulseAudio JACK Source:front-left
PulseAudio JACK Source:front-right
Non-Mixer/Input:in-1
Non-Mixer/Input:in-2
Non-Mixer/Input:out-1
Non-Mixer/Input:out-2
Non-Mixer/Input-Monitor:in-1
Non-Mixer/Input-Monitor:out-1
Non-Mixer/Jack-Apps-Out:in-1
Non-Mixer/Jack-Apps-Out:in-2
Non-Mixer/Jack-Apps-Out:out-1
Non-Mixer/Jack-Apps-Out:out-2
Non-Mixer/PulseAudio-Out:in-1
Non-Mixer/PulseAudio-Out:in-2
Non-Mixer/PulseAudio-Out:out-1
Non-Mixer/PulseAudio-Out:out-2
a2j:Midi Through (capture): Midi Through Port-0
a2j:Midi Through (playback): Midi Through Port-0
a2j:iRig PRO I/O (capture): iRig PRO I/O MIDI 1
a2j:iRig PRO I/O (playback): iRig PRO I/O MIDI 1
I'm quite a Linux newb, so for starting jackd manually correctly I got to check out the syntax and stuff. :oops: Will follow, though.

Re: Question regarding new_song template

Posted: 08 May 2020 10:31
by kjetil
Thank you. I don't think you need to test jackd manually, at least not yet.
But can you post the output of this too?

Code: Select all

jack_lsp -p -t

Re: Question regarding new_song template

Posted: 08 May 2020 10:52
by TheYke
sure:

Code: Select all

system:capture_1
        properties: output,physical,terminal,
        32 bit float mono audio
system:playback_1
        properties: input,physical,terminal,
        32 bit float mono audio
system:playback_2
        properties: input,physical,terminal,
        32 bit float mono audio
PulseAudio JACK Sink:front-left
        properties: output,terminal,
        32 bit float mono audio
PulseAudio JACK Sink:front-right
        properties: output,terminal,
        32 bit float mono audio
PulseAudio JACK Source:front-left
        properties: input,terminal,
        32 bit float mono audio
PulseAudio JACK Source:front-right
        properties: input,terminal,
        32 bit float mono audio
Non-Mixer/Input:in-1
        properties: input,
        32 bit float mono audio
Non-Mixer/Input:in-2
        properties: input,
        32 bit float mono audio
Non-Mixer/Input:out-1
        properties: output,
        32 bit float mono audio
Non-Mixer/Input:out-2
        properties: output,
        32 bit float mono audio
Non-Mixer/Input-Monitor:in-1
        properties: input,
        32 bit float mono audio
Non-Mixer/Input-Monitor:out-1
        properties: output,
        32 bit float mono audio
Non-Mixer/Jack-Apps-Out:in-1
        properties: input,
        32 bit float mono audio
Non-Mixer/Jack-Apps-Out:in-2
        properties: input,
        32 bit float mono audio
Non-Mixer/Jack-Apps-Out:out-1
        properties: output,
        32 bit float mono audio
Non-Mixer/Jack-Apps-Out:out-2
        properties: output,
        32 bit float mono audio
Non-Mixer/PulseAudio-Out:in-1
        properties: input,
        32 bit float mono audio
Non-Mixer/PulseAudio-Out:in-2
        properties: input,
        32 bit float mono audio
Non-Mixer/PulseAudio-Out:out-1
        properties: output,
        32 bit float mono audio
Non-Mixer/PulseAudio-Out:out-2
        properties: output,
        32 bit float mono audio
a2j:Midi Through (capture): Midi Through Port-0
        properties: output,physical,terminal,
        8 bit raw midi
a2j:Midi Through (playback): Midi Through Port-0
        properties: input,physical,terminal,
        8 bit raw midi
a2j:iRig PRO I/O (capture): iRig PRO I/O MIDI 1
        properties: output,physical,terminal,
        8 bit raw midi
a2j:iRig PRO I/O (playback): iRig PRO I/O MIDI 1
        properties: input,physical,terminal,
        8 bit raw midi


Re: Question regarding new_song template

Posted: 08 May 2020 10:56
by kjetil
Thanks! The error is that radium tries to connect an audio port to a midi port. Will be fixed in next release. Until then, just ignore the error.

Re: Question regarding new_song template

Posted: 08 May 2020 11:31
by TheYke
Brilliant news! Thanks a lot for your efforts ... really amazing. I'm afraid I got another issue i stumbled upon today, should I open a new topic or can I put it directly here (very likely it's a user error this time)? :lol: