2042 Scanning through Transport Stream causes freezing.

[flyordie]

I recently got a SiliconDust HDHomeRun over the air ATSC tuner. I used BeyondTV 4 to capture the stream from fox. The raw stream appears to be 1280x720 at 59.940 fps. Since BeyondTV seems to just write the raw transport stream to a file I opened the file with the DGIndexNV for segment cutting. I usually hold down the left or right arrow key to find the begging or the end of the section I want to export the audio and cut later. This file keeps freezing up during the scanning. I have to wait a bit before I can go back to scanning. Its rather odd. With the original 6GB file one of the threads will max a cpu core for a bit, but once its stopped I can return to scanning. Its always the same thread that maxes. Sometimes after its finished maxing a processor, my cursor in the navigation timeline has jumped near the end. I've cut 1080i/29.976 source material I capture using the same equipment without any of the hangups. I've uploaded a segment of the file. Any idea what I should to to mitigate this issue in the future?
This happens with x86 or x64 bit version of DGIndexNV 2042
Thanks.
http://goo.gl/GLf6l

[admin]

You say I cannot duplicate the issue with your sample?

I don't have any immediate idea about it. It don't think it can be queued messages because I abort a pending seek if a new one starts.

Maybe you can click and drag the timeline position instead of holding down the arrow key
to get close to your desired location.

[flyordie]

Thanks for getting back with me. After opening the transport stream with your software, holding down the right arrow key to scan forward didn't cause your software to hiccup?

Clicking on the timeline conservatively was the only way I was able to get the sections I wanted out of that file. I have another show on fox tonight which should give more data points.

For me, using the left and right arrow keys or even the skip to next GOP buttons to get to the correct black transition would even cause the freeze-ups.

I'm running a GTX 570 with the 296.10 x64 drivers. I have a 32-bit machine running the GTX 460 I can test it on tonight and see if the problem reappears.

Is there some specific diagnostics or debug output I could generate with your software?
The threads from inside your executable in Process Explorer are denoted as an offset from the beginning of your .exe. It is always the same thread/offset that freezes up. Would knowing that help you at all?

[admin]

I misunderstood your post. I'll download and try it now.

[admin]

Not seeing any problem here with GTX 460, 32-bit, 296.10, also no problem with GT 520, 32-bit, 296.10.

[flyordie]

I tried it on my 32-bit Windows 7 PC with the GTX 460 and the 296.10 drivers and the problem still happened. My files are rather large. I also noticed when that thread is consuming one of the processors 9 times out of 10 my hard drive is getting thrashed.

I tried using your DGSplit to chunk it under 3GB per file and it still would freeze. It appears to be a container issue. I tried re-muxing with tsMuxeR 1.10.6 and the file scans a lot better. I still have issues scanning backwards and have to click on the timeline with the mouse, but it doesn't freeze up.

So since I have this work around will you close this case?

[admin]

Rather than close it I'd like to try to solve it. I'm going to try on some very large files I have.

[flyordie]

I sent you a PM. The BeyondTV 4 files have a .tp extension which MediaInfo sees it as a MPEG-TS container.

MediaInfo Info

Code: Select all

General
ID                                       : 0 (0x0)
Complete name                            : Q:\Recorded TV\Glee-(Props; Nationals)-2012-05-15-0.tp
Format                                   : MPEG-TS
File size                                : 13.4 GiB
Duration                                 : 2h 39mn
Overall bit rate mode                    : Variable
Overall bit rate                         : 12.0 Mbps

Video
ID                                       : 49 (0x31)
Menu ID                                  : 3 (0x3)
Format                                   : MPEG Video
Commercial name                          : HDV 720p
Format version                           : Version 2
Format profile                           : Main@High
Format settings, BVOP                    : Yes
Format settings, Matrix                  : Default
Format settings, GOP                     : M=3, N=12
Codec ID                                 : 2
Duration                                 : 2h 39mn
Bit rate mode                            : Variable
Bit rate                                 : 11.0 Mbps
Maximum bit rate                         : 11.9 Mbps
Width                                    : 1 280 pixels
Height                                   : 720 pixels
Display aspect ratio                     : 16:9
Frame rate                               : 59.940 fps
Standard                                 : Component
Color space                              : YUV
Chroma subsampling                       : 4:2:0
Bit depth                                : 8 bits
Scan type                                : Progressive
Compression mode                         : Lossy
Bits/(Pixel*Frame)                       : 0.200
Stream size                              : 12.3 GiB (92%)

Audio
ID                                       : 52 (0x34)
Menu ID                                  : 3 (0x3)
Format                                   : AC-3
Format/Info                              : Audio Coding 3
Codec ID                                 : 129
Duration                                 : 2h 39mn
Bit rate                                 : 384 Kbps
Channel(s)                               : 2 channels
Sampling rate                            : 48.0 KHz
Compression mode                         : Lossy
Delay relative to video                  : -801ms
Stream size                              : 439 MiB (3%)
Language                                 : English

