Thanks Ice. Yes, sorry, its always hard to get a workflow across.
At present I have two Skype PCs. Video is captured via NDI. I'm bringing audio in via a Behringer x18 mixer, using Behringers ASIO driver. So Skype audio is there as separate inputs giving me a lot of flexibility.
What I do is add the Skype audio inputs to each video input where I want to hear it - studio cameras, graphics, Skype full screen shots, side by side shots etc, and not to others, mainly video clips, opening & closing titles etc, and then automix it so that I don't need to worry about accidental open mics. (It has happened ...)
In addition, I have buttons on my midi controller which use shortcuts to manually mute Skype audio. This is mainly so that when I am not speaking to a particular guest, I can mute their fidgeting and paper rustling. In this case, when I mute a Skype audio input, I have to also switch off auto mix for that input, so that when I switch back and forth between shots, the Skype call mute setting is respected. So the midi button toggles on/off audio and on/off automix simultaneously for that Skype audio input.
If it is not possible with vMix Call to split the audio onto a separate (audio only) input, then what could I do to replicate this behaviour?
I could switch off automix for all taking head inputs, and use triggers to mute all the necessary audio channels when, for example, I'm playing a video clip. But as far as I can see, my only option for when I want to switch away from the video clip again, is to use triggers to unmute all talking head inputs, including any I want to keep muted.
The way I have things set up now, I don't need to rely on guests managing background noise, or managing their own muting (they inevitably forget to unmute before speaking), and I can still make programmes when I don't have anyone to help on the production side.
vMix Call would allow us to have guests jump on without having someone to manage Skype calls, but what I don't want is someone joining a programme for a particular segment and, intentionally or not, disrupting someone else's flow.
@cruiseweekTV - sorry for hijacking your thread, but I think the issue is related ...
Mike.