Commerical Skip

[MaBo]

Stefan, bgowland,

Quote[/b] ]

Quote[/b] ]Quote (AK75 @ Mar. 13 2005,23:09)
play_nice_start=0100
play_nice_end=0600

Comskip will only run between 1:00am and 6:00am? Do I have this correct?

Hmm... I haven't tried that, but I would guess that it means that between 1:00am and 6:00am comskip will run slower than other times, thus making the processor less hot, hence making the fan go slower (hopefully quieter).

It is just so! I'm not sure about the =-sign, but if the ini file looks like that it is that way.

Another advantage is that the computer is more responsive, as comskip is not eating up all cpu-cycles.


Greetz,
MaBo

[Torque]

Anyone care to post the contents of their comskip .ini file. I've been trying to use comskip all week and it's random as ####. Maybe it gets one commercial break right in every show. Most of the time it shows what it thinks is a commercial in the middle of show but doesn't flag the actual commercials.

[MaBo]

Did you set the correct framespersecond in you ini-file?

PAL: 25 fps, NTSC its different

Greetz,
MaBo

[gwyden]

Mine has a crash issue when I use logo detection so I removed that and closed caption. This works most of the time and i am hopinh to refine it a little more but here is my comskip.ini if you want to use it.

Quote[/b] (Torque @ Mar. 17 2005,11:14)]Anyone care to post the contents of their comskip .ini file. I've been trying to use comskip all week and it's random as ####. Maybe it gets one commercial break right in every show. Most of the time it shows what it thinks is a commercial in the middle of show but doesn't flag the actual commercials.

<table border="0" align="center" width="95%" cellpadding="0" cellspacing="0"><tr><td>Code Sample </td></tr><tr><td id="CODE">
detect_method=45;1=black frame, 2=logo, 4=scene change, 8=fuzzy logic, 16=closed captions, 32=aspect ration, 255=all
verbose=10;show extra info
fps=29.97;frames per second (NTSC=29.970, PAL=25)
border=10 ;border around edge of video to ignore
max_brightness=120 ;frame not black if any pixels checked are greater than this (scale 0 to 255)
test_brightness=80 ;frame not pure black if any pixels checked are greater than this, will check average brightness (scale 0 to 255)
max_avg_brightness=40;maximum average brightness for a dim frame to be considered black (scale 0 to 255)
max_commercialbreak=350;maximum length in seconds to consider a segment a commercial break
min_commercialbreak=90;minimum length in seconds to consider a segment a commercial break
max_commercial_size=300;maximum time in seconds for a single commercial or multiple commercials if no breaks in between
min_commercial_size=4 ;mimimum time in seconds for a single commercial
min_show_segment_length=30
require_div5=0
div5_tolerance=.75
live_tv=0
delete_logo_file=0
min_black_frames_for_break=1;
two_pass_logo=0
intelligent_brightness=0
black_percentile=.0073
score_percentile=.71
output_default=1
output_videoredo=1
give_up_logo_search=600
play_nice_start=1500
play_nice_end=2359[/QUOTE]

[gwyden]

anyone else having problems with comskip .64? If i run it with Logo detection enabled with the other tests i get a GPF and the program dies. If i run it as a standalone it runs fine, but in combination it fails. I guess this is just a rant unless someone has any ideas?

[Gulla]

What does the logo detection do?

[rtiangha]

Quote[/b] (Gulla @ Mar. 18 2005,05:00)]What does the logo detection do?

It detects when the bug (what TV stations call their logo that they make appear in the corner of the screen during TV shows) dissapears since this usually occurs when a comercial is about to start.

[xsherlock]

in my case comskip .64 almost lways kills my PVR machine always no matter what detection methods are being set. Recordings are beeing done with PVR350. setting nice makes it survive 10 times longer (it dies on 10-15 minutes into the show and not within first 2 minutes). Hardware is shuttle barebone with p4 2.4 and 512 mb ram.

The strange issue is that I can proccess the same files on my the desktop machine without problems.

[rtiangha]

Then perhaps it's a heating issue (as in your CPU is getting too hot)? Running a comskip scan usually takes about 100% CPU usage which generates a lot of heat. If your system doesn't have adequate cooling (especially in a small form factor case), then the excess heat can cause your system to lock up or other errors.