First question is if there are more than one vmix modules for Companion? I think the one I am using is called StudioCoast (sorry, not at my Vmix computer atm so can remember wrong).

This can of course be solved by create a shortcut in vMix, assign a key to it and then make a vMix Keypress command in the companion calling this key.

It works great but one thing I discovered is that there are quite a few shortcut commands from Vmix missing in the companion module.
But still, it would of course be easier to call the commands directly from the companion module.

Anyone know why there are shortcuts missing in companion?

Thanks for a very informative reply!
Is there a list somewhere over how the shortcuts are groupet in the StudioCast module?

Not currently, I'm working on the Wiki for the module to add this sort of info but isn't the highest priority currently. If you browse the actions most of them are obvious by the label so just browse through.

Some functions aren't actions because it would be excessive to add functions that no one really uses, so all of the most commonly used ones are available (what functions are wanted usually comes from the broadcast studios and events we work with, so if it's not natively an action in Companion it's because no on has requested it and none of our studios use it).

For how to use the "Run Custom Command" action, the help icon next to the vMix connection in Companion will open up a help screen with a link to a vMix API reference https://util.dist.dev/vmixapi and how to structure the function to be used within that action.

Feature requests for additional functions to be added can be requested here https://github.com/bitfocus/companion-module-studiocoast-vmix/issues/, but keep in mind we don't bloat the module with every command if only one person uses it, as that's what Run Custom Command is for.

-ReplayPLayLastEventToOutput
-ReplayPlayAllEventsToOutput
-ReplayPlayAllEventsToOutput
-ReplayStopEvents
-ReplayShowHide
-AudioMixerShowHide
These aren't part of the workflows for the productions we work or consult with, so you'd need to use a Custom Command if you wish to use them. If you have a use case for these as opposed to traditional workflows feel free to submit a feature request!

- LoopOn (replay)
- LoopOff (replay)
These are covered by the action "Media - Playback Actions", where there are options for Loop On, Off, or Toggle.

- FullscreenOn
This is covered by the action "Output - Output Functions".

You`re right. May i ask you something else? Is there any way to make a trigger when in a input a layer is on or off (visible or not visible) to do an action?

Also in the events the "time of day" can be multiple in same trigger? I mean for example i want to do an action at 19.30 and same action at 22.00? Do i have to do 2 different triggers for this? or if i do 2 events in same trigger it will be ok?

Also for the value if condition is true -->do an action and if condition is false do an action can be in the same trigger? For example i want when in a vmix list input the selected index is 4 to toggle a layer on and when the selected index is 5 to toggle the layer off. Is possible this,under the same trigger?

Is there a trigger "master program remaining" so it do something when a video in mix1 remain x time?

And also is there a way to enter the delay in hours-minutes-seconds and the program to transform it in the needed milliseconds?

Hi, I know a lot of people here use Companion for controlling vMix with a Streamdeck, so I wanted to get some feedback/suggestions for an overhaul of the module that I'm currently working on as it is somewhat out of date currently. For Companion 2 this will be backwards compatible, there should not be any breaking changes to any existing buttons you have set up to work with vMix.

Here are some quick previews of what the version of will include:

Updated Preview/Program feedback, as well as a new feedback that displays time remaining on a video input (with options to change colour when less than 30s remaining, 10s remaining, or not change if set to loop)
Tally.png (25kb) downloaded 61 time(s).

Feedbacks and actions for mixes 2 to 4 that were added in vMix 23. One thing to note though is that mix 2 to 4 doesn't support CutDirect, so if you use the program buttons to do a hot take, the preview will follow to what the program was previously, unlike the main mix where you can CutDirect to any input and it wont change what is being previewed.
Mix.png (25kb) downloaded 31 time(s).

Feedback and actions for toggling vMix functionality, such as recording, external etc...
Status.png (23kb) downloaded 32 time(s).

Feedback and actions for input/bus muting and solo, and for input routing (bus routing has no feedback, for example the API has no way to show if Bus A to G is or isn't routed to Master, or another bus)
Audio Routing.png (23kb) downloaded 18 time(s).

Feedback for titles. This means you can easily see what a lower third, or any text will be, right on your Streamdeck. This also means you can use it for countdowns!
Titles.png (22kb) downloaded 27 time(s).


As well as what I've shown here, I've also added some more commonly used actions, an interactive cheat sheet that's a full list of functions/params so if a function isn't include in Companion you can quickly an easily copy/paste it as a custom command or HTTP request.

If anyone has any suggestions, feedback, or things they would like to see in this then please let me know, as depending on how the final few bits I'm working on goes, and testing, I plan for this to be pulled to Companion in the next few weeks.