retiming comskip to run

[dflipb]

Is there also a way that comskip could be set up to run at a certain time. I'm recording hdtv and when comskip goes, it take up processing power and if I am recording a show right after another, then I get skipping. Would this be possible?

[stefan]

Try this:
In postprocessing.bat, instead of running comskip straight away, enter

at 02:00 comskip %1

I am not sure about the exact format of the time (i.e. am and pm), but with some trial and error you should be able to get it to work. This would make all files be run through comskip at the same time, which might or might not be a problem for you.

[reboot]

Alternatively, try running a parallelprocessing.bat
Put comskip, comclean, rename recording etc. in it.
Comskip will run during the recording, thus using far less cpu power.
If you don't run any other processing, this method will probably work best, as comskip will finish within a few seconds of the show/recording end.

If you wish to have comskip run at a given time, try DirMon to schedule it, or even windows scheduler (task manager?).
The problem may be to get comskip to run on all files.
If you have 3 recordings during the day, and run comskip at night, it may not find the first two files, depending on how you set it all up.

[dflipb]

Wow, thanks for the help, I'll give that a try.

[stefan]

Np. Please tell us if it helps =)

[dflipb]

I'll probably have to try it on the weekend. thanks again

[mikeneron]

Does comskip.exe run in low priority by default? I know when I run comclean, it calls different executables that do not run in low priority mode and I needed to edit the batch file and add "start /low" before calling each executable so that it doesn't use up a lot of CPU while running.

I was going to create my ParallelProcessing.bat file with the following:
start /low /min comskip -n %1

But if comskip.exe always runs in low priority, then I would just need:
comskip -n %1

Can someone verify that comskip always runs in low priority mode?

Thanks,
Mike.

[reboot]

Comskip will run, using what it needs for CPU. If other processes need CPU cycles, comskip will automatically throttle back.
If you run comskip in parallel, then it uses almost no cpu at all, thus you won't need the "start /low /min".