Setting Audio Out to analogue jack interferes with mouse and webcam

[NicknDi]

I discovered this was a big part of the problem I was requesting help with in this thread: viewtopic.php?f=28&t=303998

My setup:
RPi4B Rev 1.4 8GB Raspbian 10 desktop 32 bit (11/01/21), updated. Kernel 5.10.11-v7l+
Powered USB2 hub to which keyboard and mouse connected. Webcam Logitech C270 (but same result with a Logitech C920) plugged into the powered USB2 hub on the RPi. Audio out jack on RPi connected with standard cable to an old pair of powered Labtech desktop speakers. Ethernet network connection (wi-fi not configured). Two NEC monitors connected with micro-HDMI to DVI-D cables; but for the test below one of them connected via an HDMI to VGA converter which splits the audio off to an analogue jack.

To reproduce the issue:
1. Device profiles:
AV Jack Off
HDMI-1 Off
HDMI-2 Digital Stereo Output
USB Device 0x46d:0x825 Analog Mono Input

2. Launch Chromium, go to meet.jit.si (or Google Hangouts/Meet, or any other web based video calling platform) and set up a meeting.
Camera and camera microphone detected and permissions granted.
Fluid video on screen

3. Change Device Profiles to :
AV Jack Analogue Stereo Output
HDMI-1 Off
HDMI-2 Off
USB Device 0x46d:0x825 Analog Mono Input
Immediately the mouse starts momentarily freezing to the point where it becomes near impossible to operate and the camera freezes or cuts out altogether. A warning message pops up in Jit.si/Chromium: Unable to access camera

4. Unplug the webcam (or, if the mouse allows, deactivate the AV Jack) and immediately fluid mouse response returns.

(If you start with the AV Jack active, you never get as far as having a working webcam.)

I've no idea how widespread this is. It may be that many (most?) users are unaware of it because they use HDMI out anyway. But it has been flagged up here: viewtopic.php?f=28&t=303998&start=25#p1823597 here: viewtopic.php?f=28&t=299929&p=1802779&h ... V#p1802779 and here: viewtopic.php?f=28&t=303998&start=25#p1825330

Any suggestions as to a fix would be very welcome as we really need to use the AV jack for audio out.

For those who understand it, here's the output from dmesg covering steps 3 & 4 above:

Code: Select all

