SageMCTuner - anyone have this working with cablecard?

[babgvant]

Originally Posted by xj-boonie

Still get some, but not as much. I enabled verbose logging. What's the best way to get you the log file?

Hold off for now. I'm in the middle of switching to a different UPnP stack and fixing a bunch of issues.

Hope to have a new build out sometime next week.

[AlphaCrew]

Originally Posted by babgvant

Hold off for now. I'm in the middle of switching to a different UPnP stack and fixing a bunch of issues.

Hope to have a new build out sometime next week.

Andy You are my hero

Sending some cash your way.... , why..." Just because... "

[babgvant]

Originally Posted by AlphaCrew

Andy You are my hero

Sending you some cash your way.... , why..." Just because... "

Might want to hold off on that too, I haven't had a chance to look at alternate ways to receive the data yet.

[AlphaCrew]

Originally Posted by babgvant

Might want to hold off on that too, I haven't had a chance to look at alternate ways to receive the data yet.

Doesn't matter, you deserve it.

[MickBurke]

Couple questions:
Does this work reliably with FIOS?
Has anybody used this with the Ceton InfiniTV 4?
Do you need a special cable card for the Celton quad tuner?

I REALLY want to get rid of the three HD boxes that I;m renting each month from Verizon!!!

Any input is appreciated!

mick

[babgvant]

Originally Posted by babgvant

Hold off for now. I'm in the middle of switching to a different UPnP stack and fixing a bunch of issues.

Hope to have a new build out sometime next week.

New build is out; doesn't have the resource leaks that I was seeing w/ the original UPnP stack, but it's quite likely that I introduced new issues when changing it over.

Make sure you get the latest drivers/firmware for the Ceton card when using this rev.

[AlphaCrew]

Originally Posted by MickBurke

Couple questions:
Does this work reliably with FIOS?
Has anybody used this with the Ceton InfiniTV 4?
Do you need a special cable card for the Celton quad tuner?

I REALLY want to get rid of the three HD boxes that I;m renting each month from Verizon!!!

Any input is appreciated!

mick

Q1) I think it depends on where you are located. It (Ceton InfiniTV 4) works VERY well with FiOS in the greater Baltimore area. Very few channels that are > 0x00 (Copy Protected).

Q2) I will assume you mean Sage with the Ceton InfiniTV 4: Personaly I have not had good results with either solution useing SageTV and the Ceton.

Although I'm not using it like many are here. I already have video streamers though out the house, so I need a compliant MPEG2 file. Because the solutions discussed in this thread can't seem to provide a stable MPEG2 File at this time, I have had to resort to using WMC7. WMC7 produces perfect files 99.5% of the time, so converting them to MPEG2 is trivial.

Q3) You do need a CableCard from Verizon in order to do anything (even ClearQAM) with the Ceton.

[Gustovier]

Now that ceton orders are caught up I'm thinking about going this route. I have comcast in Chicago. And I think pretty much every channel will work except the premiums(isn't there a site to validate the copy flags?) But is this now a stable option to pursue? How fast are the channel changes now? Thanks for the help

[babgvant]

Originally Posted by Gustovier

Now that ceton orders are caught up I'm thinking about going this route. I have comcast in Chicago. And I think pretty much every channel will work except the premiums(isn't there a site to validate the copy flags?) But is this now a stable option to pursue? How fast are the channel changes now? Thanks for the help

I'm in Chicago using Comcast. I don't have any premiums so I can't speak to that, but every channel (Digital Premier + Sports Package) in my lineup I've tried has worked.

[LehighBri]

Originally Posted by babgvant

New build is out; doesn't have the resource leaks that I was seeing w/ the original UPnP stack, but it's quite likely that I introduced new issues when changing it over.

Make sure you get the latest drivers/firmware for the Ceton card when using this rev.

I'm using the latest beta Ceton drivers and was using SageDCT 1.1 with no issues. I then upgraded to SageDCT 1.2 and while it still works, it seems like there is a much longer lag in how long it takes to tune channels.

Should this be expected or is there something wrong here that I can help debug?

[Mythikal]

Originally Posted by LehighBri

I'm using the latest beta Ceton drivers and was using SageDCT 1.1 with no issues. I then upgraded to SageDCT 1.2 and while it still works, it seems like there is a much longer lag in how long it takes to tune channels.

I'm seeing the same thing. Channel changes take twice as long with the new version.

[Endymion]

Originally Posted by babgvant

New build is out; doesn't have the resource leaks that I was seeing w/ the original UPnP stack, but it's quite likely that I introduced new issues when changing it over.

Make sure you get the latest drivers/firmware for the Ceton card when using this rev.

