I upgraded a desktop computer to the Anniversary edition, and as expected, a preset with a c920 and a c930e loaded but said the cameras were offline.
I deleted those inputs and was able to add and configure two new inputs, and now the cameras appear to be working as expected.
I am using the vMix output for Skype and Zoom, so the system is configured for 720p. I haven't tried 1080p.

Here's a thread about this matter that has emerged on MSDN.

https://social.msdn.micr...diafoundationdevelopment

Someone from the MS camera dev team is explaining and even defending the change.

Anyone who develops on Windows (Martin & Co?) should add their voices to the discussion.

Yes, the change was deliberate, if not well communicated.

That means that there's some work for application developers to get in sync with the new reality.

There's an opportunity for someone to write a wrapper that gets around the new architecture, which most people will find simply unnecessary.

It's worth mentioning that this kind of trickery in the driver was one of the things that relegated the Microsoft Lifecam Studio to the back of the bus, leaving Logitech to a command of the marketplace for such devices.

The LifeCam Studio had a 1080p sensor and was supposed to be able to deliver 1080p30. When init'd to 1080p30 the camera compressed the frames and the MS driver was supposed to decompress them at the host PC. The idea was to insulate the client application from from the details. The process, while effectively hidden, was not very robust. Few actually achieved what was possible. Eventually people simply preferred Logitech webcams.

Hi guys,

I've done a little bit of research on this, and it looks like the changes made in the Anniversary update are well intentioned
and would even be beneficial to vMix if implemented correctly, but it looks like there are some side effects to these updates that Microsoft didn't consider.

The change is for allowing webcam sharing, and it does this by converting the webcam format to YUY2 within Windows regardless of source format, so
all applications have access to the uncompressed video without having to decode things like MJPG and H264 multiple times.

So far so good, as Windows could actually do this at lower latency and less CPU than vMix could. YUY2 is also the highest possible quality in this scenario.

Problem is many USB 2.0 webcams offer direct support for YUY2 alongside MJPG and H264 and the Anniversary update appears to choose YUY2 if available.
This results in very low frame rates in HD as sending uncompressed YUY2 over USB2 is just not fast enough.

The simply fix in my view, is for there to be a "preferred native video format" dropdown box for each webcam in the control panel.

In any case, it looks like Microsoft have heard your feedback and are working on an alternative. We shall see what they come up with...

Regards,

Martin
vMix

Many people are reporting that the new frame service is a serious problem. Further, it seems that the most common webcam in the world (Logitech C920) is now failing with Skype.

This has pushed Microsoft to agree to work on allowing MJPEG access via the new frame server mechanism. That will be implemented in a future update.

There's conceptual agreement with respect to H.264 as well. Although it seems that will be harder to achieve, so considered a separate matter.

Today there seems to have been a firestorm as the masses came to see that Skype is fundamentally broken as a result.

http://arstechnica.com/i...?comments=1&start=40

https://www.thurrott.com...ws-10-anniversary-update

The real news is that someone has revealed a registry hack the disables the frame server, bringing the system back to normal behavior.



I just applied this fix to my laptop. Both vMix and OBS Studio can now use the C930e in 1080p30 MJPEG mode.

What version/revision of windows 10 are you using?

I had to recently do a rebuild of windows from scratch, and first run of vMix worked straight up on the newly up to date machine.