QAM Support for US ATSC tuners (2 Viewers)

davidvr

Portal Member
October 13, 2007
12
0
Home Country
United States of America United States of America
here is a copy of the scan,

here is a section with issues, look at KOPB-HD, it is detected but the entries result in no audiovideodetected.
10]: ATSC tune: PhysicalChannel: -1 Frequency: 559250 Modulation: Mod256Qam
2007-10-25 16:28:49.739321 [5]: atsc:Tune:ATSC:tv: Freq:559250 ONID:-1 TSID:-1 SID:-1 PMT:FFFFFFFF FTA:False LCN:10000 phys:-1 maj:-1 min:-1 SR:-1 mod:Mod256Qam audio pid:FFFFFFFF video pid:FFFFFFFF
2007-10-25 16:28:49.739321 [5]: Setting ATSC BDA Digital Demodulator to 256QAM
2007-10-25 16:28:49.739321 [5]: dvb:confused:ubmiting tunerequest Channel: subChannel:0
2007-10-25 16:28:49.739321 [5]: dvb:confused:ubmit tunerequest size:1 new:0
2007-10-25 16:28:49.739321 [5]: subch:0 OnBeforeTune
2007-10-25 16:28:50.676821 [5]: subch:0 OnAfterTune
2007-10-25 16:28:50.676821 [5]: subch:0 OnGraphStart
2007-10-25 16:28:50.676821 [5]: subch:0 RunGraph: already running
2007-10-25 16:28:50.676821 [5]: subch:0 SetupPmtGrabber:pid FFFFFFFF sid:FFFFFFFF
2007-10-25 16:28:50.676821 [5]: Scan: tuner locked:True signal:100 quality:100
2007-10-25 16:28:51.926821 [5]: 0) 0x0 0x20F0 0x1 0x0 OC v:0 a:0 ac3:0 type:1
2007-10-25 16:28:51.926821 [5]: atsc:Found: ATSC:tv:unknown OC Freq:559250 ONID:0 TSID:8432 SID:1 PMT:0 FTA:False LCN:10000 phys:-1 maj:10 min:4 SR:-1 mod:Mod256Qam audio pid:FFFFFFFF video pid:FFFFFFFF
2007-10-25 16:28:51.926821 [5]: 1) 0x0 0x20F0 0x2 0x0 KOPB-HD v:0 a:0 ac3:0 type:1
2007-10-25 16:28:51.926821 [5]: atsc:Found: ATSC:tv:unknown KOPB-HD Freq:559250 ONID:0 TSID:8432 SID:2 PMT:0 FTA:False LCN:10000 phys:-1 maj:10 min:1 SR:-1 mod:Mod256Qam audio pid:FFFFFFFF video pid:FFFFFFFF
2007-10-25 16:28:51.926821 [5]: 2) 0x0 0x20F0 0x3 0x0 Create v:0 a:0 ac3:0 type:1
2007-10-25 16:28:51.926821 [5]: atsc:Found: ATSC:tv:unknown Create Freq:559250 ONID:0 TSID:8432 SID:3 PMT:0 FTA:False LCN:10000 phys:-1 maj:10 min:3 SR:-1 mod:Mod256Qam audio pid:FFFFFFFF video pid:FFFFFFFF
2007-10-25 16:28:51.926821 [5]: 3) 0x0 0x20F0 0xD 0x33 v:880 a:881 ac3:881 type:0
2007-10-25 16:28:51.926821 [5]: DVBBaseScanning: service_name is null so now = Unknown 559250-51
2007-10-25 16:28:51.926821 [5]: atsc:Found: ATSC:tv: Unknown 559250-33 Freq:559250 ONID:0 TSID:8432 SID:13 PMT:33 FTA:True LCN:10000 phys:-1 maj:0 min:0 SR:-1 mod:Mod256Qam audio pid:881 video pid:880
2007-10-25 16:28:51.926821 [5]: 4) 0x0 0x20F0 0xE 0x32 v:840 a:841 ac3:841 type:0
2007-10-25 16:28:51.926821 [5]: DVBBaseScanning: service_name is null so now = Unknown 559250-50
2007-10-25 16:28:51.926821 [5]: atsc:Found: ATSC:tv: Unknown 559250-32 Freq:559250 ONID:0 TSID:8432 SID:14 PMT:32 FTA:True LCN:10000 phys:-1 maj:0 min:0 SR:-1 mod:Mod256Qam audio pid:841 video pid:840
2007-10-25 16:28:51.926821 [5]: 5) 0x0 0x20F0 0xF 0x34 v:8C0 a:8C1 ac3:8C1 type:0
 

dman_lfc

