Free forever·no account, no tracking, no third-party requests ·open data, free API
showstack / protocols / soundgrid

SoundGrid

Waves' networked audio and processing protocol, carrying audio between interfaces, consoles and a dedicated DSP server over standard gigabit Ethernet at low latency.

Audio transportProprietaryReported
Media Large, continuous, on time and in order

Continuous streams that are large enough to be sized properly, and that must arrive in order and on time.

What kills it. Anything that starves the link — usually a management transfer nobody scheduled — and jitter that outruns the receive buffer.

What it carries

Sample rates
44.1 kHz, 48 kHz, 96 kHz

Audio: Channel capacity halves as the rate doubles: an interface rated 128 channels at 48 kHz carries 64 at 96 kHz. Bandwidth is also counted per receiving device, so 64 channels sent to four destinations spends 256 channels of it. Bit depth is a property of the interface rather than the transport, and several console cards are held to their host console's rates, so check both ends.

What goes wrong

SoundGrid wants its own dedicated network interface and its own switch. Sharing the NIC with a show network or the internet is the standard cause of dropouts.
It is a layer 2 protocol on ordinary gigabit hardware, which makes the switch choice matter more than people expect: energy-saving features and cheap switches both cause problems.

What speaks SoundGrid (2)

ProductDirectionNotes
Allen & Heath Avantis
Allen & Heath
bidirectional Via option card.
DirectOut PRODIGY.MP
DirectOut
bidirectional Via module.

Typical use

Sources

Something wrong, or missing?

Known gaps on this entry: default_ports, first_published, implementations. If you can source one of them, that is a ten minute pull request.

Edit this entry on GitHub — one file, editable in your browser, and your handle goes on it permanently.