Hi !

I have an idea in my head for a long time, I think time has come for me to try to explain it to you, vMix community, to request your support for this potential new feature.

I guess some of you know I try to use shortcuts and the API as much as possible to extend vMix capabilities and split the workflow and responsabilities over multiple computers/people. I also have a little knowledge in coding principles like the use of constants and variables to feed functions dynamically in a program or a script. Thus I came to the conclusion that it would be great to add such capacity to vMix shortcuts and its API.

Because it's difficult for me to explain this to you in english, let's start with an explicit example.

I'm working on a CC module using vMix Panel Builder as a test. I need to provide full CC controls for at least 8 cams, that means around 200 widgets (sliders, buttons, etc) for all CC commands... It's a lot of buttons, takes a lot of space and it's pretty stupid in fact 'cos it's not possible to use controls for the 8 inputs at the same time but it's rather one after another. That's also the reason I can't plan to use a Midi controller or X-Keys for this task. It would require far too much buttons and faders...

So obviously if we could use variables or dynamic inputs, it would be possible to first select an input number, set it as a variable and make the function buttons use this variable to be mapped to the pre-chosen input number.

Here's how I can think of this potential implementation in vMix

- Add a command "SetDynamicInput"
- Add this "DynamicInput" entry in the list of special inputs (next to ActiveInput/PreviewInput) in order to be selected in shortcuts, triggers, scripts and thirdparty applications like UTC and VPB.

Best would even be to have several (maybe 5 ?) Dynamic Inputs to be used simultaneously for different things: SetDynamicInput1, SetDynamicInput2, ..., SetDynamicInput5

Check the image below that shows how easy it would be to replace 200 buttons and widgets by just an input selector (here for 8 cams = 8 buttons) and the appropriate commands (only 25 widgets/buttons).
Each input button (on top) would set this Dynamic Input variable so that vMix would store it in its memory and make it available to the API > DynamicInput1 = GUID
Then each function widget would use this "DynamicInput1" as the input target for the command to be executed.

cc-module.jpg (207kb) downloaded 26 time(s).

I think it's enough explanation to get the general idea and the overall potential...

If I'm thinking right, I believe we need 3 types of variables/dynamic entries in vMix:
- Input Variables (DynamicInput1-5) to dynamically map inputs to functions
- Function Variables (DynamicFunction1-5) to dynamically map functions to shortcuts/buttons/widgets (a single button can be used for multiple purposes, like the AUTO button in traditional control panels for example)
- Numeric Variables (DynamicValue1-5) to dynamically set numeric values to functions (durations, overlay indexes, etc...)

I have started to think about this long ago and see a lot of potential use cases. Main advantage would be to drastically reduce the number of shortcuts/buttons/widgets required when using Midi controllers, X-Keys, third-party apps, as well as any code driven logic, externally or even in internal scripts. The use of constants and variables is the very base of any programming language when it comes to feed functions, which is exactly how vMix works internally... Unfortunately so far vMix functions are only static for us...

I also believe this Feature Request could be an answer for another Feature Request that many of us support : the one about MODIFIERS (use of CTRL, SHIFT, etc...). > a single button could be used for multiple commands.

If you use shortcuts or scripts in vMix, if you use Midi or X-Keys controllers or Skaarhoj devices, if you use third-party softwares like UTC or Panel Builder or Android/iOS apps like Seth's vMix Virtual Control Surface for Ipad, I truly believe this feature can be a game changer for so many things in Vmix. So please, give it full support with your +1. (I also accept +100 and +1000!)

And feel free to ask any questions for more explanations or details. I know it seems a little technical at first view, but it's very simple in fact!

Thanks!

Bien à vous
Guillaume, aka DWAM

Exactly! That's also how most (like BMD, Roland, Ross, etc...) switchers and control panels work when it comes to assigning specific media or functions to buttons.
For example, the AUTO button in ATEM switchers can be assigned any transition effects.

