3 ms·

Or Dante for that matter.

• detaro 7y ago
  any pointers to open implementations of those two?
  • holy_city 7y ago
    AES67 is just an interoperability standard, it's more of a device level protocol than anything. You buy AES67 compatible gear for your application, then use the vendors' tools like Dante Virtual Soundcard (so you can essentially treat the networked audio system as a normal soundcard on your machine through CoreAudio/WASAPI/JACK/etc). It's actually pretty great, most of the time there's no need for a separate API just to handle streaming. It "just works."
    • tootie 7y ago
      Doesn't Dante also require proprietary hardware?
      • holy_city 7y ago
        Kinda? You need hardware at some point. AES67 was all about creating an open protocol for connecting different proprietary stuff, and frankly there's only a handful of places where I've seen open hardware worth its salt in audio. If you need high capacity, low latency audio over networked machines, you're going to need proprietary hardware/software in the chain somewhere.
• holy_city 7y ago
  I'm including Dante/Ravenna/Livewire in that question. My guess is that this is more an application toolkit for home/consumer applications instead of professional use, but a lot of the problems they have listed on their roadmap are already solved through a family of open* standards. The name escapes me but there's an industry initiative to provide FOSS APIs on top of web tech to build these kinds of applications. Engineering manager from Fox/Disney gave a talk about it last month (maybe it was march?) at the LA SMPTE meeting. Lots of money is going into this domain. * with an AES membership, but you should have that for this kind of project anyway