PCH Pre-Ordered

[mvallevand]

Great!

After video playback stops it seems to take a few seconds before control returns to mvpmcx2, so try waiting 5 - 10 seconds after playback finishes, then press a key. According to your putty.log you didnt press a key after video playback completed - I can only guess you tried pressing it during this period after playback ends but before control returns to mvpmcx2?

The PCH player typically returns control very quickly, less than one second, but it is GBPVR that is not sending a screen refresh for several seconds after the video plays. Using mvpmc I was able to store the screen but this is not practical on the PCH platform.

Martin

[sub]

The PCH player typically returns control very quickly, less than one second, but it is GBPVR that is not sending a screen refresh for several seconds after the video plays. Using mvpmc I was able to store the screen but this is not practical on the PCH platform.

The control does seem to come back that quickly. Lindsay's putty.log is a prime example http://forums.gbpvr.com/showpost.php?p=2...stcount=86. I see the same behaviour here.

mvpmcx2 produce a message like '(*) em86remote: received command' every time the user presses a button on the remote. At the end of mono playing the file he tried to press a key but that message didnt appear, and as a result no key was sent to GBPVR, so no screen was sent.

Sure, ultimately we dont want to have to send any key force the screen refresh after playback, but for now users seem to have to wait a few seconds after video playback completes before they can press a key and have it recognised by mvpmcx2.

[mvallevand]

The control does seem to come back that quickly. Lindsay's putty.log is a prime example http://forums.gbpvr.com/showpost.php?p=2...stcount=86. I see the same behaviour here.

mvpmcx2 produce a message like '(*) em86remote: received command' every time the user presses a button on the remote. At the end of mono playing the file he tried to press a key but that message didnt appear, and as a result no key was sent to GBPVR, so no screen was sent.

Sure, ultimately we dont want to have to send any key force the screen refresh after playback, but for now users seem to have to wait a few seconds after video playback completes before they can press a key and have it recognised by mvpmcx2.

I agree that Lindsay is not sending a key like the right arrow I recommended, but I use the GBPVR logs to see what is sent after mvpmcx2 sends after the stop command when it gains controls and I don't see any screen refresh even when the logs indicate it was requested by the client.

Martin

[mvallevand]

PLS file below. There is also an mp3 file that won't play in WMP but I changed it to wma and while complaining about wrong format, WMP did play it.


song0|0|0|stream?f=D:\My Music\-02-Easy Listening\Bic Runga\Drive\01 Drive.wma|
song1|0|0|stream?f=D:\My Music\-02-Easy Listening\Bic Runga\Drive\02 Sway.wma|
...

Lindsay this playlist plays fine for me so unless it is the beta firmware I run, I suggest that there isn't a problem with the logic.

Code:

song0|0|0|stream?f=C:\My Music\-02-Easy Listening\Bic Runga\Drive\01 Drive.wma|
song1|0|0|stream?f=C:\My Music\-02-Easy Listening\Bic Runga\Drive\02 Sway.wma|
song2|0|0|stream?f=C:\My Music\-02-Easy Listening\Bic Runga\Drive\03 Hey.wma|
song3|0|0|stream?f=C:\My Music\-02-Easy Listening\Bic Runga\Drive\04 Bursting Through.wma|
song4|0|0|stream?f=C:\My Music\-02-Easy Listening\Bic Runga\Drive\05 Swim.wma|
song5|0|0|stream?f=C:\My Music\-02-Easy Listening\Bic Runga\Drive\06 Roll Into One.wma|
song6|0|0|stream?f=C:\My Music\-02-Easy Listening\Bic Runga\Drive\07 Suddenly Strange.wma|
song7|0|0|stream?f=C:\My Music\-02-Easy Listening\Bic Runga\Drive\08 Sorry.wma|
song8|0|0|stream?f=C:\My Music\-02-Easy Listening\Bic Runga\Drive\09 Heal.wma|
song9|0|0|stream?f=C:\My Music\-02-Easy Listening\Bic Runga\Drive\10 Delight.wma|
song10|0|0|stream?f=C:\My Music\-02-Easy Listening\Bic Runga\Drive\11 Without You.wma|

