Defective TS files with displayed zero length

[johnsta]

As you suggested, the channel scan did take a long time.

I've collected a bunch of information from NPVR, from the HDHR setup
dialog, and from the HDHR web page, and I'll summarize it all below.

If I understand the implications of what you and Brett are suggesting,
it's that I'm somehow getting cable tv from Comcast bypassing the
Cablecard. That's absolutely impossible. It used to be that all
channels below 100 were unencrypted. In those days I was using
BeyondTV, and it was really nice and convenient. However, those days
are long gone. Comcast has done everything possible to prevent anyone
from getting free cable tv, so now all channels are encrypted, even
those available over the air.

So I don't know what's going on with the lengthy channel scan,
but the bottom line is that I'm still using the Cablecard.

• Anyway, so I brought up Settings | Devices, and clicked on the
  first of the 3 HDHR tuners. Then right-click | Setup device to get
  "HDHR Settings" dialog, then clicked "Scan". After about 20 minutes
  it displayed the channels and I clicked OK. I clicked "No" to the
  request to do a new EPG update. The device panel shows that the
  number of channels on the first HDHR tuner is now 465, while the other
  two are 463. I did not bother to do the device setup for the other
  two tuners.
  
  
• I brought up the HDHomeRun Setup dialog. It did not look anything
  like Brett's description. In particular, there's no "Tuners" tab.
  
  
• There's a Configuration tab that shows this information: Location
  - United States; BDA Compatibility Mode - Windows Media Center (other
  choices are: Default, Easy HDHR DVR, For the Record, J River Media
  Center, Media Portal, NextPVR)
  
  
• The Device table shows one device: Device input - 1325E4C2; Tuners
  - 3; Source type - CableCARD; Status - ok. That's all the information
  on the Configuration tab.
  
  
• The "CableCard" tab just shows the device, with a "Scan" button.
  
  
• The "DVR" tab just says "Use this PC for making recordings," the
  other choice being "Use Network Attached Storage (NAS) for making
  recordings."
  
  
• The "Advanced" tab shows: Unchecked box: Windows Media Center
  background channel scan; BDA Driver Virtual Channel Table mode - Auto
  (other choices: Normal, Block, Inject TVCT, Inject CVCT); Checked box:
  Automatically select from available tuners (recommended); Unchecked
  box: Send diagnostic information to Silicondust support. There's also
  a "Repair" button.
  
  
• There's a text line at the bottom of the "Advanced" tab: HDHomeRun
  Setup version 20171221. This caused me to do a check, and all the
  HDHR software dates are on 12/21, even though I installed HDHR on
  12/9. So it must have done an automatic software update on 12/21
  without telling me (I hate that), and that's the date when things
  started getting worse.
  
  
• I brought up the HDHomeRun PRIME web page. It shows the following
  status information:
  
  HDHomeRun PRIME
  Model: HDHR3-CC
  Device ID: 1325E4C2
  Firmware: 20170930
  Status
  Card Authentication success
  Card OOB Lock success
  Card Validation success
  
  
• Clicked the CableCard option. Displayed status information:
  CableCARD Status
  Card Manufacturer Motorola
  Card Authentication success
  Card Validation success
  3DES encryption supported
  OOB Frequency 75.250 MHz
  OOB Lock 2.048 Mbps
  Signal Strength 81% (-11.6 dBmV)
  Signal Quality 100% (37.4 dB)
  Channel List cablecard-oob
  
  
• Clicked on Tuner Status, displayed this summary:
  Summary
  Tuner 0 Channel 5 WCVB5
  Tuner 1 Channel 190 BBC WORLD NEWS
  Tuner 2 Channel none
  
  
• Clicked on Tuner 0:
  Tuner 0 Status
  Virtual Channel 5 WCVB5
  Frequency 135.000 MHz
  Program Number 4
  Authorization subscribed
  CCI Protection unrestricted
  Modulation Lock qam256
  PCR Lock locked
  Signal Strength 88% (-7.6 dBmV)
  Signal Quality 100% (36.0 dB)
  Symbol Quality 100%
  Streaming Rate 2.158 Mbps
  Resource Lock 192.168.1.115
  
  
