No Skip (Most Times) on TS HD Recrodings

[UncleJohnsBand]

While you are there you might one to grab at least segment 1 of Elephant's Dream. I've used that file to benchmark each beta of mvpmcx2 on the PCH to make sure things work ok with GBPVR.

Martin

I have the full elephant's dream mp4 but it will not play via the PCH....my understanding is that they recorded it using an older propriatry MS codec that PCH can not decode.

[UncleJohnsBand]

Hi UJB,

I ran into the same problems. From my testing it seems to be due to discontinuity errors. I've been following some of your previous threads as well. I shouldn't having problems writing 2-6MB/sec to disk and the performance counters reflect that. I'm thinking that it may be due to a resource conflict so I'll be performing a complete reinstall by next week.

If you want to test for continuity errors, you can use xport.exe with the following commands:

http://www.w6rz.net/xport.zip
"<path>xportdev.exe" -p <file> 1 1 1

Yep...I am seeing that error using this utility...what causes those errors....silly question I guess....becuase if someone knew it could be addressed...

The below is from a 1hr CSI Miami HD TS recording...

Code:

xport Transport Stream Demuxer 1.01
program = 1, video channel = 1, audio channel = 1
Program Number = 2 (0x0002), Program Map PID = 48 (0x0030)
Discontinuity!, pid = 48 <0x0030>, received = 14, expected =  2, at 18128
Discontinuity!, pid = 1984 <0x07c0>, received =  7, expected = 15, at 18129
Discontinuity!, pid = 1986 <0x07c2>, received = 11, expected = 13, at 18185
Discontinuity!, pid = 1985 <0x07c1>, received =  7, expected =  9, at 18220
Discontinuity!, pid = 1984 <0x07c0>, received =  5, expected = 13, at 2832670
Discontinuity!, pid = 1984 <0x07c0>, received =  5, expected =  0, at 14549311
Discontinuity!, pid = 1985 <0x07c1>, received =  4, expected =  3, at 14549374
Discontinuity!, pid = 1984 <0x07c0>, received =  7, expected =  6, at 15353561
Discontinuity!, pid = 1986 <0x07c2>, received =  5, expected =  3, at 15353563
Discontinuity!, pid = 1985 <0x07c1>, received =  1, expected = 15, at 15353692
Discontinuity!, pid = 48 <0x0030>, received =  6, expected =  3, at 15354290
Discontinuity!, pid = 1984 <0x07c0>, received = 12, expected = 10, at 15359213
Discontinuity!, pid = 1986 <0x07c2>, received =  3, expected =  7, at 15359272
Discontinuity!, pid = 1985 <0x07c1>, received = 15, expected =  2, at 15359334
Discontinuity!, pid = 48 <0x0030>, received =  8, expected = 12, at 15360220
Discontinuity!, pid = 1984 <0x07c0>, received = 11, expected =  1, at 15364993
Discontinuity!, pid = 1985 <0x07c1>, received = 12, expected =  9, at 15365021
Discontinuity!, pid = 1986 <0x07c2>, received =  1, expected = 13, at 15365061
Discontinuity!, pid = 48 <0x0030>, received =  6, expected = 13, at 15365423
Discontinuity!, pid = 1986 <0x07c2>, received =  6, expected =  5, at 32266543
Discontinuity!, pid = 1985 <0x07c1>, received =  2, expected =  1, at 32266606
Discontinuity!, pid = 1984 <0x07c0>, received = 11, expected = 12, at 32266746
packets for pid    0 <0x0000> = 35825, first = 1, last = 34984370
packets for pid   48 <0x0030> = 35851, first = 5, last = 34984371
packets for pid 1984 <0x07c0> = 33975731, first = 3, last = 34984946
packets for pid 1985 <0x07c1> = 468769, first = 4, last = 34984820
packets for pid 1986 <0x07c2> = 468770, first = 6, last = 34984866
coded pictures = 0, video fields = 0
Ending audio to video PTS difference = 0 ticks, 0.000000 milliseconds

[mvallevand]

I have the full elephant's dream mp4 but it will not play via the PCH....my understanding is that they recorded it using an older propriatry MS codec that PCH can not decode.

That file (ed24p_00.ts) plays for me very nicely.

Martin

[UncleJohnsBand]

That file (ed24p_00.ts) plays for me very nicely.

Martin

I didn't know there was a TS version available....I found them and downloaded the first one.

Looks great....and seems to be working ok....I am going to download all the pieces and join them back together.

[UncleJohnsBand]

Yep...I am seeing that error using this utility...what causes those errors....silly question I guess....becuase if someone knew it could be addressed...

The below is from a 1hr CSI Miami HD TS recording...

Code:

