Behringer UMC1820 suddenly stopped working with JACK2 (after re-install)

classic Classic list List threaded Threaded
9 messages Options
Reply | Threaded
Open this post in threaded view
|

Behringer UMC1820 suddenly stopped working with JACK2 (after re-install)

Niklas Reppel

Hi,

i recently re-installed Arch Linux on my laptop after a disk swap and suddenly JACK2 (non-dbus) doesn't run with my Behringer UMC1820
anymore. I kept the old system up-to-date and it was working perfectly well. Also, I don't remember making any special adjustments to
get it up and running.

My other cheapo Behringer (UCA202) still works fine, so i assume it's not a general USB audio problem ?

The device is still shown in alsamixer, levels can be set.

A friend tried it on her Mac and it worked there, so I assume the interface itself is still running.

uname -a says:

Linux atarashii 5.0.13-arch1-1-ARCH #1 SMP PREEMPT Sun May 5 18:05:41 UTC 2019 x86_64 GNU/Linux

I usually start jack2 like this (works with the other device):

jackd -P98 -dalsa -dhw:2 -p512 -n3 -o2 -r44100

The error message is:

ALSA: use 3 periods for capture
ALSA: final selected sample format for playback: 24bit little-endian in 3bytes format
ALSA: cannot set channel count to 2 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

Has anybody experiences something similar ? I don't have any idea right now ...

Best,
Niklas
_______________________________________________
Linux-audio-user mailing list
[hidden email]
https://lists.linuxaudio.org/listinfo/linux-audio-user
Reply | Threaded
Open this post in threaded view
|

Re: Behringer UMC1820 suddenly stopped working with JACK2 (after re-install)

Chris Caudle
On Mon, May 6, 2019 3:24 pm, [hidden email] wrote:
> i recently re-installed Arch Linux on my laptop after a disk swap and
> suddenly JACK2 (non-dbus) doesn't run with my Behringer UMC1820
> anymore.
...
> I usually start jack2 like this (works with the other device):
>
> jackd -P98 -dalsa -dhw:2 -p512 -n3 -o2 -r44100

Have you verified the device number?  The device number can change between
reboots even, so definitely could change when reinstalling your OS.
Easiest to check using aplay -l to list all ALSA devices, perhaps hw:2 is
no longer your UMC interface.

--
Chris Caudle
_______________________________________________
Linux-audio-user mailing list
[hidden email]
https://lists.linuxaudio.org/listinfo/linux-audio-user
Reply | Threaded
Open this post in threaded view
|

Re: Behringer UMC1820 suddenly stopped working with JACK2 (after re-install)

Niklas Reppel
Chris Caudle wrote on 06.05.2019 23:04:

> On Mon, May 6, 2019 3:24 pm, [hidden email] wrote:
> > i recently re-installed Arch Linux on my laptop after a disk swap and
> > suddenly JACK2 (non-dbus) doesn't run with my Behringer UMC1820
> > anymore.
> ...
> > I usually start jack2 like this (works with the other device):
> >
> > jackd -P98 -dalsa -dhw:2 -p512 -n3 -o2 -r44100
>
> Have you verified the device number? The device number can change between
> reboots even, so definitely could change when reinstalling your OS.
> Easiest to check using aplay -l to list all ALSA devices, perhaps hw:2 is
> no longer your UMC interface.
>

Thanks for the quick reply !

Yes, i checked that, so that problem can be ruled out.

Best,
Niklas
_______________________________________________
Linux-audio-user mailing list
[hidden email]
https://lists.linuxaudio.org/listinfo/linux-audio-user
Reply | Threaded
Open this post in threaded view
|

Re: Behringer UMC1820 suddenly stopped working with JACK2 (after re-install)

Will Godfrey
In reply to this post by Chris Caudle
On Mon, 6 May 2019 16:04:38 -0500
"Chris Caudle" <[hidden email]> wrote:

>On Mon, May 6, 2019 3:24 pm, [hidden email] wrote:
>> i recently re-installed Arch Linux on my laptop after a disk swap and
>> suddenly JACK2 (non-dbus) doesn't run with my Behringer UMC1820
>> anymore.  
>...
>> I usually start jack2 like this (works with the other device):
>>
>> jackd -P98 -dalsa -dhw:2 -p512 -n3 -o2 -r44100  
>
>Have you verified the device number?  The device number can change between
>reboots even, so definitely could change when reinstalling your OS.
>Easiest to check using aplay -l to list all ALSA devices, perhaps hw:2 is
>no longer your UMC interface.