Text #1
ID                                       : 49 (0x31)-CC1
Menu ID                                  : 3 (0x3)
Format                                   : EIA-608
Muxing mode                              : A/53 / DTVCC Transport
Muxing mode, more info                   : Muxed in Video #1
Duration                                 : 2h 39mn
Bit rate mode                            : Constant
Stream size                              : 0.00 Byte (0%)

Text #2
ID                                       : 49 (0x31)-1
Menu ID                                  : 3 (0x3)
Format                                   : EIA-708
Muxing mode                              : A/53 / DTVCC Transport
Muxing mode, more info                   : Muxed in Video #1
Duration                                 : 2h 39mn
Bit rate mode                            : Constant
Stream size                              : 0.00 Byte (0%)

Text #3
ID                                       : 49 (0x31)-4
Menu ID                                  : 3 (0x3)
Format                                   : EIA-708
Muxing mode                              : A/53 / DTVCC Transport
Muxing mode, more info                   : Muxed in Video #1
Duration                                 : 2h 39mn
Bit rate mode                            : Constant
Stream size                              : 0.00 Byte (0%)

Text #4
ID                                       : 49 (0x31)-6
Menu ID                                  : 3 (0x3)
Format                                   : EIA-708
Muxing mode                              : A/53 / DTVCC Transport
Muxing mode, more info                   : Muxed in Video #1
Duration                                 : 2h 39mn
Bit rate mode                            : Constant
Stream size                              : 0.00 Byte (0%)

[admin]

I couldn't reproduce it with any of my large files. I've answered your PM. Best bet is to mail me the disks as you suggested.

[flyordie]

I will test what you asked tonight. Its a shame I can do it over a remote desktop.
I will let you know and we can move forward accordingly.

Lets say there is a file made up of ABC where A is the first 100MB, B is the second 100MB, and C is the rest of the large file.
Lets say (will confirm tonight) ABC messes up, BC messes up, A messes up, and B messes up.

Should I then upload A and B and see if those parts mess up for you?

Right now my ini file is set to
Decode_Modes=0,1,0

Does this matter?

[admin]

Give a try to Decode_Modes=0,0,0.

The idea is to give me the smallest piece that still fails for you. If it is small enough, I can download it. If not, use mail.

[flyordie]

Side note:
x32/x64 act the same. If I try and use your Output Trimmed TS feature with a small section that encloses one of the freezes I can make your program crash. I can save project and demux video without a problem.

Like we talked about before I used DGSplit to Chunk the stupid large file into 100MB chunks. Scene one is a subset of the first 100MB chunk and scene two is from the second 100MB chunk.

I used your DGSplit 1.2 to chunk the first scene into 20MB chucks.

This is where the file freezes for me when I use the Step forward by GOP |> button or when I hold down the right arrow key on the keyboard.

http://goo.gl/xqgBV

The second scene I was able to narrow into a 10MB chuck size and its still obvious there is more video left.

http://goo.gl/0NZKx

You will probably not have issues. Since I don't get a timestamp in your software I thought the cursor in the timeline might help you narrow down the issue.
Decode_Modes=0,0,0 or Decode_Modes=0,1,0 made no difference.

[admin]

You will probably not have issues.

Correct. No issue here.

Are you overclocked?

[flyordie]

Yes (4Ghz), I will undo and let you know.

update: I put everything back to stock and it still sticks. I put the two files on my other machine with 32-bit win 7, q6600, and the GTX 460. Both machines cannot advance past the point in those pics. I can click past that point but the next GOP button and the right arrow will not go any farther. I can click past that point and then I can advance with the right arrow or the next GOP button.

One the Q6600 PC I even downloaded a new .zip of the software and verified it would not work until I added the license.txt file and it still sticks at the places indicated above.

[admin]

Can you try the latest 301 driver from here?

[flyordie]

No difference still cannot move past those stops using the next GOP button. I have to click past it to continue moving to GOP locations. I'm not sure what is different between your setup and mine.
I have three PCs.
i7 980x now running stock, 16 GB of DDR3, GTX 570 now running 301.24 Driver - BETA, Windows 7 Pro 64-bit, AviSynth 2.58, build:Dec 22 2008 [08:46:51].
Core 2 Quad Q6600 (stock), 4GB of DDR2, GTX 460 still running 296.10, Windows 7 Pro 32-bit, same AviSynth.
Intel Core 2 Duo E8400, 4GB of DDR2, GT 520, Windows 7 Pro 32-bit.

I haven't been testing the core 2 duo machine. I have have to reinstall windows 7 32-bit. That should happen this weekend for another data point.