Can you please contact me on Yahoo Messenger (firstname.lastname@example.org
) to find out what is happening ?
Things should go like this usually:
- insert a disc in the drive unit
- the disc drive device will detect the disc type and fire a DCE Event with this type on the DCERouter.
- a Router plugin will detect this event and send back a command to the Disk Drive to "mount" that DVD. This command will send back a "xine formatted" url to the plugin (the url looks somthing like dvd://localhost:5152/ ).
- The plugin will use that url and locate a Xine Player device on the same media director that launched the original MediaInserted event.
- After it located this it will send the Play Media command to the Xine Player device. This should appear on the screen and play the DVD.
Now there are a couple of places where things can go wrong but in a good installation it should be automatically. One of the most fragile places would be the DVD mount part (this uses dvdcss if it is installed on the machine to mount the DVD). If the dvdcss is not installed then this step might fail. One quick way to check this is to see if there is a network server running on the ports starting with 5150 20-30 seconds after the Media Inserted event is fired.
Anotehr place where you can look is to see if tehre are any coredumps in the /usr/pluto/coredump. If there are cores for dvdcss_server then you
hit a bug that is solved in the 18.104.22.168 build (upcoming soon). The quick solution for this would be to change the mountDVD*.sh script in the /usr/pluto/bin and add a ulimit -n 128 somewhere before the script launches the mount command.
Or you can open a secure tunnel to our host and let us take a peek :-).
The procedure for this is:
- open the pluto-admin site (http://<your-core-ip/pluto_admin )
- go to 'wizard' 'security' 'outside accesss'
- put a password
- click ok
- send the password and the installation ID to one of our representatives and we will take a look and try to fix your setup.