That Jack does not want to start w/ this device is worrisome.vladanl wrote:Just to repeat, that means a device can work properly in Jack even if it doesn't in Alsa / PulseAudio. This is an important info for me, thanks.Linuxmusician01 wrote:Another tip. My 4 IN and 4 OUT usb audio device (Behringer 404HD) won't work properly in Alsa/PulseAudio. Will only work good w/ Jack.
Also, thanks for another info, if I don't manage to solve this problem, Behringer 404HD might be a good alternative.
I tried the command you specified and variations: 2,0, S1810c, S1810c,0, -P instead of --device, specified the number of out channels with -o, in all these cases jack fails. For example:Linuxmusician01 wrote: So you might have luck w/ Jack. Start Jack for audio device number 2 like so:Then start QJackctl and look for IN and OUT-puts of your card.
Code: Select all
jackd -d alsa --device hw:2
Increasing verbocity didn't provide more info, ALSA lines were the same.
Code: Select all
jackd -d alsa --device hw:2 jackdmp 1.9.12 Copyright 2001-2005 Paul Davis and others. Copyright 2004-2016 Grame. Copyright 2016-2017 Filipe Coelho. jackdmp comes with ABSOLUTELY NO WARRANTY This is free software, and you are welcome to redistribute it under certain conditions; see the file COPYING for details no message buffer overruns no message buffer overruns no message buffer overruns JACK server starting in realtime mode with priority 10 self-connect-mode is "Don't restrict self connect requests" audio_reservation_init Acquire audio card Audio2 creating alsa driver ... hw:2|hw:2|1024|2|48000|0|0|nomon|swmeter|-|32bit configuring for 48000Hz, period = 1024 frames (21.3 ms), buffer = 2 periods ALSA: final selected sample format for capture: 32bit integer little-endian ALSA: use 2 periods for capture ALSA: final selected sample format for playback: 32bit integer little-endian ALSA: use 2 periods for playback ALSA: cannot set hardware parameters for playback ALSA: cannot configure playback channel Released audio card Audio2 audio_reservation_finish Cannot initialize driver JackServer::Open failed with -1 Failed to open server
From some other command line output that you posted it seemed to me that the (standard?) USB audio device driver from Alsa was loaded. It almost looks like the Presonos Studio 1810 is not supported by this driver. Almost every cheap USB sound "stick" up to my Behringer 404HD works with the driver called snd_usb_audio.
Check if the kernel module (read: driver) named snd_usb_audio is loaded:
Code: Select all
$ lsmod | grep usb snd_usb_audio 155107 0 snd_usbmidi_lib 29282 1 snd_usb_audio usb_storage 62209 0 usblp 22891 0 snd_hwdep 13602 3 snd_usb_audio,snd_hda_codec,snd_opl3_lib snd_pcm 102099 7 snd_usb_audio,snd_hda_codec_hdmi,snd_hda_codec,snd_hda_intel,snd_cmipci snd_rawmidi 30731 3 snd_usbmidi_lib,snd_mpu401_uart,snd_seq_midi snd 69416 32 snd_hda_codec_realtek,snd_hrtimer,snd_usb_audio,snd_hwdep,snd_timer,snd_hda_codec_hdmi,snd_pcm,snd_seq,snd_rawmidi,snd_usbmidi_lib,snd_hda_codec,snd_hda_intel,snd_mpu401_uart,snd_seq_device,snd_seq_dummy,snd_cmipci,snd_seq_midi_emul,snd_opl3_lib,snd_seq_midi usbhid 52659 0 hid 106148 2 hid_generic,usbhid
Wat seems very strange to me is that they say that the device works in MacOS because it's class compliant. The Presonus Studio1810c looks like a very nice audio card to me. Pity that it doesn't seem to work in Linux. I couldn't find anything on the internet about this device and Linux, other than that Linuxers ask for a port to Linux of Presonos' software. Is it a very new device?
If it is really class compliant then the developers at Alsa might pick up on it and find a way to support it. The tip you got from somebody to contact ALsa might be your best option at the moment...