NBX100 RTI driver setup:

NAB100 is a multi channel streaming product.  You will use:

1. The NetPlay audio driver if you want to display metadata from mobile streaming connections

2. The Squeezebox driver for local and internet streaming sources

First, you need to decide how you will use the two enhanced user interface features of NetPlay audio.

Publishing mode: 

Mobile streaming renderers normally publish themselves as a single device or virtual speaker.  When you try to connect from your phone, you can select the device to play to.  Then you switch to your RTI remote to actually select that device as the source for your room and turn on the amps/etc.  This is the default publishing mode known as "source mode".

NetPlay Audio offers a patent pending enhanced publishing mode known as "room mode".  This mode allows you to publish channels for every zoned audio room and/or groups of rooms in the house.  This allows the user to simply select the room to play to directly on the mobile device.  The RTI source selection and turn-on/off happens automatically.  This mode provides a much better user experience, but takes more setup for the installer.

Note that with NBX100, the whole family can stream different audio to different rooms simultaneously.

Volume mode:

Most mobile apps allow volume control.  However, integrating this "remote" volume with the RTI room endpoint volume can be done different ways.  NetPlay audio provides three different modes.

"Source volume" is the default mode and also how most mobile streaming renderers work.  In this mode, the remote volume is applied to the signal before it is output from NBX, effectively making it a source volume control.  The users RTI remotes and touch panels would then control the room endpoint volume, and the total effective volume is (remote_vol * room_vol).  Even though this is how most devices work today, we think this is confusing and don't recommend using this mode in RTI.

"No volume" mode simply allows you to disable/ignore the remote volume control.  This is easy to setup, easy for the customer to understand, but does mean they need to switch from the phone to the RTI remote to change the volume.

"Remote volume forwarding" is a Video Storm enchanced mode that applies the remote volume control directly to the RTI room volume endpoint.  This allows the customer to control volume directly using any device. 

Driver architecture:

The recommended driver setup for NBX100 for RTI is:

• Squeezebox will have 1-3 dedicated players, each with its own Squeezebox only driver.  These will be fixed channels/outputs 1-3.

• Bonjour / DLNA streaming uses "room mode" publishing and 3 to 5 simultaneous audio streams.  3-5 NBX drivers will be dedicated to mobile streaming (no squeezebox).  These will be dynamic assignment (not fixed) to the next 3-5 audio outputs.

NBX setup:

The next sections refer to the config pages located at the root index.php  (http://NBX_IP_ADDRESS).

General config:  Normally no changes needed here.  If you do not plan to use LMS, you will need to set the "Logitech Media Server" to OFF. 

Renderer config:  The first 1-3 channels will be squeezebox.  Set them up with "enabled", "squeeze", and "fixed" set.  The rest of the channels are available for normal "Room mode" setup.  Refer to these instructions for more details.  These mobile streaming should be setup with "fixed" OFF, "squeeze" OFF, and make sure outputs 1-8 are all set in the output mux.

Renderer volume config:  For NBX, if you are using "Remote volume forwarding" or "No volume" modes, check the "check to use optional output volume" box and set Outputs 1-8 default volume to 100.  If you are using "Source volume", then nothing should be changed on this page.

Renderer LMS config:  If you have more than one enabled LMS server on the network, you will need to enter the IP address of the server to connect to here.  However, this is very rare so most people don't need to change anything here.

Announcement service config:  If you want to use the announcement engine on NBX, config it on this page.  The NBX driver exposes the annoucement engine commands to director programming.

After making all these changes, we need to REBOOT NBX100.  This is NOT done by power cycling.  Go to the "manual control" page and click on the REBOOT button there.

Driver setup:

NetPlay driver:

1. The "Channel Y connect" events are used to signal "turn on" events to room Y
2. The "Channel Y disconnect" event are used to signal "turn off" events to room Y
3. The "Output X volume changed" event and "Output X volume" variables are used to forward volume to the current endpoint
4. Current metadata is available via these driver variables.  The "Output X new metadata" event signals when these have changed.
5. Coverart can be loaded from http://NAB_IP/coverartX
6. Metadata, coverart, and transport controls are indexed to the OUTPUT of the device
7. Metadata, coverart, and transport controls  from this driver also are valid for squeezebox streams, so it can be used in all cases.
8. The variable "Output X source" maps these outputs to the published room. 
9. There is also an inverse mapping of ROOM => OUTPUT in the variable "Channel Y current output"
10. These two variables allow you to find the correct metadata to display.  For example, in room Y you would lookup the value X from variable "Channel Y current output", then use X to retrieve the metadata and coverart.

Squeezebox driver:

1. See RTIs instructions for setup
2. NBX100 has 1 server and 1-3 players