pi@raspberrypi:~ $ sudo dmesg --follow
[  239.414245] restoring control 00000000-0000-0000-0000-000000000101/10/5
[  239.414261] restoring control 00000000-0000-0000-0000-000000000101/12/11
[  248.718419] restoring control 00000000-0000-0000-0000-000000000101/10/5
[  248.718435] restoring control 00000000-0000-0000-0000-000000000101/12/11
[  252.438489] usb 1-1.4.4.4: USB disconnect, device number 8
[  252.439038] usb 1-1.4.4.4: cannot submit urb (err = -19)
[  252.457235] usb 1-1.4.4.4: cannot submit urb 0, error -19: no device
[  252.837174] usb 1-1.4.4.4: new high-speed USB device number 9 using xhci_hcd
[  253.179273] usb 1-1.4.4.4: New USB device found, idVendor=046d, idProduct=0825, bcdDevice= 0.12
[  253.179286] usb 1-1.4.4.4: New USB device strings: Mfr=0, Product=0, SerialNumber=2
[  253.179295] usb 1-1.4.4.4: SerialNumber: 98259510
[  253.180925] uvcvideo: Found UVC 1.00 device <unnamed> (046d:0825)
[  253.180934] uvcvideo: Forcing device quirks to 0x480 by module parameter for testing purpose.
[  253.180940] uvcvideo: Please report required quirks to the linux-uvc-devel mailing list.
[  253.293013] input: UVC Camera (046d:0825) as /devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb1/1-1/1-1.4/1-1.4.4/1-1.4.4.4/1-1.4.4.4:1.0/input/input3
[  253.351540] v3d fec00000.v3d: MMU error from client L2T (0) at 0x2c41000, pte invalid
[  254.664525] usb 1-1.4.4.4: set resolution quirk: cval->res = 384
[  255.509966] restoring control 00000000-0000-0000-0000-000000000101/10/5
[  255.509977] restoring control 00000000-0000-0000-0000-000000000101/12/11
[  256.815117] restoring control 00000000-0000-0000-0000-000000000101/10/5
[  256.815127] restoring control 00000000-0000-0000-0000-000000000101/12/11
[  261.660315] restoring control 00000000-0000-0000-0000-000000000101/10/5
[  261.660332] restoring control 00000000-0000-0000-0000-000000000101/12/11
[  268.981239] restoring control 00000000-0000-0000-0000-000000000101/10/5
[  268.981255] restoring control 00000000-0000-0000-0000-000000000101/12/11
[  273.322306] restoring control 00000000-0000-0000-0000-000000000101/10/5
[  273.322322] restoring control 00000000-0000-0000-0000-000000000101/12/11
[  275.842701] restoring control 00000000-0000-0000-0000-000000000101/10/5
[  275.842719] restoring control 00000000-0000-0000-0000-000000000101/12/11
[  278.102836] restoring control 00000000-0000-0000-0000-000000000101/10/5
[  278.102846] restoring control 00000000-0000-0000-0000-000000000101/12/11
[  280.338164] restoring control 00000000-0000-0000-0000-000000000101/10/5
[  280.338184] restoring control 00000000-0000-0000-0000-000000000101/12/11
[  285.549963] restoring control 00000000-0000-0000-0000-000000000101/10/5
[  285.549978] restoring control 00000000-0000-0000-0000-000000000101/12/11
[  287.908871] restoring control 00000000-0000-0000-0000-000000000101/10/5
[  287.908888] restoring control 00000000-0000-0000-0000-000000000101/12/11
[  291.099899] usb 1-1.4.4.4: USB disconnect, device number 9
[  291.100213] uvcvideo: Failed to resubmit video URB (-19).
[  291.100679] usb 1-1.4.4.4: cannot submit urb (err = -19)
[  291.104241] uvcvideo: Failed to resubmit video URB (-19).
[  291.108251] uvcvideo: Failed to resubmit video URB (-19).
[  291.112366] uvcvideo: Failed to resubmit video URB (-19).
[  291.116360] uvcvideo: Failed to resubmit video URB (-19).
[  291.117428] usb 1-1.4.4.4: cannot submit urb 0, error -19: no device
[  291.221224] xhci_hcd 0000:01:00.0: ERROR Transfer event for disabled endpoint slot 8 ep 2
[  291.221236] xhci_hcd 0000:01:00.0: @000000041ed07340 00000000 00000000 0f000000 08038001

[jeffbl]

I am having the same issue on a Pi4 4GB running Google Meet inside Chromium. I'm running Raspbian, and tried a completely fresh install with the latest January image. I am using a Logitech c920 webcam. It is fluid and good when in the cheese app, or with HDMI audio selected. But when I go to Google Meet and turn on analog out, the entire system starts freezing and is unusable. So, just another data point indicating you are not alone!

I'd been using this system successfully for videoconferencing between kids and grandparents until earlier this year, and despite considerable time spent, have been unable to resolve this issue, so have stopped using the pi.

UPDATE: Confirmed that if I use a USB sound device, it works fine. It is only when using the internal sound output that it goes haywire.

[NicknDi]

I am having the same issue on a Pi4 4GB running Google Meet inside Chromium. I'm running Raspbian, and tried a completely fresh install with the latest January image. I am using a Logitech c920 webcam. It is fluid and good when in the cheese app, or with HDMI audio selected. But when I go to Google Meet and turn on analog out, the entire system starts freezing and is unusable. So, just another data point indicating you are not alone!

I'd been using this system successfully for videoconferencing between kids and grandparents until earlier this year, and despite considerable time spent, have been unable to resolve this issue, so have stopped using the pi.

UPDATE: Confirmed that if I use a USB sound device, it works fine. It is only when using the internal sound output that it goes haywire.