xport Transport Stream Demuxer 1.01
program = 1, video channel = 1, audio channel = 1
Program Number = 2 (0x0002), Program Map PID = 48 (0x0030)
Discontinuity!, pid = 48 <0x0030>, received = 14, expected =  2, at 18128
Discontinuity!, pid = 1984 <0x07c0>, received =  7, expected = 15, at 18129
Discontinuity!, pid = 1986 <0x07c2>, received = 11, expected = 13, at 18185
Discontinuity!, pid = 1985 <0x07c1>, received =  7, expected =  9, at 18220
Discontinuity!, pid = 1984 <0x07c0>, received =  5, expected = 13, at 2832670
Discontinuity!, pid = 1984 <0x07c0>, received =  5, expected =  0, at 14549311
Discontinuity!, pid = 1985 <0x07c1>, received =  4, expected =  3, at 14549374
Discontinuity!, pid = 1984 <0x07c0>, received =  7, expected =  6, at 15353561
Discontinuity!, pid = 1986 <0x07c2>, received =  5, expected =  3, at 15353563
Discontinuity!, pid = 1985 <0x07c1>, received =  1, expected = 15, at 15353692
Discontinuity!, pid = 48 <0x0030>, received =  6, expected =  3, at 15354290
Discontinuity!, pid = 1984 <0x07c0>, received = 12, expected = 10, at 15359213
Discontinuity!, pid = 1986 <0x07c2>, received =  3, expected =  7, at 15359272
Discontinuity!, pid = 1985 <0x07c1>, received = 15, expected =  2, at 15359334
Discontinuity!, pid = 48 <0x0030>, received =  8, expected = 12, at 15360220
Discontinuity!, pid = 1984 <0x07c0>, received = 11, expected =  1, at 15364993
Discontinuity!, pid = 1985 <0x07c1>, received = 12, expected =  9, at 15365021
Discontinuity!, pid = 1986 <0x07c2>, received =  1, expected = 13, at 15365061
Discontinuity!, pid = 48 <0x0030>, received =  6, expected = 13, at 15365423
Discontinuity!, pid = 1986 <0x07c2>, received =  6, expected =  5, at 32266543
Discontinuity!, pid = 1985 <0x07c1>, received =  2, expected =  1, at 32266606
Discontinuity!, pid = 1984 <0x07c0>, received = 11, expected = 12, at 32266746
packets for pid    0 <0x0000> = 35825, first = 1, last = 34984370
packets for pid   48 <0x0030> = 35851, first = 5, last = 34984371
packets for pid 1984 <0x07c0> = 33975731, first = 3, last = 34984946
packets for pid 1985 <0x07c1> = 468769, first = 4, last = 34984820
packets for pid 1986 <0x07c2> = 468770, first = 6, last = 34984866
coded pictures = 0, video fields = 0
Ending audio to video PTS difference = 0 ticks, 0.000000 milliseconds

Ran the TS file through the VideoReDo with the Quick Stream Fix and now skipping works on the new file.

I really hate to have to add a 15 minute post-processing step if I don't have to.....

Any ideas on whether this is issue is just native to the stream I am getting from the cable company (ComCrap) or is it hardware or something else?

[steveum]

My version doesn't handle .TS files. Has there been a later version? I was told they were working on it, but I've not hear since.

I guess so. I just downloaded the trial last Friday. It was version 3.1.5. It has support for TS files.

[-stattik-]

Ran the TS file through the VideoReDo with the Quick Stream Fix and now skipping works on the new file.

I really hate to have to add a 15 minute post-processing step if I don't have to.....

Any ideas on whether this is issue is just native to the stream I am getting from the cable company (ComCrap) or is it hardware or something else?

I've been trying to figure out exactly what's causing it but I haven't nailed it down yet. I had some recordings on Monday that had over 500 discontinuity errors. Others on Monday were clean. On Tuesday, all the recordings were perfect. There's no specific pattern with any channel or show.

There's a number of apps that will remux a TS stream. tsmuxer, tsremux, and even ffmpeg.

Martin, what command line do you use with mencoder? When I tried in the past to remux a HD show to a MPEG file, mencoder typically spams the screen with time stamp errors and then mencoder proceeds to eat up all available memory.

[-stattik-]

Yep...I am seeing that error using this utility...what causes those errors....silly question I guess....becuase if someone knew it could be addressed...

The way it looks to me is that packets are getting dropped somewhere along the line. Xport is expecting the next sequence but instead is getting info from one of the later packets.

[mvallevand]

There's a number of apps that will remux a TS stream. tsmuxer, tsremux, and even ffmpeg.

Martin, what command line do you use with mencoder? When I tried in the past to remux a HD show to a MPEG file, mencoder typically spams the screen with time stamp errors and then mencoder proceeds to eat up all available memory.

Just this

mencoder {SOURCE_FILE} -ovc copy -oac copy -of mpeg -o {DEST_FILE}

Discontinuity errors can be shown in vlc too if you turn on messages

Martin

[martint123]

It was version 3.1.5. It has support for TS files.

Thanks, I have V2 - must check the upgrade path/cost.