One could easily tie a shortcut to the pan/zoom settings to go in increments of move per keystroke on the fly

I believe this would also be a good use of the new dynamic feature in v24 to specify which one of the inputs the shortcut would apply
Yes it applies to the input ( or a virtual one) and depends on how you "designed" the multiview layout (masking or so) but IMO the layout would be preferable be a virtual set with UVmaps ( less issues with the framing, cropping and masking within the layout )

+1

This is a game changer shortcut for all digital event.

In top if that i would love to have :
Set crop
On/off layer number

If Someone has hack for this while waiting for this coming true I'm in.

+1

Hi Peter, here is a work around for up to 3 speakers/cameras using luma masks and panning with keystroke shortcosts (as doggy mentioned).
Instead of cropping your camera inputs, you create a Mask input (white box on a black back ground -2 layers) and output it in a mix input (you have Mix2,3 & 4 available). That mix you assign to you your camera feed as key/fill input.
That way you have a "cropped" camera shot in the shape of the white box you created.
You do this to all 3 camera inputs and then assign them in your desired position and size as a multiview.

Now you just have to pan the mask input by assigning shortcuts - SetPanX - you can do -0.3/-0.2/-0.1/0/0.1/0.2/0.3 as shortucts which should give you enough flexibility to move around and get the speaker in the center of your shot.
However, when you move the mask input your "cropped" camera input will also move and thus your multiview will be out of position. To counter act that you need to pan your camera input opposite to your mask pan. (e.g. you assign a shortcut key to pan the mask input by 0.1 and that same shortcut key to pan the camera input by -0.1)

And of course you do this with dynamic inputs so that you don't have to use too many shortcuts keys.

This way you avoid going into settings. I am not sure though if this is worth the effort :-)


Hope this helps

Cheers

++1

Let me add to that on MultiView

The motivation is achieving what the Merge transition does, without having to duplicate scenes again and again.

a) all operations in the multiview tab, should have a script-shortcut equivalent. Pan, Zoom, Crop, Border
b) Pan and Zoom should have a combined scripting solution.

For example API.Function("TransformMultiViewOverlay", Input:="The Input Name", Value:="Index,panDx, panDy, newZoomX, newZoomY", duration:="milliseconds")

What will that do?

For the Overlay in Input with the given name and at the given index
- increase the panX by panDx, panY by panDy
- set the newZoomX and newZoomY
- do this transformation in the given time.

This will allow simple animations such as

- move a layer out of the view, replace it with a new input and bring it back in.
- turn of other layers and make fullscreen on of the layers and many more


No need to create additional inputs, scenes etc. Create one scene and move pieces by shortcuts.

Yes i know....maybe this is the wrong post.

What i want to do is to move an Input (SetPanX, SetanY, an SetZoom). Then, that Input is going to be in an Overlay...but thats doesnt matter actually.



This...

But the SetPanX and SetPanY only allows to make statics movements...from one point to another.

Thanks!

...

The implementation I use is a little different, but the TL:DR is:
The "SetPanX" and "SetPanY" calls do allow you to just move by a delta amount, not only the fixed position you enter.


I run vMix on virtual machines in a cloud production environment I'm building for my employer, so my use of StreamDecks is a little different than most. BitFocus Companion is a good substitute for a lot of the local/USB usability for vMix, but our current use is set up to just use HTTP Get calls. So each StreamDeck button is just a "Website" with "GET request in background" checked.

The URLs use the API calls, and sometimes I have to make multi-action buttons to combine some actions [that don't need triggers assigned to vMix Inputs]. The URL's look like this:

http://ip:port/api/?function=OverlayInput4&input=Intro-Revised.mov (Run this Overlay with this Input)
http://ip:port/api/?function=SetMultiViewOverlay&Value=1,56 (Change layer 1 to this Input)

Recently I too have had to setup the "Move Under A Mask With a Mix Input... because of Leaning Talent" (since vMix STILL won't let us add Alpha Masks to individual layers regardless of position... I wouldn't even mind using up layers as Masks, if we could gain that functionality [a simple 'Use layer as mask to adjacent underlayer' checkbox would be great])

The syntax on the URL looks like:


"SetPanX&Value=-=.1&Input=X"

- '&Value='Minus by .1' (this would be "Move Left by .1 amount")
- But URLs use Percent Encoding.. and usually don't like the '+' and '-' characters so these have to be converted, so the final URL actually looks like:

http://ip:port/api/?function=SetPanX&Value=%2D%3D.1&Input=61

The inverse of this to move right (%2D = '+' [Plus]):

http://ip:port/api/?function=SetPanX&Value=%2B%3D.1&Input=61


Key:
%2D = '-'
%2B = '+'
%3D = '='


This also works for Raising Volume by a percentage amount:

http://ip:port/api/?function=SetBusAVolume&Value=%2B%3D4


I'm constantly amazed by what we're able to do with vMix, but I know a lot of us are frustrated by some big issues like:
- 1080p Calls
- Ability to crop masks (I understand computing issues here.. but most of us would be okay with limits "Only able to crop 10 total nested inputs)
- Ability to use a layer as a mask to an adjacent layer would be a complete game changer for most of us.. and it shouldn't add too much computing drain because of the 0 / 100 alpha values and the fact that you can already crop each layer in an input is already there, the mask would just say what pixels are transparent or not... PLEASE LET US EAT LAYERS FOR MASKS!


My rambling is finished, but I hope the Delta Syntax usages above help someone out there!

In the September vMix Fun Time Live Show from IBC, Martin mentioned that more shortcuts will be implemented in vMix 26. I hope that these will be some of them :)

Thx!

+1

Why did you just +1 this? Layer specific shortcuts was one of the major changes added in vMix 27.