Differences
This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
sonobus [2021/03/31 07:29] – [Multi-Channel Setup Illustrated - AUM] sonosaurus | sonobus [2021/04/03 03:17] (current) – espiegel123 | ||
---|---|---|---|
Line 3: | Line 3: | ||
It can be used to stream one or more audio streams between networked devices (desktop and mobile) and can even be used to on an iPad or iPhone to stream to itself in order to get audio streams into and out of apps that support AUv3 but not IAA or Audiobus protocols. | It can be used to stream one or more audio streams between networked devices (desktop and mobile) and can even be used to on an iPad or iPhone to stream to itself in order to get audio streams into and out of apps that support AUv3 but not IAA or Audiobus protocols. | ||
+ | |||
+ | At this writing (March 2021), Sonobus for iOS is available through a public beta through the [[https:// | ||
+ | |||
+ | ===== Mac-to-iPad/ | ||
+ | For fast low-latency connections between and iOS device and a MacOS device, you can establish a network connection over a direct USB connection. In order to do this, go to the System Preferences on your MacOS device and turn on Sharing-> | ||
===== Self-Streaming with Sonobus ===== | ===== Self-Streaming with Sonobus ===== | ||
Line 26: | Line 31: | ||
=== Adding the Sonobus Instances === | === Adding the Sonobus Instances === | ||
- | {{: | + | {{: |
- | {{: | + | {{: |
After you have added all your ' | After you have added all your ' | ||
+ | |||
{{: | {{: | ||
Line 38: | Line 44: | ||
In the master Sonobus instance that actually sends the audio out, you need to bring in each of the sources that you want to send out. In the Sonobus receivers, the receiver will be able to grab whichever of the sources are needed. | In the master Sonobus instance that actually sends the audio out, you need to bring in each of the sources that you want to send out. In the Sonobus receivers, the receiver will be able to grab whichever of the sources are needed. | ||
- | {{: | + | {{: |
+ | |||
+ | {{: | ||
+ | |||
+ | {{: | ||
+ | |||
+ | {{: | ||
- | {{:sonobus_input_mixer_setup_2.jpg?400|}} | + | {{:sonobus_input_mixer_setup_4.jpg?600|}} |
- | {{:sonobus_input_mixer_setup_3.png? | + | After you have added all your buses, you will have something like this: |
- | {{:sonobus_input_mixer_setup_4.jpg?400|}} | + | {{:sonobus_input_mixer_setup_5.png?600|}} |
+ | MONITORING SETUP | ||
+ | By default, each input is monitored by the main Sonobus instance (the sender) rather than on its own bus. It is usually convenient to have each input monitored on its original bus. The pictures below demonstrate how to set this up. | ||
- | {{:sonobus_input_mixer_setup_4.jpg?400|}} | + | {{:sonobus_monitor_setup_1.jpg?600|}} |
- | Also set the monitoring output routing for each of the input groups, in this case you will want to use the same Aux # output as you used for the input so that AUM will have access to it. The button on the right side of the input groups lets you select the monitoring output. (TODO: the screenshots show that 1-2 are selected for monitor routing but they should be updated). | + | {{:sonobus_monitor_setup_2.jpg?600|}} |
- | {{: | ||
{{tag> | {{tag> |