New Teams: Camera Settings Gone

<QUOTE>

Thank you for the tip, but when I extracted the ffmpeg file, at first I could not find the .exe file but then took a closer look and I had downloaded the code instead. I have now found the correct .exe file.

I tried to write a bat file, but I don't think I got it quite right.

@echo off

cd "C:\Users\OneDrive - Adobe\Documents\LAP\ffmpeg files\ffmpeg-master-latest-win64-gpl\bin>ffmpeg -f dshow -show_video_device_dialog true -i video="Logitech Webcam C925e""

pause

Is this the correct way? Any guidance from you guys on how to correct this bat file would be very helpful!

<\QUOTE>

This is what mine looks like:

cd "D:\Programs\ffmpeg-N-112848-g2020ef9770-win64-gpl\bin"
ffmpeg -f dshow -show_video_device_dialog true -i video="NexiGo N930AF FHD Webcam"

Here's what worked for me. Put the following in a text editor:

cd "Full\Path\to\ffmpeg\bin\folder"
.\ffmpeg -f dshow -show_video_device_dialog true -i video="Camera Name"

Camera Name is literally what's listed as the camera's name in Windows Settings -> Devices. Save the file with a .bat extension, then double-click it to run it.

Note that, as I understand it, you'll have to create a different .bat file for each camera you intend to use.

Same issue for me - we use the Yealink UVC30 4k cameras and they consistently default back to a wide FOV - in the "classic Teams" you could adjust pan/tilt/zoom - now there is nothing.

Did anyone actually get to the bottom of why this has been removed in "new Teams"?

Mark

Interestingly - as well as the Yealink UVC30 I also have a Microsoft Lifecam Studio - which you now cannot adjust through Windows App (as there is not one) OR Teams !

Same issue for me - we use the Yealink UVC30 4k cameras and they consistently default back to a wide FOV - in the "classic Teams" you could adjust pan/tilt/zoom - now there is nothing.

Did anyone actually get to the bottom of why this has been removed in "new Teams"?

Mark

I work for an S&P500 M365 customer. After reporting, I was told that Microsoft's engineers are aware of it and looking into fixing it.

As for why the feature was removed, my guess is since it's an ffmpeg feature there may have been licensing or packaging challenge. 1 of the major reasons for new Teams was a lighter client, and I suppose shipping the entire ffmpeg library - if that's what they did previously - wasn't in line with that.

If you're an IT admin you might be able to push ffmpeg and a matching .bat file to users who want the feature back, and then possibly remove it after the feature has been reinstated.

Thanks for the information. I am currently using old teams because I really do need to have zoom feature, and I like the exposure/brightness etc control as well. I can't install FFMPEG or have that done for me with my org, as its more locked down, so I really do benefit a lot from the device settings options. Well, not just benefit, but frankly *need* given my office space, and the way it helps me to be much more professionally presented with more control.