Getting pixels when recording with Ceton InfiniTV 4 PCIe

[rdefino]

I have been running sage for years, but since I installed this tuner, back about 2yrs ago, I get freezes and pixels at times when recording with it. Not all the time, but it happens real bad at time, or very little. No rhyme or reason.

But my HDpvr that is recording from my set top box have never had this issue. So I figure the signal coming in is good.

Ceton was not so helpful since I'm on sagetv they don't support it.

You think moving to the Ceton InfiniTV 6 ETH would help since it's usb? Or do you think it's not the pci card itself?

Just wondering if anyone has any thoughts.

Thanks

[KryptoNyte]

Have you checked the signal levels and compared them against what Ceton recommends for an optimal range? At some point, you have at least one splitter in there, and sometimes you have to try different splitters and cables if the signal appears to be a problem. If I can repeat the problem on command, I've found that Time Warner will typically just come out for no fee and check the signal levels off each cable and make onsite recommendations.

I have found that STB's seem to negotiate a lower signal better than the cablecard solutions, so just because the STB doesn't act up much doesn't mean there isn't a problem that may affect the cablecard. Cable companies make changes on their end all the time, and it can affect signal on a system that has been working perfectly without any changes over time.

Probably start here;

http://cetoncorp.com/support/index.p...evel-explained

[rdefino]

Thanks for the reply and link.

I used ceton signal app and it all looks to be with in their specs.

Any other thoughts on how I can trouble shoot this?

thanks

[KryptoNyte]

When I setup my Ceton pcie with the SageDCT software, I only assigned three of the four tuners to Sage. The fourth tuner I assigned to Windows Media Center, so that if I had any problems in Sage, I had a control [in WMC] that I could compare to and see if it was a global problem, or just a Sage issue. I also used WMC to schedule my favorite programs as a temporary backup while I was getting comfortable with the setup in Sage.

If possible, reserving one tuner for WMC might save you some time in zeroing in on the problem during troubleshooting.

If you haven't already, make sure that you're running the most recent SageDCT, which as I understand it, is using a more current version of ffmpeg (I'm assuming your using the ffmpeg option instead of "dump"). I see that Andy now has a 2.7.4, and I have no idea how that is different than 2.7.3 (which was an ffmpeg only upgrade from 2.7.2). Here's the link to the 64bit version (assuming you're running on 64bit windows):

http://babgvant.com/files/folders/li...ntry21866.aspx

On second thought, if you are using ffmpeg, try using the "dump" method instead, if your system allows, and see if the problem is eliminated (which would quickly determine if the issue is ffmpeg).

[KryptoNyte]

Okay, it appears that SageDCT 2.7.4 includes the registry fix for HDHomerun Prime tuners, so Ceton users should be unaffected.

[rdefino]

So I switched to "dump" and it seems the issues are gone. What's the difference between using ffmpeg and Dump?

Now it seems ffmpeg is the issue. How do I go about fixing it. Or is it needed?

Thanks

[Tiki]

Dump basically takes the stream exactly as the cable card tuner receives it and saves it to a file with no manipulation.

FFMpeg re-muxes the file before saving it.

Re-muxing can sometimes fix errors or anomlies in the stream that might cause Sage trouble during playback. For most people, this feature was added because shows recorded from some stations on some providers (mostly Comcast, I think) would sometimes refuse to play back on Sage Extenders (would get No Signal) or other weirdness.

It's also possible to use FFMPEG to completely transcode the program to a different format, but SageDCT does not currently do that.

[KryptoNyte]

If you go with the dump method, you do need to keep an eye on your recordings. As Tiki said, it still records, and VLC will play it, but Sage devices can't render some recordings. This usually only happens on a handful of channels (I have seen it happen on Charter also), and it's sporadic on the offending channel, a channel will work one day, but not the next.

[rdefino]

Thanks for the replies everyone.

How can I figure why ffmpeg is causing the issues? How can I go about fixing it?

thanks for any help.

[KryptoNyte]

What version of SageDCT are you running?

If the dump method works for your system, then it's preferable to use it instead of the ffmpeg option. I would test dump for a couple weeks to see if it creates any bad recordings.

[rdefino]

Running 2.7.0.2.

I know there is another version out, but get a little nervous gadding it. Seems some others have issues with it.

[KryptoNyte]

Per this page;

http://babgvant.com/blogs/andyvt/arc...T/default.aspx

if you have 2.7.2, then you might consider the ffmpeg update from here;

http://babgvant.com/blogs/andyvt/arc...dct-2-7-3.aspx

Andy mentions there that you could apply them directly from that download (32 or 64 bit) which is equivalent to upgrading to 2.7.3. This would mean that you could locate and move the old files into a temporary directory, and then try the new files.

Other things to try;

- Swap out any coaxial cables, and any coaxial splitters between the cable service and the sage box. If that's too much work, disconnect and physically move the Sage box to the cable service right where it enters the house and see if pixelation persists.
- Shutdown the SageTV Service and assign the fourth tuner to Windows Media Center and see if it exhibits the same pixelation problem in WMC.
- Call the cable company to see if they can come out and check the signal.

[KryptoNyte]

Remove and re-insert the cablecard. Open up the machine and remove and re-seat the Ceton pcie card. Request a cablecard replacement from the cable company (perhaps you could remind them to bring another when they come to check signal). Run a full scan on the hard drive that Sage records to.

[KryptoNyte]

... just to reiterate, if the "dump" method isn't experiencing any problems, ignore all my posts and just continue using the dump method.