You could use virtual sets instead? Then you just pick the cameras from the side.

Otherwise, VMix 24 has a new dynamic input feature that might be some help.

Without getting into scripting, the new shortcuts for the Dynamic Input feature in v24 made it really simple to set up Source and Destination buttons for multiviews on my streamdeck recently.

For each source, I added a shortcut 'SetDynamicInput1 Value=x', and then for each destination, a 'SetMultiViewOverlay' shortcut using the 'Dynamic1' value to supply the input number of the new source.

With the current stable build of Companion, I had to add a 'custom' command, but I believe that the latest beta build has built-in support for dynamic inputs.

On that project, I had 3 live cameras and 4 vMix Calls, so a row of 7 SRC buttons. There were about half-a-dozen Multiviews (PIP with slide, PIP Cam and Call, 2x Calls/Cams, etc), with 1 or 2 (and just one with 3) switchable layers.

Obviously if you have dozens of sources and even more destinations, it's going to get messy !

Most of the time I already have multiple layer changes assigned to a button per speaker according to the show notes, so the SRC/DEST buttons are mostly there for last-minute changes ("Hey it looks like call 4 has a question for call 1, can you put them both in the 2-up ?")

Thanks for the great suggestions. I tried SetMultiViewOverlay, and it works, but I found I needed to use "DynamicInputn" as the index/input value (e.g., 2,DynamicInput1). The online doc does not mention this, but I got lucky with the guess. I think this is a great feature, but I see two drawbacks:
1) There are only 4 dynamic inputs. Not sure how I would use the feature to select 5 or more cameras.
2) The SetDynamicInput shortcut does not take effect immediately on the inputs where it is used. I still need to press the shortcut key that does the SetMultiViewOverlay to actually have it take effect. So, I just can't go plucking a row of keys to quickly observe the effects of each SetDynamicInput. Maybe this should be a feature request.

The SetDynamicInput shortcut works in a similar way to setting & getting a variable in scripting - it allows you to store a value (which camera Input you selected) and then use that value in another command (set the multiview layer to the camera input). So you only need one DynamicInput value to handle all your sources. So DynamicInput1 might be used for your multiview layer switching, leaving the other 3 DynamicInputs free for some other use.

If you want to speed up the process of previewing different cameras in the multiviews, you could setup your shortcuts the other way around - choose the destination first and set DynamicInput1 as the Input number of the multiview, then add a SetMultiViewOverlay shortcut to each source and use Dynamic1 as the value. That way you can hit the button for the multiview layer you want to update, then keep hitting the source buttons (which will keep updating the same multiview) until you are happy with the look.

So yes, it's a 2-step process, but that makes it more flexible than before where, as you said in your first post, you would have needed to setup buttons for all possible combinations or add multiple shortcuts to one button.

Ey Matkeane. How are you?. Could you expand this idea?

I think i understand what you suggest but im not being able to make it work

When i use the the SetDynamicInput1 to store the input value and then give that value to the SetMultiviewOverlay (Index, Dynamic1) it works perfctly.

But im trying to do it, as you said, the other way around. By selecting the destination box first (multiview layer or Index) and then the Input i want on that box.

But im not sure how to set the shortcuts to store the layer and then call back that variable on the SetMultiviewOverlay shortcut.

It seems that its not possible to use that varible (Dynamic1) to modify the Index parameter

I have also tryed to SetDynamicValue ant then transfer the Value to the Index. But it doesn't work neither.

Actually, what im looking for is the folowing way to work:
1-Having the Multiview i want to modify in the preview monitor.
2-Select the Layer i want to change (i call them boxes)
3-Then the Input i want in that layer.

Like a matrix. Destination first. Feed later.

The other way works great but i feel that it is opposite than the usual logic. I just want to improve it a little bit and maybe im not thinking clearly.

Thanks for your time!!

@pablodna:

Yeah, as you'd discovered, using dynamic values doesn't entirely work for DST -> SRC switching because it doesn't seem to be possible to use a DynamicValue to modify an Index parameter, so you can choose which MultiView to update, but not which layer. I guess a workaround would be to use the MoveMultiViewOverlay shortcut when you select the MultiView, so that the layer to be updated always had the same Index, but that might have some unwanted side-effects if you're using merge transitions.

I'm not sure why a DynamicValue can't be used to populate the Index parameter of a shortcut. For example, the other day I was hoping to be able to use a DynamicValue to make deferred selection to a DataSource, so that lower-thirds could be selected at the same time as preparing the next guest call in a multiview, but only calling the DataSourceSelectRow shortcut on the next transition. In the API XML, the DynamicValues seem to be stored as integers, so it seems like it could work - maybe Martin can chime in and explain, or perhaps it's time for another feature request !

What is the best way for me to quickly assign a given camera to one of the layers? I know I could make shortcuts for every possible assignment, but with n cameras and 5 layers that would be n*5 shortcuts and could be more trouble than it's worth. vidmate download instasave

Hi kumar3vineet

If you just want to use your keyboard without using the mouse:

Using SetDynamicInput1 to store the input value and then give that value to the SetMultiviewOverlay (Index, Dynamic1) it works perfctly.
You will need N keys for the inputs and 5 for the Layers, in your case

Example: keys F1-F12
SetDynamicInput1
Value: input nº 1-12

Keys numeric pad 1-5
SetMultiviewOverlay (Index, Dynamic1)
Input: Preview or the composing you want to modify

Bye!

What about if we want to expand the concept.

Look here, at the gif image.

https://github.com/bitfo...yers--multiview-overlays

Using bitfocus companion it seem to be possible to route together Input with multilayer, Layer and input for the specific layer.

In the page the developer of the companion wmix module says that is possible to route an input into a specific layer of a multilyered input.

If you press the buttons you can choose first the box (the multilayered input to modify)
than on the second row you have buttons to select the layer you want to change
and the third row just let you choos the content for that layer....

I'm trying to do the same using the SetMultiViewOverlay - Set Input as Multiview Overlay Layer function
but it is not possible to use dynamicValueX for the "Layer" param, but I can use DynamicInputY for the first Input and "Input to use on Layer" params...

do you have any idea on how could be possible to use a var for the Layer in order to reach that goal using bitfocus companion?