Hello together

I wanted to ask if there is a way to de-embed separately the audio channels of cameras in the vmix. We would like to control the audio separately for our larger productions and leave this work to a sound engineer.

Of course, there would also be the option to de-embed any audio signal beforehand, but a solution in vmix would be much more elegant.

At the moment I have looked around if there is a VST plugin which translates the signal to Dante. So far I haven't found it.

An internal plugin or a possibility to de-embed the signals and convert them into Dante would be great.

Best
Jan

Yes, I already do that, but the outputs are limited to bus A maximum 2 channels and bus B maximum 2 channels. But if I have e.g. 7 cameras, this system doesn't open anymore. In addition, I use bus A and bus B differently than the de-embedding of the cameras.

what elgarf said should work if your cameras are on the network if they're on hdmi then try getting them on the network (have you seen the adapters for the soundcard?) or send to a mixer and then put the mixer on the network?

Thanks for your answers. It is a pity to use additional resources like a separate computer for this purpose if it could be de-embedded much easier in the existing system.

@Barney Box Lane - As soon as the cameras enter the vMix as SDI sources, every source is available as NDI. In this case the Studio Monitor in combination with DanteVia might work on another system, but external resources e.g. another PC system are required.
Edit: I tried out. Only one export to DanteVia from Studio Monitor is possible. Multiple instances of the Studio Monitor on the same PC cannot be converted to DanteVia.

My main concern is to solve such "simple" processes as centrally as possible. I much prefer to outsource other ressources to other systems. For example, streaming, multicorder or slomo.

Maybe this could be a future feature. ;)

Again. I think it's much easier without much effort. I have a magewell 4ch SDI card and each input is visible in VIA. With the "enable Dante" switch each input is available on the network.

I'll show you a live demo today, July 5th, 4pm UTC at my facebook (mavikav), youtube (https://www.youtube.com/channel/UCYOVBlgfc2heMW6M-YIDInQ) and twitter (@mavikstreaming) accounts.

No worries, the restreaming failed anyway. Here is a recording available. Enjoy.

This may not be a direct answer to your requirement however the following helped me to run fixed installation mostly unattended for nearly two years now without a blimp.

Time source: network scast, ucast or mcast in theory should not depend on the time sync. Since my audio is independent from video – stitching was failing altogether with lip-sync. This was quite visible across multiple cameras where audio was ahead or behind a video capture. Days of pocket captures using wireshark provided a clue. Long story short – added stratum 1 NTP clock to my infrastructure using a raspberry PI with two independent GPS modules. From dealing with tens of seconds of delays it helped me to reduce the jitter to tens of milliseconds.

Network switching: congestion as apparent as it seem is not always easy to assess. Using network broadcast isolation approach with help of segmenting vlans reduced underlying network chatter to the absolute “need-to-know-basis” between devices.

Network switching capacity: no secret here – more sources and overall data traversing your network – longer it takes for a switch to process. The final solution was a hardware segmentation, where video streams landed on one switch, dante with fall-back on another two, WIFi and all production non related yet on another. Management headache, not to mention contention between switches. Obvious choice was to move to the fully managed fiber stack. Current setup 10GB fiber between switches (stacked) and to all video production systems.

Dante: with all above current peak latency reported by the Dante Controller is at 0.375 ms. Using mixture of the ASIO, hardware, AVIO sources and destinations uni and multicast, altogether 15 devices with quite extensive routing. Moved completely to dante as the audio delivery layer.

Decoupling audio from video: “Tried that, been there, now I want a t-shirt”. What worked for me was to discard audio from cameras and used dedicated microphones setup connected to the X-32 rack furnished with the dante interface. Sound engineer has his full freedom with what to do with the sound, using mixer’s capabilities and additional digital snakes. Actually there are two sets of X-32 – one fixed setup and another one for the stage gigs where sound is distributed using ultranet.

Vmix production: Video from sources and stitched sound from X-32 master channels with dante ASIO sources. Audio and video thanks to the stratum NTP stays solid 17ms apart and this much audio is delayed in Vmix directly.

Andy