Hi
still trying to find solutions for easy switching inside multiviews, virtual sets or external2 out as explained in a previous feature request concerning the creation of a new AUX/MATRIX input type. See :
https://forums.vmix.com/....aspx?g=posts&t=8622SetMultiviewOverlay is a great help to do it, but it requires a lot of shortcuts/activators. Using it with 6 inputs to manipulate 3 overlays in a single multiview requires 18 buttons! Now that we have 10 possible overlays in multiviews, we will soon need 512 buttons on midi devices if we want to trigger everything. My Akai APC Mini is already too small to handle all possible combinations for 6 inputs and 2 multiviews (+ obvious preview/pgm/overlays/PiP switches for sure)!
Last night I was playing with the "Hover" command and it came to my mind that this principle of hovering inputs could be very handy for sub-switching inside multiviews/virtualsets if we had a "HOVER TO" or "SWITCH TO" command.
Let me explain:
Hover works like this > you place your mouse over an input - input1 e.g. - and when you trigger the hover command, it sends a pre-defined input as an overlay into input1
The command is like this :
Code:?Function=Hover&Input={mouse-hovered-input}&Value=1,2
(where 1 is the overlay and 2 the input to insert)
If we could have a Hover-To/Switch-To command, it could work like this :
- Press a button that activates the Hover-To mode for a defined overlay inside a defined multiview
- Position your mouse over an input and release the button
> the overlay input in my multiview is replaced by new one
So for Multiview=input7, if I want to switch input for overlay1, command would be like this:
Code:?Function=Hover-To&Input=7&Value=1,{mouse-hovered-input}
For a 3 overlay multiview and 6 possible inputs, it would require only 3 buttons to do that when it requires 18 buttons right now!
Ideal would be if mouse hover could also be an input select either from an external controller or a mouse click. In fact, this Hover-To command would need to be pressed (midi on), kept pressed until an input is selected and command sent on midi off (if we use a midi controller for example). So maybe the name "Hover-To" is not ideal, as mouse hovering is not the preferred method, but having a mode activation that waits for input selection is more what I'd like to see in vMix.
Same principle could be used for VirtualSets and External2.
Hope you'll like the idea. It could open a lot of perspectives.
Thanks
Guillaume