Thanks for this. My understanding is that Pi engineers will be investigating this issue in the coming days; Rich from the PiHut has been very helpful in this regard.

As a matter of interest, exactly what "USB sound device" are you using, that does work OK?

[valentim]

It's perhaps worth mentioning that, in my experience, the symptoms are the same when combining a usb webcam with outputting sound to bluetooth headphones (not just to analogue jack).

I am using Sony WH-CH510, but it probably is not model specific.

[fivenote]

This seems like what I'm experiencing when trying to run Zoom in Chromium. It started for me after the 2021-01-07 update.

I posted it here...

viewtopic.php?t=297921

After seeing this thread I switched from analogue audio jack to a USB sound device. Zoom in Chromium works without the mouse and webcam freezing.

I need to go back to the analogue audio jack eventually, so looking forward to a possible fix.

Thanks pi engineers!

[GradyCole]

Thank you guys!!!!

Yesterday I upgraded the Pi my son uses for his online school, and today he was complaining all the time about his Google Meet being jerky, the camera cutting out, and his cursor not moving (I confirmed it all). So I've spent the last few hours trying to reinstall a backup of his system, trying a different SD card, and just losing my mind.... until I found this thread.

I'm going HDMI out to a DVI monitor, but using analog out for the audio. Sure enough when I changed it to HDMI (which I can't use), all the problems stop. Now I use need to figure out a way to hook his speakers up to the Pi before Monday.

Thanks again for the troubleshooting.

[NicknDi]

Now I use need to figure out a way to hook his speakers up to the Pi before Monday.

Difficult to sort it by Monday unless you already have the kit. I've tested two methods, both of which work. Simplest is to use a USB sound card. I can confirm this (https://www.amazon.co.uk/gp/product/B01 ... =pd_gw_unk) works with my setup. The PiHut sell a cheaper one but it seems to be currently out of stock. Alternatively, I found a combination of this (https://www.amazon.co.uk/dp/B00B2HORKE/ ... asin_0_img ) and this (https://www.amazon.fr/gp/product/B00ZMV ... UTF8&psc=1) worked. But my monitors have vga as well as dvi-d inputs (most do?) and I already had several vga cables.

Best of luck!

I'm disappointed to have seen nothing yet from the Pi engineers. It's nearly a fortnight now since I started this thread and there's clearly an issue here that needs fixing.

[jdb]

I'm disappointed to have seen nothing yet from the Pi engineers. It's nearly a fortnight now since I started this thread and there's clearly an issue here that needs fixing.

It's unreasonable to expect "the engineers" to read every single thread in the troubleshooting forum.

This bug is already being tracked on Github: https://github.com/raspberrypi/firmware/issues/1546

For now, the fix is to revert to firmware shipped with the last release of Raspberry Pi OS, or use a USB audio device.

[NicknDi]

It's unreasonable to expect "the engineers" to read every single thread in the troubleshooting forum.

Sorry! Last thing I want to do is cause offence - I need your help, not your irritation! Though to put it in context, I had been hoping to get a fairly quick response having been asked by Rich at the PiHut to start a thread on this to which he would draw you folks' attention. But I full understand you have a lot of stuff to look at and must prioritise.

This bug is already being tracked on Github: https://github.com/raspberrypi/firmware/issues/1546

For now, the fix is to revert to firmware shipped with the last release of Raspberry Pi OS, or use a USB audio device.

Are you sure this is the same issue? I see no mention of the audio out configuration in that Github thread, and for those of us experiencing the problem on this thread, the firmware isn't a problem; the problem arises on earlier and current firmwares, and the only fix is either hardware to split off / convert the HDMI audio to analogue or, as you suggest, use a USB card.

[jdb]

Does the symptom change with the version of the installed firmware? Follow the steps in the github issue to swap between a version I suspect to be causing the issue and the one prior.

[NicknDi]

Does the symptom change with the version of the installed firmware? Follow the steps in the github issue to swap between a version I suspect to be causing the issue and the one prior.

