Audio interfaces - JACK problems

[Dr.Boot]

Hi,
----- update:
I have now also bought a Behringer UMC22 and it behaves in the same way as ZOOM R8 described below:
It doesn't show up in qJackCtl on the "Audio"-tab! What is wrong ?
------
Original post:
As you may know, Zoom R8 is supposed to work as a USB Audio Interface (and Control Surface) and it has built-in stereo condenser microphones and High-Z jack allowing guitar input. I can plug it into Windows and get sound output (with horrible latency/delay) - and I can use it with ALSA directly in e.g. Audacity. It is detected by lsusb, aplay -l etc.

BUT: starting JACK it shows up in MIDI and ALSA tabs - but not in Audio tab. Audio tab shows no change, and only offers standard input/output (assumingly built-in Intel sound chip).

Has anybody got any tips? I have read many forums, and many claims it "works out of the box" ? I have tested with Ubuntu Studio 18.04 and 19.10 as well as regular Ubuntu 18 + 19 without realtime kernel - but same (or worse) behaviour...
Did it work for some of you with older versions of Linux / JACK ?

Thanks in advance!
Jan

[minty_melody]

Hi Jan,

I seem to have the same problem with my Presonus AudioBox iTwo on regular Ubuntu 18.04. Did you figure it out by now?

I recently posted on reddit linuxaudio here:
https://www.reddit.com/r/linuxaudio/com ... _as_audio/

[bluebell]

Hi,
----- update:
I have now also bought a Behringer UMC22 and it behaves in the same way as ZOOM R8 described below:
It doesn't show up in qJackCtl on the "Audio"-tab! What is wrong ?
------
Original post:
As you may know, Zoom R8 is supposed to work as a USB Audio Interface (and Control Surface) and it has built-in stereo condenser microphones and High-Z jack allowing guitar input. I can plug it into Windows and get sound output (with horrible latency/delay) - and I can use it with ALSA directly in e.g. Audacity. It is detected by lsusb, aplay -l etc.

BUT: starting JACK it shows up in MIDI and ALSA tabs - but not in Audio tab. Audio tab shows no change, and only offers standard input/output (assumingly built-in Intel sound chip).

Has anybody got any tips? I have read many forums, and many claims it "works out of the box" ? I have tested with Ubuntu Studio 18.04 and 19.10 as well as regular Ubuntu 18 + 19 without realtime kernel - but same (or worse) behaviour...
Did it work for some of you with older versions of Linux / JACK ?

Thanks in advance!
Jan

Code: Select all

aplay -l

shows if the kernel recognises it as an audio interface.

[minty_melody]

Thanks for your reply!

Yes,

Code: Select all

aplay -l 

list the audio interface as

Code: Select all

card 1: iTwo [PreSonus AudioBox iTwo], device 0: USB Audio [USB Audio]
  Subdevices: 1/1
  Subdevice #0: subdevice #0

If it didn't recognize it, other applications like audacity or alsamixer would not be able to receive its signal (if I understood correctly). And, as Jan described, it even shows up in JACK. However, unlike Jan's interface that appears in the MIDI and ALSA tab, mine only appears in ALSA.
I am also able to select the interface as output device in Settings->Advanced. This will connect the system captures in the Audio tab to my interface. In this way I can make audio connections with my interface, but I cannot connect my internal microphone at the same time.

I don't know if it helps but this is the output of

Code: Select all

pacmd list-cards

Code: Select all

