Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Don't ban low-resolution cameras #1559

Closed
TheLastProject opened this issue May 7, 2017 · 11 comments
Closed

Don't ban low-resolution cameras #1559

TheLastProject opened this issue May 7, 2017 · 11 comments

Comments

@TheLastProject
Copy link
Contributor

I don't know when this change happened, but for some reason Jitsi has been refusing to use my camera for a while because "Your camera does not satisfy some of the required constraints."

Is there any reason this change was made? Could it be reverted? Perhaps replaced with a warning suggesting the user buy a newer camera?

I know my ThinkPad x200's camera resolution is low, but being able to use it sure beats the hell out of having no camera at all, especially because it always worked just fine and I've had many, many video chats over Jitsi Meet with it.

@damencho
Copy link
Member

damencho commented May 8, 2017

Does your camera work ok with https://appr.tc?
You are having a problem with meet.jit.si right?
Please provide more info like OS, browser and browser version and attaching console log with the error.
Thanks

@saghul
Copy link
Member

saghul commented May 8, 2017

Please note that the error comes from the browser itself, it's not an error we generate. This is caused when we request the camera is opened at a given resolution, but there is a fallback mechanism, so your camera should have been opened :-S Please provide some more info as @damencho requested.

@damencho damencho added the info:feedback-needed The maintainer needs more feedback, please refer to the comment section label May 8, 2017
@TheLastProject
Copy link
Contributor Author

TheLastProject commented May 8, 2017

This indeed involves meet.jit.si. Framatalk, which probably runs on an older version of Jitsi Meet, works fine. Appr.tc works fine, as does Riot. I haven't tested other services.

OS: Debian Testing
Browser: Firefox ESR 45.9.0

Logs:

(TIME) index.html loaded:	 354.51 CrazyRatsUniteStrongly:9:9
(TIME) Sending external connect XHR:	 490.265 external_connect.js:75:5
[modules/RTC/RTCBrowserType.js] <o>:  This appears to be Firefox, ver: 45 lib-jitsi-meet.min.js:6:10419
mutating the [[Prototype]] of an object will cause your code to run very slowly; instead create the object with the correct initial [[Prototype]] value using Object.create lib-jitsi-meet.min.js:26:7745
(TIME) external connect XHR done:	 718.89 external_connect.js:40:13
DEPRECATED JS - Cookie has been deprecated since 5.8.0 and will be removed in a future release. Use cookie instead.   
 t.default@https://cdn.jitsi.net/1924/libs/app.bundle.min.js?v=1924:1:1287 app.bundle.min.js:7:22147
[react/index.web.js] <>:  (TIME) document ready:	 1565.0900000000001 app.bundle.min.js:60:1035
[modules/URL/ConferenceUrl.js] <e>:  "Stored original conference URL: https://meet.jit.si/CrazyRatsUniteStrongly" app.bundle.min.js:60:1035
[modules/URL/ConferenceUrl.js] <e>:  "Conference URL for invites: https://meet.jit.si/CrazyRatsUniteStrongly" app.bundle.min.js:60:1035
[modules/RTC/RTCUtils.js] <be</<.value>:  Get media constraints Object { audio: true, video: false } lib-jitsi-meet.min.js:6:10419
[modules/xmpp/strophe.jingle.js] <t>:  Configured STUN servers:  Array [ Object, Object, Object ] lib-jitsi-meet.min.js:6:10419
[modules/xmpp/xmpp.js] <x</<.value>:  (TIME) Strophe Attaching	:1943.23 lib-jitsi-meet.min.js:6:10419
[modules/xmpp/xmpp.js] <x</<.value>:  (TIME) Strophe attached:	 1945.025 lib-jitsi-meet.min.js:6:10419
[modules/xmpp/xmpp.js] <x</<.value>:  My Jabber ID: e1c3fe51-a72a-4490-a26b-db40f14c69da@meet.jit.si/84f89afb-53ba-4c71-808e-61bfa0404200 lib-jitsi-meet.min.js:6:10419
GET 
https://cdn.jitsi.net/1924/ [HTTP/2.0 403 Forbidden 14ms]
navigator.mozGetUserMedia has been replaced by navigator.mediaDevices.getUserMedia lib-jitsi-meet.min.js:2:31342
Use of attributes' nodeValue attribute is deprecated. Use value instead. app.bundle.min.js:61:14192
[modules/xmpp/strophe.ping.js] <y</<.value>:  XMPP pings will be sent every 10000 ms lib-jitsi-meet.min.js:6:10419
not well-formed <unknown>:1:168
[modules/RTC/RTCUtils.js] <be</<.value/<>:  onUserMediaSuccess lib-jitsi-meet.min.js:6:10419
[modules/RTC/RTCUtils.js] <be</<.value>:  Get media constraints Object { audio: false, video: Object } lib-jitsi-meet.min.js:6:10419
[modules/RTC/RTCUtils.js] <be</<.value/<>:  Failed to get access to local media. Error  MediaStreamError { name: "OverconstrainedError", message: "Constraints could be not satisfied.", constraint: "width", stack: "" } Object { audio: false, video: Object } lib-jitsi-meet.min.js:6:10419
[modules/RTC/RTCUtils.js] <w/<>:  failed to obtain video stream - stop Object { gum: Object, name: "gum.constraint_failed", message: "Constraint could not be satisfied: …", stack: "i@https://cdn.jitsi.net/1924/libs/l…" } lib-jitsi-meet.min.js:6:10419