The last thing is already possible.

You get all inputs and their keys from 127.0.0.1:8088/api

Your "Dynamic Transition Selector" should save selected transition in variable. When you press "auto" use Fader etc. you recall Web API with that variable:
127.0.0.1:8088/API/?Function=SelectedDynamicTransition&Input=21b32e53-a4e4-4eb4-970a-4a2bd2548f21&Duration=500

No idea about how to implement it in Panel Builder. In my own software, it's easy

+1

Hello BETech,

For the request about the shortcut to open the input settings window I have already started a feature request some time ago.
Please +1 there.
Shortcut Input settings

To be perfectly clear (for those who don't read carefully), this FR is about vMix SHORTCUTS !!!

I only illustrated it with Panel Builder 'cos it's VISUALLY EXPLICIT (at least more than internal shortcuts used with keys on my keyboard)

I don't shut down FR Yannick. I may express a negative "opinion" sometimes but most of the times, I just try to indicate alternate ways to achieve the same results.

What your suggesting here is not really a workaround as it relies on a specific equipment and it only answer partially to the overall scope I'm trying to cover here. My point is to bring this feature to vMix for the benefit of the ENTIRE ecosystem. If you can do this with a basic keyboard with simple shortcuts or internally with triggers, it's not the same thing as controlling it from YOUR midi controller. However YOUR midi controller could use it too. Does your Midi Controller improves in any way how a trigger can work in vMix ? I guess not...

+1 +1 +1

Yes Yannick, you can do this with 3rd Party apps (I use Ross Dashboard for my work).

But DWAM suggestion is very powerful, because you could use this with just the scripts built in to vMix. All of my shortcuts are now powered by scripts.

It would be a way easier way to use hardware devices without the "man in the middle".

This would be AWESOME.

Steve

I like it +1

Thank you for your support Ross. You’re close but it’s even much simpler than that

With the very same use case : a CC module, with the CC interface I provided as an illustration for (it’s just an example)

On top you have 8 cams inputs > these are used with the SetDynamicInput1 function
Below are the CC controls > these use DynamicInput1 as the input number

Step one
- press any CAM Input, 3 for example > ?function=SetDynamicInput1&Value=3 (or GUID)
- now DynamicInput1 = Input 3 GUID. I know it and vMix knows it

Step two
- all the CC widgets are set to use DynamicInput1 as a target (instead of a pre-determined input number)
- if I move the Hue slider, it sends ?function=SetCCHue&Input=DynamicInput1&Value=0.36
- vMix gets the request and knows that DynamicInput1 is Input 3, so Hue for Input 3 is adjusted

That’s it!

Now if I select Cam5 input on top, DynamicInput1 will become Input 5 and any of the CC controls will trigger the appropriate CC command for Input 5 in vMix. And so on…

This illustrates how the DynamicInput variable works

For SetDynamicFunction/DynamicFunction, it’s the same principle but for Functions, not Inputs.

A simple use case would be when a single button can send different commands. This is quite what I illustrated in my second post in the thread for Transitions (I could have used an AUTO button too but with my principle it’s useless)

So we have a Transition Selector on the right side, this is Step 1 (using for example DynamicFunction3)
- by clicking any transition button, it sets the Function variable. If I click “Slide” it sends: ?Function=SetDynamicFunction3&Value=Slide
I know now that DynamicFunction3 = Slide. vMix knows it too. It’s set.

Step 2
- The Program row uses DynamicFunction3 as the command function for all buttons with regular input numbers
- If I switch to CAM4, it sends to vMix > ?function=DynamicFunction3&Input=4
- vMix gets the request, it knows that DynamicFunction3 is set for Slide so it slides Input4 to PGM

Step3
- Now I click CUT in the Transition Selector, DynamicTransition3 becomes CUT
- If I press CAM1, vMix will CUT to CAM1
And so on…

You see it’s real simple !