The Official "Working SageTV + Ceton Firmware + SageDCT Version Combinations" thread

[Deacon Crusher]

Actually, it's a little stranger then I thought.

I have 3 of my 4 ceton tuners configed in Sage. And right now, 2 have been marked as Active = False, but one has successfully made 3 recordings today.

Why would that happen?

Thanks

[ThePaladinTech]

This is a total guess... but I've had similar issues with the HVR-2250.

The card has a four way splitter in it to go to the four tuners, some tuners get a different signal quality then others. (too weak or too strong both seem to be able to cause problems on the 2250) - So I guess I'd check signal strength

[Endymion]

Originally Posted by Deacon Crusher

Actually, it's a little stranger then I thought.

I have 3 of my 4 ceton tuners configed in Sage. And right now, 2 have been marked as Active = False, but one has successfully made 3 recordings today.

Why would that happen?

Thanks

I had a somewhat similar issue when I first tried to use SageDCT v 1.3 or 1.4... Usually 1 or 2 of my Ceton tuners out of the 4 would be marked as non-working in SageTV, so I would only have 2 or 3 usable tuners. Which tuner was inactive would change on reboot or restarting SageDCT and things like that.

So I went back to SageDCT v1.1 and just reset the service every few hours (because I got a horrible memory leak with it). I moved my server to another location (as I got an HD300 a week before the acquisition), and for grins and giggles I uninstalled SageDCt v1.1, and installed v1.4. It now works just fine, all 4 tuners there and working! As far as I can tell, the only difference is that previously I had the SageDCT service starting using my user credentials. Now it runs as a SYSTEM service. I don't recall having made any other changes. Not sure if that helps at all.

[Deacon Crusher]

So, looked at SageDCT which is of course running on the same box as my Ceton (sage server on another box.)

When I go to the Test tab and run a test on a encoder that is associated with a tuner that is marked bad in sage like

127.0.0.1:6972 the response I get is

No connection could be made because the target machine actively refused it 127.0.0.1:6972

When I do the same test on a tuner that is still marked fine in Sage it works fine. I then restarted sagedct and the problem stays the same. Nothing appears in the Ceton logs.

Curiouser and Curiouser as someone once said. Seems like maybe windows firewall or ??

Any ideas on how to troubleshoot?

Thanks

[Deacon Crusher]

actually, after that last sagedct restart the problem was the same for a few minutes and then it got worse, suddenly couldn't successfully test against any tuner and then it turned out the sagedct service wasn't running at all. Started it and then could successfully test against all 4 tuners again and went to sage and it now says all 4 tuners are fine again.

So, problem is temporarily resolved by restarting SageDCT 3 times???

[Deacon Crusher]

Sage actually crashed today when this problem recurred. Had to go to services control panel to fix/restart sagedct.

Then Sage was fine again.

[splicer]

This doesnt look right to me, after looking at other post it seems some info is missing in the top box. I have configured the Ceton card I can tune channels in WMC but cant seem to get things going in sage.

In sage I can see the tuners but cannot configure them. Any help would be greatly appreciated!!!

Phil,

[babgvant]

^^^
That is what you should see.

[splicer]

Thanks at least Im good to here.

Why am I having problems here then? This is on a local machine?
http://i533.photobucket.com/albums/e...phil/crop1.png

[splicer]

All Fixed, Unistalled Reinstalled SAGTV

[The Truth]

Originally Posted by Deacon Crusher

Actually, it's a little stranger then I thought.

I have 3 of my 4 ceton tuners configed in Sage. And right now, 2 have been marked as Active = False, but one has successfully made 3 recordings today.

Why would that happen?

Thanks

DONT YOU NEED YOUR SERVER TO BE RUNNING WINDOWS 7 for the centon to work... that could be your problem

[AlphaCrew]

Andy.. Heeeeeeelp...

Updated to the latest version of SageDCT (1.9) and have a strange audio stream issue.

This is how I updated:
1) Stopped Sage Service.
2) Uninstalled SageDCT 1.4
3) Installed SageDCT 1.9
4) Used the SageDCT Utility to statically assign my current tuner ports in the SageDCT Utility (instead of using SageDCT defaults) so I would not have to modify my SageTV Prop. File.
5) Check to make sure all ports saved correctly and match my existing sage.prop... file.
6) Rebooted machine.

