Current version: 0.5.4 (April 15th 2012)

Download the Windows Installer
Download zip archive

Changelog 0.5.4

added HTTPS support for connecting. Default port is 58051. Works with Android BubbleUPnP 1.3.3+ and foo_upnp 0.99.37+
added support for sending compressed data to foo_upnp 0.99.37+ to save bandwidth
added support for logging media streams connections, in the NCSA common file format Media streams logs are added to file access_log.txt found in the installation directory. Can be enabled/disabled in the "Network and Security" tab. Disabled by default
fixed obscure startup crash on some Windows installs
fixed new version check notification not working since v0.5
updated documentation (https)

What is BubbleUPnP Server ?
Download and installation
Configuration

Status
Network and security
Media Servers
Media Renderers

Creating OpenHome renderers

Connecting with BubbleUPnP for Android

Remote UPnP Network configuration
Audio and video transcoding settings

Music Internet streaming with foobar2000 on Windows
FAQ

Where do I report issues, get support or leave feedback ?
How do I change the default HTTP or HTTPS port ?
How is security handled ?
I'm hearing gaps when streaming audio on my Android device
How do I enable MP3 audio transcoding support ?
How do I enable H264 video transcoding support ?
How do I tweak H264 video transcoding parameters ?
How do I install Java, ffmpeg on a QNAP NAS ?
How do I install on a Synology NAS ?

Troubleshooting server startup
Changelog

What is BubbleUPnP Server ?

BubbleUPnP Server:

extends your existing UPnP AV Media Servers and Media Renderers on your network with new functionality
allow easy Internet streaming and downloading of your music and videos over mobile and WiFi connections with BubbleUPnP for Android, in a secure and network bandwidth efficient way.
since v0.5.3 it is possible to do Internet streaming on Windows as well

BUBBLEUPNP SERVER IS NOT AN UPNP AV MEDIA SERVER.
It requires at least one working UPnP AV Media Server (Windows Media Player, Twonky, Asset UPnP, ...) or Media Renderer to do something useful.

At this time, the following features are supported:

Internet streaming and downloading

BubbleUPnP Server makes your LAN Media Servers available to BubbleUPnP for Android, for streaming over mobile (3G/4G) and WiFi connections, with the following advantages:

Easy to setup: you do not have to modify your Media Servers configuration in any way
Secure: all communication between BubbleUPnP for Android and your Media Servers go through BubbleUPnP Server and is password protected. HTTPS is supported (since v0.5.4).
Network bandwidth efficient: bandwidth is greatly optimized between Android BubbleUPnP and your Media Servers, reducing loading times over mobile networks
Transcoding: BubbleUPnP Server can transcode audio on the fly to MP3 and video to H264, to adapt to lower bandwidth usually available on mobile networks
Transcoded downloads: you can download a transcoded version of your tracks for playback on your Android device with any audio player. Useful to download an MP3 version of your FLAC or lossless albums stored on your NAS.

This functionality can also be used on a regular LAN, for example to bypass regular UPnP SSDP device discovery in the rare cases it is not available for whatever reason (blocked by a firewall, UDP multicast disabled at the router level, ...).

Internet UPnP tethering

Using BubbleUPnP for Android, you can make your Media Servers from your home local network visible on another LAN to any UPnP AV devices of this LAN (TV, Control Points, ...).

To illustrate this functionality consider this scenario:

Suppose you have a Twonky server at home (replace Twonky with your favorite Media Server) and you go visit a friend who has a brand new UPnP/DLNA device connected to his stereo and a Windows 7 PC with Window Media Player. Using your Android device and BubbleUPnP you can push music from your Twonky Server to his stereo.

With UPnP tethering you can do the same using the "Play to" functionality of Windows Media Player. In short, your Android device makes your home Twonky server visible to Windows Media Player on you friend's network. This is UPnP tethering.

LAN Media Server proxying

Many Media Servers have bugs and sometimes return incorrect data which can prevent them from working fully with some UPnP Software. BubbleUPnP Server can create a "proxy" Media Server (associated to a real Media Server on your LAN), that will attempt to convert incorrect data into correct data. Data is always reformatted in a more compact format with the benefit of speeding up browsing on slower devices. Except for this difference, the proxy Media Server acts exactly as the real Media Server it is linked to.

