thedist
commented
1 year ago The instance variables input_X_meterf1 and input_X_meterf2, where X is the input name, number, or key, should return the dB of the meters for each input, even if the audio isn't live.
From that instance variable it's possible to have triggers to light up buttons or trigger functions or anything of that nature should you need.
Is this a feature relevant to companion itself, and not a module?
Is there an existing issue for this?
Describe the feature
I would like to suggest an enhancement of the Input live dB value feedback function. At present it only works with an input when audio is routed to both channels of the master bus and post fade. It would be great if this could have an option of metering pre fade input regardless of whether it was routed to any bus so it shows the presence of a signal. Also in its' present state it would be good if it metered routing to either L or R of the master bus rather than having to be routed to both before registering as it currently is. Would also be great to add a peak hold time so it stays lit for x number of seconds (see usecase below).
Usecases
I use some inputs as comms channels for remote presenter, remote cam op, remote floor managers etc. I then use companion as push to talk to each of those channels. Incoming comms from all those is routed pre fade to a vmix bus (it is removed from master in the audio matrix for safety, as a result it only meters pre-fade on the input). That bus then goes to a USB speaker. Having the ability to meter each input pre fade and have a peak hold would give instant visual feedback of which person just spoke making it much quicker to press the correct talkback button on the streamdeck. I looked at using the Bus live dB value function but of course that illuminates all the keys as the inputs all go to one bus for the speaker output.