Starting to test Comskip with h.264 support

[Taddeusz]

Erik, I keep on getting comskip crashing on HD-PVR 480i recordings with the following left on the screen:

[h264 @ 036B3A70]mmco: unref short failure
[h264 @ 036B3A70]mmco: unref short failure
[h264 @ 036B3A70]illegal short term buffer state detected
[h264 @ 036B3A70]illegal short term buffer state detected
Frame   7646 - Black frame with brightness of 16,uniform of 175 and volume of 107
[h264 @ 036B3A70]mmco: unref short failure
[h264 @ 036B3A70]mmco: unref short failure
[h264 @ 036B3A70]illegal short term buffer state detected
Frame   7647 - Black frame with brightness of 16,uniform of 195 and volume of 128
[h264 @ 036B3A70]illegal short term buffer state detected
Frame   7648 - Black frame with brightness of 16,uniform of 129 and volume of 121
Frame   7650 - Black frame with brightness of 16,uniform of 387 and volume of 111
[h264 @ 036B3A70]mmco: unref short failure
[h264 @ 036B3A70]mmco: unref short failure
[h264 @ 036B3A70]illegal short term buffer state detected
Frame   7651 - Black frame with brightness of 16,uniform of 314 and volume of 131
[h264 @ 036B3A70]illegal short term buffer state detected
Frame   7652 - Black frame with brightness of 16,uniform of 8 and volume of 121
Frame   7653 - Black frame with brightness of 16,uniform of 325 and volume of 118
Frame   7654 - Black frame with brightness of 16,uniform of 261 and volume of 138
[h264 @ 036B3A70]mmco: unref short failure
[h264 @ 036B3A70]mmco: unref short failure
[h264 @ 036B3A70]illegal short term buffer state detected
Frame   7655 - Black frame with brightness of 16,uniform of 233 and volume of 131
[h264 @ 036B3A70]illegal short term buffer state detected
Frame   7656 - Black frame with brightness of 16,uniform of 69 and volume of 129
Frame   7657 - Black frame with brightness of 16,uniform of 122 and volume of 126
Frame   7658 - Black frame with brightness of 16,uniform of 192 and volume of 137
[h264 @ 036B3A70]mmco: unref short failure
[h264 @ 036B3A70]mmco: unref short failure
[h264 @ 036B3A70]illegal short term buffer state detected
Frame   7659 - Black frame with brightness of 16,uniform of 197 and volume of 153
[h264 @ 036B3A70]illegal short term buffer state detected
Frame   7660 - Black frame with brightness of 16,uniform of 48 and volume of 133
Frame   7661 - Black frame with brightness of 16,uniform of 2 and volume of 147
Frame   7662 - Black frame with brightness of 16,uniform of 1 and volume of 153
[h264 @ 036B3A70]mmco: unref short failure
[h264 @ 036B3A70]mmco: unref short failure
[h264 @ 036B3A70]illegal short term buffer state detected
Frame   7663 - Black frame with brightness of 16,uniform of 28 and volume of 158
[h264 @ 036B3A70]illegal short term buffer state detected
Frame   7664 - Black frame with brightness of 16,uniform of 21 and volume of 144
Frame   7665 - Black frame with brightness of 16,uniform of 22 and volume of 144
Frame   7666 - Black frame with brightness of 16,uniform of 0 and volume of 120
[h264 @ 036B3A70]mmco: unref short failure
[h264 @ 036B3A70]mmco: unref short failure
[h264 @ 036B3A70]illegal short term buffer state detected
Frame   7667 - Black frame with brightness of 16,uniform of 0 and volume of 119
[h264 @ 036B3A70]illegal short term buffer state detected
Frame   7668 - Black frame with brightness of 16,uniform of 19 and volume of 128
Frame   7669 - Black frame with brightness of 16,uniform of 449 and volume of 138
Frame   7670 - Black frame with brightness of 16,uniform of 364 and volume of 123
[h264 @ 036B3A70]mmco: unref short failure
[h264 @ 036B3A70]mmco: unref short failure
[h264 @ 036B3A70]illegal short term buffer state detected
[h264 @ 036B3A70]illegal short term buffer state detected
[h264 @ 036B3A70]mmco: unref short failure
[h264 @ 036B3A70]mmco: unref short failure
[h264 @ 036B3A70]illegal short term buffer state detected
[h264 @ 036B3A70]illegal short term buffer state detected
[h264 @ 036B3A70]mmco: unref short failure
[h264 @ 036B3A70]mmco: unref short failure
[h264 @ 036B3A70]illegal short term buffer state detected
[h264 @ 036B3A70]illegal short term buffer state detected
[h264 @ 036B3A70]illegal short term buffer state detected
[h264 @ 036B3A70]reference picture missing during reorder
[h264 @ 036B3A70]Missing reference picture
[h264 @ 036B3A70]reference picture missing during reorder
[h264 @ 036B3A70]Missing reference picture