Another possible use of proxying is to solve potential Media Servers discovery issues in your network with some UPnP software. As long as BubbleUPnP Server is able to discover your Media Server, it can create a proxy Media Server which in turn has more chance to be discovered by UPnP software.

Persistent and shared playlist for UPnP AV Renderers (OpenHome)

When operating an UPnP AV Renderer, the playlist of audio tracks resides on the Control Point which must remain running for playlist track advance to happen. It has 2 main drawbacks:

keeping a Control Point app running isn't the best solution, in particular on mobile devices as it consumes battery.
two or more Control Points cannot control the same UPnP AV Renderer and share the same playlist. For example, you cannot create a playlist on your smartphone Control Point and later modify it on your PC or tablet Control Point

To tackle these issues, the OpenHome Playlist specification addresses the deficiencies of UPnP AV, adding the ability for an OpenHome Renderer to store and manage its playlist. It can advance playback by itself without requiring a Control Point to be running. Several OpenHome enabled Control Points can be connected to the renderer, sharing the same playlist. Any playlist change on one Control Point is immediately reflected on the others.

BubbleUPnP Server makes it easy to create an OpenHome renderer from any exisiting UPnP AV Renderer (WMP for example). Refer to this section for more information on how to create and control an OpenHome Renderer with BubbleUPnP for Android or other OpenHome Control Points.

Download and installation

Requirements

BubbleUPnP Server can run on any platform where Java 1.6 is available. This includes:

Windows XP/Vista/Seven
MacOS X
Linux
Any NAS on which Java is available

Windows XP/Vista/Seven

On Windows, the easiest way to get started is to download the installer below.

Download the Windows Installer

Run the installer. If Java 1.6 is not installed on your system, the installer will launch the Java installer before installing BubbleUPnP Server. At the end of the installation process, BubbleUPnP Server should be running as a Windows service. The installer will launch your Web Browser to configure it. You can also connect to it pointing your Web Browser to http://localhost:58050 or launch the Desktop shortcut. If the Web Browser cannot connect to BubbleUPnP Server, refer to the troubleshooting section.

You will find shortcuts in the Windows Start menu to stop/start the service and launch the configuration interface in your web browser.

If you do not want to run BubbleUPnP Server as a Windows service you can download the archive for other platforms.

Other Java platforms (Linux, MacOS X, NAS, ...)

Download BubbleUPnP Server

BubbleUPnP Server is distributed as an archive containing a jar file.

unpack the archive in a directory
on unix platforms make launch.sh executable: chmod +x launch.sh
on unix platforms run launch.sh, on Windows run launch.bat. Java 1.6 must be installed and the "java" executable must be in your PATH
point your Web Browser to http://localhost:58050 to show the configuration interface
for Internet access with Android BubbleUPnP, configure your firewall / Router NAT to allow access to TCP port 58050 (see server configuration below)

If you want transcoding support you will need to install ffmpeg on your system.

Here are specific installation guides for:

QNAP NAS
Synology NAS

Alternatively you can run the server with:

java -jar BubbleUPnPServer.jar

If you get an error on startup, refer to the troubleshooting section.

IMPORTANT: There is a known JRE crash with some versions of OpenJDK on the ARM platform. It can be workarounded starting the server with:

java -XX:+PrintCommandLineFlags -jar BubbleUPnPServer.jar

Configuration

The core of BubbleUPnP Server is Web Server running on port 58050 by default for HTTP and on port 58051 for HTTPS.

The server must be accessible from the Internet on this port (LAN proxying functionality does not require this). The Windows Installer will try to auto-detect network settings so the server is usable straight away adding the required firewall and NAT rules, but this might not work in all network setups.

The configuration front-end is divided into 4 tabs:

Status

This page displays a summary of the server operational status and has all information required to configure BubbleUPnP for Android:

the server's status when connecting from the Internet
the server's public IP Address and hostname
the server's public HTTP Port
the server's public HTTPS Port
the server's LAN IP Address
the Internet connection test for both HTTP and HTTPS
the server's version and expiration date if any
the server's support for audio transcoding
the server's support for video transcoding

If "Server is reachable from Internet" is displayed, everything is fine and BubbleUPnP Server is ready to use.

Otherwise something is preventing the Internet to connect on the HTTP or HTTPS port. This will likely be a NAT or firewall issue. For example, if the public HTTP port is 58050 and the LAN IP Address displayed is 192.168.1.10

