Millumin training how to#
I can’t enforce that end users of a system I spec take a course to know how to use it.As far as I know MADI connection latency is essentially zero if no SRC is involved. One other point is that latency will be higher on a Dante network than with MADI, but Dante network latency is typically 1ms or 0.5 with a smaller network, which is largely irrelevant unless you’re hopping between a lot of devices. The one point of failure I don’t like is that DVS exists only the primary network, but that can be solved by using Yamaha PCIe cards (in a thunderbolt chassis if necessary) or their counterpart from Focusrite. I do think a well-designed Dante network can be highly reliable and not require IP knowledge from the daily users as long as they are given basic guidelines on what not to do, and maybe what to reboot when if there is a failure. Need to record something in tech from the band or an actor? Just send it to the tech table via dante.īut, if MADI covers all of your possible use cases and you don’t forsee any unusual routing being useful in the future, then yes, it is a more straightforward protocol. System tuning can all be done with DVS and a Ri-8, or just spare console inputs for measurement mics. For example, setting up an A2 monitoring station can happen on a computer running DVS and some routing software (or with one of the newer 2ch Dante headphone amps).
Certainly Dante can do what MADI does as a single-wire multichannel transmission scheme, but having devices on a network means there are vastly more possibilities for routing, which open up a multitude of use cases that in my shows I’m still discovering. If the latter, to me this is somewhat of an apples to oranges comparison and the use cases don’t totally overlap.
Is your question about what to use for playback, or a venue-wide audio distribution backbone?
0 kommentar(er)