Both those versions have the same effect: camera doesn't come on, Jit.si gives "Unable to access camera" message. But the mouse doesn't become jerky. This is different behaviour to that described in my OP, which was using the current firmware.

[GradyCole]

Now I use need to figure out a way to hook his speakers up to the Pi before Monday.

I can confirm this (https://www.amazon.co.uk/gp/product/B01 ... =pd_gw_unk) works with my setup.

Thanks, Nick, that's pretty much what I ordered (same company, slightly different model). I ordered it on Friday and it was here on Sat. Gotta love Prime delivery when you're in a pinch. I can confirm that works on my end as well, and the kid was able to do his Google Meet chat today without issues.

[jdb]

Does the symptom change with the version of the installed firmware? Follow the steps in the github issue to swap between a version I suspect to be causing the issue and the one prior.

Both those versions have the same effect: camera doesn't come on, Jit.si gives "Unable to access camera" message. But the mouse doesn't become jerky. This is different behaviour to that described in my OP, which was using the current firmware.

You are experiencing the same symptoms as the poster on github, but in addition have some other issue where the browser can't start the video stream. The thing causing the mouse lag can actually cause the USB controller to crash, and is an identifiable regression, so needs fixing.

[jdb]

Latest rpi-update firmware should contain a fix for the USB controller lockup issue. This should prevent the mouse from becoming unresponsive and in our testing Google Meet functions normally.

Please test and report back. If you still have non-functional video then please report which version of Chromium you're using.

[valentim]

Eureka! Things are finally working as they should (both audio to analogue jack and bluetooth headphones here)!

[NicknDi]

Sad to report there's little change for us. On Jit.si the mouse keeps going now, just freezing momentarily as the camera tries to work, and operating smoothly again once the camera cuts out. Jit.si gives an error message "unable to access camera".

On Google Meet it's just the same as before: with audio out set to the jack mouse and camera both fail.

Using Chromium v. 88.0.4324.187

I've done a full upgrade and rebooted, so presumably this is the latest firmware:

pi@raspberrypi:~ $ sudo /opt/vc/bin/vcgencmd version
Feb 25 2021 12:10:40
Copyright (c) 2012 Broadcom
version 564e5f9b852b23a330b1764bcf0b2d022a20afd0 (clean) (release) (start)

I'm perplexed!

[jdb]

That's not the latest firmware. It's in rpi-update, not apt. Eventually the apt package will be updated to bump the firmware revision.

[NicknDi]

That's not the latest firmware. It's in rpi-update, not apt. Eventually the apt package will be updated to bump the firmware revision.

Ah! Thanks for pointing that out. I've now run rpi-update and it certainly helps, but I think to the extent that it reveals I've probably had another issue all along. Everything works smoothly now on Jitsi and Meet .... for up to a minute or so, then the camera cuts out. This even happens with the audio jack off and using a usb card for the audio out. I'm wondering if it's to do with bcm2835-isp, which would seem to be an inbuilt camera module (???) and which always pops up and seems to take over from the actual connected webcam when I look at video settings in Jitsi and Meet. But I guess I need to join or start another thread to find help with that. Thanks again for your help with the AV jack issue.

[6by9]

New thread on bcm2835-isp at viewtopic.php?f=28&t=310921

I very much doubt it has any real involvement in your issue, but there you go.

[Fidelius]

I experience the exact same problem like the original poster and others do.

My two Pi4 devices run with up-to-date Raspbian (just the normal way via "apt update" and "apt full-upgrade"). One Pi4 is a rev 1.1 with 4 GB, and the other one is a rev 1.4 with 8 GB.

Both Pis use the analogue audio output (jack).

My Webcam is a "Logitech C270".

When the Webcam is connected to a Pi and I start the "cheese" application or the browser for meet.jit.si , the Pi (or its mouse) freezes for several seconds, then works for a short second, then again freezes for various seconds, etc.

However, when in the tool "pavucontrol" (or how it is called) I disable analogue audio, the Webcam video is shown nicley in the same applications.
So by disabling the analogue audio, everything works fine – except no sound.

Are there some simple steps we could do in order to solve this problem? Thanks!