A few things I've noticed with the MVP...
I found it to be more stable with a quicker PC. Initially, I used a dedicated P3/800 with 640megs, all video stored on network shares from a linux box.
It was stable enough, but I'd occasionally get MVP reboots when stopping playback (the most common problem), as well as FF/skip.
I noticed that when using my P4/2.4 during testing, I never had any problems.
I recently upgraded the GBPVR PC to an old Athlon 1600 with 512M and the number of resets are much less. This past weekend I relocated the drives from the linux box to the GBPVR box, and that helped a bit more. Now FF/skip is more responsive. I've not seen a "reset" since making these changes.
I think alot of it has to do with the sensative timing between the MVP and the PC. If the PC takes too long to do something, the MVP resets.
The other trick I use to help with the wife factor, is run 1 more MVP server process than you need. ie; if you have 1 MVP, have GBPVR start 2 MVP servers. When the MVP does do a reset, it'll often latch onto the 2nd one, while the 1st is bust resetting (or restarting if gbpvr crashed).
I noticed this one because I have 2 MVP's, though they're rarely in use at the same time. I noticed that having an available GBPVR server "waiting", the MVP resets are much less painful.
I've considered hacking around in the dongle.bin to see if that "timeout" setting is changeable without re-compiling kernels and such. It seems like if the timeout on the MVP was a few seconds longer, it would be far more stable.
I found it to be more stable with a quicker PC. Initially, I used a dedicated P3/800 with 640megs, all video stored on network shares from a linux box.
It was stable enough, but I'd occasionally get MVP reboots when stopping playback (the most common problem), as well as FF/skip.
I noticed that when using my P4/2.4 during testing, I never had any problems.
I recently upgraded the GBPVR PC to an old Athlon 1600 with 512M and the number of resets are much less. This past weekend I relocated the drives from the linux box to the GBPVR box, and that helped a bit more. Now FF/skip is more responsive. I've not seen a "reset" since making these changes.
I think alot of it has to do with the sensative timing between the MVP and the PC. If the PC takes too long to do something, the MVP resets.
The other trick I use to help with the wife factor, is run 1 more MVP server process than you need. ie; if you have 1 MVP, have GBPVR start 2 MVP servers. When the MVP does do a reset, it'll often latch onto the 2nd one, while the 1st is bust resetting (or restarting if gbpvr crashed).
I noticed this one because I have 2 MVP's, though they're rarely in use at the same time. I noticed that having an available GBPVR server "waiting", the MVP resets are much less painful.
I've considered hacking around in the dongle.bin to see if that "timeout" setting is changeable without re-compiling kernels and such. It seems like if the timeout on the MVP was a few seconds longer, it would be far more stable.