PDA

View Full Version : OSD Screen speedup



mvallevand
2007-04-07, 11:28 PM
I have uploaded a new alpha dongle which thanks to Sub's guidance should prove to be much faster for the normal emulation mode screen display Because of these Hauppauge specific changes, I don't expect screen displays to be much different then the Hauppauge dongle, except when the forced pause on the remote key happens every 10 seconds to avoid collisions and increase stability.

I don't know where Sub finds the time to do all he does, but I am grateful.

This dongle (hopefully) has also fixed the PAL start up so the blue mvpmc splash should look okay on PAL TV's. I can't test PAL right now so feedback on this is welcome. If the splash is still distorted, you probably have to load the Hauppauge software and dongle and store the PAL setting in flash using their Setup option. Some of you might want to change the default aspect ratio too. The splash is onscreen before mvpmc and the config are loaded so mvpmc's command line PAL option will not make difference.

Martin

HtV
2007-04-07, 11:39 PM
Sounds good everything.
I'll try it out tomorrow, nothing planned tomorrow:) , gone get some sleep first.:)

pBS
2007-04-08, 02:00 AM
except when the forced pause on the remote key happens every 10 seconds
Martin

what does that mean?

sub
2007-04-08, 02:23 AM
I just gave the new dongle a go. Much quicker. Good job!

mvallevand
2007-04-08, 03:05 AM
what does that mean?

" except when the forced pause on the remote key happens every 10 seconds"

It's a bit technical, but the dongle and gbpvr exchange a 2 byte handshake message on the GUI tcpip socket every 5 or 10 seconds depending if video is playing. I have determined that the returned handshake message can collide or interupt other messages being sent on the same socket and this was causing most of the failures in mvpmc. To prevent the possibility of collision, each 9.5 seconds I won't allow a keystroke to be passed until either the server message is returned, or worst case 1.5 seconds later but the server so that any resulting screen change doesn't get interupted. I'm still playing with different logic ideas, but this seems to be working.

I tested using ML2 because I could stream music and switch screens quickly with the colour button allowing lots of chance for collision. The Hauppauge dongle definitely handles it differently but still has problems. It can crash to the blue Hauppauge screen on a collision although more typically it just seems to die for several seconds as some kind of reset occurs.

Martin

mvallevand
2007-04-08, 03:28 AM
I just gave the new dongle a go. Much quicker. Good job!

Thanks for your help, implementation was easy yet from the mvpmc source code I never would have figured this out. What is amazing is the fact the old code was literally doing millions of computer operations unnecessarily for each screen update and it even worked.

Martin