• Clicked on Tuner 1:
  Tuner 1 Status
  Virtual Channel 190 BBC WORLD NEWS
  Frequency 231.000 MHz
  Program Number 8
  Authorization subscribed
  CCI Protection unrestricted
  Modulation Lock qam256
  PCR Lock locked
  Signal Strength 87% (-8.3 dBmV)
  Signal Quality 100% (35.4 dB)
  Symbol Quality 100%
  Streaming Rate 3.495 Mbps
  Resource Lock 192.168.1.115
  
  
• Clicked on System Status:
  
  System Status
  Hardware Model HDHR3-CC
  Firmware Version 20170930
  DTCP-IP DTCP 1.7-SD20140607
  WMDRM-NDT WMDRM 10-SD20130219
  Memory Report 64 MB SDRAM, 2 MB Flash
  Power Status Active
  Boot Status Booted
  Device ID 1325E4C2
  MAC Address 00:18: DD:32:5E:4C
  IP Address 192.168.1.126
  Subnet Mask 255.255.255.0
  
  Firmware Upgrade
  Up to date
  
  
• Clicked on System Log. The log seems to go back for a week. Here
  are the last few lines:
  
  20180211-08:59:03 Tuner: tuner1 tuning 190 BBC WORLD NEWS (auto:231MHz-8)
  20180211-08:59:03 Tuner: tuner1 streaming rtp to 192.168.1.115:36323
  20180211-08:59:03 CableCARD: tuner1 190 BBC WORLD NEWS (auto:231MHz-8) access = subscribed
  20180211-10:59:01 Tuner: tuner2 tuning 42 CNN (auto:153MHz-2607)
  20180211-10:59:01 Tuner: tuner2 streaming rtp to 192.168.1.115:36312
  20180211-10:59:01 CableCARD: tuner2 42 CNN (auto:153MHz-2607) access = subscribed
  20180211-11:00:34 Tuner: tuner0 rtp stream ended (usage timeout)
  20180211-12:02:33 Tuner: tuner2 rtp stream ended (usage timeout)
  20180211-13:59:00 Tuner: tuner0 tuning 5 WCVB5 (auto:135MHz-4)
  20180211-13:59:00 Tuner: tuner0 streaming rtp to 192.168.1.115:36313
  20180211-13:59:00 CableCARD: tuner0 5 WCVB5 (auto:135MHz-4) access = subscribed
  
  
• Since you've previously looked at data for the recordings that
  started at 6pm ET (2300 GMT) on 2/9, here's the log data for
  that time period:
  
  20180209-20:37:42 Tuner: tuner0 tuning 45 BLOOMBG (auto:201MHz-1214)
  20180209-20:37:43 CableCARD: tuner0 45 BLOOMBG (auto:201MHz-1214) access = subscribed
  20180209-20:37:43 Tuner: tuner0 rtp stream ended (new request)
  20180209-20:37:43 Tuner: tuner0 streaming rtp to 192.168.1.115:36312
  20180209-20:37:44 Tuner: tuner1 tuning 46 CNBC (auto:153MHz-2604)
  20180209-20:37:45 Tuner: tuner1 rtp stream ended (new request)
  20180209-20:37:45 Tuner: tuner1 streaming rtp to 192.168.1.115:36313
  20180209-20:37:45 CableCARD: tuner1 46 CNBC (auto:153MHz-2604) access = subscribed
  20180209-20:37:46 Tuner: tuner2 tuning 190 BBC WORLD NEWS (auto:231MHz-8)
  20180209-20:37:46 Tuner: tuner2 rtp stream ended (new request)
  20180209-20:37:46 Tuner: tuner2 streaming rtp to 192.168.1.115:36314
  20180209-20:37:47 CableCARD: tuner2 190 BBC WORLD NEWS (auto:231MHz-8) access = subscribed
  20180209-23:00:00 Tuner: tuner0 tuning 41 FOXNEWS (auto:159MHz-2707)
  20180209-23:00:00 Tuner: tuner0 rtp stream ended (new request)
  20180209-23:00:00 Tuner: tuner0 streaming rtp to 192.168.1.115:36315
  20180209-23:00:00 Tuner: tuner1 tuning 42 CNN (auto:153MHz-2607)
  20180209-23:00:00 CableCARD: tuner0 41 FOXNEWS (auto:159MHz-2707) access = subscribed
  20180209-23:00:00 Tuner: tuner1 rtp stream ended (new request)
  20180209-23:00:00 Tuner: tuner1 streaming rtp to 192.168.1.115:36316
  20180209-23:00:00 CableCARD: tuner1 42 CNN (auto:153MHz-2607) access = subscribed
  20180210-00:00:02 Tuner: tuner0 tuning 41 FOXNEWS (auto:159MHz-2707)
  20180210-00:00:02 Tuner: tuner0 rtp stream ended (new request)
  20180210-00:00:02 Tuner: tuner0 streaming rtp to 192.168.1.115:36317
  20180210-00:00:03 CableCARD: tuner0 41 FOXNEWS (auto:159MHz-2707) access = subscribed
  20180210-00:00:04 Tuner: tuner1 tuning 42 CNN (auto:153MHz-2607)
  20180210-00:00:04 Tuner: tuner1 rtp stream ended (new request)
  20180210-00:00:04 Tuner: tuner1 streaming rtp to 192.168.1.115:36318
  20180210-00:00:05 CableCARD: tuner1 42 CNN (auto:153MHz-2607) access = subscribed
  