index: 1
	name: <alsa_card.usb-PreSonus_PreSonus_AudioBox_iTwo_AB5C16050898-00>
	driver: <module-alsa-card.c>
	owner module: 29
	properties:
		alsa.card = "1"
		alsa.card_name = "PreSonus AudioBox iTwo"
		alsa.long_card_name = "PreSonus PreSonus AudioBox iTwo at usb-0000:00:1a.0-1.4, high speed"
		alsa.driver_name = "snd_usb_audio"
		device.bus_path = "pci-0000:00:1a.0-usb-0:1.4:1.0"
		sysfs.path = "/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.4/1-1.4:1.0/sound/card1"
		udev.id = "usb-PreSonus_PreSonus_AudioBox_iTwo_AB5C16050898-00"
		device.bus = "usb"
		device.vendor.id = "194f"
		device.vendor.name = "PreSonus Audio Electronics, Inc."
		device.product.id = "0403"
		device.product.name = "PreSonus AudioBox iTwo"
		device.serial = "PreSonus_PreSonus_AudioBox_iTwo_AB5C16050898"
		device.string = "1"
		device.description = "PreSonus AudioBox iTwo"
		module-udev-detect.discovered = "1"
		device.icon_name = "audio-card-usb"
	profiles:
		input:analog-stereo: Analog Stereo Input (priority 60, available: unknown)
		input:iec958-stereo: Digital Stereo (IEC958) Input (priority 55, available: unknown)
		output:analog-stereo: Analog Stereo Output (priority 6000, available: unknown)
		output:analog-stereo+input:analog-stereo: Analog Stereo Duplex (priority 6060, available: unknown)
		output:analog-stereo+input:iec958-stereo: Analog Stereo Output + Digital Stereo (IEC958) Input (priority 6055, available: unknown)
		output:iec958-stereo: Digital Stereo (IEC958) Output (priority 5500, available: unknown)
		output:iec958-stereo+input:analog-stereo: Digital Stereo (IEC958) Output + Analog Stereo Input (priority 5560, available: unknown)
		output:iec958-stereo+input:iec958-stereo: Digital Stereo Duplex (IEC958) (priority 5555, available: unknown)
		off: Off (priority 0, available: unknown)
	active profile: <output:analog-stereo+input:analog-stereo>
	sinks:
		alsa_output.usb-PreSonus_PreSonus_AudioBox_iTwo_AB5C16050898-00.analog-stereo/#1: PreSonus AudioBox iTwo Analog Stereo
	sources:
		alsa_output.usb-PreSonus_PreSonus_AudioBox_iTwo_AB5C16050898-00.analog-stereo.monitor/#2: Monitor of PreSonus AudioBox iTwo Analog Stereo
		alsa_input.usb-PreSonus_PreSonus_AudioBox_iTwo_AB5C16050898-00.analog-stereo/#3: PreSonus AudioBox iTwo Analog Stereo
	ports:
		analog-input: Analog Input (priority 10000, latency offset 0 usec, available: unknown)
			properties:
				
		iec958-stereo-input: Digital Input (S/PDIF) (priority 0, latency offset 0 usec, available: unknown)
			properties:
				
		analog-output: Analog Output (priority 9900, latency offset 0 usec, available: unknown)
			properties:
				
		iec958-stereo-output: Digital Output (S/PDIF) (priority 0, latency offset 0 usec, available: unknown)
			properties:

[bluebell]

Only ONE sound system can "own" the audio interface at a given time. Either you suspend or stop Pulseaudio while using jack or you configure Pulseaudio to output via jack, see for example http://marzen.de/Holger/pulseaudio_and_jack/

I recommend configuring Pulseaudio to output via jack. You have then all audio sources avaiable for jack clients, e.g. record Youtube's sound with Audacity, insert Plugin hosts, have a pitched voice when Using a telephony app and all other stuff.

[minty_melody]

Hi bluebell,

sorry to add complication with pulseaudio. I don't think it is the cause of the problem. I checked pulseaudio --check without any output.
To reduce sources of errors I just removed pulseaudio-module-jack and pulseaudio. After restarting my system, I still cannot see the audio interface in the Audio tab of qjackctl.

[bluebell]

Hi bluebell,

sorry to add complication with pulseaudio. I don't think it is the cause of the problem. I checked pulseaudio --check without any output.
To reduce sources of errors I just removed pulseaudio-module-jack and pulseaudio. After restarting my system, I still cannot see the audio interface in the Audio tab of qjackctl.

Can you select it in qjackctl -> Setup -> Settings -> Advanced as Input and Output?

You have to tell jackd which interface to use.

[minty_melody]

Yes, I am am able to select the interface as output and input device

