I would say, rather than being able to add 'shortcuts-inputs', it would be best to work on the already existing shortcuts window in the software.
Adding the behaviour of a shortcut would probably create a lot of confusion; like adding null inputs that act as shortcuts, and in the end clutter the interface as well as occupying precious input slots for basic users.

Instead, reworking the shortcut window so that it can integrate in the interface as the audio mixer does, adding the ability to color, rename and reorganize the virtual buttons, and maybe even have multipe shortcuts in one button would probably be best. It could even integrate an equivalent to the activators mechanics and work like a complete virtual controller embeded in vmix's interface, but separate to the inputs.

If I understood well, I guess you can already do this using vMix Web Controller (http://yourPC:8088) where there is a page that shows all configured shortcuts as big buttons.
http://www.vmix.com/help18/WebController.html

Guillaume

Thank you for all the comments!

The begin with, my guess is that adding a shortcut selection to the click behavior drop down menu would need very little programming efforts. A nice addition that opens up many possibilities.

Perhaps the main advantage with soft shortcuts is that the Input's preview monitor may show a live representation. Very intiutive! Imagine that you have a MultiView Input, and the soft key Inputs control which camera should occupy one of the PiPs. Or you select which input goes to Fullscreen just by clicking/touching it.

While I agree with User4365,and Harty that reworking the shortcut window would be nice, that would imply relatively much programming efforts. And I am afraid that alternative control surfaces, including midi, x-keys, tablets, web controllers, etc, already provides a good range of options.

With respect to screen cluttering, I am also considering "walk packs" (compare flight packs). Read, one wants to keep everyting on one (1) sceen. There are cases where you have a tripod with a camera and a touch screen (laptop) mounted on it for vMix control. No room for extra controllers (eg midi), monitors (for floating control windows), keyboards, etc. We tend to end up with hardware cluttering ;). And I guess we are not alone that having many presets that currently only contain five Inputs, and a bunch of shortcuts controlled via the keyboard. In other words, lots of available screen estate without risking cluttering.

Would love to see some comments too on the ideas about "virtual shortcuts" and "named shortcuts".

Keep'em coming :)

Hi Richard

I found a way to do what you wish (and part of what I wish) using NDI. So it is not a vMix only solution but it helps.

Martin from zenVideo.co.uk was kind enough to let me experiment his new NDI app called NDIRouter.
http://zenvideo.co.uk/ndi.htm#Router

Basically it's a NDI Video Hub with 6 in and 2 out

It works very well for many use cases. I used it as a turnaround (for my sub-group virtual input feature request) to build switchable dynamic multiviews.

I set my 6 inputs in NDIRouter and create my multiview.
NDIRouter Out1 and NDIRouter out2 can feed 2 out all the inputs in the multiview
So I can send any of the 6 inputs anytime in the multiview with a single click

Unfortunately it cannot be routed within vMix to External but for multiview usage only it is quite a perfect solution.

@DWAM
Thanks. I am already aware of ZEN's NDI Router, but I am after a what I believe is an easily implemented function that would require no extra h/w (midi-controller, X-keys, switches, u name it). Think it would open up a range of possibilites. Consider those who use not-so-well-trained-operators (eg students for a soccer game). Create an Input with an image (or even better a Thumbnail) that reads "START" and starts the Recorder, Streamer, and Fullscreen. Can't do that with NDI.

@IceStream
What You Saw Was What I Did. No right-click action. Just live touching on the Input's preview :)
I thought that it would be a nice can't-go-to-sleep excercise for other users to figure out how I did it :)

Aaargh Ice, you spoiled it ;)

Or rather, nailed the trick :) But I do not see it as a workaround/solution because of two reasons. First, that hack uses one Overlay for each Input, rendering the Ovarlay/s usesless for its real purpose. Second, and here I think I failed to describe my request properly. Let me elaborate that.

My idea is that the Mouse click action should be able to initiate a "simulated key stroke". That is, not execute a Shortcut command, but rather do the same thing as if the user press a key. For example key "1", which is in the default keyboard template does a Fade Preview (1s). And, more important, can initiate a sequence of shortcut commands, as "1" (or any other key) could be set up to execute multiple shortcuts.

So, the drop down menu for the Input's Click key action should include keys as defined in the Settings/Shortcuts tab. Perhaps there should also be an option for each key to "Show in Click Actions" (compare current "Show in Web Controller).

Then, over to my related idea. Instead of being limited to keyboard keys, it would be nice to have "Virtual keys". Perhaps in its own tab next to All, Keyboard, MIDI, Surface, Shuttle PRO, and Joystick. The Virtual keys should be identified by user defined names. Hence the idea of named shortcuts.

Finally, regarding Matrix/AUX switching vs Click action ("Soft") shortcuts. I would rather say that the latter could solve some of the requests within the former - but not the other way around. Take a look at the different Shortcut Functions, a minority of these are switching related. And as I mention in the demo video, another request concerns a new graphical interface full Floating Windows. If the Input tabs in the future would become dockable, then that and Soft shortcuts would perhaps be a viable path instead of a matrix layout. (Better to discuss further in DWAM's topic).

@ richardgatarski

I agree Richard, the "end result" gives the desired "effect" but not the desired "behavior", that is to be able to switch within the "MultiView", and hence why I like the idea of adding such options to the "Mouse Click Action" menu and "Shortcuts" in general.
As I suggested earlier, I'd be open to the idea of "bigger" buttons, I'm just not so sure how that can be accomplished. As I reflect on it, though, adding them as a "specialized" Button Input (not selectable as a "program" Input), I see the merits of your request for touch screen Users, you could theoretically design your own custom "Control Surface" right within the main vMix GUI.
In that respect, I think it's worth discussing further and I'll give it a

+ 1


Ice