Please also read the Disclaimer

MediaNet - Device Modules - ExStreamer

Purpose: To support the Barix ExStreamer Device

Once this module is activated, and MediaNet started, you should configure the ExStreamer with a fixed IP address and set the Server mode to 0 = zServer (Auto)

You also need to ensure the "TCP Stream Port" and "UDP Command Port" match the settings in LOADER.xml (or change to loader.xml to match your ExStreamers)

Also please set "Start Threshold" to 32768

All ExStreamers must use the same settings, except the IP address of course!

When the devices boot they should be detected by MediaNet. They are recognised by their IP address so always use a fixed IP

In future when MediaNet is started it will auto load all known clients and the communication between client and MediaNet will allow MediaNet to detect if the device is present

Although the ExStreamer has no physical display, internally the client has a display identical to the Rio (title and 4 lines). This allows you to emulate a display on an OSD device and/or remote control the ExStreamer from any other supported device (Rio, SliMP3, MVP etc)

LOADER.xml

Most entries in loader.xml are default values assigned to newly discovered ExStreamer's. Those items that can be changed on a per-device basis are editable in clients.xml

<loader>
    <instance>
        <device module="EXSTREAMER" enabled="n" type="exstr" />
          set enabled="y" to enable ExStreamer support
        <settings keymap="keymap.xml" />
          specify the default keymap xml file
        <settings command="12301" stream="2020" />
          specify the UDP Command and TCP Stream ports here
        <settings volume="25" volstep="5" balance="0" />
          sets the default volume, volume step (1 to 10 allowed)
        <settings volmin="0" volmax="100" />
          set volmin= and volmax= in the range 0 to 100 to restrict the devices volume levels
        <settings zone="master" />
          this defines the 'zone' that a device is in, used by protocols like xPL
        <settings prontoenabled="n" prontoclear="y" prontoplay="y" />
          specify whether support for pronto and prontopro remotes should be enabled,
          and whether they should auto clear/play
        <settings playstyle="clear" />
          set the default playstyle for adding tracks (allowed values are clear, insert and append) 
        <settings osd_enabled="n" osd_device="tonyt-tivoosd.lounge" osd_menu="y" osd_status="y" osd_helper="XPLOSD" />
          specify an OSD device to use for On-Screen-Display
        <settings tts_enabled="n" tts_helper="TTS" tts_threshold="60000" />
          specify whether to support Text-to-Speech
        <settings stats_enabled="y" stats_helper="STATS" />
          specify whether played tracks should be added to the play statistics in the database
        <settings scripting="n" />
          specify whether scripting menus are enabled (requires scripting module loaded)
        <module>
            <load module="EXSTRDISCOVERY" enabled="y" />
            <settings port="12321" />
        </module>
        <module>
            <load module="EXSTRREMOTE" enabled="y" />
            <settings port="12301" />
              specify the UDP Command port here
        </module>
          the module sections above load all the support files for an ExStreamer device
    </instance>
</loader>

All remote control buttons are mapped via keymap.xml

How the Remote Control is Mapped (by default)

Items in BLUE are not specifically listed in the appropriate section, but are the result of a cascade search thru the sections

* Lock means that key presses are ignored other than for protocol functions until either lock is pressed again or unit is powered off. This allows the use of remote control for home automation duties (like controlling lights, tivo etc) while the unit is in use

** @ signifies items beginning with non-alpha tracks

ExStreamer Settings (to match defaults in Loader.xml)