Andy, I noticed today that I had some slowdowns in the Sage GUI and some odd moments in show playback where it would sound all Max Headroom for about a second... So I got to looking and SageDCT was eating up 500+MB of memory, and sitting at around 30% CPU usage with no recordings.

So I hopped on here and saw you had a new version out that mentioned resource leak fixes. I updated by uninstalling 1.1, installing 1.2, and then rebooting. After installing 1.2, the 4 tuners showed as not working in the video source setup, and doing anything there, like changing the EPG or channels, results in a circle of death for at least 20 seconds. Sage also said that no tuners were available when I tried to tune to a channel that the Ceton was used for. I rebooted, re-did the .properties, etc. No change, still couldn't tune, still got the circle of death on changing tuner properties, etc.

I then went back and reinstalled SageDCT 1.1. No reboot, just uninstalled 1.2, then installed 1.1. Now everything is working great.

So... not sure if I'm upgrading from 1.1 to 1.2 wrong, or what. Any ideas? I do have the latest Ceton drivers.firmware.

[babgvant]

Originally Posted by LehighBri

I'm using the latest beta Ceton drivers and was using SageDCT 1.1 with no issues. I then upgraded to SageDCT 1.2 and while it still works, it seems like there is a much longer lag in how long it takes to tune channels.

Should this be expected or is there something wrong here that I can help debug?

1.2 is slower. I hope to make it slightly faster in 1.3, but I may not be able to depending on what the root cause is.

[LehighBri]

Originally Posted by babgvant

1.2 is slower. I hope to make it slightly faster in 1.3, but I may not be able to depending on what the root cause is.

Let me know if you need some help to debug/identify the root cause. And what was the tradeoff for slower performance/why was it required? Improved stability? etc? Just trying to understand.

[babgvant]

Originally Posted by Endymion

I updated by uninstalling 1.1, installing 1.2, and then rebooting. After installing 1.2, the 4 tuners showed as not working in the video source setup, and doing anything there, like changing the EPG or channels, results in a circle of death for at least 20 seconds. Sage also said that no tuners were available when I tried to tune to a channel that the Ceton was used for. I rebooted, re-did the .properties, etc. No change, still couldn't tune, still got the circle of death on changing tuner properties, etc.

I'd have to see the logs.

[babgvant]

Originally Posted by LehighBri

Let me know if you need some help to debug/identify the root cause. And what was the tradeoff for slower performance/why was it required? Improved stability? etc? Just trying to understand.

I was seeing memory leaks (500MB+) and CPU usage when the service wasn't doing anything that wasn't related to my code. After switching I haven't observed those issues, so it seems safe to say that the old stack was the cause.

Hopefully I'll be able to figure out why it's slower and do something about it.

[kmp14]

Any chance that SageDCT 1.2 might solve the lost packets resulting in freeze/pixelate that myself and 1 other person (I think) are getting?

Just wondering if I should give it a try......still on SageMCTuner.

[babgvant]

Originally Posted by kmp14

Any chance that SageDCT 1.2 might solve the lost packets resulting in freeze/pixelate that myself and 1 other person (I think) are getting?

Just wondering if I should give it a try......still on SageMCTuner.

Probably not. Once the stability and speed issues get worked out, I plan to take another look at PBDA tuning (what MC uses). FWIW, I did figure out how to create the capture graph, but must be missing something because I'm not getting samples.

[kmp14]

Originally Posted by babgvant

Probably not. Once the stability and speed issues get worked out, I plan to take another look at PBDA tuning (what MC uses). FWIW, I did figure out how to create the capture graph, but must be missing something because I'm not getting samples.

Thanks. I would be happy to try any PBDA attempts if you want me to.

Also, I initiated a support request with Ceton for the lost packets issue. Not sure if they will help or not. I will post the results of the support request.

[SuiDog]

Originally Posted by Endymion

I updated by uninstalling 1.1, installing 1.2, and then rebooting. After installing 1.2, the 4 tuners showed as not working in the video source setup, and doing anything there, like changing the EPG or channels, results in a circle of death for at least 20 seconds. Sage also said that no tuners were available when I tried to tune to a channel that the Ceton was used for. I rebooted, re-did the .properties, etc. No change, still couldn't tune, still got the circle of death on changing tuner properties, etc.

I then went back and reinstalled SageDCT 1.1. No reboot, just uninstalled 1.2, then installed 1.1. Now everything is working great.

So... not sure if I'm upgrading from 1.1 to 1.2 wrong, or what. Any ideas? I do have the latest Ceton drivers.firmware.

I had the exact same problem. I am running 64bit btw. I also saw a huge amount of disk activity.