Martin

[sub]

I agree that Lindsay is not sending a key like the right arrow I recommended, but I use the GBPVR logs to see what is sent after mvpmcx2 sends after the stop command when it gains controls and I don't see any screen refresh even when the logs indicate it was requested by the client.

Yeah, I agree that it doesnt send any screen update until the first key. Thats not what I was saying though. I was saying it seems to take quite a while for mvpmcx2 to regain control after playback completes, and if the user press a key before that time then the key is swallowed, which is why lindsay didnt get a screen update even when he tried pressing a key after playback stopped. Its not something worth worrying about though.

Try the attached patch. It now sends a screen refresh when the GB-PVR receives the stop message.

[sub]

Thanks, guys, I have now discovered that the video does return after a wait. Also, will it be possible to make the loading of GBPVR a little less geeky? Can these rough edges be eliminated or are you too removed from the code?

Thats certainly the ultimate goal.

Your install seemed a bit more painful than other users, so I dont think yours was the typical experience. That said, there is a few setup complications at the moment:

- Most of the good PCH work has been done post 1.2.9, so currently the user has to apply patches to get this stuff working. This wil be resolved when I do the next release since this functionality will be rolled into the main release.

- Setting up mvpmcx2 current requires the user to edit scripts etc, mount shares etc. Syabas have indicated they'll add direct support for running user apps. We're hoping this will enable us to do something easier than what we have today. I suspect not though, and instead we'll solve it with some good instructions on exact steps to set it up.

Even in its current state, once the user has been through the current geeky process, its pretty easy to use - after starting the PCH, just click the GB-PVR link and it starts.

On the rough edges front, we're still working though stuff. If you'd tried it a few weeks ago you would have found a hell of a lot more rough edges (standard def UI, slower, problems play avi/mov files etc). For the specific screen refresh thing, try the patch above.

[Lindsay]

Thanks for reply. When I mentioned the geeky start up I was not referring to the initial setup but to the process required to get to the GBPVR screen after turning on the PCH. I will describe what I do and you can tell me if I am doing it wrong!

- PCH loads and after about 90sec the Start screen appears.
- Select 'Files' icon.
- Select Telnetd link.
- Press 'Return' key on remote.
- Select GB-PVR link.

(Tried selecting GB-PVR link without the telnet phase and the system hangs).

[sub]

I've done away with the need to run Telnetd by editing my gbpvr.cgi to:

Code:

#!/bin/sh

echo "Content-Length: 29";
echo "Content-type: text/html";
echo "";

#check if files have been copied
if [ -f /usr/bin/utelnetd ]
then
   #try to start telnet
   /etc/mvpmc/utelnetd -l /bin/sh -p 23 & >/dev/null
else
   #else copy and start telnet
   cd ~
   mkdir /etc/mvpmc
   mount -t cifs //192.168.0.22/mvpmc /etc/mvpmc/ -o username=guest,ro;
   cp /etc/mvpmc/utelnetd /usr/bin;
   utelnetd -l /bin/sh -p 23 &
   ln -s /lib/librmjpeg.so /lib/libjpeg.so.62
   ln -s /lib/librmzlib.so /lib/libz.so
   ln -s /lib/librmzlib.so /lib/libz.so.1
   ln -s /lib/librmzlib.so /lib/libz.so.123

fi

killall gaya
sh -c /etc/mvpmc/startmeup 2>/dev/null >/dev/null &

exit 0;

[Lindsay]

OK. That's what I figured I could do, too. Thanks for saving me the trouble!

[mvallevand]

Note that I don't support deviating at all from the survival instructions until after you get it working for many reasons,

- you have no idea what changes will be incorporated in future releases
- they could be incompatible with running other apps
- mod's won't be tested with new releases.
- it's one more thing for people to screw up.

As an example sub's script already totally messes up my documentation for running multiple PCH"s, explaining where to change ro to rw etc etc.

Martin