[conference.js] <m/<>:  failed to create local tracks Array [ "audio", "video" ] Object { gum: Object, name: "gum.constraint_failed", message: "Constraint could not be satisfied: …", stack: "i@https://cdn.jitsi.net/1924/libs/l…" } app.bundle.min.js:60:1035

[modules/RTC/RTCUtils.js] <be</<.value>:  Get media constraints Object { audio: true, video: false } lib-jitsi-meet.min.js:6:10419
MediaStream.stop() is deprecated and will soon be removed. Use MediaStreamTrack.stop() instead. lib-jitsi-meet.min.js:3:9262
[modules/RTC/RTCUtils.js] <be</<.value/<>:  onUserMediaSuccess lib-jitsi-meet.min.js:6:10419
[conference.js] <t.default.init/<>:  initialized with %s local tracks 1 app.bundle.min.js:60:1035
[modules/remotecontrol/RemoteControl.js] <f</<.value>:  Initializing remote control. app.bundle.min.js:60:1035
[modules/xmpp/ChatRoom.js] <t>:  Joined MUC as crazyratsunitestrongly@conference.meet.jit.si/e1c3fe51 lib-jitsi-meet.min.js:6:10419
[modules/connectivity/ParticipantConnectionStatus.js] <e>:  RtcMuteTimeout set to: 2000 lib-jitsi-meet.min.js:6:10419
[JitsiConference.js] <o>:  backToP2PDelay: 5 lib-jitsi-meet.min.js:6:10419
[JitsiConference.js] <o.prototype._doReplaceTrack>:  _doReplaceTrack - no JVB JingleSession lib-jitsi-meet.min.js:6:10419
[JitsiConference.js] <o.prototype._doReplaceTrack>:  _doReplaceTrack - no P2P JingleSession lib-jitsi-meet.min.js:6:10419
[modules/xmpp/moderator.js] <o.prototype.setFocusUserJid>:  Focus jid set to:  undefined lib-jitsi-meet.min.js:6:10419
[modules/xmpp/moderator.js] <o.prototype.createConferenceIq>:  Session ID: null machine UID: 1fd1a0c8b5d0aae534eeee7a0fcc4bb7 lib-jitsi-meet.min.js:6:10419
[modules/xmpp/moderator.js] <o.prototype.setFocusUserJid>:  Focus jid set to:  focus@auth.meet.jit.si lib-jitsi-meet.min.js:6:10419
[modules/xmpp/moderator.js] <o.prototype.parseConfigOptions>:  Authentication enabled: false lib-jitsi-meet.min.js:6:10419
[modules/xmpp/moderator.js] <o.prototype.parseConfigOptions>:  External authentication enabled: false lib-jitsi-meet.min.js:6:10419
[modules/xmpp/moderator.js] <o.prototype.parseConfigOptions>:  Sip gateway enabled:  true lib-jitsi-meet.min.js:6:10419
not well-formed <unknown>:1:168
[modules/xmpp/ChatRoom.js] <w</<.value>:  entered crazyratsunitestrongly@conference.meet.jit.si/focus Object { show: "", status: "", affiliation: "owner", role: "moderator", jid: "focus@auth.meet.jit.si/focus1024484…", isFocus: true, isHiddenDomain: false } lib-jitsi-meet.min.js:6:10419
[modules/xmpp/ChatRoom.js] <w</<.value>:  Ignore focus: crazyratsunitestrongly@conference.meet.jit.si/focus, real JID: focus@auth.meet.jit.si/focus1024484449429 lib-jitsi-meet.min.js:6:10419
[modules/UI/UI.js] <Y.initEtherpad>:  Etherpad is enabled app.bundle.min.js:60:1035
[modules/version/ComponentsVersions.js] <i.prototype.processPresence/<>:  Got xmpp version: Prosody(trunk nightly build 747 (2017-02-19, 428d4abee723),Linux) lib-jitsi-meet.min.js:6:10419
[modules/version/ComponentsVersions.js] <i.prototype.processPresence/<>:  Got focus version: JiCoFo(1.0.1.0-348,Linux) lib-jitsi-meet.min.js:6:10419
[modules/xmpp/recording.js] <r.prototype.handleJibriPresence>:  Handle jibri presence :  off lib-jitsi-meet.min.js:6:10419
[conference.js] <t.default._setupListeners/<>:  Received recorder status change:  available undefined app.bundle.min.js:60:1035
[conference.js] <t.default._setupListeners/<>:  My role changed, new role: moderator app.bundle.min.js:60:1035
[JitsiConference.js] <o.prototype._maybeStartOrStopP2P>:  P2P? isModerator: true, peerCount: 0 => false lib-jitsi-meet.min.js:6:10419
[modules/xmpp/ChatRoom.js] <w</<.value>:  (TIME) MUC joined:	 5541.545 lib-jitsi-meet.min.js:6:10419
[modules/xmpp/ChatRoom.js] <w</<.value>:  Subject is changed to  lib-jitsi-meet.min.js:6:10419
[modules/UI/videolayout/LargeVideoManager.js] <b</<.value/<>:  hover in %s e1c3fe51 app.bundle.min.js:60:1035
not well-formed <unknown>:1:168
not well-formed <unknown>:1:168
[modules/RTC/RTCUtils.js] <m>:  list of media devices has changed: Array [ MediaDeviceInfo, MediaDeviceInfo, MediaDeviceInfo ] lib-jitsi-meet.min.js:6:10419
[modules/RTC/RTCUtils.js] <be</<.value>:  Get media constraints Object { audio: false, video: Object } lib-jitsi-meet.min.js:6:10419
[modules/RTC/RTCUtils.js] <be</<.value/<>:  Failed to get access to local media. Error  MediaStreamError { name: "OverconstrainedError", message: "Constraints could be not satisfied.", constraint: "width", stack: "" } Object { audio: false, video: Object } lib-jitsi-meet.min.js:6:10419
[modules/RTC/RTCUtils.js] <w/<>:  failed to obtain video stream - stop Object { gum: Object, name: "gum.constraint_failed", message: "Constraint could not be satisfied: …", stack: "i@https://cdn.jitsi.net/1924/libs/l…" } lib-jitsi-meet.min.js:6:10419

