Originally Posted by TPeterson
It's clearly not just
the MyHD sw, since I failed to reproduce the error here and nobody else has reported seeing it. (Well, IIRC, Jacob said that he's seen something like it, but not the same thing because his sequencing error is only occasional and it goes away after restarting the app) Obviously, there's something consistently unusual about your installations. Let's figure out what that is and, if it's actually an MIT bug that you've exposed, get MIT to fix it.
When you said, "1.65 is also incapable of playing through an entire [movie] without the OSD messing up....", did you mean to say "1.66"? I also don't see that behavior here with either app version, BTW, so maybe that is another clue to this system-related problem.
Well, I had to go back and edit the other post.
1.65 played one movie correctly. Now it won't play anything, including that very same movie. Same behavior : 0000.ts, then 0009.ts, then 0099.ts, etc.
It does not go away if I reinstall the app, nor if I restart the computer.
It seems if I install a fresh WinXP, then MyHD, I get exactly ONE playback of a show, then the same behavior as above.
Same thing with the OSD display; it glitches about 1/2 way through the show, thereafter it's glitched. Only restarting the PC fixes it. This happens with 1.65. With 1.66 I get multiple plays (albeit with the sequence problem) before it glitches, if at all.
As I said, it's clearly messing up the filenames. There's a repeatable, definite pattern : take the sequence number, rotate the digits one spot to the left, add a "9". Ie: 0017.ts becomes 0179.ts.
This happens no matter what PC I try it on (both amd and intel - I've tried this on every single PC I own). The only common denominators are the MDP software, and WinXP SP2 (I don't own another version of windows).
This is driving me nuts. I can't play a darned thing anymore unless I use hdtvtompeg2 to write it out to a single file.
If it wasn't for the fact that the MyHD is, by far, the most capable card I've ever owned or used, I'dve long since switched to another product by now ... :-(
Is there NOTHING that can be done to activate a debug mode, run a special debug version or anything like that?
I would like to help fix things, but there's only so much time I have for reformatting computers, installing OS's and other troubleshooting. I spent all day working on this to come to one result : it doesn't work no matter what I try.
The release software that's available is simply not going to give us whatever information we need to find this bug.