Add a rule on your router to redirect connection on TCP port 58050 to LAN IP Address 192.168.1.10 on port 58050. You must use the same port for the redirection
Add a rule on your firewall to allow incoming traffic on TCP port 58050 on the 192.168.1.10 machine
For HTTPS access repeat the 2 steps above with the HTTPS port (58051 by default)

IMPORTANT: if you use HTTPS access, the HTTP port must still be open as it is still used for media streaming requests only.

Network and Security

In this page you can set the login and password that you will use to connect to the server:

in BubbleUPnP for Android
in foobar2000
to access the configuration interface when connecting from the Internet (if "Allow to access server from the Internet" is enabled)

If you are using a dynamic DNS service because your ISP changes your IP address at regular interval, you can change the public hostname to your stable dynamic DNS hostname.

If option "Allow to access server from the Internet" is disabled, the server will deny all Internet connections. If you plan to use BubbleUPnP Server with BubbleUPnP for Android, you must enable this setting.

If option "Allow to configure the server from the Internet" is enabled, these credentials are also used to connect to the configuration web interface from the Internet. By default this option is disabled and the configuration web interface is only accessible on the LAN.

If option "Enable media access log file" is enabled, all media streaming connections will be logged to the access_log.txt file found in the installation directory.

Media Servers

This page displays the list of Media Servers detected on your local network. For each Media Server you can configure:

if this Media Server should be made available to BubbleUPnP for Android when it connects
if a proxy of this Media Server should be created on the LAN

When a proxy Media Server is created, a new Media Server with the same name will appear on your LAN with "[proxy]" appended to the name. For example if you have a Media Server named "Awesome" then a new one called "Awesome [proxy]" will appear. You can connect to it with any UPnP software like you would connect to "Awesome".

Media Renderers

This page displays the list of UPnP AV Media Renderers detected on your local network.

Creating OpenHome renderers

For each UPnP AV Renderer you can create a playlist aware OpenHome Renderer that you can control with either BubbleUPnP for Android (requires 1.3.3+) or other OpenHome Control Points.

An OpenHome Renderer has the following advantages over a regular UPnP AV renderer:

each OpenHome renderer has its own playlist
no need to leave the Control Point running for playlist track advance to happen
several OpenHome Control Points (BubbleUPnP, Linn Kinsky) can be connected to the same renderer simultaneously, showing the same playlist and playback state
create a playing playlist on a device and pick it up later on another device

For example, consider this scenario:

with BubbleUPnP Server you create an OpenHome renderer from WMP
in BubbleUPnP for Android on your phone you select this renderer and make a playing playlist and start playback
you exit BubbleUPnP. Playlist track advance is still performed by BubbleUPnP Server
sometimes later you launch BubbleUPnP on your tablet (or phone) and select the WMP OpenHome renderer. The initial playlist is displayed

To create an OpenHome Renderer from the selected UPnP AV Renderer just check "Create an OpenHome renderer". A new UPnP Device will appear on the network named after the UPnP AV Renderer's name with "(OpenHome)" appended. For example if you select a Windows Media Player Renderer called "bob (MYPCNAME: Windows Media Player)", then the newly created OpenHome Renderer will appear as "bob (MYPCNAME: Windows Media Player) (OpenHome)" in BubbleUPnP for Android. An OpenHome renderer has two optional parameters that you can modify:

Room: the physical room where your renderer is located. Limited to 20 characters
Name: the name of the renderer within the room. Limited to 20 characters

Room and Name are ignored by BubbleUPnP for Android. However they are used by other OpenHome Control Points such as Linn Kinsky to get the full name of the renderer which will usually be "Room: Name".

To control an OpenHome renderer you cannot use a regular UPnP AV Control Point. You need an OpenHome Control Point:

BubbleUPnP since version 1.3.3 (Android)
BubbleDS (Android)
Linn Kinsky (Windows, MacOS X). Also runs on iOS but untested.
foobar2000 + foo_upnp >= 0.99.36 plugin (Windows)

Untested Control Points: ChorusDS (iOS, MAC), Konductor (iOS), PlugPlayer (iOS), SongBook DS (iOS), SongBook Mac.

Here are screenshots of both Linn Kinsky (left, PC) and BubbleUPnP for Android showing the same playlist for the Windows Media Player renderer as an OpenHome Renderer:

Help

This page. The FAQ section will be updated over time.

Connecting with BubbleUPnP for Android

Once BubbleUPnP Server is up and running you can configure BubbleUPnP to connect to it and start streaming music.

Remote UPnP Network configuration

In BubbleUPnP:

Go into Settings > Networks and settings, select an unused Network and set the connection parameters (left screenshot)
Use the Test button to test the connection
Use the Apply button to connect to BubbleUPnP Server and have the remote Media Servers listed in the Devices tab of the app (right screenshot)

Name

This is the name used to identify the remote BubbleUPnP Server network. You can choose any name you want. It is used to identify Media Servers from different networks. For example if your home Media Server is named "My Media Server" and you set Name to "Home", this Media Server will be listed as "My Media Server [Home]" in the Library tab (as shown in the right screenshot).

Server address

This is the public connection URL to BubbleUPnP Server. The information used to set this field is displayed in the Status tab of BubbleUPnP Server.

For example if the Status tab shows:

Public IP Address:  1.2.3.4
Public HTTP Port: 58050
Public HTTPS Port: 58051
Public host name: my.host.org

To connect through HTTP, you must set "Server Address" to either http://1.2.3.4:58050 or http://my.host.org:58050
To connect through HTTPS, you must set "Server Address" to either https://1.2.3.4:58051 or https://my.host.org:58051

Login

Use the login that you defined in the Security tab.

Password

Use the password that you defined in the Security tab.

Active on connection

This setting allow you to set when BubbleUPnP should automatically connect to this remote network to make the associated Media Servers available in the Devices tab of the app.

For example you may want to connect to this network only when your Android device uses a Mobile data connection. In that case you would set this setting to "Mobile". Now every time your Android device switches to a mobile connection, BubbleUPnP will connect to BubbleUPnP server to make your Media Server available in the Devices tab. And if you switch from a mobile connection to WiFi, it will disconnect and remove them from the Devices tab.

The possible choices are:

Disabled: never connect to this network
Mobile: connect to this network on mobile connections
WiFi /Ethernet: connect to this network on WiFi or Ethernet connections
Mobile / WiFi / Ethernet: connect to this network on mobile or WiFi or Ethernet connections

Advertise on LAN

This setting if enabled will make all Media Servers of this remote network (those listed in the right screenshot) visible on the target LAN on which your Android device is currently connected. This only work if your Android device uses a WiFi or Ethernet connection. It means that your UPnP devices on the target LAN (a PS3, a DNLA TV, etc) should be able to see and browse your remote Media Servers. This is UPnP tethering.

For example a PS3 accessing to your home Media Server follows this path when issuing commands (browsing, searching, etc):

PS3 -> Android device (BubbleUPnP) -> Internet -> BubbleUPnP Server -> Your Media Server.

For streaming audio or retrieving album art the PS3 talks directly to BubbleUPnP Server without Android BubbleUPnP in the middle:

PS3 -> Internet -> BubbleUPnP Server -> Your Media Server.

Audio and video transcoding settings

BubbleUPnP Server can optionnaly transcode audio (to MP3) and video (to H264/MP3) for playback on the Android device itself (using the local renderer).
No transcoding is ever performed if streaming to an external renderer, as it may have a faster connection to BubbleUPnP Server than your Android device.

Separate transcode settings are also available for downloaded files.

For transcoding to work, BubbleUPnP Server must report that audio and/or video transcoding are supported in its Status tab.
NOTE: Video transcoding is only available since BubbleUPnP 1.3.2

In BubbleUPnP for Android, you can configure how BubbleUPnP Server should perform the transcoding in Settings > Networks and settings.
There are separate settings for Audio and Video and for each connection type.

Music playback transcoding

Mobile Max Bitrate: on a mobile connection, BubbleUPnP Server will transcode to the specified bitrate all audio whose bitrate is higher than this bitrate
WiFi / Eth Max Bitrate: on a WiFi / Eth connection, BubbleUPnP Server will transcode to the specified bitrate all audio whose bitrate is higher than this bitrate
Lossless only: enabling this setting will ensure that only lossless tracks will be possibly affected by the transcode settings. This is to prevent lossy->lossy transcodes which should be avoided if possible are they are bad for audio quality (unless the source is 320Kbps in which case it might be acceptable)