OK, what's next?

[BrettB]

[*] The "CableCard" tab just shows the device, with a "Scan" button.

So did you click the Scan button to get it to populate the list of CableCard channels?

And then (after populating the list of CableCard channels in the HDHR setup) do a scan in NPVR?

[BrettB]

If I understand the implications of what you and Brett are suggesting,
it's that I'm somehow getting cable tv from Comcast bypassing the
Cablecard. That's absolutely impossible. It used to be that all
channels below 100 were unencrypted. In those days I was using
BeyondTV, and it was really nice and convenient. However, those days
are long gone. Comcast has done everything possible to prevent anyone
from getting free cable tv, so now all channels are encrypted, even
those available over the air.

So I don't know what's going on with the lengthy channel scan,
but the bottom line is that I'm still using the Cablecard.

• Anyway, so I brought up Settings | Devices, and clicked on the
  first of the 3 HDHR tuners. Then right-click | Setup device to get
  "HDHR Settings" dialog, then clicked "Scan". After about 20 minutes
  it displayed the channels and I clicked OK. I clicked "No" to the
  request to do a new EPG update. The device panel shows that the
  number of channels on the first HDHR tuner is now 465, while the other
  two are 463. I did not bother to do the device setup for the other
  two tuners.
  
  
• I brought up the HDHomeRun Setup dialog. It did not look anything
  like Brett's description. In particular, there's no "Tuners" tab.
  
  
• There's a Configuration tab that shows this information: Location
  - United States; BDA Compatibility Mode - Windows Media Center (other
  choices are: Default, Easy HDHR DVR, For the Record, J River Media
  Center, Media Portal, NextPVR)
  
  
• The Device table shows one device: Device input - 1325E4C2; Tuners
  - 3; Source type - CableCARD; Status - ok. That's all the information
  on the Configuration tab.
  
  
• The "CableCard" tab just shows the device, with a "Scan" button.

OK. I just took a look at my latest HDHomeRun Setup. It looks like they have "combined" the Configuration tab and the Tuners tab. So, to translate those original instructions:

1. Make sure that you are running the HDHR Setup on the NPVR server computer.
   
2. Go to the Configuration tab.
   
3. If you are using the "HDHR" type device in NPVR (NOT the "QAM" or "ATSC" ones), the BDA compatiblity mode shouldn't matter. But I would recommend setting it to Default just in case. While it is conter-intuitive, DO NOT set it to NextPVR!
   
4. Still on the Configuration tab, in the Device Input column, click on the address of the HDHR Prime (it should be a blue, underlined link).
   
5. This should open the web page of the HDHR Prime device.
   
6. On there, click the "Channel Lineup" link.
   
7. Does yours already list channels? Either way, go ahead and click on the "Detect Channels" button to get the most up-to-date channel listing.
   
8. No go back to NextPVR with the clean/empty database.
   
9. Go to Settings | Devices.
   
10. It should detect the devices available on your system.
    
11. It used to be that you would get 3 tuner devices in NPVR for each physical tuner on the HDHR Prime (one of each type: HDHR, QAM, and ATSC). But when I just looked on my system, I'm only seeing the HDHR ones for my Prime tuners. That might be because sub is filtering the other ones or maybe because I had deleted them and they aren't automtically coming back.)
    
12. At any rate, when using a CableCard, make sure that you select the HDHR type tuners.
    