I find it's safer to use device names rather than numbers (unless you have two
identical ones).

My MIDI keyboard identifies as 'Hua Xing'
and audio is 'HW:K6'


--
Will J Godfrey
http://www.musically.me.uk
Say you have a poem and I have a tune.
Exchange them and we can both have a poem, a tune, and a song.
_______________________________________________
Linux-audio-user mailing list
[hidden email]
https://lists.linuxaudio.org/listinfo/linux-audio-user
Reply | Threaded
Open this post in threaded view
|

Re: Behringer UMC1820 suddenly stopped working with JACK2 (after re-install)

David Runge
In reply to this post by Niklas Reppel
Hi Niklas,

On 2019-05-06 22:24:33 (+0200), [hidden email] wrote:
> jackd -P98 -dalsa -dhw:2 -p512 -n3 -o2 -r44100
Add some more verbosity with `-v`

> ALSA: use 3 periods for capture
> ALSA: final selected sample format for playback: 24bit little-endian in 3bytes format
> ALSA: cannot set channel count to 2 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
And you're sure it is not already running and/or being used by something
else (e.g. pulseaudio)?

Best,
David

--
https://sleepmap.de

_______________________________________________
Linux-audio-user mailing list
[hidden email]
https://lists.linuxaudio.org/listinfo/linux-audio-user