Video playback transcoding

Here you can specify which profile should be used for video transcoding:

No transcoding
720p / 128Kbps audio
480p / 128Kbps audio
360p / 128Kbps audio
240p / 128Kbps audio
240p / 64Kbps audio
120p / 64Kbps audio

All profiles will transcode to H264 for video and MP3 for audio, into an AVI container (for technical reasons it cannot be MP4). Aspect ratio is preserved. The transcoded video IS NOT playable by the standard Android video player and requires a third party video player app supporting software decoding. DicePlayer and MoboPlayer have been verified to work but there are probably many others.

Mobile transcoding: profile to be used on a mobile connection
Wifi / Eth transcoding: profile to be used on a WiFi / Eth connection

Downloads transcoding

Here you will find specific transcode settings applied to downloaded files:

Lossless audio bitrate: downloaded lossless audio files will be transcoded by BubbleUPnP Server as MP3 of the specified bitrate

Music Internet streaming with foobar2000 on Windows

This feature allows you for example to stream to your work PC your music from your home Media Server.

Connecting with foobar2000

First you must make sure the status page of BubbleUPnP Server shows that it is accessible from the Internet.

You can access your Media Server from the Internet for streaming music on Windows, using the foobar2000 music player as the client.

install foobar2000
install foo_upnp (instructions for installing plugins in foobar2000)

After installation, in the View menu of foobar2000 select "UPnP Browser". The UPnP Browser window displays all your discovered LAN Media Server allowing browsing an playing music as shown in the left screenshot. In the view Menu, select "Add remote Internet UPnP Server..." and enter BubbleUPnP Server connection settings (left screenshot):

the public hostname of BubbleUPnP Server with the protocol (http or https) and port. For example: http://1.2.3.4:5081 or https://1.2.3.4:5081.
It is recommended that you use https whenever possible (foo_upnp v0.99.37+ required)
the login and password you defined in the "Network and Security tab" of BubbleUPnP Server
If you are behind a HTTP proxy, you must set it before connecting with "Configure http proxy settings..." or in File > Preferences > Tools > UPnP > Browser

TIP: If you are on a corporate network only allowing outgoing HTTP traffic on port 80, you can setup BubbleUPnP Server to run on port 80 (provided you have no other web server using this port). For HTTPS, use port 443.

After clicking OK and if the connection to BubbleUPnP Server is successful, the UPnP Browser tree will show a new Media Server named "BubbleUPnP Server (<Remote PC Network name>) [Internet]", as shown in the right screenshot.

This "Super" Media Server lists all your Media Servers on your remote LAN for which the setting "Make this Media Server available in BubbleUPnP for Android and foobar2000 for Internet access" is enabled in BubbleUPnP Server (in the Media Servers tab).

To disconnect or remove the BubbleUPnP Server "Super" Media Server from the UPnP Browser, right click its root node and select "Remove server" in the context menu.

Note that you can integrate the "UPnP Browser" as a panel in the main foobar2000 window to avoid having a separate floating window. Here are basic instructions to do so:

make sure the standalone "UPnP Browser" window is closed
enter layout editing mode: View > Layout > Enable layout editing mode
right click in an existing panel
select "Replace UI Elements..."
select a splitter in the list
right click again in the new created area and select "Replace UI Elements..." again
in the list select "UPnP Browser"
exit layout editing mode: untick View > Layout > Enable layout editing mode

Transcoding audio to mp3

As with BubbleUPnP for Android as a client, it is possible to transcode audio on the fly when accessing your Media Servers with foobar2000. Unlike BubbleUPnP for Android, the transcoding settings are configured in BubbleUPnP Server, in the "Settings / foobar2000 remote access" tab.

Max audio bitrate: all files whose bitrate is greater than the specified bitrate will be transcoded to the specified bitrate. If bitrate is unknown, transcoding is performed. Set to "None" to disable all transcoding.
Apply Max audio bitrate only to lossless audio: if enabled, only lossless files (FLAC, ALAC, ...) are applied the Max audio bitrate rule so only lossless files will possibly be transcoded. This prevents any lossy->lossy transcoding which should be avoided if possible, if audio sound quality is important.

IMPORTANT: Transcoded files will not be seekable in foobar2000.