[bluebell]

Yes, I am am able to select the interface as output and input device

Then start jack and look unter Qjackdtl -> Connect -> Audio if there's something under system.

[minty_melody]

Hi bluebell,
thanks for your reply! As I mentioned, I am able to select the interface as input/output and access its signal in Connect->Audio under system. But I thought it would be possible to have the internal microphone input at the same time to mix them.

I am also able to select the interface as output device in Settings->Advanced. This will connect the system captures in the Audio tab to my interface. In this way I can make audio connections with my interface, but I cannot connect my internal microphone at the same time.

So I was not aware that pulseaudio was relevant to the system and it is not a good idea to uninstall it altogether. So I reinstalled them and followed the steps in your link:

• apt-get install pulseaudio
  apt-get install pulseaudio-module-jack
• created /.asoundrc in my home directory with the given content
• modified /etc/pulse/default.pa so. I added/commented out the given lines. The rest of the file should remain as before, right?
• suppressed autostart of the PulseAudio daemon in /etc/pulse/client.conf
• Start and stop the PulseAudio in qjackctl options

Unfortunately, now I get errors when starting qjackctl. Did I miss anything?

Code: Select all

15:19:35.868 Statistics reset.
15:19:41.929 ALSA connection change.
15:19:41.936 D-BUS: Service is available (org.jackaudio.service aka jackdbus).
Cannot connect to server socket err = No such file or directory
Cannot connect to server request channel
jack server is not running or cannot be started
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock
15:19:41.963 ALSA connection graph change.
15:20:06.182 D-BUS: JACK server could not be started. Sorry
Sun May 10 15:20:05 2020: Starting jack server...
Sun May 10 15:20:05 2020: Jack: Server `default' registered
Sun May 10 15:20:05 2020: Jack: JackConnectionManager::InitConnections size = 6522944 
Sun May 10 15:20:05 2020: Jack: JackConnectionManager::InitClients
Sun May 10 15:20:05 2020: JACK server starting in realtime mode with priority 10
Sun May 10 15:20:05 2020: self-connect-mode is "Don't restrict self connect requests"
Sun May 10 15:20:05 2020: Jack: JackShmMem::new index = 4 attached = 7b3ca000 size = 82280346 
Sun May 10 15:20:05 2020: Jack: JackShmMem::new placement size = 13047706
Cannot connect to server socket err = No such file or directory
Cannot connect to server request channel
jack server is not running or cannot be started
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock
Sun May 10 15:20:05 2020: Jack: Succeeded in locking 82280346 byte memory area
Sun May 10 15:20:05 2020: Jack: JackConnectionManager::InitConnections size = 6522944 
Sun May 10 15:20:05 2020: Jack: JackConnectionManager::InitClients
Sun May 10 15:20:05 2020: Jack: JackConnectionManager::InitConnections size = 6522944 
Sun May 10 15:20:05 2020: Jack: JackConnectionManager::InitClients
Sun May 10 15:20:05 2020: Jack: JackShmMem::new index = 5 attached = 89eba000 size = 1187 
Sun May 10 15:20:05 2020: Jack: Succeeded in locking 1187 byte memory area
Sun May 10 15:20:05 2020: Jack: JackPosixThread::StartImp : create non RT thread
Sun May 10 15:20:05 2020: Jack: JackPosixThread::ThreadHandler : start
Sun May 10 15:20:06 2020: Jack: playback device hw:0
Sun May 10 15:20:06 2020: Jack: capture device hw:0
Sun May 10 15:20:06 2020: Jack: capture device hw:0
Sun May 10 15:20:06 2020: Jack: playback device hw:0
Sun May 10 15:20:06 2020: Jack: apparent rate = 48000
Sun May 10 15:20:06 2020: Jack: frames per period = 1024
Sun May 10 15:20:06 2020: Jack: JackDriver::Open capture_driver_name = hw:0
Sun May 10 15:20:06 2020: Jack: JackDriver::Open playback_driver_name = hw:0
Sun May 10 15:20:06 2020: Jack: Check protocol client = 8 server = 8
Sun May 10 15:20:06 2020: Jack: JackEngine::ClientInternalOpen: name = system
Sun May 10 15:20:06 2020: Jack: JackEngine::AllocateRefNum ref = 0
Sun May 10 15:20:06 2020: Jack: JackLinuxFutex::Allocate name = jack_sem.1000_default_system val = 0
Sun May 10 15:20:06 2020: Jack: JackEngine::NotifyAddClient: name = system
Sun May 10 15:20:06 2020: Jack: JackGraphManager::SetBufferSize size = 1024
Sun May 10 15:20:06 2020: Jack: JackConnectionManager::DirectConnect first: ref1 = 0 ref2 = 0
Sun May 10 15:20:06 2020: Jack: JackGraphManager::ConnectRefNum cur_index = 0 ref1 = 0 ref2 = 0
Sun May 10 15:20:06 2020: Jack: JackDriver::SetupDriverSync driver sem in flush mode
Sun May 10 15:20:06 2020: Acquired audio card Audio0
Sun May 10 15:20:06 2020: creating alsa driver ... hw:0|hw:0|1024|3|48000|0|0|nomon|swmeter|-|32bit
Sun May 10 15:20:06 2020: ERROR: 
ATTENTION: The playback device "hw:0" is already in use. Please stop the application using it and run JACK again
Sun May 10 15:20:06 2020: Jack: JackDriver::Close
Sun May 10 15:20:06 2020: Jack: JackConnectionManager::DirectDisconnect last: ref1 = 0 ref2 = 0
Sun May 10 15:20:06 2020: Jack: JackGraphManager::DisconnectRefNum cur_index = 0 ref1 = 0 ref2 = 0
Sun May 10 15:20:06 2020: Jack: JackEngine::ClientInternalClose ref = 0
Sun May 10 15:20:06 2020: Jack: JackEngine::ClientCloseAux ref = 0
Sun May 10 15:20:06 2020: Jack: JackGraphManager::RemoveAllPorts ref = 0
Sun May 10 15:20:06 2020: Released audio card Audio0
Sun May 10 15:20:06 2020: Jack: ~JackDriver
Sun May 10 15:20:06 2020: ERROR: Cannot initialize driver
Sun May 10 15:20:06 2020: Jack: no message buffer overruns
Sun May 10 15:20:06 2020: Jack: JackPosixThread::Stop
Sun May 10 15:20:06 2020: Jack: JackPosixThread::ThreadHandler : exit
Sun May 10 15:20:06 2020: ERROR: JackServer::Open failed with -1
Sun May 10 15:20:06 2020: Jack: Succeeded in unlocking 82280346 byte memory area
Sun May 10 15:20:06 2020: Jack: JackShmMem::delete size = 0 index = 4
Sun May 10 15:20:06 2020: Jack: ~JackDriver
Sun May 10 15:20:06 2020: Jack: Succeeded in unlocking 1187 byte memory area
Sun May 10 15:20:06 2020: Jack: JackShmMem::delete size = 0 index = 5
Sun May 10 15:20:06 2020: Jack: Cleaning up shared memory
Sun May 10 15:20:06 2020: Jack: Cleaning up files
Sun May 10 15:20:06 2020: Jack: Unregistering server `default'
Sun May 10 15:20:06 2020: ERROR: Failed to open server
Sun May 10 15:20:07 2020: Saving settings to "/home/~/.config/jack/conf.xml" ...
15:20:41.708 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 request channel
jack server is not running or cannot be started
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock

EDIT: Ah, I see, I still need to set input/output in Setup->Advanced to use the audio interface. When I do that, I get no errors. I connect system capture and playback and I am able to hear the interface. Still, how about the internal microphone? Is that possible?

EDIT: Do I need to change the files every time I want to use another playback device than the audio interface? I don't seem to be able to start a JACK session with an input/output device other than the interface. I mean, I only plug in my audio interface from time to time. I don't want it to be the default playback, or maybe only if it is plugged in.

[lilith]

Btw: the zoom r8 should work fine.