Yes, I'm still running a "vintage CE", 0x339, the last one with MRV in it.
Like many others, since the 'universal playlist' went in, I started having problems with MRV and receiver stability. My receivers would go about 2.5-3 days before MRV would start splatting like crazy to an unwatchable point, then MRV would stop working on one box or the other. Sometimes turning MRV on and off would fix it, but in general I needed a reboot. On occasion one box would freeze or reboot itself.
My network is two HR20-100's with cat5e to a gigabit switch. Pretty simple.
So even though this isnt a current CE, I thought it'd be interesting to try removing complexities from the arrangement to see what things had effect. I know the Directv guys are still working on MRV and others like me are sticking with the MRV release.
After taking things like the phone line away, changing out switches and wiring and trying IR vs RF remote control, nothing improved or changed the results.
My last plausible option was to transplant the disk from the external esata chassis into the HR and eliminate the esata arrangement altogether.
It seems to have worked. One box has been running for 5 days and the other for 4. Neither has needed a reboot or frozen up. MRV hasnt gone dead on either box. I still get splats but they're fewer and shorter, maybe one or two every few minutes for a second or so.
I'd be suspicious of the esata, but I have zero local playback problems except for the occasional well known "briiip/zipper". No problems with directv2pc. And the first rounds of MRV CE's before the UPL worked fine for me.
So it seems that there is some sort of combination glitch between the most recent MRV release and an esata drive. Maybe this explains why some folks have/had no problems with it while others did/do have problems.
To wrap things up, I put some drives in the enclosures and put them on a desktop machine using the same esata cables and had them running tests for the better part of a day without a single reported glitch.
Unfortunately its not a solution that everyone is going to want to implement...
Like many others, since the 'universal playlist' went in, I started having problems with MRV and receiver stability. My receivers would go about 2.5-3 days before MRV would start splatting like crazy to an unwatchable point, then MRV would stop working on one box or the other. Sometimes turning MRV on and off would fix it, but in general I needed a reboot. On occasion one box would freeze or reboot itself.
My network is two HR20-100's with cat5e to a gigabit switch. Pretty simple.
So even though this isnt a current CE, I thought it'd be interesting to try removing complexities from the arrangement to see what things had effect. I know the Directv guys are still working on MRV and others like me are sticking with the MRV release.
After taking things like the phone line away, changing out switches and wiring and trying IR vs RF remote control, nothing improved or changed the results.
My last plausible option was to transplant the disk from the external esata chassis into the HR and eliminate the esata arrangement altogether.
It seems to have worked. One box has been running for 5 days and the other for 4. Neither has needed a reboot or frozen up. MRV hasnt gone dead on either box. I still get splats but they're fewer and shorter, maybe one or two every few minutes for a second or so.
I'd be suspicious of the esata, but I have zero local playback problems except for the occasional well known "briiip/zipper". No problems with directv2pc. And the first rounds of MRV CE's before the UPL worked fine for me.
So it seems that there is some sort of combination glitch between the most recent MRV release and an esata drive. Maybe this explains why some folks have/had no problems with it while others did/do have problems.
To wrap things up, I put some drives in the enclosures and put them on a desktop machine using the same esata cables and had them running tests for the better part of a day without a single reported glitch.
Unfortunately its not a solution that everyone is going to want to implement...