NOTE: changing these settings will only take effect in foobar2000 when browsing folders that were not previously browsed. To apply changes on browsed folders, you must disconnect/reconnect the BubbleUPnP Server "Super" Media Server.

FAQ

Where do I report issues, get support or leave feedback ?

You can leave a message in the XDA forums thread.

How do I change the default HTTP or HTTPS port ?

To change the HTTP or HTTPS port used by the server you must edit the configuration file and restart the server.

The configuration file is named configuration.xml. It is located in the installation directory. Open it with your favorite editor and modify the field httpPort (or httpsPort). If you set a port < 1024 on unix you will need to start the server as root otherwise you will get a permission error on startup.

To restart the server:

on Windows: use the "Stop BubbleUPnP Server Service" then "Start BubbleUPnP Server Service" found in the "BubbleUPnP Server" sub-menu of the Windows Start Menu
on other platforms: kill and restart the BubbleUPnP Server java process

How is security handled ?

HTTP requests from outside the LAN (Internet) are authenticated using HTTP Digest Authentication.
Since v0.5.4 connecting with HTTPS is also supported which will encrypt all traffic.

Note that for technical reasons, audio/video stream requests are neither authenticated nor use HTTPS.

I'm hearing gaps when streaming audio on my Android device

This is the symptom of the network bandwidth being insufficient, especially over a mobile connection. Try lowering the max bitrate setting in the Remote Network settings.

How do I enable MP3 audio transcoding support ?

On Windows, ffmpeg is bundled in the Windows Installer so transcoding will work out of the box. Transcoding support is enabled if the ffmpeg executable can be found in the PATH. ffmpeg must be compiled with libmp3lame support.

To check that libmp3lame is supported the command below should return this output:

$ffmpeg -codecs | grep libmp3lame
  EA    libmp3lame      libmp3lame MP3 (MPEG audio layer 3)

If ffmpeg doesn't recognize the -codecs option then ffmpeg is too old and cannot be used. Make sure you are using ffmpeg 0.6 or later (0.7+ recommended).

On other platforms, ffmpeg must be installed:

Linux (debian and derivatives): apt-get install ffmpeg
MacOS X: you can install ffmpeg from MacPorts: sudo port install ffmpeg
Windows: ffmpeg binaries can be found here

How do I enable H264 video transcoding support ?

On Windows, ffmpeg bundled in the Windows Installer supports video transcoding out of the box.

A prerequesite for video transcoding is that MP3 audio transcoding is working (see paragraph above).

Additionaly you will need ffmpeg with libx264 present as well and the scale filter.

To check if libx264 is supported the command below should return this output:

$ffmpeg -codecs | grep libx264
  EV    libx264         libx264 H.264 / AVC / MPEG-4 AVC / MPEG-4 part 10

To check if the scale filter is available the command below should return this output:

$ffmpeg -filters | grep scale
scale            Scale the input video to width:height size and/or convert the image format.

How do I tweak H264 video transcoding parameters ?

BubbleUPnP Server uses a preset file named libx264-current.ffpreset in the installation directory, containing common H264 encoding parameters. These parameters are used for all video profiles that you can set in BubbleUPnP for Android (these profiles only change video size and audio quality).

You can tweak this file provided that you do not set parameters that change video size or audio codec. Some presets are included in the ffpresets subfolder. On NASes with less CPU power it can be interesting to use an alternate preset file which favours encoding speed over image quality.

How do I install Java, ffmpeg on a QNAP NAS ?

Tested on QNAP TS-419p+ with ARM CPU, but should work the same way for others.

Install Java: http://forum.qnap.com/viewtopic.php?f=163&t=45963

Install “Optware (IPKG)” qpkg from http://www.qnap.com/qpkg.asp

In case the “ipkg update” fails, try to adjust the following two config files:

[/opt/etc/ipkg] # more tsx19-kmod.conf
src/gz cs08q1armel http://ipkg.nslu2-linux.org/feeds/optware/cs08q1armel/cross/unstable
[/opt/etc/ipkg] # more tsx19.conf
src/gz cs08q1armel http://ipkg.nslu2-linux.org/feeds/optware/cs08q1armel/cross/unstable

ipkg update
ipkg install optware-devel
ipkg install git
ipkg install yasm
ipkg install lame

mkdir /opt/compile
cd /opt/compile
git clone git://git.videolan.org/ffmpeg.git