It appears that libavcodec.dll is causing the problem at offset 00061eaf

I've attached both the crash log created by Windows and the comskip log for the file.

[erik]

Could you upload a short recording to my ftp server?
If yes I will PM you the details.

EDIT

Don't mind, I already have a recording that shows the same problem.

[erik]

Build 0.80.010 is out.
Please test if the problem is solved

[Peter_h]

Hi Erik,

I had the same problems as above and build 0.80.010 fixed it.

Thanks for the quick fix.

[Taddeusz]

Yes, thank you for responding so quickly. That seems to have done the trick.

[gplasky]

Same here. Looking good.

Gerry

[SWKerr]

This is a great tool and the latest version I am using which is 0.80.008 seems to have been very stable on both the HD-PVR files and the HDHR files. Now that I am using the latest Demux Beta life has been good.

I was wondering if there was anyway to set a limit on the size of a clear area. What I seem to run into is that comskip will identify the start and end Ok but there will be a small area in between the commercials that is not flagged so the auto skip stops in the middle. Since there is no show I can think of that would just have 20 seconds of good stuff between adds would it be possible to scan the file after it completes and not identify any range that is less than a set number of seconds or frames. It seems like that is something that would be doable or already supported but I can’t seem to find it.

[Peter_h]

Originally Posted by SWKerr

This is a great tool and the latest version I am using which is 0.80.008 seems to have been very stable on both the HD-PVR files and the HDHR files. Now that I am using the latest Demux Beta life has been good.

I was wondering if there was anyway to set a limit on the size of a clear area. What I seem to run into is that comskip will identify the start and end Ok but there will be a small area in between the commercials that is not flagged so the auto skip stops in the middle. Since there is no show I can think of that would just have 20 seconds of good stuff between adds would it be possible to scan the file after it completes and not identify any range that is less than a set number of seconds or frames. It seems like that is something that would be doable or already supported but I can’t seem to find it.

The min commercial length is in the .ini file I believe as:

min-commercial_size=4

Mine was set to 4 (seconds) by default.

However, it sounds like there is something else that is causing the commercial not to detect like a logo, etc. You might might want to take a closer look at that commercial block and see what you can find then tweak or report back.

-Peter

[jasongrimme]

Hello,

I'm running 80.009 against my .ts files captured with the HDPVR. I've tried setting skip_b_frames to 0, 1 and 2, and each time it has taken approx 1h20m to run.

Should I expect different results with changing that paramater? The content is HD 1080i episode of Lost, and I'm running comskip on an Intel Quad core 2.4GHz box.

Just wondering if there is anything I can do to speed things along, or if what I am seeing is as expected.

Thanks in advance, great tool with great support!

[erik]

Skip_b_frames only works for mpeg, not yet for h.264
and only in the donators version

[jasongrimme]

Sorry, should have clarified, using donated version.

So, I don't think I can run comskip with a higher priority, at this point my options to increase throughput are more powerful processor or comskip updates. Does that sound accurate?

Thanks again!

[erik]

Comskip does not have the fastest h.264 decoder
Maybe you can try using dvrmttoolbox to convert the h.264 to log resolution mpeg and use comskip on the mpeg
Ugly but it MAY be faster

[Taddeusz]

On the 480i recordings from my HD-PVR I see a lot of short term buffer failures. What could be causing this?

[erik]

Originally Posted by Taddeusz

On the 480i recordings from my HD-PVR I see a lot of short term buffer failures. What could be causing this?

I suspect the demux, not sure.

[Taddeusz]

Originally Posted by erik

I suspect the demux, not sure.

Would you like a sample?

[erik]

yes, 20MBytes would be enough.
Can I download from somewhere or shall I PM you with my ftp details?

[Eckwell]

Erik-

Comskip is so awesome that I decided to Re-donate some funds to the cause... You should see it shortly. THANK YOU for your hard work and dedication on defeating H.264.

[Peter_h]

Originally Posted by erik

I suspect the demux, not sure.

I get the same but the job still finishes. Is this a problem?

[erik]

Originally Posted by Peter_h

I get the same but the job still finishes. Is this a problem?

Nope.
Picture quality is degraded but that does not cause a big problem.

[Phydeaux]

I've donated to the cause based purely on the generally high satisfaction I'm seeing here and elsewhere with Comskip. And I've downloaded the latest version to use on my h.264 files as output by a Hauppauge HD PVR. I'm having some issues getting it configured correctly. At times it seems too aggressive and chomps out part of the programming along with the commercials. At other times it seems timid and leaves several seconds of commercial in place before the program actually comes back on after a break.

I've read the tuning file and... frankly I'm lost. Is there a tuning guide for dummies? And does this tuning have to be done for different channels or is this based primarily on the source, and once tuned is generally good for anything from that source?

Thanks,
RLW