issues with initialization and closing

[landroni]

I would like to report two issues with RMPlayer.

First, and this is somewhat minor, it takes about 7sec between the start of a video on the desktop and the moment when VLC Remote on Android starts displaying the progress of the movie (and the remote becomes functional, generally). To reformulate, the script seems to wait 7sec before starting to listen to the 8080 port. Is this intended?

Second, and this is more problematic, closing the MPlayer window doesn't close down the script. What happens is that the ruby script keeps displaying request status messages, and moreover keeps listening to the 8080 port. To close down the script one needs to 'ctrl+c' in the console, which may or may not be available depending on how the programme was started. Could the script detect when MPlayer shuts down and exit gracefully including shutting down the port listening activity?

[peterseverin]

I don't use RMPlayer anymore so I'll just give you a few hints. The startup delay is probably caused by Webrick HTTP server. I used options such as DoNotReverseLookup that should have made it faster, but perhaps you should check that they are actually used. There are plenty of discussions on the web about speeding up Webrick.

I think that the fact the the script keeps running was intentional. The idea is that you can use Browse button in remote up and select a different movie file to play. To implement what you want I think you'll need a second thread that polls the status of the mplayer sub-process and exits the script when mplayer dies. Still you'll need to think how this will work with Browse function.

[landroni]

I see. Thanks for the hints. Unfortunately I do not have enough programming skills to tackle this by myself.

I wanted to slightly improve the documentation, though, so I'll send a pull request for that.