[mythtv-users] New release of scte65scan (mainly for Comcast users)

Mark Knecht markknecht at gmail.com
Fri May 22 23:00:00 UTC 2009


Do you have one of the Pace DTA's activated so you can see your VCT_ID
in the info page?

If the Pace displays channel numbers on your TV screen when you change
channels then this program *should* pick up the same data.

Note that before you can really get data into Myth you do also have to
enable the channels in your lineup at SchedulesDirect.

The -p attempts to pick up the HD channels. It seems you aren't
getting any data which makes me wonder whether having a DTA authorized
is a requirement for Comcast to transmit the data. Brad and I both had
them authorized. Larry and Jason were, I beleive, doing other things.

- Mark

On Fri, May 22, 2009 at 3:48 PM, Andrew Burgess <aab at cichlid.com> wrote:
> Got nothing with the supplied freq table. I saw my hdhr locking on
> frequencies that weren't in your table so I made my own. Still no luck.
> I'm in Santa Cruz CA. Is it possible that Comcast here isn't
> broadcasting this stuff? They are giving out the STBs...
>
> Thanks for any help
> Andrew
>
> PS Reread the README and tried again with -p. No change except an extra
> "PID 0x1ffc timeout" each freq and an empty PSIP table at the end.
>
> ----------------------------------
>
> My table:
>
> A 627000000 QAM256
> A 621000000 QAM256
> A 615000000 QAM256
> A 609000000 QAM256
> A 603000000 QAM256
> A 597000000 QAM256
> A 591000000 QAM256
> A 585000000 QAM256
> A 573000000 QAM256
> A 567000000 QAM256
> A 561000000 QAM256
> A 555000000 QAM256
> A 549000000 QAM256
> A 543000000 QAM256
> A 537000000 QAM256
> A 531000000 QAM256
> A 525000000 QAM256
> A 519000000 QAM256
> A 273000000 QAM256
> A 255000000 QAM256
> A 249000000 QAM256
> A 225000000 QAM256
> A 207000000 QAM256
> A 117000000 QAM256
> A 111000000 QAM256
>
> Results:
>
> scte65scan -H 1011BA29 ../table
> tuning 627000000hz.locked...PID 0x1ffc timeout
> tuning 621000000hz.locked...PID 0x1ffc timeout
> tuning 615000000hz.locked...PID 0x1ffc timeout
> tuning 609000000hz.locked...PID 0x1ffc timeout
> tuning 603000000hz.locked...PID 0x1ffc timeout
> tuning 597000000hz.locked...PID 0x1ffc timeout
> tuning 591000000hz.locked...PID 0x1ffc timeout
> tuning 585000000hz.locked...PID 0x1ffc timeout
> tuning 573000000hz.locked...PID 0x1ffc timeout
> tuning 567000000hz.locked...PID 0x1ffc timeout
> tuning 561000000hz.locked...PID 0x1ffc timeout
> tuning 555000000hz.locked...PID 0x1ffc timeout
> tuning 549000000hz.locked...PID 0x1ffc timeout
> tuning 543000000hz.locked...PID 0x1ffc timeout
> tuning 537000000hz.locked...PID 0x1ffc timeout
> tuning 531000000hz.locked...PID 0x1ffc timeout
> tuning 525000000hz.locked...PID 0x1ffc timeout
> tuning 519000000hz.locked...PID 0x1ffc timeout
> tuning 273000000hz.locked...PID 0x1ffc timeout
> tuning 255000000hz.locked...PID 0x1ffc timeout
> tuning 249000000hz.locked...PID 0x1ffc timeout
> tuning 225000000hz.locked...PID 0x1ffc timeout
> tuning 207000000hz.locked...PID 0x1ffc timeout
> tuning 117000000hz.locked...PID 0x1ffc timeout
> tuning 111000000hz.locked...PID 0x1ffc timeout
>
>
> _______________________________________________
> mythtv-users mailing list
> mythtv-users at mythtv.org
> http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
>


More information about the mythtv-users mailing list