| Doors Install Instructions | ||
|---|---|---|
| Prev | ||
Problem: Upon starting the Midi File Player, you get the error: 'Error: cannot open /dev/sequencer2 (fd=-1)'
Solution: MIDI is not set up correctly, or is already in use. See seq2test for more help.
Problem: Starting the Midi File Player hangs at this line:
Searching for Controller... |
Or the User Interface produces this error:
UiUtil: Could not find the Controller: java.io.InterruptedIOException: Receive timed out UserInterfaceServer: Could not connect to Controller |
Cause: The Controller has not been started
Solution: See the Controller section on how to start the Controller. Then restart the MIDI File Player.
Cause: The broadcast packet from the MIDI File Player cannot reach the Controller
Solution: See the section on Finding the Controller in Routed Neworks.
Problem: Upon starting the Midi File Player or the User Interface, you get the error: 'Error sending request to 255.255.255.255: Network is unreachable'
Solution: Your network setup does not permit a broadcast message to be sent to 255.255.255.255, ie. typing 'ping 255.255.255.255' will also result in a network unreachable error. To permit this, type the following commands:
route add -host 255.255.255.255 dev eth0 |
If you get the error : '255.255.255.255: Unknown host', try adding the following entry to your /etc/hosts file:
255.255.255.255 bdcast |
Problem: Upon starting the Midi File Player, the Controller only registers the first Device, and the Midi File Player hangs at this point:
Using config file generalmidi.config Looking for IorServer at 255.255.255.255:17125 Found Controller! Registering devices |
Cause: The Controller returned an invalid CORBA header, because of a bug in the Java VM.
The only trusted solution at present is to reinstall ORBit 0.5.12 from the source code, applying a patch to work around the invalid header. This is explained in installing ORBit. If you have success with Orbit > 0.5.12 or JVM > 1.3 please tell me.