Ubuntu studio and Behringer UMC404, Jack is not my friend

Talk about your MIDI interfaces, microphones, keyboards...

Moderators: khz, MattKingUSA

Post Reply
Jonniejlo
Established Member
Posts: 3
Joined: Sat Jul 11, 2020 2:51 pm

Ubuntu studio and Behringer UMC404, Jack is not my friend

Post by Jonniejlo »

Hello fellow linux crew and musicians!
Loved finding this forum.

I've bought a Behringer UMC404 and a Thomann T.Bone "rip-off shure" mic and connecting it up with Jack has been damn frustrating.
After 6 hours of forums/youtube & endless tinkering I've found that the solutions are quite customised to each system and I haven't found anything that works for mine yet.
I really liked the solution of forcing the alsa input into the jack connection list with;

Code: Select all

alsa_(in/out) -d hw:1
But it did not work for me.

So Now is the time to ask for help.

Behringer UMC404 (not the HD)
T.Bone cc75
Ubuntu Studio 16.04 LTS
Jack 0.4.2 (Qtjackcl)

My process
- doing a cat /proc/asound/cards shows me that the AI is seen. WIN.
- The only way that Jack will start is with "default" chosen as the input.
- The AI shows up in Jack-->setup-->paramters--> interface. And in setup-->advanced-->input device. But selecting anything other than default for these throws Dbus errors and jack does not start.

- I've explored the pulseaudio-Jack sink and this seems to be active. <--- I really liked this solution.. Harmony between two monsters, if only it worked.
- Killing pulseaudio and starting Jack with "default", the Pulse-Jack sink then shows up in the Jack connections.
- The AI shows up in the ALSA tab of the Jack connections, however only with MIDI inputs (for some reason).
- Using Ardour I can connect the onboard laptop mic with JAck running to the Ardour track.

So Jack to Ardour seems to work. Ai to Jack input-capture seems to be where the problem lies.


Please advise some diagnostic commands so I can give you some hard data to work with.


Thank you!!
User avatar
bluebell
Established Member
Posts: 1509
Joined: Sat Sep 15, 2012 11:44 am
Location: Saarland & Frankfurt, Germany
Has thanked: 2 times
Been thanked: 3 times

Re: Ubuntu studio and Behringer UMC404, Jack is not my friend

Post by bluebell »

Code: Select all

aplay -l

arecord -l
Linux – MOTU UltraLite AVB – Qtractor – https://soundcloud.com/suedwestlicht
Jonniejlo
Established Member
Posts: 3
Joined: Sat Jul 11, 2020 2:51 pm

Re: Ubuntu studio and Behringer UMC404, Jack is not my friend

Post by Jonniejlo »

Thanks Bluebell.

Playback

Code: Select all

**** List of PLAYBACK Hardware Devices ****
card 0: PCH [HDA Intel PCH], device 0: ALC3227 Analog [ALC3227 Analog]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: PCH [HDA Intel PCH], device 7: HDMI 1 [HDMI 1]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: PCH [HDA Intel PCH], device 8: HDMI 2 [HDMI 2]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 1: UMC404 [BEHRINGER UMC404], device 0: USB Audio [USB Audio]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
Capture

Code: Select all

**** List of CAPTURE Hardware Devices ****
card 0: PCH [HDA Intel PCH], device 0: ALC3227 Analog [ALC3227 Analog]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 1: UMC404 [BEHRINGER UMC404], device 0: USB Audio [USB Audio]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
Jonniejlo
Established Member
Posts: 3
Joined: Sat Jul 11, 2020 2:51 pm

Re: Ubuntu studio and Behringer UMC404, Jack is not my friend

Post by Jonniejlo »

It can see it. Just the link between capture device in Alsa to Jack is the missing link.

Interestingly.... In my research I found that Jack was made as an "in between" to make Alsa access easier for programs/developers.

It feels like if Alsa can "see" my mic.... then I shouldn't need Jack at all. hmm.
Plug&Play
Established Member
Posts: 46
Joined: Sat Jan 14, 2017 2:09 am

Re: Ubuntu studio and Behringer UMC404, Jack is not my friend

Post by Plug&Play »

Jonniejlo -

Don't give up, and don't expect Jack to be your friend. Jack is a daemon, and we don't "use" Jack, we make a pact with it through its minion QjackCTL :lol:

I am having similar problems, which, as I work through this I find they are most often self inflicted. I am following this thread to see how it shakes out.

I hope this is not a distration, but I ws looking at this page
https://jackaudio.org/faq/multiple_devices.html
at the bottom is a warning:

"When using -P or -C to specify different devices, do not use the -d argument (which specifies a single device) and do not use the -D argument (which tells JACK to configure a device for playback & capture)."
I think your setup qualifies as "multiple devicces" : System and UMC404.

My other comments are
  1. in qjackctl/settings there is an "interface" selection with a pull down. Do you see your USB device there?
  2. when I use a microphone on my USB interface, all I seen in QjackCTL is the name of the interface, nothing about "microphone".

Rob

Music Music Music !
Post Reply