Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Logitech 4K Pro Magnetic Webcam for Pro Display XDR
- Thread starter Nomad110
- Start date
- Sort by reaction score
Not for me either. A few seconds of video when opening, then it freezes and eventually blacks out all together.
[automerge]1590593924[/automerge]
@DeanLubaki , so after update it works for you in Chrome? That would be interesting, as it might help solving the issue.
[automerge]1590593924[/automerge]
@DeanLubaki , so after update it works for you in Chrome? That would be interesting, as it might help solving the issue.
Not necessarily after the update-always. I've been flagging for a while that I do not have any issues.
So I tried it again today with Google Meet (which previously displayed the message "Camera is starting" but nothing happens) and this time it worked. I quit the meeting and recreated it 3 or 4 times with the camera working each time....at 720p resolution. After the 5th time it now has resorted back to not working. The only difference I did from previous tests was I tested the camera with Web Cam Test first and then went straight to Google Meet. However, when I try this again now I am back to the same issues I had before.
Last edited:
Same here, I noticed the first time it worked it showed at a much lower resolution (480p, 640 x 480).
Something interesting... It seems like Chrome is using WebRTC to access the webcam. Check out this example and choose anything but set the resolution width to <= 640px and the webcam will start working.
A few other things...
1. Logitech Camera Settings now works with macOS.
2. You can join a Google Meet from Safari and it will work
Last edited:
Here is a thread over in the Apple Community forums which would correlate with our findings:
https://discussions.apple.com/thread/251227658
Slack responded that the camera was not supported by apps that use WebRTC. Unfortunately Slack does not support video calling under Safari.
Yes WebKit and Chromium would be using different codecs as per the log events. I took the chance to install Chrome Canary but not dice either.
At this point I am considering purchasing a new iMac should they be announced at the WWDC or even an LG UltraFine 5K which has a pretty decent 1080p camera.
I will probably be getting in touch with the Apple Store to let them know that they are selling a defective product. I will also be asking Logitech for a refund through the regular support channels.
https://discussions.apple.com/thread/251227658
Slack responded that the camera was not supported by apps that use WebRTC. Unfortunately Slack does not support video calling under Safari.
Yes WebKit and Chromium would be using different codecs as per the log events. I took the chance to install Chrome Canary but not dice either.
At this point I am considering purchasing a new iMac should they be announced at the WWDC or even an LG UltraFine 5K which has a pretty decent 1080p camera.
I will probably be getting in touch with the Apple Store to let them know that they are selling a defective product. I will also be asking Logitech for a refund through the regular support channels.
I opened a Chromium bug today, found here. Hopefully, it gets some traction; feel free to comment on the bug stating you also have the same issue.
There is a subpar workaround I found to get it working with Chrome but only at 640x480px. Use the WebRTC sample page and choose VGA. Then open up Google Meet in another tab and start your video before joining. You can then close the WebRTC tab.
I'm not convinced yet that the issue is with WebRTC since it works in Safari.
I also tried in Firefox and can get the camera up to HD (1280x720px) before the stream fails to load. It's different though, as WebRTC gives the error "getUserMedia: Constraints could be not satisfied" and doesn't even try to start the camera. I don't get anything in the process logs at 4K, but I do see some similarities to the Chrome logs even when the stream is working in HD.
Chrome:
Firefox:
After a bit of searching it seems these errors are permissions related. This may be our culprit as things changed a bunch from Mojave to Catalina. I do not see these errors in the Safari process logs.
I wish I had a Brio laying around to play with simultaneously and compare.
There is a subpar workaround I found to get it working with Chrome but only at 640x480px. Use the WebRTC sample page and choose VGA. Then open up Google Meet in another tab and start your video before joining. You can then close the WebRTC tab.
I'm not convinced yet that the issue is with WebRTC since it works in Safari.
I also tried in Firefox and can get the camera up to HD (1280x720px) before the stream fails to load. It's different though, as WebRTC gives the error "getUserMedia: Constraints could be not satisfied" and doesn't even try to start the camera. I don't get anything in the process logs at 4K, but I do see some similarities to the Chrome logs even when the stream is working in HD.
Chrome:
Code:
default 19:12:41.286369-0400 Google Chrome Helper (Plugin) CMIO_Unit_ScopeElement.h:200:SafeGetElement Throwing err: -67454, elementIndex: 1
default 19:12:41.287309-0400 Google Chrome Helper (Plugin) CMIOHardware.cpp:357:CMIOObjectGetPropertyData no object property for given ID 33
default 19:12:41.331850-0400 Google Chrome Helper (Plugin) CMIO_Unit_Input_Device.cpp:246:GetPropertyInfo CMIOUInputFromProcs::GetPropertyInfo() failed for id 102, Error: -67456Firefox:
Code:
default 19:01:43.036730-0400 firefox CMIO_Unit_ScopeElement.h:200:SafeGetElement Throwing err: -67454, elementIndex: 1
default 19:01:43.037930-0400 firefox CMIOHardware.cpp:357:CMIOObjectGetPropertyData no object property for given ID 50
default 19:01:43.040118-0400 firefox CMIO_Unit_Input_Device.cpp:246:GetPropertyInfo CMIOUInputFromProcs::GetPropertyInfo() failed for id 102, Error: -67456After a bit of searching it seems these errors are permissions related. This may be our culprit as things changed a bunch from Mojave to Catalina. I do not see these errors in the Safari process logs.
I wish I had a Brio laying around to play with simultaneously and compare.
Last edited:
It clearly is a defective product if the software or firmware layer do not work as intended. This webcam is being marketed for the Pro Display XDR running under macOS Catalina alongside the new Mac Pro.
Still hopeful that @raha613's WebRTC effort will lead to conclusive results but I remain doubtful since the webcam has been shown to work as intended under macOS Mojave.
In any case it shouldn't be up to to the customer to debug their highest-end personal webcam because of lacklustre QA and support processes.
Now that they have acknowledged the problem, our only hope is to move forward and keep putting pressure on them for a fix. Or move on and try to get a refund.
Still hopeful that @raha613's WebRTC effort will lead to conclusive results but I remain doubtful since the webcam has been shown to work as intended under macOS Mojave.
In any case it shouldn't be up to to the customer to debug their highest-end personal webcam because of lacklustre QA and support processes.
Now that they have acknowledged the problem, our only hope is to move forward and keep putting pressure on them for a fix. Or move on and try to get a refund.
Meanwhile my Logitech 4k Pro for XDR got delivered as well (after a long waiting time). So far I'm not impressed at all. Both USB-C cables needs extremely high force to get connected to XDR or MacPro, camera runs very hot when active, focus seams to be a bit blurry (potentially not yet running at full resolution), first access via QuickTime Player for a recording trial lead to kernel panic..., and so far I haven't seen it to run beyond 1080p at full 4k resolution (so far I tried Zoom, Teams, Facetime, PhotoBooth, Quicktime,...).
What software does support 4k recording and 4k video conference with this webcam meanwhile? I expected plug and play, especially considering that the camera is advertised especially for the XDR.
What software does support 4k recording and 4k video conference with this webcam meanwhile? I expected plug and play, especially considering that the camera is advertised especially for the XDR.
Last edited:
Yes, it’s very far from plug and play. I notice focus issues every once in a while too. Download Logitech Camera Settings and you can toggle auto focus on and off which usually fixes the issue.
I also don’t get 4K resolution in Apple apps, very frustrating.
With Zoom you can try going into preferences and enabling HD.
Also anything based on Chromium does not work at any resolution over 640x480px.
I opened a Chromium bug but haven’t gotten any traction since it requires hardware (the webcam) which they don’t have.
I think I’m pretty close to nailing down where in the source code the exact problem is. It’s related to how Chromium implements AVFoundation.
I also don’t get 4K resolution in Apple apps, very frustrating.
With Zoom you can try going into preferences and enabling HD.
Also anything based on Chromium does not work at any resolution over 640x480px.
I opened a Chromium bug but haven’t gotten any traction since it requires hardware (the webcam) which they don’t have.
I think I’m pretty close to nailing down where in the source code the exact problem is. It’s related to how Chromium implements AVFoundation.
I'm getting around the limitation by using Snap Camera. Set the input for the Snap Camera to be the Logi 4k Pro, then use Snap Camera with Google Meet on Chrome. Works with Chrome 83.0.4103.106 running on macOS 10.15.5
Wow, that app is pretty neat in general, above and beyond the fact that it can be used as a workaround. Thanks for the tip!
Are you getting 4K (4096x2160)? I only seem to get HD (1280x720) via Snap Camera...
Last edited:
I have some good news. I built Chromium from source to enable verbose logging and the logs show Chromium is trying to start the capture with an unsupported pixel format for this webcam (PIXEL_FORMAT_I420).
One of the members of the Chromium dev team picked up the bug and is going to work on creating a patch for me to test in the next few days.
We might finally be turning the corner... I'll post an update when I have one.
One of the members of the Chromium dev team picked up the bug and is going to work on creating a patch for me to test in the next few days.
We might finally be turning the corner... I'll post an update when I have one.
@raha613 Great work!
Odd that it would start a stream at the wrong resolution. As if this specific camera model and specifications had not been properly defined within Chromium.
Why would the stream request differ between Mojave and Catalina ?
I received a reply back from Logitech stating that their engineering team are still working on a fix.
I pressed them for additional details and a specific timeline. I'll keep you posted!
Odd that it would start a stream at the wrong resolution. As if this specific camera model and specifications had not been properly defined within Chromium.
Why would the stream request differ between Mojave and Catalina ?
I received a reply back from Logitech stating that their engineering team are still working on a fix.
I pressed them for additional details and a specific timeline. I'll keep you posted!
I am happy to report that the fix is available in today's Canary build, version 85.0.4182.0. It's going to be a while until we see this in the stable build; version 85 is scheduled for the end of August.
My guess is it will be even longer before it reaches Electron based apps like Slack. e.g., Electron will have to upgrade to the new Chromium build and then Slack will have to upgrade to that Electron build.
A huge thanks to Guido U. @ Google for making this happen and so quickly!
Patch details: https://chromium-review.googlesource.com/c/chromium/src/+/2264053
My guess is it will be even longer before it reaches Electron based apps like Slack. e.g., Electron will have to upgrade to the new Chromium build and then Slack will have to upgrade to that Electron build.
A huge thanks to Guido U. @ Google for making this happen and so quickly!
Patch details: https://chromium-review.googlesource.com/c/chromium/src/+/2264053
Last edited:
It’s the nightly developer build found here: https://www.google.com/chrome/canary/
There’s a chance the patch could be included in the next regular Chrome build (84). I’m not sure when that is scheduled for though. Cross your fingers.