Introducing mvpmc

[jksmurf]

Hi martin

Wow, extraordinary piece of work-in-a-Dongle. Kudos. 1
I have queries & suggestion (10 Feb 07 Daily Build). I played around with a few of the other menus, changed VLC server IP (even though I don't run a aVLC server, yet ..)

1. The Music Client does not seem ready yet, just a funny sort of screen and when I went back out one time it crashed?
2. I power off each night so the next Recording Widget on the MVP doesn't disturb GBPVR IF I run GBPVR on the PC. When you power off it goes through the loading application stuff each time (maybe an option to hide the ugly stuff at some stage and just have a progress bar with "loading application" :-). The first time it reconnected to GBPVR immediately, 2nd time on attempt 18/30, 16/30 on the third. That whole process seems to take longer than the native dongle?
3. Any possibility that you can set it default to emulation mode, so wife can turn it on with green button and it just finds the GBPVR server, rather than manually choosing emulation mode (not sure how you'd change it back OUT of that, though... SCRAP THAT, I see you've done it in the Web Part...SO Darn GOOD, it has to become the default dongle!!

Just some thoughts..

k.

btw how good is that Web-access!! It's GREAT. I static-IP my MediaMVP (WRT54GS with Thibor 15c) to an IP that I give a name http://mediamvp.lounge/ ... Awesome!

[mvallevand]

1. The Music Client does not seem ready yet, just a funny sort of screen and when I went back out one time it crashed?

MClient is the Interface to SlimServer which might not be what you are looking for. I will pass on your comments to the developer, he just put a change into the nightlies.

The interface to multimedia files is just the file system browser. For this to be useful you would need to have files on a share or a UPnP server, but in /usr/share/playlist there is a file default.m3u that has some native streaming examples.

2. I power off each night so the next Recording Widget on the MVP doesn't disturb GBPVR IF I run GBPVR on the PC. When you power off it goes through the loading application stuff each time (maybe an option to hide the ugly stuff at some stage and just have a progress bar with "loading application" :-). The first time it reconnected to GBPVR immediately, 2nd time on attempt 18/30, 16/30 on the third. That whole process seems to take longer than the native dongle?

I'm not sure what is too bad about the login info. The nightlies do have on long string of data
to identify the source code so it can be rebuilt, if we find a problem. For a normal release it is just the release number.

One thing I would like to do is compare the login timings, do you run the dongle that sub distributes?

3. Any possibility that you can set it default to emulation mode, so wife can turn it on with green button and it just finds the GBPVR server, rather than manually choosing emulation mode (not sure how you'd change it back OUT of that, though...

I posted some instructions on this in the install thread, but no promises about the WAF yet.

Martin

[jksmurf]

MClient is the Interface to SlimServer which might not be what you are looking for. I will pass on your comments to the developer, he just put a change into the nightlies.

The interface to multimedia files is just the file system browser. For this to be useful you would need to have files on a share or a UPnP server, but in /usr/share/playlist there is a file default.m3u that has some native streaming examples.

Cheers, yeah I wouldn't use it, just an observation.

I'm not sure what is too bad about the login info. The nightlies do have on long string of data to identify the source code so it can be rebuilt, if we find a problem. For a normal release it is just the release number.

Don't get me wrong it's just reducing it so WAF is not affected.... :-)

One thing I would like to do is compare the login timings, do you run the dongle that sub distributes?

Nope, the latest shs version...

I posted some instructions on this in the install thread, but no promises about the WAF yet.

No worries about WAF, but those instructions about modifying the bin look a bot scary...any chance of that becoming web-page configurable?

k.

[mvallevand]

The first time it reconnected to GBPVR immediately, 2nd time on attempt 18/30, 16/30 on the third. That whole process seems to take longer than the native dongle?

I just thought of something about this, planning on how I was going to test this tomorrow. Are you saying that the Hauppauge dongle immediately reconnects to GB-PVR after a power off/power on for you? For me, the GB-PVR MVP Server always waits 20 seconds until I get one of these in the logs

MVP data taking too long, connection must have been dropped!

Anytime after these first 20 seconds, the connection is the typical 1 or 2 seconds.

Martin

[mvallevand]

No worries about WAF, but those instructions about modifying the bin look a bot scary...any chance of that becoming web-page configurable?

Actually you don't modify the bin, you just create a text file dongle.bin.config with a one line entry

mvpmc --startup emulate --emulate ?

In any case it is also web configurable. In the option "Startup Item:" select Emulation and then push the "Update Config" button. The trouble with this is it doesn't get saved and it is lost on a hard reboot. I have talked with the Hauppauge developers and we will be able to store all the mvpmc configuration options in flash, but it will be tested a lot before users will see it.

Martin

[jksmurf]

Are you saying that the Hauppauge dongle immediately reconnects to GB-PVR after a power off/power on for you?

It's reasonably quick tbh. The later H dongles have an server IP you choose. But yours worked well the first time and was also very quickafter restarting GBPVR. It was just subsequent loads. I was testing this as I use power off every day.

k.

[jksmurf]

Actually you don't modify the bin, you just create a text file dongle.bin.config with a one line entry

mvpmc --startup emulate --emulate ?

Ah ... OK. I'm just thinking for "general use" for an easy way to achieve this...

In any case it is also web configurable. In the option "Startup Item:" select Emulation and then push the "Update Config" button. The trouble with this is it doesn't get saved and it is lost on a hard reboot.

Yes, I saw and I tried this. It looked like the business.... (teh cat's pyajamas actually) but. it didn't save...

I have talked with the Hauppauge developers and we will be able to store all the mvpmc configuration options in flash, but it will be tested a lot before users will see it. Martin

Wow, Coolio!!

k.

[mvallevand]

It's reasonably quick tbh. The later H dongles have an server IP you choose. But yours worked well the first time and was also very quickafter restarting GBPVR. It was just subsequent loads. I was testing this as I use power off every day.

I don't see this quick restart at all, using the 1.51 dongle on an older model I get the Contacting Server message for the 20 second period it takes gb-pvr to reset. On the model H it is actually worse because once I get a failed to contact gui message. I end up in the setup screen which requires a key press to get out of the preferred server screen, which would even delay longer if I hit Ok and not Back because it writes to flash, and then I have to press even more keys to select Go on a wMVP.

This is really a theoretical problem because in reality there aren't many times that you will want to power off and on in the 20 second window but it is interesting how we see such different behaviour with the Hauppauge dongle.

Martin

[Lindsay]

I'm trying the latest nightly on a Vista m/c. The dongle loads OK and I can navigate around the menu but many functions don't work. LiveTV (reboots), music (nothing happens) , videos (reboots) don't work. Displaying photos, TV Guide, Find does work.

After a reboot, the first button press is swallowed.

But it does communicate under Vista which is a plus! However, the above problems don't make it a likely replacement just yet, unfortunately.

[mvallevand]

I don't see this quick restart at all, using the 1.51 dongle on an older model I get the Contacting Server message for the 20 second period it takes gb-pvr to reset. On the model H it is actually worse because once I get a failed to contact gui message. I end up in the setup screen which requires a key press to get out of the preferred server screen, which would even delay longer if I hit Ok and not Back because it writes to flash, and then I have to press even more keys to select Go on a wMVP.

jksmurf, as a follow up, when I configure gbpvr to auto start more then one server even the added 20 second delay goes away so I am not sure why you are seeing the problem you do.

Martin