Make sure you have updated to the latest version of the module
Is there an existing issue for this?
Describe the feature
While building a button layout in Companion, I needed to mute individual audio inputs on the TriCaster. The module doesn't currently expose this as a named action, but the following shortcut strings work correctly via the existing Send Custom Shortcut action:
Mute/unmute a specific input:
shortcut?name=input1_mute&value=true
shortcut?name=input1_mute&value=false
Replace 1 with the input number (input2_mute, input3_mute, etc.)
Set input volume (0–100):
shortcut?name=input1_volume&value=50
These were confirmed working on a TC2 running Companion 4.2.
Usecases
It would be great to have a proper named action for this — something like "Mute Audio Input" with a dropdown for input number and a toggle for mute state, similar to how other module actions are structured. This would make it discoverable without needing to know the raw shortcut string.
Make sure you have updated to the latest version of the module
Is there an existing issue for this?
Describe the feature
While building a button layout in Companion, I needed to mute individual audio inputs on the TriCaster. The module doesn't currently expose this as a named action, but the following shortcut strings work correctly via the existing Send Custom Shortcut action:
Mute/unmute a specific input:
Replace 1 with the input number (input2_mute, input3_mute, etc.)
Set input volume (0–100):
shortcut?name=input1_volume&value=50These were confirmed working on a TC2 running Companion 4.2.
Usecases
It would be great to have a proper named action for this — something like "Mute Audio Input" with a dropdown for input number and a toggle for mute state, similar to how other module actions are structured. This would make it discoverable without needing to know the raw shortcut string.