cd ffmpeg
./configure --enable-ssse3 --prefix=/opt --extra-cflags='-I/opt/include' --extra-ldflags='-L/opt/lib' --enable-static --disable-shared --disable-ffplay --disable-ffserver --enable-libmp3lame
make
make install

Execute those commands AND add to autostart script: make libraries in /opt/lib visible, otherwise libmp3lame.so library etc. is not detected

echo "/opt/lib" >> /etc/ld.so.conf
ldconfig

replace built-in ffmpeg with link to new version

rm /usr/bin/ffmpeg
ln -s /opt/bin/ffmpeg /usr/bin

To start BubbleUPnP Server automatically after system startup, add this to the autostart script. This will log all output to BubbleUPnPServer.log. If this is not wanted replace with /dev/null.

#remove old logfile
rm <locationOfBubbleUPnPServer>/BubbleUPnPServer.log
#Change directory is needed, otherwise BubbleUPnPServer will use configuration.xml in root director (/). Config is lost after reboot because QNAP cleares this dir on every startup.
cd <locationOfBubbleUPnPServer>
#Start the BubbleUPnPServer
/share/MD0_DATA/.qpkg/JRE/jre/bin/java -jar <locationOfBubbleUPnPServer>/BubbleUPnPServer.jar >> <locationOfBubbleUPnPServer>/BubbleUPnPServer.log 2>> <locationOfBubbleUPnPServer>/BubbleUPnPServer.log &

How do I install on a Synology NAS ?

Install Java. See this guide or this one.
Download the Linux package of BubbleUPnP Server and extract it

Modify launch.sh

#!/bin/sh
#remove old logfile
rm /var/bubbleupnpserver/BubbleUPnPServer.log
#Change directory is needed, otherwise BubbleUPnPServer will use configuration.xml in root director (/). 
cd /var/bubbleupnpserver
#Start the BubbleUPnPServer
/opt/java/ejre1.7.0/bin/java -jar BubbleUPnPServer.jar >> /var/bubbleupnpserver/BubbleUPnPServer.log 2>> /var/bubbleupnpserver/BubbleUPnPServer.log &

Note that you need to adjust the JAVA path according to your version...

Put a file with the following script into /usr/syno/etc/rc.d/ to have BubbleUPnP Server started automatically at every reboot:
```
#!/bin/sh
sh /var/bubbleupnpserver/launch.sh
```

After doing these steps, go to http://:58050 to configure BubbleUPnPServer.

Troubleshooting server startup

A number of issues may prevent BubbleUPnP Server to start. Most of them are network related.

First, make sure the version of Java is 1.6 or higher. BubbleUPnP Server will not work with older versions.

You can find the execution log file named server.log in the installation directory (by default on Windows: C:\Program Files (x86)\BubbleUPnP Server). You can check this file for startup error messages:

org.teleal.cling.transport.spi.InitializationException: Could not discover any bindable network interfaces and/or addresses

On startup, usable network interfaces are enumerated. This error happens if none is found. A network interface is usable if:

it is up (connected)
it has at least one assigned ip address
it is not a VMWare or Parallels virtual interface
it is not a PPP interface
it is not a loopback interface

Furthermore, at least one network interface must have an IPv4 address that is neither a loopback address (127.0.0.1) nor a link-local address (169.254.xxx.xxx).

MultiException[java.net.BindException: Address already in use, java.net.BindException: Address already in use]

The port (58050 by default) used by BubbleUPnP Server is currently used by another application (or BubbleUPnP Server is already running). You can check which ports are used with the netstat command. Configure a different port or kill the application using the current port.

org.teleal.cling.transport.spi.InitializationException: Could not initialize MulticastReceiverImpl: java.net.BindException: Address already in use

Some other program is bound to SSDP port 1900. You can check which ports are used with the netstat command.

org.teleal.cling.transport.spi.InitializationException: Could not initialize StreamServerImpl: java.net.SocketException: Permission denied: listen

Check that your firewall or other security software is not blocking Java

MultiException[java.net.BindException: Permission denied, java.net.BindException: Permission denied]

If you set a HTTP port < 1024, make sure you are running BubbleUPnP Server as root (on unix).

org.teleal.cling.transport.spi.InitializationException: Could not initialize StreamServerImpl: java.net.BindException: Cannot assign requested address: bind

