Detection near perfect, but goes really bad

To discuss the tuning of comskip and for posting your ini files
Post Reply
Posts: 22
Joined: Mon Jul 31, 2006 2:15 am
Location: New Mexico

Detection near perfect, but goes really bad

Post by toricred »

I've got comskip nearly perfect most of the time, but lately I've been seeing several occasions where it looks good while processing and everything gets screwed up just before it finishes processing. What is it enforcing at the very end?
Posts: 1
Joined: Mon Apr 06, 2009 7:28 pm

Re: Detection near perfect, but goes really bad

Post by Skindred »

I have a similar issue, when using -d 2
It doesn't want to build any commercial blocks (big gray blocks on the top line).

-d 10 doesn't help to make it understand that I only want to use logo as a detection method, and still have it create good blocks.

-d 11 (which includes uniform frames), does however allow me to see gray blocks representing the commericalbreak.

Is comskip uniformity oriented?

Because it seems that it will only process the final results, if it knows where the black frames are...
Problem is that one of the commercials is mostly black with some white text in the middle..
and so it stops the commercialbreak before that commercial, while infact it should continue for another 20s or so.
Site Admin
Posts: 3368
Joined: Sun Aug 21, 2005 3:49 pm

Re: Detection near perfect, but goes really bad

Post by erik »

During live processing a simplified algorithm is used that does not use sound.
If the sound decoding fails you can have bad results.
Also the global heuristics only work when all processing is done.

Send me a .csv file, .log file and a .ref file as described in the "how to ask for help" topic in the support forum and I will have a look.
Post Reply