Multiconference setup unachievable


I’m writing this post to address an issue we’ve encountered. We’re currently unable to patch multiple clients into an ADR Session and enable communication between them via group tracks, as we can effortlessly do in Pro Tools using aux sends. I suspect that there may be a feature blocking any routing that could be perceived as a feedback loop.

Some background on the setup: We have the actor in the booth on our end recording the ADR. We’re linking up with external studios via Source Connect Pro using a group track, which works great. However, when our client requested to include the director via Zoom, we set up another group track to pipe in the required audio streams using Source Nexus. The feedback loop prevention prevents us from connecting the Zoom client with Source Connect Pro, even though this setup wouldn’t result in feedback because both plugins on these groups send audio out of Nuendo and only play back what the clients are sending back through.

I’m aware that this issue could be resolved by creating a convoluted method of sending audio out to my desk and patching it back in. However, this seems like a cumbersome workaround when it would make more sense to simply allow loops with the check of a setting. Considering all the amazing features Nuendo offers for ADR and audio post-production, it seems like an oversight not to include this feature, especially when multi-conference routing is so common in this space now.

So, I’m reaching out to ask if anyone has found a better workaround or if there’s a feature request we could make.


1 Like

I’ve only used SC on PT and it was a while back so I can’t really offer much other than looking into patching outputs ‘dead’ on Group tracks, if possible, and then maybe using sends or something to get around the problem.

If you’re on Windows and your audio interface is multi-client capable you could set up using something like VB-Audio’s mixer app. That’s how I’ve done Zoom reviews from home on my computer. VB’s mixer app receives Nuendo via an interface internal software mixer “return” to the computer and sends that to the client. Incoming Zoom audio goes directly to my speakers via VB mixer. Technically I should be able to route that back via the interface so it comes back into Nuendo (I never had the need to do that).

Anyway, the point of that workaround is that at least if you could do it that way you should be able to have it all routed in software and recallable with a few presets.

1 Like


We do this with a second sound card in the recording computer which is only responsible for the web clients (Sessionlink or Zoom, Teams etc).
We also have an old RME Fireface400 running on the Win11 Studio computer. This is registered as a system card and out1+2 goes to any input port of the Asio recording card and is routed to an audio channel (Mutomatic inserted - is a VST plugin from Sound Radix) and switched to monitoring. As a return path, we simply set up a cue path in the control room exclusively for the signal to the WebClient and connect this to Input 1+2 of the RME. This ensures that you are always independent. (and you can still use the old sound cards) We (Germany) have already done ADR sessions with 6 Zoom clients (in the UK) at the same time and it worked great.
By the way, both sound cards are installed in the same computer!
It works better than all the software tools we have tested.
The use of multi-client drivers (Asio+WDM simultaneously) under Windows did not work well. There were often problems with it.
Maybe this is a suggestion …

Greetings Michael

1 Like

Thanks for taking the time to reply and sharing how you would solve this issue.

I had a feeling that many users would be using some form of internal or external loopback routing. Our current fix is to use a second instance of Source Nexus VST on the Source Connect group and put this in pass-through mode. We then use the same send that is on Source Nexus VST in the Zoom group as a hacky send workaround.
This works, but it would be nice if Nuendo acknowledged this and allowed users to do the routing internally without the use of third-party hardware or software.