Channel Update for Prime

[mistergq]

I noticed that a couple channels added to the FIOS lineup have not shown up on the HD Prime. I rescaned in the Setup utility for Homerun and they are there. Should I rescan in Video Setup in STV?

[teedublu]

You have to rerun the SageDCT utility to create a new discovery file to paste into sage.properties.

However, I think you need to delete the sources first since you already have them in your properties file.

Hmmm

(keep in mind that SageDCT is a workaround)

[nyplayer]

Originally Posted by mistergq

I noticed that a couple channels added to the FIOS lineup have not shown up on the HD Prime. I rescaned in the Setup utility for Homerun and they are there. Should I rescan in Video Setup in STV?

Don't you just have to enable them in the Video Source .. Channel setup scanning is not going to do anything. If the Sage server added the channels to the guide you just have to enable them.

[teedublu]

Originally Posted by nyplayer

Don't you just have to enable them in the Video Source .. Channel setup scanning is not going to do anything. If the Sage server added the channels to the guide you just have to enable them.

I don't do that with what I consider Non-Native tuners like HD HomeRun QAM and Prime. In fact, when I setup the lineup for these tuners, I create a separately managed lineup, which will not get channels added from the EPG -- since those channels won't have the "channel mapping" info for these non-native tuners.

I then (painfully) rescan using the external utility, then cut-n-paste the addition / changes (with QAM, sometimes Comcast changes the frequency stuff). The cut-n-paste keeps me from having to do a lot of work within Sage.

So, I'd probably do the same for Prime. Just look in the newly generated Discovery file and paste only the new channel into the sage.properties file.

TW

[nyplayer]

Originally Posted by teedublu

I don't do that with what I consider Non-Native tuners like HD HomeRun QAM and Prime. In fact, when I setup the lineup for these tuners, I create a separately managed lineup, which will not get channels added from the EPG -- since those channels won't have the "channel mapping" info for these non-native tuners.

I then (painfully) rescan using the external utility, then cut-n-paste the addition / changes (with QAM, sometimes Comcast changes the frequency stuff). The cut-n-paste keeps me from having to do a lot of work within Sage.

So, I'd probably do the same for Prime. Just look in the newly generated Discovery file and paste only the new channel into the sage.properties file.

TW

I guess since my Prime is my primary tuner and I get all the channels I subscribe to .. I simply give it the main full digital listing for my area. Then I simply enable all the channels I get any others I leave not enabled. That way when a new channel is added Sage gives me a message I then can preview it in my Prime and if it comes in clearly I enable it.


As far as the Hd Homeruns I choose not to use any listing but in the HD Homerun software I have the channels mapped the same name as my main guide. That way I only have 1 listing to worry about my main one. So all I have to do is create the scn and do a scan.

I have a powershell script that someone had written that does a scan on the Hd Homeruns and emails me if there are any changes... to the location of the channels. This is it if anyone is interested qam_scan

[teedublu]

Thanks nyplayer -- It didn't occur to me that the EPG lineup had enough to fill in the new channel info for the Prime. Makes sense, since the cable card system performs tune frequency translation stuff.

I have an HDPVR as my main lineup and I need to keep it for the copy-once channels (HBO etc.).

I was hoping to retire the HDHomeRun, but since I had to go with the VLC option to fix Comcast glitches, I've put the HDHR as the highest priority tuner.
Of course this makes it painful to test new channels on the Prime within Sage (have to make both tuners on the HDHR busy, or use Silicondust utilities.

Thanks for that script link -- I need that!
BTW, I manually edit the HDHR scn file to fix channel issues by comparing the before-n-after, then run the Sage scan (the HDHR is at least a partly-native Sage tuner).

TW

[Tiki]

Originally Posted by teedublu

Of course this makes it painful to test new channels on the Prime within Sage (have to make both tuners on the HDHR busy, or use Silicondust utilities.
TW

A trick that I found helpful when testing tuners in Sage is to make sure that there are a couple of channels that are only available on the tuner I want to test with and pick those channels to test with.

The other trick is to go into the channel setup for a particular tuner and use the preview to test the channel.