signature.asc (849 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: Behringer UMC1820 suddenly stopped working with JACK2 (after re-install)

Niklas Reppel
David Runge wrote on 06.05.2019 23:20:

> Hi Niklas,
>
> On 2019-05-06 22:24:33 (+0200), [hidden email] wrote:
> > jackd -P98 -dalsa -dhw:2 -p512 -n3 -o2 -r44100
> Add some more verbosity with `-v`
>
> > ALSA: use 3 periods for capture
> > ALSA: final selected sample format for playback: 24bit little-endian in
> 3bytes
> > format
> > ALSA: cannot set channel count to 2 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
> And you're sure it is not already running and/or being used by something
> else (e.g. pulseaudio)?

Hi David,

I don't have pulseaudio installed, so I'm pretty sure that can be ruled out.
There's no other program running that could block the device, as far as I can see.

The only two other things I notices are the strange sample format and the this two messages in dmesg that
appear when switching the device on after attaching (not when attaching the already switched-on device)

[   37.512914] usb 1-2: device descriptor read/64, error -71
[   37.742890] usb 1-2: device descriptor read/64, error -71


-v says:

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 98                                                                                                                      
self-connect-mode is "Don't restrict self connect requests"                                                                                                                
Jack: JackPosixThread::StartImp : create non RT thread                                                                                                                      
Jack: JackPosixThread::ThreadHandler : start                                                                                                                                
Jack: playback device hw:2                                                                                                                                                  
Jack: capture device hw:2                                                                                                                                                  
Jack: apparent rate = 44100                                                                                                                                                
Jack: frames per period = 512                                                                                                                                              
Jack: JackDriver::Open capture_driver_name = hw:2                                                                                                                          
Jack: JackDriver::Open playback_driver_name = hw:2
Jack: Check protocol client = 8 server = 8
Jack: JackEngine::ClientInternalOpen: name = system
Jack: JackEngine::AllocateRefNum ref = 0
Jack: JackLinuxFutex::Allocate name = jack_sem.1000_default_system val = 0
Jack: JackEngine::NotifyAddClient: name = system
Jack: JackGraphManager::SetBufferSize size = 512
Jack: JackConnectionManager::DirectConnect first: ref1 = 0 ref2 = 0
Jack: JackGraphManager::ConnectRefNum cur_index = 0 ref1 = 0 ref2 = 0
Jack: JackDriver::SetupDriverSync driver sem in flush mode
audio_reservation_init
Acquire audio card Audio2
creating alsa driver ... hw:2|hw:2|512|3|44100|0|2|nomon|swmeter|-|32bit
configuring for 44100Hz, period = 512 frames (11.6 ms), buffer = 3 periods
ALSA: final selected sample format for capture: 32bit integer little-endian
ALSA: use 3 periods for capture
ALSA: final selected sample format for playback: 24bit little-endian in 3bytes format
ALSA: cannot set channel count to 2 for playback
ALSA: cannot configure playback channel
Jack: JackDriver::Close
Jack: JackConnectionManager::DirectDisconnect last: ref1 = 0 ref2 = 0
Jack: JackGraphManager::DisconnectRefNum cur_index = 0 ref1 = 0 ref2 = 0
Jack: JackEngine::ClientInternalClose ref = 0
Jack: JackEngine::ClientCloseAux ref = 0
Jack: JackGraphManager::RemoveAllPorts ref = 0
Released audio card Audio2
audio_reservation_finish
Jack: ~JackDriver
Cannot initialize driver
Jack: no message buffer overruns
Jack: JackPosixThread::Stop
Jack: JackPosixThread::ThreadHandler : exit
JackServer::Open failed with -1
Jack: Succeeded in unlocking 82280346 byte memory area
Jack: JackShmMem::delete size = 0 index = 0
Jack: ~JackDriver
Jack: Succeeded in unlocking 1187 byte memory area
Jack: JackShmMem::delete size = 0 index = 1
Jack: Cleaning up shared memory
Jack: Cleaning up files
Jack: Unregistering server `default'
Failed to open server

Best,
Niklas
_______________________________________________
Linux-audio-user mailing list
[hidden email]
https://lists.linuxaudio.org/listinfo/linux-audio-user
Reply | Threaded
Open this post in threaded view
|

Re: Behringer UMC1820 suddenly stopped working with JACK2 (after re-install)

Chris Caudle
On Mon, May 6, 2019 5:02 pm, [hidden email] wrote:
> creating alsa driver ... hw:2|hw:2|512|3|44100|0|2|nomon|swmeter|-|32bit
> configuring for 44100Hz, period = 512 frames (11.6 ms), buffer = 3 periods
> ALSA: final selected sample format for capture: 32bit integer
> little-endian
> ALSA: use 3 periods for capture
> ALSA: final selected sample format for playback: 24bit little-endian in
> 3bytes format
> ALSA: cannot set channel count to 2 for playback
> ALSA: cannot configure playback channel

Maybe the first error text is the only critical error for some reason
(changed driver version?).

"ALSA: cannot set channel count to 2 for playback"

Have you tried not specifying the -o parameter as an experiment?  I admit
it is grasping, it seems that jackd should be able to use just a subset of
the channels if that is what you were using before.  Is this exactly the
same kernel version/ALSA version you were using successfully before?

--
Chris Caudle
_______________________________________________
Linux-audio-user mailing list
[hidden email]
https://lists.linuxaudio.org/listinfo/linux-audio-user
Reply | Threaded
Open this post in threaded view
|

Re: Behringer UMC1820 suddenly stopped working with JACK2 (after re-install)

David Runge
On 2019-05-06 17:23:14 (-0500), Chris Caudle wrote:
> On Mon, May 6, 2019 5:02 pm, [hidden email] wrote:
> > ALSA: cannot set channel count to 2 for playback
> > ALSA: cannot configure playback channel
I also think this is the problem (for whatever reason).

> Have you tried not specifying the -o parameter as an experiment?  I admit
> it is grasping, it seems that jackd should be able to use just a subset of
> the channels if that is what you were using before.  Is this exactly the
> same kernel version/ALSA version you were using successfully before?

Alternatively you can try to boot with the linux-lts kernel and see if
it is kernel related (that would suck).

Best,
David

--
https://sleepmap.de

_______________________________________________
Linux-audio-user mailing list
[hidden email]
https://lists.linuxaudio.org/listinfo/linux-audio-user

signature.asc (849 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: Behringer UMC1820 suddenly stopped working with JACK2 (after re-install)

Niklas Reppel

David Runge wrote on 07.05.2019 00:46:

> On 2019-05-06 17:23:14 (-0500), Chris Caudle wrote:
> > On Mon, May 6, 2019 5:02 pm, [hidden email] wrote:
> > > ALSA: cannot set channel count to 2 for playback
> > > ALSA: cannot configure playback channel
> I also think this is the problem (for whatever reason).
>
> > Have you tried not specifying the -o parameter as an experiment? I admit
> > it is grasping, it seems that jackd should be able to use just a subset
> of
> > the channels if that is what you were using before. Is this exactly the
> > same kernel version/ALSA version you were using successfully before?
>
> Alternatively you can try to boot with the linux-lts kernel and see if
> it is kernel related (that would suck).

Huh, that's a bit embarrassing, but, not using the output parameter actually did it ... maybe i just never used that on the old system ?
Weird, guess I became victim to habit ...

Well, at least it's not a kernel issue (phew)

This works (no -o):

jackd -P98 -dalsa -dhw:2 -p512 -n3 -r44100 &

Thanks for your help everybody !

Best,
Niklas
_______________________________________________
Linux-audio-user mailing list
[hidden email]
https://lists.linuxaudio.org/listinfo/linux-audio-user