13. Select Device Setup and then click the Scan button. For an HDHR type tuner, it should pop up with the channel list almost instantly.
    
14. If you then select the next device and click Device Setup, you should get a prompt saying something like "a similar device is already configured, do you want to copy the configuration?". You should select Yes to copy that channel configuration from the first physical tuner to each of the other 2 tuners.
    

[johnsta]

Originally Posted by johnsta
> [*] The "CableCard" tab just shows the device, with a "Scan"
> button.

> So did you click the Scan button to get it to populate the list of
> CableCard channels?

> And then (after populating the list of CableCard channels in the
> HDHR setup) do a scan in NPVR?

OK, I did the scans, and the NPVR scans are now instantaneous,
which I assume is what you expected.

I assume you also expect that this should fix the problem. I hope
so. I'll keep my eye on the recordings, and let you know within
a couple of days whether there are any more defective recordings.

Thanks for your help.

John

[sub]

OK, I did the scans, and the NPVR scans are now instantaneous,
which I assume is what you expected.

I assume you also expect that this should fix the problem. I hope
so. I'll keep my eye on the recordings, and let you know within
a couple of days whether there are any more defective recordings.

Thanks for your help.

John

Honestly, I don't know if it'll fix it or not, but hopefully it will.

Basically the log messages I was seeing in your logs were different than what I see in other HDHomeRun Prime users. Your tunings were trying to do two steps, (1) tune to a frequency, (2) locate a specific service in that frequency. Whereas Prime users would usually tune in a single step, (1) tune to channel number x, and the cable card would take care of know where the channel is, frequency etc. (this also has the advantage of automatically dealing with cable channel frequency changes that the cable company might make later)

Given we're not seeing widespread reports of this problem you're easy reproducing, it was worth getting your setup doing cable card tuning, rather than old fashioned digital cable (QAM) tuning.

[johnsta]

> Honestly, I don't know if it'll fix it or not, but hopefully it
> will.

> Basically the log messages I was seeing in your logs were
> different than what I see in other HDHomeRun Prime users. Your
> tunings were trying to do two steps, (1) tune to a frequency, (2)
> locate a specific service in that frequency. Whereas Prime users
> would usually tune in a single step, (1) tune to channel number x,
> and the cable card would take care of know where the channel is,
> frequency etc. (this also has the advantage of automatically
> dealing with cable channel frequency changes that the cable
> company might make later)

> Given we're not seeing widespread reports of this problem you're
> easy reproducing, it was worth getting your setup doing cable card
> tuning, rather than old fashioned digital cable (QAM)
> tuning.

Configuration update: I'm running NPVR 4.0.5, modified with
the 2/8 version of NPVRWriter.ax.

I had hoped that the HDHR and NPVR scans would fix the problem, but as
you point out, that was just wishful thinking on my part.

At any rate, the problems at 6 pm each weekday are still occurring,
and seem to be reliably repeatable. That's probably because the
same channel changes are made every day at 6 pm.

Looking over the past 20 months, the general problem has remained the
same, but the particular programs that are "reliably repeatable" in
producing defective files have changed. Apparently almost all
recordings of "blackish" using the Ceton card from May 2016 until I
replaced the Ceton card with the HDHR box in early December 2017 were
defective. I haven't tested all of them, but it seems pretty
consistent.

Then after the HDHR installation, there was a switch to all the
recordings of "WBZ News at 11" being consistently defective. That no
longer happens.

Today the reliably repeatable defective recordings are at 6 pm, when
the BBC* recording is OK, but the CNN* and FNC* recordings are
defective.

So the bug that I had thought to be completely random is apparently
quite repeatable, as long as the underlying conditions such as
recording schedules don't change.

This still suggests to me that there's an issue related to Comcast's
digital cable encoding formats, as I wrote in a previous message.
It's likely that Comcast uses a different encoding format for
different programs and different channels, since they've changed
encoding formats many times in the past, as described in those two
articles that I linked to.

Continuing along these lines, since Boston, New York, Chicago, etc.,
all have different published channel lineups, it's likely that Comcast
uses different combinations of encoding formats in different markets.

Since defective recordings seem to be related to channel changes, it's
possible the problems are not more widespread because I have far more
recurring recordings scheduled than most people, which means more
channel changes, which means a greater likelihood of defective
recordings.

