• Can I use Remuco for multiple players simultaneously?
• Bluetooth problems
• Timeout while waiting for Hello message
• Incompatible client and server versions
• What's that report tool for?
• How can I control the master volume?
• I have another question ...

Can I use Remuco for multiple players simultaneously?

For sure. This works out of the box using Bluetooth connections.

For WiFi connections you have to tweak player adapter configurations so that each adapter uses a unique port. Here is an example which sets distinct ports for Banshee and VLC in ~/.config/remuco/remuco.cfg:

...
[Banshee]
wifi-port 40001
...
[VLC]
wifi-port 40002
...

Note: Remuco ≤ 0.9.2 had a slightly different configuration system. See PlayerAdapterConfiguration in case you are using an older Remuco version.

On the client, create a new WiFi connection for each player and set the port as configured.

Bluetooth problems

Device scan fails

First, check if the Bluetooth device on your computers is in inquiry mode, i.e. it must be discoverable. You can check this with:

 $ hciconfig

In the output must be a line like this:

 UP RUNNING PSCAN ISCAN

If this is not the case, you can enable inquiry mode with:

 $ hciconfig hciX piscan

where X is the number of the Bluetooth device to configure (0 for the first). If available, you may also use your graphical tool of choice for setting your Bluetooth dongle visible and conncetable.

If this does not help, you can set your system's Bluetooth address manually in the client when creating a new Bluetooth connection - this circumvents the need for a device scan.

Service search fails

First, when a player adapter is running, check if the Remuco Bluetooth service is active: $ sdptool browse local Among others this should list an entry for each running player adapter. Here is an example when using Rhythmbox: Service Name: Rhythmbox Service RecHandle: 0x10007 Service Class ID List: UUID 128: 025fe2ae-0762-4bed-90f2-d8d778f020fe "Serial Port" (0x1101) Protocol Descriptor List: "L2CAP" (0x0100) "RFCOMM" (0x0003) Channel: 1 Profile Descriptor List: "Serial Port" (0x1101) Version: 0x0100 Some devices fail with the standard service/channel search. On the client you can edit Bluetooth connections to try alternative service/channel search strategies. Try a failsafe search! If even this does not help, try to manually set the channel of the service to connect to (in the example above it is 1) in the Bluetooth connection editor screen (see image on the right). Based on user feedback you have to manually set the channel on Blackberry devices. Server and client must use a channel ≥ 7! See the player adapter configuration instructions for how to set a fixed Bluetooth channel on the server side.

I'm still lost ...

Finally it is always a good idea to test Remuco on another computer or with another mobile device or both. Bluetooth problems mostly are caused by the Bluetooth stack on the computer or on the mobile device. Using Remuco in another environment helps to detect where the problem originates.

If all this does not help check if your specific problem is a known one.

Timeout while waiting for Hello message

This may have several reasons, however, some users with Bluetooth devices reported that this could be fixed by setting a fixed Bluetooth channel number (preferably not 1). See the section Service search fails above.

Incompatible client and server versions

The reason is probably because you installed a distribution specific package of Remuco and the distribution package has been updated but you did not install the corresponding new client on your device yet.

You find the server version at the beginning of a player adapter's log file, for instance ~/.cache/remuco/xmms2/log.

You can check the client version by issuing the System command in the client's Log screen.

What's that report tool for?

The tool remuco-report makes it easy for users to contribute to the list of Remuco compatible devices. It sends information about seen client devices to http://remuco.sourceforge.net/cgi-bin/report.

Before this tool submits any data, you get a chance to review the data to report.

How can I control the master volume?

The Remuco configuration file has some options to enable and configure master volume control instead of controlling a player's volume.

The information below is only relevant for Remuco ≤ 0.9.2.

If you prefer to control your system's master volume instead of a player's volume level, put a script called volume into the configuration directory of the corresponding player adapter, e.g. into ~/.config/remuco/banshee/. Alternatively, to use the master volume for all player adapters, put this script into ~/.config/remuco/

The volume script must behave as follows.

• Given no argument, it must print out the volume in percent.
• Given argument up, it must increase volume by some percent (5 is good value).
• Given argument down, it must decrease volume by some percent (5 is good value).
• Given argument mute, it must mute volume.

An example script can be found in the documentation directory of the Remuco package. This script uses the tool amixer. In most cases it should work out of the box. Otherwise just have a look into it for how to adjust it for your system.

Make sure the script is executable!

I have another question ...

Have you read the known issues? Please also check existing support tickets? If you don't find an answer there, ask a new question.