Every thing seems to work (slightly longer tuning time) but every so often I will get a recording that has multiply identical audio streams mux in. This causes WMP to throw an error when opening.

This was no big deal at first, because I have created an elaborate repair system (using VRD QuickSteam Fix) for all my completed recordings because of the SageDCT muxing flaws.

BUT..

What I have found is that after QSFing some of the files they will now play in WMP, but will have no audio.

I don't ever remember having more then one audio stream mux in by SageDCT 1.4 or lower.

Any Idea's Andy?

[babgvant]

Originally Posted by AlphaCrew

Andy.. Heeeeeeelp...

Updated to the latest version of SageDCT (1.9) and have a strange audio stream issue.

This is how I updated:
1) Stopped Sage Service.
2) Uninstalled SageDCT 1.4
3) Installed SageDCT 1.9
4) Used the SageDCT Utility to statically assign my current tuner ports in the SageDCT Utility (instead of using SageDCT defaults) so I would not have to modify my SageTV Prop. File.
5) Check to make sure all ports saved correctly and match my existing sage.prop... file.
6) Rebooted machine.

Every thing seems to work (slightly longer tuning time) but every so often I will get a recording that has multiply identical audio streams mux in. This causes WMP to throw an error when opening.

This was no big deal at first, because I have created an elaborate repair system (using VRD QuickSteam Fix) for all my completed recordings because of the SageDCT muxing flaws.

BUT..

What I have found is that after QSFing some of the files they will now play in WMP, but will have no audio.

I don't ever remember having more then one audio stream mux in by SageDCT 1.4 or lower.

Any Idea's Andy?

SageDCT doesn't mess with the TS packets. It just writes what is received from the DCT.

[AlphaCrew]

Originally Posted by babgvant

SageDCT doesn't mess with the TS packets. It just writes what is received from the DCT.

I just don't understand why this is happening.. It didn't start until I upgraded, and I have made no changes to my system. I have to believe that it has to do with SageDCT 1.9 in some way, shape or form...

[Naylia]

Hey guys,

Just installed Ceton tuner and SageDCT 1.9 today. Latest firmware, drivers, etc.

All check marks are green in Ceton control panel.

Windows Media Center can see all 4 tuners and playback video without issue.

SageDCT gets responses like "1" or "OK" when I use the Test tab to interact with the tuners.

However, when I add a tuner in SageTV and then run a channel scan, all I get are 200 "OK-OK#" channels. OK-OK1, OK-OK2, etc.

Any thoughts? I'm starting to think about backing up my wiz.bin and reinstalling SageTV but I don't really want to.

[Naylia]

Update...backed up Sage and tried against a clean install that had no other tuners or anything setup. Ran into the same issue.

Another note - I also can not successfully preview any of the OK-OK channels (or then they actually would be OK!).

Channels are showing up as Copy Freely in the Ceton web control panel so that's not the problem.

[babgvant]

Originally Posted by Naylia

Hey guys,

Just installed Ceton tuner and SageDCT 1.9 today. Latest firmware, drivers, etc.

All check marks are green in Ceton control panel.

Windows Media Center can see all 4 tuners and playback video without issue.

SageDCT gets responses like "1" or "OK" when I use the Test tab to interact with the tuners.

However, when I add a tuner in SageTV and then run a channel scan, all I get are 200 "OK-OK#" channels. OK-OK1, OK-OK2, etc.

Any thoughts? I'm starting to think about backing up my wiz.bin and reinstalling SageTV but I don't really want to.

The current rev doesn't support channel scanning.

[Naylia]

Ah, so just load the standard channel listing and work off of that? Gonna go try that right now.

[Naylia]

So sweet.....it works so good!!!!

Thanks for all your work on this!

[babgvant]

Originally Posted by Naylia

Ah, so just load the standard channel listing and work off of that? Gonna go try that right now.

Yes, for now. 2.0 will have an experimental feature which at the very least will fix the "OK" problem, but should also remove duplicate channels and provide rudimentary support for trimming out SD channels.

Ideally, I'd like to get a list of channels that are actually in the lineup (so if you don't subscribe to HBO I could remove those) from the DCT but I haven't had much luck figuring out how to get that information from the device.