This combination of provider, tuner and schedule configuration is
probably rare enough that it could explain why the bug is not
affecting more people. It's also possible that many people ignored or
worked around the problem, if they only see the problem occasionally.

At any rate, now that I know all the forms of data that I can collect,
I'll try again at 6 pm today, and get everything together and send it
to you.

[sub]

At any rate, the problems at 6 pm each weekday are still occurring,
and seem to be reliably repeatable. That's probably because the
same channel changes are made every day at 6 pm.

Looking over the past 20 months, the general problem has remained the
same, but the particular programs that are "reliably repeatable" in
producing defective files have changed. Apparently almost all
recordings of "blackish" using the Ceton card from May 2016 until I
replaced the Ceton card with the HDHR box in early December 2017 were
defective. I haven't tested all of them, but it seems pretty
consistent.

Then after the HDHR installation, there was a switch to all the
recordings of "WBZ News at 11" being consistently defective. That no
longer happens.

Today the reliably repeatable defective recordings are at 6 pm, when
the BBC* recording is OK, but the CNN* and FNC* recordings are
defective.

Post the NPVR and file-writer logs showing these defective recordings, and I'll take another look through the logs.

This still suggests to me that there's an issue related to Comcast's
digital cable encoding formats, as I wrote in a previous message.

I've not seen anything non-standard in the streams yet.

One of those articles talked about Comcast moving to IPTV, which they havn't yet (since they'd need to roll out new set top boxes to everyone, and your cablecard devices would no longer work), so we can ignore that one. The other article was about Comcast moving to 720p as their standard for HD - that's fine, and shouldn't cause any issues.

[johnsta]

> Post the NPVR and file-writer logs showing these defective
> recordings, and I'll take another look through the logs.

>> "This still suggests to me that there's an issue related to
>> Comcast's digital cable encoding formats, as I wrote in a previous
>> message."

> I've not seen anything non-standard in the streams yet.

> One of those articles talked about Comcast moving to IPTV, which
> they havn't yet (since they'd need to roll out new set top boxes
> to everyone, and your cablecard devices would no longer work), so
> we can ignore that one. The other article was about Comcast moving
> to 720p as their standard for HD - that's fine, and shouldn't
> cause any issues.

As promised, I've collected all the relevant files from 6pm yesterday
(2300 gmt 2/13). Three recordings began at 6pm.

As usual, BBC* was OK, while CNN* and FNC* were defective.

I canceled these recordings after two minutes.

Here are the TS files:

http://jxenakis.com/gdgraphics/FNC-6-7pm...8001900.ts
http://jxenakis.com/gdgraphics/CNN-6-7pm...8001900.ts
http://jxenakis.com/gdgraphics/BBC-6-8pm...8002000.ts

Here are the file-write* and nrecord.log files:

http://jxenakis.com/gdgraphics/fw-1810-180213.zip
http://jxenakis.com/gdgraphics/nr-1810-180213.zip

Here is the HDHomeRun Prime log:


20180213-17:00:01 Tuner: tuner0 rtp stream ended (new request)
20180213-17:00:01 Tuner: tuner0 streaming rtp to 192.168.1.115:36315
20180213-17:00:01 CableCARD: tuner0 45 BLOOMBG (auto:201MHz-1214) access = subscribed
20180213-17:00:02 Tuner: tuner1 tuning 46 CNBC (auto:153MHz-2604)
20180213-17:00:02 Tuner: tuner1 rtp stream ended (new request)
20180213-17:00:02 Tuner: tuner1 streaming rtp to 192.168.1.115:36316
20180213-17:00:02 CableCARD: tuner1 46 CNBC (auto:153MHz-2604) access = subscribed
20180213-17:00:02 Tuner: tuner2 tuning 190 BBC WORLD NEWS (auto:231MHz-8)
20180213-17:00:02 Tuner: tuner2 rtp stream ended (new request)
20180213-17:00:02 Tuner: tuner2 streaming rtp to 192.168.1.115:36317
20180213-17:00:03 CableCARD: tuner2 190 BBC WORLD NEWS (auto:231MHz-8) access = subscribed
20180213-23:00:00 Tuner: tuner0 tuning 41 FOXNEWS (auto:159MHz-2707)
20180213-23:00:00 Tuner: tuner0 rtp stream ended (new request)
20180213-23:00:00 Tuner: tuner0 streaming rtp to 192.168.1.115:36318
20180213-23:00:00 Tuner: tuner1 tuning 42 CNN (auto:153MHz-2607)
20180213-23:00:00 Tuner: tuner1 rtp stream ended (new request)
20180213-23:00:00 Tuner: tuner1 streaming rtp to 192.168.1.115:36319
20180213-23:00:00 CableCARD: tuner0 41 FOXNEWS (auto:159MHz-2707) access = subscribed
20180213-23:00:00 CableCARD: tuner1 42 CNN (auto:153MHz-2607) access = subscribed
20180213-23:02:51 Tuner: tuner0 rtp stream ended (usage timeout)
20180213-23:02:56 Tuner: tuner1 rtp stream ended (usage timeout)
20180213-23:03:01 Tuner: tuner2 rtp stream ended (usage timeout)
20180213-23:03:15 Tuner: tuner0 tuning 41 FOXNEWS (auto:159MHz-2707)
20180213-23:03:15 Tuner: tuner0 streaming rtp to 192.168.1.115:36320
20180213-23:03:16 CableCARD: tuner0 41 FOXNEWS (auto:159MHz-2707) access = subscribed
20180213-23:03:43 Tuner: tuner1 tuning 42 CNN (auto:153MHz-2607)
20180213-23:03:43 Tuner: tuner1 streaming rtp to 192.168.1.115:36321
20180213-23:03:44 CableCARD: tuner1 42 CNN (auto:153MHz-2607) access = subscribed
20180213-23:04:22 Tuner: tuner2 tuning 190 BBC WORLD NEWS (auto:231MHz-8)
20180213-23:04:22 Tuner: tuner2 streaming rtp to 192.168.1.115:36322
20180213-23:04:22 CableCARD: tuner2 190 BBC WORLD NEWS (auto:231MHz-8) access = subscribed
20180213-23:59:59 Tuner: tuner0 tuning 41 FOXNEWS (auto:159MHz-2707)
20180213-23:59:59 Tuner: tuner0 rtp stream ended (new request)
20180213-23:59:59 Tuner: tuner0 streaming rtp to 192.168.1.115:36323
20180213-23:59:59 Tuner: tuner1 tuning 42 CNN (auto:153MHz-2607)
20180213-23:59:59 Tuner: tuner1 rtp stream ended (new request)
20180213-23:59:59 Tuner: tuner1 streaming rtp to 192.168.1.115:36312
20180213-23:59:59 CableCARD: tuner0 41 FOXNEWS (auto:159MHz-2707) access = subscribed
20180214-00:00:00 CableCARD: tuner1 42 CNN (auto:153MHz-2607) access = subscribed
20180214-01:00:04 Tuner: tuner0 tuning 41 FOXNEWS (auto:159MHz-2707)
20180214-01:00:04 Tuner: tuner0 rtp stream ended (new request)
20180214-01:00:04 Tuner: tuner0 streaming rtp to 192.168.1.115:36313
20180214-01:00:04 CableCARD: tuner0 41 FOXNEWS (auto:159MHz-2707) access = subscribed
20180214-01:00:05 Tuner: tuner1 tuning 45 BLOOMBG (auto:201MHz-1214)
20180214-01:00:05 Tuner: tuner1 rtp stream ended (new request)
20180214-01:00:05 Tuner: tuner1 streaming rtp to 192.168.1.115:36314
20180214-01:00:06 CableCARD: tuner1 45 BLOOMBG (auto:201MHz-1214) access = subscribed

As the above shows, BBC* (tuner2) continued recording without tuning
to a new channel, while CNN* (tuner1) and FNC* (tuner0) do require
channel changes.

I don't claim to understand the above log, but just looking at the
order of the entries at 23:00, it looks like the HDHR (tuners 1 and 2)
continues transmitting the old channel data for a few milliseconds
before implementing the channel change and transmitting data from the
new channel.

Thanks,

John

[sub]

As promised, I've collected all the relevant files from 6pm yesterday
(2300 gmt 2/13). Three recordings began at 6pm.

As usual, BBC* was OK, while CNN* and FNC* were defective.

What problem are you seeing with FNC that makes you think it's defective? I doesn't appear to have the problem with extra data at the start of it, and plays for me in VLC, Windows Media Player and NextPVR.

[sub]

I've just checked the CNN file and it seems ok too. I can't see any signs of extra data on that file either.