NBX022 RTI driver setup:

NBX022 is a single channel streaming product.  You can use more than one NBX022 in a project (each with it's own driver).  However, this will limit you to using "Source mode" publishing.  "Room mode" publishing can only have a single NBX/NAB in the project, so if you want to use this mode and need more than one streaming channel use NBX100 or NAB100 instead.

NBX022 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 NBX022, only one user can stream at a time (others will be refused if device is busy).  If you would like to enable the whole family to stream different audio to different rooms simultaneously, please use NBX100 or NAB100.

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.

"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. 

NBX setup:

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

General config:  If you have more than one NBX022 in this project, you will need to set the "Logitech Media Server" to OFF on every device except one.  This allows you to consolidate your library and settings to a single server.  If you only have one NBX022, nothing should be changed here. 

Renderer config:  If you are using "Source mode", no changes are needed here.  If using "Room mode", refer to these instructions for this page.  For NBX022 "Room mode", all channels must be virtual.  Also make sure that output 1 is selected in the output mux for all enabled channels.  Your room channels should only have "Bonjour" and/or "Upnp" enabled.  You should setup 1 other channel with only "Squeeze" enabled.

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 Output 1 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 NBX022.  This is NOT done by power cycling.  Go to the "manual control" page and click on the REBOOT button there.

 

Driver setup:

Please use the NetPlay_example_single.rti example project as a baseline.

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 1 volume changed" event and "Output 1 volume" variables are used to forward volume to the current endpoint
  4. The current room can be found in the "Output 1 source" variable
  5. Current metadata and cover art is available via these driver variables.  The "Output 1 new metadata" event signals when these have changed.
  6. Metadata, coverart, and transport controls are always on OUTPUT 1
  7. Metadata and coverart from this driver also are valid for squeezebox streams, so it can be used in all cases.

Squeezebox driver:

  1. See our example project for setup
  2. NBX022 uses 1 driver instance with 1 player
  3. Enter your mysqueezebox account in the driver config (as well as in the LMS server config)
  4. Set the default player to the name of your Squeeze renderer channel
  5. Some of the "jump to browse location" commands do not work.  Browsing through "Apps" is the way to access all online services.
  6. If you do not want to see particular services in "Apps", disable those plugins in the LMS server config