Can you run ComClean manually

[SteveO]

I've been playing around with the Comskip debug window and find I normally need to adjust the commercial endpoints at the beginning and ending of recordings. My question is, rather than have Comclean run automatically by using the postprocessing bat file, can I do it manually after I've checked and modified the commercial markers?

Thanks,
SteveO

[ram4x4nut]

Yep ... from the command line, cd to the directory where comclean is then:

comclean "{drive}\{directory}\{filename}"

You must have the quotes around it, and it must have the files created by comskip in the same directory as the .mpg file. It's that simple.

[SteveO]

Thanks, gave that a try but dialog in the command prompt window indicates...

range [0:5:45-2:6:11] results in invalid [173067222-3797947660] range
resulting cutpoints: 0:0:0 2:0:26
the system cannot find the file specified.

Any idea what may be the cause? Is there a log file that may help troubleshoot the problem?

Thanks again for the help.

[ram4x4nut]

rerun comskip on the original file. You can run it manually the exact same way as running comclean manually. Don't delete any files create by comskip as they are needed by comclean.

[dgeezer]

You can also run both programs manually by right clicking the mpeg file and then "open with" then "choose program" and browse to comclean or comskip in the gbpvr directory. After the first time you run it this way comclean will appear as one of the default choices whenever you right click an mpeg file.

[DeadRun]

If you are going to touch the process manually on a regular basis, I think you would be better off by just using Cuttermaran to manually identify the commercials and letting Cuttermaran cut the file. This way you will end up with a perfect cut every time. If you let postprocessing.bat or some other automatic process demux the files, the manual commercial identification with Cuttermaran takes about 3.5 minutes per show.

I only say this if you are going to manually touch the process as a routine.

[SteveO]

Thanks for the feedback and suggestions. For some reason reason I'm still unable to get comclean to work successfully. I've tried running a new comskip and generating new files, but comclean still generates the same errors. It renames the .mpg file to _original.mpg, but never generates the new cleaned file. I'm open to more ideas, I really want to get this to work.

Thanks,
SteveO

[DeadRun]

First, I would suggest that you use comclean2. My experience is that the cutting program (mpgtx) used in comclean leaves the file with a "corrupt" timeline. Comclean2 uses Cuttermaran to cut the file after demuxing and then remuxes the file. This eliminates the timeline problem.

It is probably not you comclean.bat file, but if you post it we can take a look to see if it is a problem there.

[erik]

Some late reply's, have been traveling,
The problem could be a currupt timeline in the recording.
mpgtx uses the PTS info to find the cut positions.

The log states
range [0:5:45-2:6:11] results in invalid [173067222-3797947660] range
resulting cutpoints: 0:0:0 2:0:26

Is your recording indeed more the two hours?
Did you use the logging trick as explained in the comclean wiki entry?

Would it be possible to send me the .csv file and a correcte .txt file so I can try to improve comskip w.r.t the start and end of the recording?

[SteveO]

Thanks for the replies. I will give comclean2 a try. I didn't realize there was a second version of comclean. It sure would be nice if I could get it to work. I've spent a ton of time today trying to use projectX and cuttermaran to 'simply' cut out the beginning and end of my capture. I've learned a lot but man what a pain! Took quite a while getting java downloaded and installed for projectX to work. Only problem I have left to resolve is getting the automatic chapters to actually work.

Eric, regarding the begin/end of capture: what I'm capturing are vcr movies. My only problem with the beginning and ending is the extra 'stuff' at each end since gbprv manual record function doesn't allow you to be too precise. It's not a problem with actual commercial detection.

I will post back with my results with comclean2.

Thanks!