Meta - camera issues

[saghul]

If your camera is not working, please test it on https://test.webrtc.org and report your results here.

https://github.com/jitsi/jitsi-meet/issues/5236 https://github.com/jitsi/jitsi-meet/issues/5335 https://github.com/jitsi/jitsi-meet/issues/3532 https://github.com/jitsi/jitsi-meet/issues/5390 https://github.com/jitsi/jitsi-meet/issues/5195 https://github.com/jitsi/jitsi-meet/issues/5372 https://github.com/jitsi/jitsi-meet/issues/5186 https://github.com/jitsi/jitsi-meet/issues/1964 https://github.com/jitsi/jitsi-meet/issues/5358 https://github.com/jitsi/jitsi-meet/issues/5479 https://github.com/jitsi/jitsi-meet/issues/5466 https://github.com/jitsi/jitsi-meet/issues/5463 https://github.com/jitsi/jitsi-meet/issues/2495 https://github.com/jitsi/jitsi-meet/issues/5492 https://github.com/jitsi/jitsi-meet/issues/5155 https://github.com/jitsi/jitsi-meet/issues/5448 https://github.com/jitsi/jitsi-meet/issues/5430 https://github.com/jitsi/jitsi-meet/issues/5490 https://github.com/jitsi/jitsi-meet/issues/4163 https://github.com/jitsi/jitsi-meet/issues/5425

Update: macOS users, please try this:

• Open Activity Monitor
• Search for "VDCAssistant"
• Right click, force quit
• Does it work now?

Update 2:

We have deployed a new Jitsi Meet version (on meet.jit.si) which we think solves this problem. Please give it a try! In order to know you are running the new version note that new mute buttons have a new appearance:

Update 3:

I found an old webcam and could reproduce the problem! Any chance you can test the following? (SomeRandomRoomNameToTestTheCamera is a room name i just made up)

https://meet.jit.si/SomeRandomRoomNameToTestTheCamera#config.constraints.video.aspectRatio=1.33

Then try to select your camera.

Update 4:

The fix mentioned on update 3 is now deployed on meet.jit.si.

[keolan]

Hi. I also have the same problem. WebRTC Camera tests were all fine. but then problems with:

Network:
Ipv6 enabled [ WARN ] Failed to gather IPv6 candidates, it might not be setup/supported on the network.

Connectivity: Reflexive connectivity [ INFO ] Gathered candidate of Type: srflx Protocol: UDP Address: 178.83.110.77 [ WARN ] Could not connect using reflexive candidates, likely due to the network environment/configuration.

Throughput Video bandwidth [ FAILED ] Frame rate mean is 0, cannot test bandwidth without a working camera. [ INFO ] Send bitrate mean: NaN kbps [ INFO ] Send bitrate standard deviation: NaN kbps [ INFO ] RTT average: 0 ms [ INFO ] RTT max: 0 ms [ INFO ] Packets lost: -1

I work on Windows 10 Pro and use Antivirus.

Thanx!

[keolan]

my provider says the above mentioned errors network and connectivity are no real errors and the system should work anyway. nevertheless I cannot access the camera. Can you please help?

In my profile windows it says I have stopped the camera, which I did not, at least not in jitsi.

[boerup]

Did this and it's working again: OSX: In Terminal do this: sudo killall VDCAssistant From this page: https://setapp.com/how-to/fix-camera-on-mac-not-working

[keolan]

I forgot to mention I work on windows 10, so the above fix for OSX doesn't help me.

[alexanderadam]

Thank you for pinning :+1:

[mitchsIM]

Can confirm does not work either. My setting: Linux Mint 4.10.0-38-generic #42-16.04.1-Ubuntu SMP None of the browsers work (chrome 80, firefox 74.0, opera) Permissions are granted in each browser

Error Msg Java Console:

2020-04-02T11:38:32.944Z [features/base/tracks] Failed to create local tracks (2) ["audio", "video"] a {gum: {…}, name: "gum.general", message: "Could not start video source", stack:

[saghul]

@mitchsIM Please the "update 2" on the initial post: https://github.com/jitsi/jitsi-meet/issues/5425#issue-589235823

[mitchsIM]

i have a hint: it worked after a reboot i got the webcam running then i used "zoom" in the same desktop session. then even after i quit "zoom" it was not possible for jitsi to access the resource and i got the previous error messages.

[saghul]

Everyone, please see "update 3" on the original post. I managed to reproduce this.

[a3c]

@saghul I can reproduce the issue mentioned in update 3 on one of my customer's 5-year-old laptop. What information would you require to address the issue?

[saghul]

You mean it gets fixed with the URL parameter?

[rtwise]

I've been unable to get laptop webcam working with Jitsi. I get stuck at the Jitsi needs to access your microphone and camera screen after allowing permissions. I can only get into the call screen if i manually block the camera permission (mic works by itself)

Acer Aspire s7 392 Integrated HD camera Windows 8.1 Opera 67.0 Chrome 80.03

-Camera Passes first two resolution tests from link above but seems to hang on 1280 X 720. Report here https://test.webrtc.org/report/AMIfv95zmL7W4EOpD3bPc-7cYMskSLeN-HqkqFdWP7HvGp8F5Sm0i-fuAPYP8dJKoZVnrW-uoXTa5PkYcaX8PHvy4adoE6JtddKfj3wEuHgq3taxbP71EUotXc8TTap0d21GUesiuicM_lKCyhn1SFvNnTgeJ7vxPg

-I am running updated version of Jitsi meet identified by mute buttons -I am unable to enter somerandomroomnametotestcamera with my camera permission allowed, still get stuck at allow access screen. With mic permission only i can enter but am unable to turn on camera,

-I have tried updating camera drivers, updated windows, restarted PC, tried reducing in call video quality and then re allowing camera still no luck.

Thank you in advance. Ryan

[reyisw]

Hi, i'm having a problem using Jitsi in iOS Safari and iOS Chrome, it's not asking for camera or microphone permission, is there a special config for that case? i tested it in Windows and Android and it works perfectly.

thank you in advance for your help!

[saghul]

@reyisw That has nothing to do with this, and we don't yet support Jitsi on mobile or desktop Safari, please remain on topic.

[saghul]

@rtwise Can you pastte the output of your browser console?

[prismopensource]

testrtc-2020-04-07T07_58_32.833Z.log Still having problems, iMac and MacBook Pro with Mac OS 10.15.4 with Safari 13.1 microphone works, integrated camera doesn't even if given manual permission.

[dkanada]

I'm running the docker-jitsi-meetup containers and whatever you added to https://meet.jit.si is working for me, how can I get that running on my personal instance?

[alsobrsp]

Happy Tuesday. I have been having a fair amount of Camera issues with a self-hosted instance of Jitsi Meet. This manifested on one user, the primary of course. So far it seems that the issue was related to the "HP Sure Click Secure Browsing Extension".

His issues were:

• No permissions on Camera/Audio, intermittent
• Resume from sleep required a reboot

Removing that extension has resolved both issues.

I am running these versions

jitsi-meet-prosody/stable,now 1.0.3969-1 all [installed,automatic] jitsi-meet-turnserver/stable,now 1.0.3969-1 all [installed,automatic] jitsi-meet-web-config/stable,now 1.0.3969-1 all [installed,automatic] jitsi-meet-web/stable,now 1.0.3969-1 all [installed,automatic] jitsi-meet/stable,now 2.0.4384-1 all [installed] jitsi-videobridge2/stable,now 2.1-164-gfdce823f-1 all [installed,automatic]

Hope this helps

[a3c]

You mean it gets fixed with the URL parameter?

No, it didn't fix. We are still facing same issue.

[chupalo11]

this issue sucks, wtf

[chupalo11]

fix this please

[saghul]

@a3c Damn. Does your ccamera work in the device preview window?

[dkanada]

@saghul if you know what branch or tag is currently running on the test link you posted on the initial comment I would love to run that on my local instance. I can build it from source if there's no binaries at the moment.

For context, the error on my local instance was that navigator.mediaDevices is null, which was getting spammed in the browser logs repeatedly.

[GitMeTheHub]

When I append "#config.constraints.video.aspectRatio=1.33" to my meeting URL (as used in Update 3), I can now switch my cameras. How do I set up a meeting with that by default?

[hklaufus]

Ref #5952 Update 2 & Update 3 not working for me.

[ghost]

Try deleting the webcam off windows 10 in devices then unplug and replugging it should reinstall drivers. I used this method for zoom when my mic wasn’t working (when I used to use zoom now jitsi is my daily driver 👍)

[SolitaryShell]

I first used Jitsi in Firefox, where my camera worked perfectly fine. Unfortunately Jitsi does not work well in Firefox (it's true) and it advised me to switch to Chrome. Well, I did. Installed Chrome and everything and started it up. But there it's suddenly 'Unable to access my camera'. This happens after a few seconds where there's actually a connection and I'm visible.

Since there's apparently no problem with my camera as it worked fine in Firefox, the problem lies somewhere else.

Any suggestions?

[ghost]

@SolitaryShell yea same happened to me took like 10 seconds to connect to a meeting usually it’s instant my guess is their upgrading servers and some are down rn for upgrade as they said in their community stream yesterday.

[SolitaryShell]

@SolitaryShell yea same happened to me took like 10 seconds to connect to a meeting usually it’s instant my guess is their upgrading servers and some are down rn for upgrade as they said in their community stream yesterday.

That's not my problem. I'm connected fine. Then after up to 20 seconds the camera stops working and Jitsi says it's not accessable.

[luixxiul]

@saghul mind sharing which information you would need to troubleshoot? I'm happy to help.

[luixxiul]

The issue looks to be fixed on https://meet.jit.si.

[prismopensource]

Not for me, still says:

Your camera does not support required video resolution.

[luixxiul]

sry, I mean the issue related with mic and video @prismopensource

[ghost]

Not for me, still says:

Your camera does not support required video resolution.

seems to be working fine https://a.cockfile.com/sOTZG4_brave_2020-04-15_17-20-44.png

[Yetangitu]

@saghul I notice config.js at https://meet.jit.si/ contains a resolutionand constraints section:

    resolution: 720,
    constraints: {
        video: {
            height: {
                ideal: 720,
                max: 720,
                min: 180
            },
            width: {
                ideal: 1280,
                max: 1280,
                min: 320
            }
        }
    },

Is this the deployed workaround? I added a similar section to my own config.js but have not had the opportunity yet to do extensive tests, it seems to work though with an older VGA-resolution camera (Philips PCVC740K).

Also, yesterday it contained aspectRatio: 16 / 9, as the first member of the video object, this has been taken out now. Still experimenting I guess?

[saghul]

Also, yesterday it contained aspectRatio: 16 / 9, as the first member of the video object, this has been taken out now. Still experimenting I guess?

We deployed the fix, that constraintt is now gone for good.

[saghul]

UPDATE: We updated meet.jit.ssi yesterday and applied the fix mentioned on "update 3". Please tet again normally and report back if you are still having problems.

[hklaufus]

Still not working with update 3 and update 4. Still unable to access camera ref #5952

[Yetangitu]

UPDATE: We updated meet.jit.ssi yesterday and applied the fix mentioned on "update 3". Please tet again normally and report back if you are still having problems.

...and the mentioned fix consists of the constraints section I mentioned minus the aspectRatio item? Inquiring minds running their own meet instances want to know... In other words, is the fix simply an edit to config.js and as such easily deployable by anyone or does it require an update to lib-jitsi-meet? I suspect the former as I have not found any relevant commits to lib-jitsi-meet.

[saghul]

@Yetangitu Correct.

[Yetangitu]

@saghul OK, thanks, an easy fix.

[Iwish767]

As of today Jitsi cannot see my camera or mike on HP laptop, with Mint/Firefox....I get a red flashing camera sign, as soon as I allow access.....any ideas.

tks

[prismopensource]

Still the same error after I check now with latest Safari on latest Mac OS X.

[ghost]

Failed to access camera

2020-04-17T08:29:09.794Z [features/base/tracks] Failed to create local tracks ["video"] s {gum: {…}, name: "gum.general", message: "Could not start video source", stack: "Error↵ at new s (https://web-cdn.jitsi.net/meet…677/libs/lib-jitsi-meet.min.js?v=4020.672:1:91969"}gum: {error: DOMException: Could not start video source, constraints: {…}, devices: Array(1)}name: "gum.general"message: "Could not start video source"stack: "Error↵ at new s (https://web-cdn.jitsi.net/meetjitsi_4025.677/libs/lib-jitsi-meet.min.js?v=4020.672:1:110290)↵ at https://web-cdn.jitsi.net/meetjitsi_4025.677/libs/lib-jitsi-meet.min.js?v=4020.672:1:91969"__proto__: Error o @ Logger.js:154 (anonymous) @ functions.js:123 Promise.catch (async) (anonymous) @ functions.js:122 Promise.then (async) E @ functions.js:99 muteVideo @ conference.js:908 (anonymous) @ conference.js:2189 s.emit @ events.js:146 g.emitEvent @ UI.js:433 _setVideoMuted @ VideoMuteButton.js:155 _handleClick @ AbstractVideoMuteButton.js:25 _onClick @ AbstractButton.js:254 m @ react-dom.production.min.js:15 w @ react-dom.production.min.js:15 (anonymous) @ react-dom.production.min.js:16 A @ react-dom.production.min.js:16 O @ react-dom.production.min.js:17 D @ react-dom.production.min.js:17 T @ react-dom.production.min.js:17 Mn @ react-dom.production.min.js:85 Bn @ react-dom.production.min.js:87 t.unstable_runWithPriority @ scheduler.production.min.js:20 fi @ react-dom.production.min.js:113 Rs @ react-dom.production.min.js:207 In @ react-dom.production.min.js:86

`	s	@	Logger.js:154
	(anonymous)	@	RTCUtils.js:992
	Promise.catch (async)
	(anonymous)	@	RTCUtils.js:991
	_newGetUserMediaWithConstraints	@	RTCUtils.js:984
	(anonymous)	@	RTCUtils.js:1358
	Promise.then (async)
	newObtainAudioAndVideoPermissions	@	RTCUtils.js:1404
	obtainAudioAndVideoPermissions	@	RTC.js:265
	createLocalTracks	@	JitsiMeetJS.js:352
	(anonymous)	@	functions.js:103
	Promise.then (async)
	E	@	functions.js:99
	muteVideo	@	conference.js:908
	(anonymous)	@	conference.js:2189
	s.emit	@	events.js:146
	g.emitEvent	@	UI.js:433
	_setVideoMuted	@	VideoMuteButton.js:155
	_handleClick	@	AbstractVideoMuteButton.js:25
	_onClick	@	AbstractButton.js:254
	m	@	react-dom.production.min.js:15
	w	@	react-dom.production.min.js:15
	(anonymous)	@	react-dom.production.min.js:16
	A	@	react-dom.production.min.js:16
	O	@	react-dom.production.min.js:17
	D	@	react-dom.production.min.js:17
	T	@	react-dom.production.min.js:17
	Mn	@	react-dom.production.min.js:85
	Bn	@	react-dom.production.min.js:87
	t.unstable_runWithPriority	@	scheduler.production.min.js:20
	fi	@	react-dom.production.min.js:113
	Rs	@	react-dom.production.min.js:207
	In	@	react-dom.production.min.js:86

`

[luixxiul]

I tried unstable build from Firefox (nightly) with a fresh profile, applying some settings discussed here https://community.jitsi.org/t/bad-audio-quality-and-users-dropping-randomly-at-25-users/35258/6, and that worked. I suspect the issue would exist between Chromium/Webkit (ie. Chrome, Vivaldi, Safari) and Jitsi. Would anyone please check with Firefox?

[prismopensource]

Testing with http://meet.jit.si here, latest Firefox and Chrome work as advertised with the same hardware, just a problem with Safari.

[luixxiul]

Thanks, but I would like to know how it will be on a self-hosted instance.

[Yetangitu]

@luixxiul if you have a self-hosted instance you can test this yourself by adding the fix to config.js, see https://github.com/jitsi/jitsi-meet/issues/5425#issuecomment-614604449 or get it fresh from https://meet.jit.si/config.js (copy resolution and constraints to your own config.js)

[luixxiul]

ah sorry, I have tested the latest unstable release on my self-hosted instance (without applying that fix). I would like to know about other instances to see if that is the issue that can be avoided on Firefox or not.

[Yetangitu]

It seems to work here on my self-hosted instance, using an older VGA-resolution webcam on Firefox nightly (77.0a1). This is with the current stable version (deb https://download.jitsi.org stable/ on Debian stable) with the fix in config.js.