Rank: Member
Groups: Registered
Joined: 5/19/2021(UTC) Posts: 14  Thanks: 1 times
|
We are running Central Control Studio v4.2.0.3 with a Stream Deck XL. We need to poll the vMix API for feedback on the state of specific functions in the vMix APi. For example, if SetHeadphoneVolume=0, then we want a Stream Deck button to be red (muted), if not, then black.
How do we do this?
|
|
|
|
|
|
Rank: Member
Groups: Registered
Joined: 6/23/2017(UTC) Posts: 29  Was thanked: 10 time(s) in 6 post(s)
|
This should be possible using the Virtual Faders module. See this video:
|
|
|
|
|
|
Rank: Member
Groups: Registered
Joined: 5/19/2021(UTC) Posts: 14 Thanks: 1 times
|
Thanks, Joe. I've watched this video, however, I'm still unclear on how to connect all of the 'device dots' to make this work. Any additional help you can offer would be greatly appreciated. Here's the basic step I've got so far: StreamDeck XL CC device > Control > Button 5: vMix Execute Function - Function: SetHeadphoneVolume
- Value: 0
- Input: (blank)
StreamDeck XL CC device > Control > Button 13: vMix Execute Function - Function: SetHeadphoneVolume
- Value: 100
- Input: (blank)
This works just fine...When I press Button 5 on the StreamDeck, the headphones are muted in vMix I would expect. When I press Button 13 on the StreamDeck, the headphones are unmuted in vMix as I would expect. Now I need to turn the StreamDeck Button 5 Red and Button 13 Black when muted (Value: 0) and Button 5 Black and Button 13 Red when unmuted (Value equal to 100). Somewhere I'm missing something conceptual and practical in how to use the Virtual Fader CC device to accomplish this. I'm stuck. Anything additional you can offer would be a big help and much appreciated. Originally Posted by: joedemax  This should be possible using the Virtual Faders module. See this video:
|
|
|
|
|
|
Rank: Newbie
Groups: Registered
Joined: 3/12/2026(UTC) Posts: 4   Location: x
|
The part you're missing is that the **Virtual Fader doesn't automatically know the value of `SetHeadphoneVolume`**.
Your two buttons already **send commands** to vMix correctly, but changing a button's color requires **feedback** from vMix. In other words, CCS needs to monitor the current headphone volume and update a variable or Virtual Fader based on that value.
Conceptually, the flow looks like this:
```
vMix XML API
↓
Virtual Fader (current headphone volume)
↓
Button feedback / color
```
The button itself doesn't know whether the headphones are muted or not—it only sends the command. Something else has to continuously read the value from vMix and drive the button state.
If the Virtual Fader can be linked to the value returned by the vMix API for the headphone volume, then you should be able to use that fader (or a comparison such as `= 0`) as the button feedback source.
I think the missing piece is not the Execute action, but configuring the Virtual Fader as a feedback source rather than just as a control.
|
|
|
|
|
|
Forum Jump
You cannot post new topics in this forum.
You cannot reply to topics in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.
Important Information:
The vMix Forums uses cookies. By continuing to browse this site, you are agreeing to our use of cookies.
More Details
Close
