I enjoy the recent educative videos you folks at ADAM channel provide, and appreciate the "beyond-our-brand" coverage, with this video though, I don't feel it's well covered topic yet, not all AoIP is Dante, and not all Dante is RedNet, although AES67 standard basically means audio can be routed across various products, their control does not though (for ex. changing gain or toggling phantom on various brands is basically a no go, and can usually be done only from within dedicated app provided by manufacturer), then there's problem of basically nonexistent samplerate conversion, as far as I know only workaround is to get 2 RedNet MADI interfaces and hook them together via MADI with SRC in order to provide same stream of two different samplerates in Dante network; on top of that sync needs to be precise and older devices with PTP won't go well on PTPv2 clocked network etc.. then there's problematic of Unicast/Multicast, which basically means you set a live gig and in last minute if you decide to add another console, you basically need to shutdown and relaunch+reconfigure entire Dante network, similarly expanding studio during runtime is not troublefree (unlike plugging regular digital or audio cables/fibres), then there's bandwidth limitation, particularly dangerous for bigger facilities, since 1Gbit can provide 128 channels audio, it's not that much, considering network is supposed to be simultaneously used for everything else like software updates, network storage etc.., I'm surprised it's not explicitly advised to have a completely separate network dedicated for reliable AoIP operation, then there's a problem with AV workflow and its conversion, let's say sending 3Gbit audio+video stream into 1Gbit audio mixer won't really work smooth, and splitting signal before and joining back after console won't work smooth either; speaking of AVoIP, Dante can do now, but so can for ex. NDI, yet they are basically incompatible together.... I'm sure AVoIP is the future, and the leap is as big as it was from analog to digital, but so far there is no "complete" standard to go for; that said, if anyone wants an AoIP-based studio, I can recommend it, but do stay with one protocol and preferably one manufacturer/brand for least troublesome experience
Hi! Thank you for watching and providing such a detailed response. We'll be sure to continue to cover complicated topics like this in future videos as holistically as we can 👍
Great question Mark, this is from the Focusrite Pro team: The RedNet PCIeR card for Dante is actually to get your computer’s audio on your Dante Network. It’s a common misconception that you need this to be able to use the Dante Network, if you have a RedNet PCIeR card it will show as an ASIO device on Windows and a Core Audio device on Mac, and will need to be connected to your ethernet chain the same way as any other Dante product. The standard ethernet port on your Mac will be used for Dante visibility, so you actually cannot run a Dante Network without connecting your devices to the standard ethernet port. Through this Dante Controller & RedNet Control will be able to see and control the devices independently. If you would like to reach out to Peter Tilley in this video directly regarding this question you can reach him here: Peter.Tilley@focusrite.com
you can use built-in ethernet for Dante audio I/O if you purchase "Dante Virtual Soundcard" software/license, but expect higher latency (still very low) compared to dedicated PCIe Dante interface or even usb interface like RME Digiface Dante
Have any questions for us? Leave them below 👇
This is the best audio over IP explanation I have seen so far. Thanks again Adam Audio Keep the series going.
We're so happy you found this video insightful! Definitely more to come
I enjoy the recent educative videos you folks at ADAM channel provide, and appreciate the "beyond-our-brand" coverage,
with this video though, I don't feel it's well covered topic yet,
not all AoIP is Dante, and not all Dante is RedNet, although AES67 standard basically means audio can be routed across various products, their control does not though (for ex. changing gain or toggling phantom on various brands is basically a no go, and can usually be done only from within dedicated app provided by manufacturer),
then there's problem of basically nonexistent samplerate conversion, as far as I know only workaround is to get 2 RedNet MADI interfaces and hook them together via MADI with SRC in order to provide same stream of two different samplerates in Dante network; on top of that sync needs to be precise and older devices with PTP won't go well on PTPv2 clocked network etc..
then there's problematic of Unicast/Multicast, which basically means you set a live gig and in last minute if you decide to add another console, you basically need to shutdown and relaunch+reconfigure entire Dante network, similarly expanding studio during runtime is not troublefree (unlike plugging regular digital or audio cables/fibres),
then there's bandwidth limitation, particularly dangerous for bigger facilities, since 1Gbit can provide 128 channels audio, it's not that much, considering network is supposed to be simultaneously used for everything else like software updates, network storage etc.., I'm surprised it's not explicitly advised to have a completely separate network dedicated for reliable AoIP operation,
then there's a problem with AV workflow and its conversion, let's say sending 3Gbit audio+video stream into 1Gbit audio mixer won't really work smooth, and splitting signal before and joining back after console won't work smooth either; speaking of AVoIP, Dante can do now, but so can for ex. NDI, yet they are basically incompatible together....
I'm sure AVoIP is the future, and the leap is as big as it was from analog to digital, but so far there is no "complete" standard to go for; that said, if anyone wants an AoIP-based studio, I can recommend it, but do stay with one protocol and preferably one manufacturer/brand for least troublesome experience
Hi! Thank you for watching and providing such a detailed response. We'll be sure to continue to cover complicated topics like this in future videos as holistically as we can 👍
I've seen special PCIE cards for Dante. Does that mean I cant use the built in ethernet port on my 2010 macbook pro?
Great question Mark, this is from the Focusrite Pro team: The RedNet PCIeR card for Dante is actually to get your computer’s audio on your Dante Network. It’s a common misconception that you need this to be able to use the Dante Network, if you have a RedNet PCIeR card it will show as an ASIO device on Windows and a Core Audio device on Mac, and will need to be connected to your ethernet chain the same way as any other Dante product. The standard ethernet port on your Mac will be used for Dante visibility, so you actually cannot run a Dante Network without connecting your devices to the standard ethernet port. Through this Dante Controller & RedNet Control will be able to see and control the devices independently.
If you would like to reach out to Peter Tilley in this video directly regarding this question you can reach him here: Peter.Tilley@focusrite.com
you can use built-in ethernet for Dante audio I/O if you purchase "Dante Virtual Soundcard" software/license, but expect higher latency (still very low) compared to dedicated PCIe Dante interface or even usb interface like RME Digiface Dante
#aes67 for the win. Gotta stop promoting the tribe of Dante and more the tribe of the logic within the Audio engineering society.