You network interface has a link-local assigned address (169.254.xxx.xxx). It must have a valid regular ip address to be usable. This error should not happen with BubbleUPnP Server 0.3.2+ as link-local interfaces are discarded.

java.lang.Exception: No WAN IP Address found

The server could not determine your public ip address by connecting to http://whatsmyip.org. This could happen if there is no Internet connectivity.

java.lang.RuntimeException: java.io.IOException: No route to host at org.fourthline.cling.transport.impl.DatagramIOImpl.send(SourceFile:159)

If you get this error on MacOS X and you are using a software called "Peer Guardian", go into Peer Guardian's settings and select the "Disable Filters" option.

Could not initialize StreamServerImpl: java.io.IOException: Unable to establish loopback connection

It seems this error is related to the Comodo firewall. Try disabling Comodo or adding a rule to allow BubbleUPnPServer.exe.

java.io.IOException: Cannot run program "netstat": error=2, No such file or directory

On non-Windows machines, the netstat command must be available and in the PATH.

Changelog

0.5.4 (April 15th 2012)

added HTTPS support for connecting. Default https port is 58051. Works with Android BubbleUPnP 1.3.3+ and foo_upnp 0.99.37+
added support for sending compressed data to foo_upnp 0.99.37+ to save bandwidth
added support for logging media streams connections, in the NCSA common file format Media streams logs are added to file access_log.txt found in the installation directory. Can be enabled/disabled in the "Network and Security" tab. Disabled by default
fixed obscure startup crash on some Windows installs
fixed new version check notification not working since v0.5
updated documentation (https)

0.5.3 (April 6th 2012)

added support for Internet music streaming on Windows using foobar2000 + foo_upnp as client. Updated documentation
foo_upnp 0.99.36 can now control OpenHome renderers created by BubbleUPnP Server

0.5.2 (Mar 22th 2012)

fixed video transcoding possibly not working on non-Windows installs
video transcoding can be customized with preset file libx264-current.ffpreset. The content of this file can be modified or replaced with one of the presets found in the ffpresets sub-directory to control transcoding parameters
fixed server sometimes not starting on boot as a Windows Service
fixed seeking not working in Linn Kinsky when operating an OpenHome Renderer
various fixes

0.5.1 (Mar 1th 2012)

added ability to create an OpenHome renderer from any UPnP AV Media Renderer. Provides persistent server-side playlist for playback, with shuffle and repeat support
added video transcoding support with BubbleUPnP for Android (requires BubbleUPnP 1.3.2 or higher)
added "Allow to access server from the Internet" setting in the Network tab. If disabled, all remote (non LAN) connections will be denied
fixed issue with stopping the Windows Service
fixed issue with bad XML encoding in some cases, on Windows
updated documentation

0.4 (Feb 1th 2012)

fixed 100% usage of 1 CPU core when serving files
fixed proxy devices not browsable by some Control Points
fixed PS3 Media Server not browsable beyond its root folder
remove unresponding Media Servers from list that failed to notify their disappearance (can be disabled with discoveryMaintenanceInterval=0 in conf file)
increased timeouts for WMP

0.3.2 (Jan 8th 2012)

increased heap from 16Mb to 24Mb on Windows when running as a service (prevents possible out of memory)
fixed 2 rare crashes on startup
fixed rare crash on Media Server disappearance
fixed network issue possibly leading server to prompt for login/password when connecting from LAN
discard link-local network interfaces
do not discard network interfaces that do not report they are multicast capable (may prevent a few undue "Could not discover any bindable network interfaces and/or addresses" errors on startup)
validate public IP Address returned by whatsmyip.org on startup
added "troubleshooting server startup"" section to documentation

0.3 (Dec 2th 2011)

fixed Media Servers possibly disappearing/reappearing after some time
added the ability to specify manually public hostname, for networks using dynamic DNS
detect and use network interface connected to the Internet instead of the first network interface found (overridable with -lanIp)
improved reliability of streaming and downloading (fixed tracks possibly truncated before the end)
updated documentation and FAQ

0.2 (Nov 24th 2011)

optimize album art size for faster download speed over mobile connections
kill ffmpeg process when client stops playback
reduced exception spam in log
various fixes
updated documentation

0.1.1

fixed crash preventing web server to start with some network interfaces

0.1

initial version