sonobus

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
Last revision Both sides next revision
sonobus [2021/03/31 04:01]
espiegel123 [Multi-Channel Setup Illustrated - AUM]
sonobus [2021/03/31 11:35]
espiegel123 [Sonobus] add beta info
Line 4: Line 4:
 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://sonobus.net|Sonobus]] web site.
 ===== Self-Streaming with Sonobus ===== ===== Self-Streaming with Sonobus =====
 You can use Sonobus to get audio into or out of an app that supports AUv3 plugins but doesn't support IAA or Audiobus. For instance, you can can pipe your guitar from AUM into NanoStudio 2 where you can then record the audio into something like MultiTrack Recorder or ENSO or another AUv3 looper/sampler to workaround NanoStudio 2's lack of audiotracks. You can also use it to get 'stems' out of GarageBand into AUM. You can use Sonobus to get audio into or out of an app that supports AUv3 plugins but doesn't support IAA or Audiobus. For instance, you can can pipe your guitar from AUM into NanoStudio 2 where you can then record the audio into something like MultiTrack Recorder or ENSO or another AUv3 looper/sampler to workaround NanoStudio 2's lack of audiotracks. You can also use it to get 'stems' out of GarageBand into AUM.
Line 11: Line 12:
 **Private Group**. The simplest way is to use a Private Group. For the group name, enter the group name that all the Sonobus instances will connect to. For example, "myGarageBandSession". For the //Your Displayed Name// field, it is useful to use an identifier that will let you recognize what track is being sent/received. If you are sending multiple streams (such as when you went to send multiple tracks out of GarageBand), you may want to use the instrument name. This method requires that wifi is active, but if you are self-sending the packets actually will stay local without going to the router. **Private Group**. The simplest way is to use a Private Group. For the group name, enter the group name that all the Sonobus instances will connect to. For example, "myGarageBandSession". For the //Your Displayed Name// field, it is useful to use an identifier that will let you recognize what track is being sent/received. If you are sending multiple streams (such as when you went to send multiple tracks out of GarageBand), you may want to use the instrument name. This method requires that wifi is active, but if you are self-sending the packets actually will stay local without going to the router.
  
-**Connect to Raw Address**. Sonobus will let you connect directly to another Sonobus instance directly even if wifi is turned off. For people that need to have wifi off, this method is convenient because you can enter use the address 127.0.0.1 which means "send to the device I am on" which works even if wifi is off. When using Connect to Raw Address, you enter the address of a different instance of Sonobus running on the same machine. +**Connect to Raw Address**. Sonobus will let you connect directly to another Sonobus instance directly even if wifi is turned off. For people that need to have wifi off, this method is convenient because you can enter use the address 127.0.0.1 which means "send to the device I am on" which works even if wifi is off. When you tap on "Connect to Raw Address", Sonobus displays the unique address of the instance you are editing. The unique local address consists of the device's IP number (which will look like something like 192.168.1.05) a colon (:) and 5-digit number. The 5-digit number is called a port number. It allows each instance on the same device to have a unique identifier. When using Connect to Raw Address, you will enter as Host the IP address and port number of the Sonobus instance you want to connect to. Don't enter the the Local Address as the Host, use the Local Address of a different Sonobus instance. The IP number will be the same for both instances, but they will have different port numbers.
  
 ===== Multi-Channel Sending ===== ===== Multi-Channel Sending =====
Line 25: Line 25:
  
 ==== Multi-Channel Setup Illustrated - AUM ==== ==== Multi-Channel Setup Illustrated - AUM ====
 +=== Adding the Sonobus Instances ===
  
-{{:sonobus_multisetup_1.jpg?400|}}+{{:sonobus_multisetup_1.jpg?600|}}
  
-{{:sonobus_multisetup_2.jpg?400|}}+{{:sonobus_multisetup_2.jpg?600|}}
  
 After you have added all your 'child' Sonobus instances, you should see something like this: After you have added all your 'child' Sonobus instances, you should see something like this:
 +
 {{:sonobus_multissetup_3.jpg?600|}} {{:sonobus_multissetup_3.jpg?600|}}
  
 Notice that the child instances have numbers next to them that identify them as : 2, 3, 4. When you are setting up the Input Mixer in the master 2, 3, and 4 correspond to Aux 1, Aux 2, and Aux 3. Notice that the child instances have numbers next to them that identify them as : 2, 3, 4. When you are setting up the Input Mixer in the master 2, 3, and 4 correspond to Aux 1, Aux 2, and Aux 3.
  
-**STUB -- MORE PICTURES NEEDED HERE**+=== Setting up the Input Mixer in the Master Instance === 
 +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_1.jpg?600|}} 
 + 
 +{{:sonobus_input_mixer_setup_2.jpg?600|}} 
 + 
 +{{:sonobus_input_mixer_setup_3.png?600|}} 
 + 
 +{{:sonobus_input_mixer_setup_4.jpg?600|}} 
 + 
 +{{:sonobus_input_mixer_setup_4.jpg?600|}} 
 + 
 +After you have added all your buses, you will have something like this: 
 + 
 +{{: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_monitor_setup_1.jpg?600|}}
  
 +{{:sonobus_monitor_setup_2.jpg?600|}}
  
  
 {{tag>stub unreviewed}} {{tag>stub unreviewed}}
  • sonobus.txt
  • Last modified: 2021/04/03 03:17
  • by espiegel123