Retired Team Member
  • Premium Supporter
  • July 28, 2004
    1,772
    30
    UK
    Home Country
    New Zealand New Zealand
    I am using a avermedia a180 to pick up QAM channels in media portal. It seems to work ok except that it picks up the QAM versions of my local channels as ATSC (channels that comcast is recieving and transformaing to QAM256).

    Sorry what do you mean? QAM is ATSC...

    Your logs look ok we are picking up some channels however with no audio & video pids i.e. FFFFFFFFF (or -1) so if they don't work you'll have to weed them out.

    DMAN
     

    davidvr

    Portal Member
    October 13, 2007
    12
    0
    Home Country
    United States of America United States of America
    sorry I men't 8vsb it was just curious that those channels do actually exist. I haven't looked at the code yet, but would it be possible to have a setting to ignore encrypted channels with scanning?
     

    dman_lfc

    Retired Team Member
  • Premium Supporter
  • July 28, 2004
    1,772
    30
    UK
    Home Country
    New Zealand New Zealand
    sorry I men't 8vsb it was just curious that those channels do actually exist. I haven't looked at the code yet, but would it be possible to have a setting to ignore encrypted channels with scanning?

    No, reasons:

    1. Some people can decrypt them.
    2. There is a simple delete scrambled button afterwards.
    3. Not all channels set the encrypted flag correctly anyway.

    DMAN
     

    dman_lfc

    Retired Team Member
  • Premium Supporter
  • July 28, 2004
    1,772
    30
    UK
    Home Country
    New Zealand New Zealand
    I still need a .TS recording (about 2mins) to look to fix the black screen issue.
    Please help me to help you...

    DMAN
     

    davidvr

    Portal Member
    October 13, 2007
    12
    0
    Home Country
    United States of America United States of America
    sorry I men't 8vsb it was just curious that those channels do actually exist. I haven't looked at the code yet, but would it be possible to have a setting to ignore encrypted channels with scanning?

    No, reasons:

    1. Some people can decrypt them.
    2. There is a simple delete scrambled button afterwards.
    3. Not all channels set the encrypted flag correctly anyway.

    DMAN

    DMAN,

    1. What hardware can decrypt a cable QAM signal (I want what ever can)
    2. The delete scambled does not delete encyrpted channels when I press it. I have to manually try each freq and wait for either a Picture or for a ChannelEncrypted type message to appear.
     

    IcePickrg

    Portal Member
    March 12, 2007
    29
    0
    Denver, Colorado
    Home Country
    United States of America United States of America
    physicial channel = tuningdetail.channelnumber

    dman,

    Thank you for all your efforts on ATSC.

    I noticed that physical channel = tuningdetail.channelnumber when using Mod8Vsb.

    NA has been utilizing tuningdetail.channelnumber for direct channel number entry zapping in full screen and tvguide, using WZ__ NA channel change fix. (see https://forum.team-mediaportal.com/change_channel_channelnumber_sid_w_code-t25614.html)

    DVB-S uses serviceid for channelnumbers in NA.
    Analog cable & NTSC use frequency for channel numbers.

    ATSC (at least with OTA/Mod8Vsb) is using "Major number", so the population for of tuningdetail.channelnumber with physical channel would not line up with other NA implementations.

    With DVB-S, channel number was never filled, leaving it open to populate it with serviceid.

    Although Analog cable used it for tuning information, it has of late become more of a zapping column then a tuning column.

    Your thoughts?
     

    dman_lfc

    Retired Team Member
  • Premium Supporter
  • July 28, 2004
    1,772
    30
    UK
    Home Country
    New Zealand New Zealand
    sorry I men't 8vsb it was just curious that those channels do actually exist. I haven't looked at the code yet, but would it be possible to have a setting to ignore encrypted channels with scanning?

    No, reasons:

    1. Some people can decrypt them.
    2. There is a simple delete scrambled button afterwards.
    3. Not all channels set the encrypted flag correctly anyway.

    DMAN

    DMAN,

    1. What hardware can decrypt a cable QAM signal (I want what ever can)
    2. The delete scambled does not delete encyrpted channels when I press it. I have to manually try each freq and wait for either a Picture or for a ChannelEncrypted type message to appear.

    1. Who said it was hardware...
    2. See point 3 from previous post.

    DMAN
     

    dman_lfc

    Retired Team Member
  • Premium Supporter
  • July 28, 2004
    1,772
    30
    UK
    Home Country
    New Zealand New Zealand
    dman,

    Thank you for all your efforts on ATSC.

    I noticed that physical channel = tuningdetail.channelnumber when using Mod8Vsb.

    NA has been utilizing tuningdetail.channelnumber for direct channel number entry zapping in full screen and tvguide, using WZ__ NA channel change fix. (see https://forum.team-mediaportal.com/change_channel_channelnumber_sid_w_code-t25614.html)

    DVB-S uses serviceid for channelnumbers in NA.
    Analog cable & NTSC use frequency for channel numbers.

    ATSC (at least with OTA/Mod8Vsb) is using "Major number", so the population for of tuningdetail.channelnumber with physical channel would not line up with other NA implementations.

    With DVB-S, channel number was never filled, leaving it open to populate it with serviceid.

    Although Analog cable used it for tuning information, it has of late become more of a zapping column then a tuning column.

    Your thoughts?

    ATSC OTA requires a "Physical Channel" put method into the ATSC Network Provider for the tunigng of the channel.
    You cannot rely on the "Major Chanel" alone.
    Currently there is no "Physical Channel" DB entry as we use ChannelNumber reference to store this information becuase it was free and made sense.
    Unfortuntely ATSC providers don't abide by the standards. It's especially worse with QAM as providers sometime don't broadcast scrambled flags, channel names & even a SID or PMT.

    It's my understanding some ATSC OTA providers derive it's channel number scheme from the Major Channel & Minor Channel number like so...
    Major Channel = 30 Minor Channel = 1 thus the Channel is on 301
    Unfortunately not all providers keep to a standard allowing them to easily change frequencies of the broadcasted channel without affecting the user.

    DMAN
     

    Users who are viewing this thread

    Top Bottom