+1

+1

+1

I would, 100%, use this as described. I currently have a convoluted workaround to get an additional, non-output video-only feed out by using OBS screen capturing my vMix full screen window.

This would solve that handily.

But the key words there are "video only".

If you look at a Mix input, you'll notice that it doesn't have any audio meters. That's because the Mix inputs don't process audio--the audio is handled within the inputs and buses themselves. Mix inputs are completely visual.

That also means that an NDI out on the Mix input would also be completely visual.

For many purposes, like mine or yours, that won't matter, which is why I 100% support this as a way to get visual only NDI monitor feeds of multiviews and other visual only elements not covered by the existing NDI outs when the Outputs are already in use elsewhere.

But I do think there will be a hesitancy to implement this, because of a perception that other users will expect to get the sync'ed and embedded audio, without realizing the limitation of this offering.

But I think if they titled it something like



expectations would be tempered, but I also get the feeling it's unlikely we'll see this until we get past the limitations preventing a 5th Output.

(And, please, nobody say "You can just select an audio bus like you can with the 4 Outputs", because, at that point, even if this isn't running up against the timing/sync issues preventing a 5th Output, that definitely would.)

+1

+1

+1 Using the Mixes to toggle between multiple vMix Caller or Zoom remote guests to project onto monitors at a hybrid event, via Birddog Play, would be another use case.

vMix is less expensive than a computer capable of running it well. If you have a need for more outputs it's probably a lot better to get another computer capable of running vMix and using it to create the additional mixes you need with an additional licensed copy of vMix.

Does ResizeableBAR help this at all? I know it helps with loading data INTO the GPU...

+1 and a little bump :)