[conference.js] <m/<>:  failed to create local tracks Array [ "video" ] Object { gum: Object, name: "gum.constraint_failed", message: "Constraint could not be satisfied: …", stack: "i@https://cdn.jitsi.net/1924/libs/l…" } app.bundle.min.js:60:1035

[modules/UI/util/MessageHandler.js] <a/<>:  Array [ Object, true, Object, Object ] undefined app.bundle.min.js:60:1035

One interesting thing to notice is that on this device, Jitsi Meet doesn't even ask for camera permission.

@damencho damencho added type:bug and removed info:feedback-needed The maintainer needs more feedback, please refer to the comment section labels May 8, 2017
@githubtefo
Copy link

githubtefo commented May 9, 2017

I reported similar issues past month on #1427

Since today Jitsi Meet Beta can't detect the webcam ("your camera doesn't fit with the requirements").
I can verify that the webcam detection issue only occurs with the built-in laptop webcam and not with an USB-connected Logitech webcam. It doesn't occur with others webrtc services that need access to webcam in Firefox 52. In Chromium the detection works fine. Jitsi Meet and Jisti Meet Beta has the issue since the last update of meet.jit.si few days ago.

Firefox 53.0.2
Arch and Ubuntu

@WohthaN
Copy link

WohthaN commented May 25, 2017

Same problem here, firefox 52.0.2 (64-bit) on Debian with a philips SPC1000NC, jitsi-meet 1.0.2104-1 on a debian testing server.
Firefox works fine on Appr.tc, chromium works fine on the same jitsimeet installation.

@geroldr
Copy link

geroldr commented Jun 4, 2017

Same problem with Debian Stretch 64 bit AMD64, Firefox 45.9.0,
Bus 005 Device 003: ID 046d:08c5 Logitech, Inc. QuickCam Pro 5000
works properly on https://appr.tc
Video no longer working on meet.jit.si when worked quite well previously.
Jitsi chat is still working.

Jitsi really needs to remain backward compatible. I do not want to return to skype.
Thanks and look forward to your successfully resolving this problem.

I will gladly do any tests to help.

Best wishes

@arevamp
Copy link

arevamp commented Jul 3, 2017

I have the same problem with firefox 54.0 on Debian Jessie 64bit on Dell Latitude 6400 with build-in camera "0c45:63f8 Microdia Sonix Integrated Webcam"
"error: there was an error connecting to your camera - your camera does not satify some of the required constraints"
With Chromium 57.0.2987.98 on the same laptop the camera works fine.
Jitsi-meet server installed today on Debian Stretch from the Debian Jitsi stable repository.
Is there a possibility to change any settings in firefox oder on the jitsi-meet server to get the camera working in firefox too?

@githubtefo
Copy link

githubtefo commented Jul 30, 2017

Last version of Jitsi support low-resolution cameras again in Firefox.
Thanks for fix it!
Should we close this issue?

@gklimm
Copy link

gklimm commented Jul 30, 2017

It works again! Thank you!

@saghul
Copy link
Member

saghul commented Jul 30, 2017

Thanks for confirming, closing then!

@saghul saghul closed this as completed Jul 30, 2017
@lamixer
Copy link

lamixer commented Sep 16, 2017

Hello: This issue emerged for me today. A 2016 Macbook running Firefox 55.0.3 connecting to my Jitsi-Meet server is asked to allow microphone access but not asked to allow camera access and the the error pops up stating camera doesn't fulfil the requirements (or something to that effect).

However, if I go to meet.jit.si, the camera works fine (lo res though it is)

How can I configure my server to work the way meet.jit.si does?

I installed my jitsi-meet on debian 8.6 using your stable packages and easy install jitsi-meet setup early September 2017.

Thank you.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

9 participants