+ 1

I fully understand the request and support it if it is possible.
In the meantime...

@ Cpilcher

There is a workaround solution. You can use the "MultiView" feature a couple of different ways either with the audio input as an overlay (better I believe) or a camera input as an overlay on that audio input.

Either way, it may require multiple 'duplicate' inputs and/or shortcuts to accomplish your goals, but it works!

The "Overlay" buttons will work as well, but they will not turn ON the audio, you would have to do that manually.


Ice

@ Cpilcher

Although I don't fully know your workflow, I do understand the situation.

If you or someone other than your TD (Switcher) is controlling the On/Off aspect of the commentators, I would suggest a series of duplicate 'Shortcuts' that will alter the "Overlay" input of each "MultiView" (camera angle) you are using, one key for ON and one key for OFF, that is use the "SetMultiViewOverlay" function such that the value is 'Overlay#,Input#'.
Example: if you are using 'Overlay' 1 in the 'Multiview' of your camera input and your audio is 'Input' 24, the Value in the function window is "1,24".
To "Turn Off" use "0" as the value for the Input Number (i.e. None), in this case the Value for Off would be "1,0".

In this way, your TD can switch normally, your Audio guy can turn Audio Inputs On and Off and your talent will see the Web Tally indicator (I assume a smart phone or tablet).
Not the simplest of set-ups, but certainly doable.

Hope that makes sense and helps.


Ice

Ok, I'm so close but I am having a few problems.

1. I am starting with a blank project with 2 inputs. 1 input is my camera input, and input 2 is my overlay (I have been using a stock vMix lower 3rd also to test this visually).

2. I have created 2 shortcuts.

SHORTCUT 1 "ON"
- Key: A
- Function: SetMultiViewOverlay
- Input: Input 1
- Value: 1,2

SHORTCUT 2 "OFF"
- Key: S
- Function: SetMultiViewOverlay
- Input: Input 1
- Value: 1,_ (I have left the second value blank as "0" did not remove the Input from Overlay, but leaving it blank did...)

Onscreen everything works as expected, but the web controller does not update the tally light (iPad mini 3). Clicking the input will make the tally show the correct status, but it doesn't seem to update the status until the input is clicked. Also in my setup I have the option for clicking input set to "NONE" since the xKeys controls that aspect. So on my production PC that wont be an option.

EDITED: Secondly, if I swap the lower 3rd for an audio input (which is what I need to work in the first place) it always plays my audio regardless of the overlay status. Audio inputs must always be live? is there a way to have the audio follow focus like a camera input, where audio is only heard when the input is actually active? I could probably duplicate the shortcut to also turn off and on the audio, as well as set the MultiView Overlay...

Thanks so much for getting me in this far, hopefully it will pan out.

Chuck

@ Cpilcher

I haven't re-read the entire thread and can't remember fully the workflow, but perhaps a "Virtual Input" of each of your camera shots with commentator's audio (double the switching for the TD for ON and OFF situations, but with all the keys available to you on the X-Keys, should be do-able).
One bus of keys for Audio ON and one Bus for Audio OFF, that should trigger the web controller tally effectively.
Switching between busses on the same Input shows no visual change, just the commentators audio is the only difference.
(as it would appear you have to switch away from the Input to disengage the tally indicator)

Ice

OK. So a very simple way to do the above is to use the Web Controller. Setup a shortcut to turn the audio on/off and make that the only shortcut that is visible in the Web Controller. Now from a device at the commentary position, perhaps a tablet or laptop---even a smartphone, browse to the Web Controller. The commentators will only have the one button to push! To see the tally open another browser window to the same address and expose the web tally light. It works extremely well. I do it a bit differently in that I have the TD turn off the audio, but I use the web tally light so that the commentators know when they are live. And it's a great use of those old smart phones that are in your bottom drawer that you never got around to recycling! LOL

@ Cpilcher

Unfortunately, until the feature request of "Tally" association with Audio ON/OFF is fulfilled, there is no simple "ONE" button solution to this...
And it's not exactly what one would desire as it may require a multitude of shortcuts and only be quasi productive.
I can effectively establish "Shortcuts" to turn the Audio ON and OFF (giving the Commentators full control) and subsequently set-up advanced triggers associated with each ON and OFF button to "SetMultiViewOverlay" of desired Cameras to the Audio Input (Tally ON) or Colour (Tally OFF), but the issue remains that the Tally indicator screen will not change until the Camera (Input) is switched in vMix by the TD, so the scenario is not fool proof (i.e. Tally could show ON when Audio is OFF and vise versa, until camera is switched) but at least it provides some semblance of what you want to accomplish.

Perhaps the best solution is to disregard the "Web Controller Tally" and focus on a "lighted" key pad midi controller or fader that the commentators have at their disposal to control, basically, their own ON/OFF switch.


Ice

@Admin. Martin, if the trigger for tally is the transition of an input into Program, would it be possible to also create a trigger on the ON/OFF of the Audio of any input and/or the Master Audio?

My final solution after a long nights work (until the XKeys arrives) is to run desktop capture and crop out the audio indicator light/button from the input. Using multiview settings I have included those 2 screen caps on my overlay 4 channel which is hidden on all but my external 2 feed (which only Commentary can view).

II have modified an old numpad so there are only 2 buttons visible at their stations (which until now have been XLR "cough switches" to mute the feed if they needed to).

I was able to also rework my time clock so it doesn't require the use of an overlay channel as well so now I have enough to feed my graphics too.

EDIT: The local Guitar Center had an Akai LPD8. It is responding to the activators using the generic button led setting. So I'm going to use that until I find a better button solution.

Chuck