Quote:
Originally Posted by
rathwine 
It could easily be driver/hardware and net framework incompatability. This is an old computer, running out dated hardware, but was working great until the software updates. That is one of my favorite things about this card. It works great in my old pc's, and records my tv for me automatically. Thanks, Troy
I like the fact that the card seems to leave the CPU alone for the most part and does its processing in the onboard chip(s). I do find that I have less glitches when I have less apps/processes/??? running. If I have a dropout (audio or video+audio) I often rewind 10 seconds to see if it's repeated. If it is repeated, I know there's nothing I can do about it at that point and that it's in the recording. However, if it is not repeated I know that some other process(es) is/are messing with the MyHD playback and shutting down competing code is apt to clean up my playback. I use the freebie EndItAll to close down all the processes/programs that look to me dispensable and playback is usually much better thereafter. Of course, this is a PITA, but don't know how else to deal with this syndrome. The machine is reasonably powerful:
Gigabyte GA-K8n Pro motherboard
AMD Athlon 64 3200+ (socket 754, FSB1600, E6, Venice, 90nm, L2-512KB)
BFG 6600 GTOC AGP video card
2 sticks Crucial 1GB PC3200 400MHz 184-pin DDR Memory - CT12864Z40B, 2 GB total
Corsair vx550w PSU
USR Model 2977 PCI hardware modem
Hercules GTXP soundcard PCI with breakout box
MyHD HDTV 120 HDTV PCI
MyHD HDTV 120 HDTV daughterboard
Windows XP SP3
I've got several HDs in the machine, but am currently recording (I have been timeshifting lately, exclusively) to my one SATA drive. The MB is pretty old and the SATA controller an early generation. I used to (and still do occasionally) have a vexing problem wherein I experience a split second glitch every 20 seconds when the changeover occurs from one 20 second timeshift file to the next, but lately it happens only rarely. I have no idea what precipitates it. The glitches are certainly in the recorded files, not the playback, so when it happens there's nothing I can do about it but tolerate it or discarding the recording as unwatchable.