In this section we will address the use of other networks alongside the standard network that connects your X32, M32 or WING console to REAPER, and to the AutoMate program you are using.
The AutoMate series of programs use and IP-based internet protocol (essentially UDP) to support communications between the program and the desk. Your desk can also accept an extension card such as an Audinate DANTE or Waves Soundgrid card that will also provide and rely on networking for transporting real-time audio and also some other data.
It is important for you to fully understand the different classes of networking as these extension boards may not rely/use the same network (even if they use the same type of cables) than the standard IP network that is used to connect your console to your standard computer. For example, you may be using a 100Mb/s network for your standard work and rely on a 1Gb/s DANTE network for your audio needs. Waves is using the layer 2 [data layer] of the network stack to offer a very low latency and as a result does not mix well with more advanced network layers that provides UDP or TCP/IP as expected by the console communications or your PC internet connection.
In setting up your Waves or DANTE networks, it is typically simpler to separate audio path and OSC (or console commands) and have these two travel on distinct networks. DANTE actually complies with layer 4 and can coexists well with UDP and TCP/IP. DANTE can obtain extremely low latency with a proper setup if you ensure the rest of your network devices comply to the highest supported speed. You can then share audio and commands (and internet as well) all on the same network if needed, although you would still benefit from a separate network if you can install one, ensuring a glitch-less audio data path for your audio stems.
Mixing Waves (layer 2) and UDP (layer 4) devices on the same network is asking for trouble and headaches. Mixing Layer2 devices and other layers is technically possible assuming you are a network specialist and is likely to require specific routing and dedicated devices/boxes that will significantly add up to your network equipment cost.
MJ Klein has setup an Audinate DANTE studio and has attained a very low latency, taking full advantage of the X32 DANTE card. He has been describing his setup and published specifics at https://phoenixmediaforge.com/tag/dante/, with a max latency of 1.2ms; Check it out.
To avoid disastrous situations [:-\], make sure you read plenty about network audio before you install one. https://www.sweetwater.com/insync/networked-audio-worship/ is one example of guides on you can find on the net; there are plenty on the subject.
X32Reaper-, X32XLive-, WingReaper-, WingWLive- AutoMate and digital network network cards
In this section we will address the use of other networks alongside the standard network that connects your X32, M32 or WING console to REAPER, and to the AutoMate program you are using.
The AutoMate series of programs use and IP-based internet protocol (essentially UDP) to support communications between the program and the desk. Your desk can also accept an extension card such as an Audinate DANTE or Waves Soundgrid card that will also provide and rely on networking for transporting real-time audio and also some other data.
It is important for you to fully understand the different classes of networking as these extension boards may not rely/use the same network (even if they use the same type of cables) than the standard IP network that is used to connect your console to your standard computer. For example, you may be using a 100Mb/s network for your standard work and rely on a 1Gb/s DANTE network for your audio needs. Waves is using the layer 2 [data layer] of the network stack to offer a very low latency and as a result does not mix well with more advanced network layers that provides UDP or TCP/IP as expected by the console communications or your PC internet connection.
In setting up your Waves or DANTE networks, it is typically simpler to separate audio path and OSC (or console commands) and have these two travel on distinct networks. DANTE actually complies with layer 4 and can coexists well with UDP and TCP/IP. DANTE can obtain extremely low latency with a proper setup if you ensure the rest of your network devices comply to the highest supported speed. You can then share audio and commands (and internet as well) all on the same network if needed, although you would still benefit from a separate network if you can install one, ensuring a glitch-less audio data path for your audio stems.
Mixing Waves (layer 2) and UDP (layer 4) devices on the same network is asking for trouble and headaches. Mixing Layer2 devices and other layers is technically possible assuming you are a network specialist and is likely to require specific routing and dedicated devices/boxes that will significantly add up to your network equipment cost.
MJ Klein has setup an Audinate DANTE studio and has attained a very low latency, taking full advantage of the X32 DANTE card. He has been describing his setup and published specifics at https://phoenixmediaforge.com/tag/dante/, with a max latency of 1.2ms; Check it out.
To avoid disastrous situations [:-\], make sure you read plenty about network audio before you install one. https://www.sweetwater.com/insync/networked-audio-worship/ is one example of guides on you can find on the net; there are plenty on the subject.
Patrick
Computer scientist, music enthusiast and guitar player, Patrick-Gilles has acquired an X32 in 2014 and wrote the UNOFFICIAL X32/M32 OSC REMOTE PROTOCOL, which soon became the reference for many X32 or M32 users and application programmers. Patrick-Gilles has also published and open-sourced several X32 or M32 utilities and applications.