ComSkip isn't happening

[pBS]

ahh, here tis...set to post-proc. and i see it starting post que but not what the cmd is...

look for "1st and ten" recording..

[sub]

2009-05-01 14:01:42.375 VERBOSE [5] getValue() loading new key/value into cache: /settings/ProcessCommercialsDuringRecording
2009-05-01 14:01:42.375 VERBOSE [5] getValue: /settings/ProcessCommercialsDuringRecording : true

That log is still set to process commercials during the recording, not post recording.

[pBS]

aha! i found the culprit.. i KNEW i'd set it to run *after* and confirmed in config.xml so was puzzled at the logs..[i cleared out all logs b4 reproducing]
another config.xml in system32!! [grrr]
no idea how it got there...
it had it set to true...
running one now with confirmed-in-logs post...

[pBS]

yep...worked for me....
i think i'll stick a blank, read-only file in system32 to prevent this again...
sorry for hijacking...

EDIT: nope,can't do that...rec service won't start...!!!
is there no way to ignore any config.xml except the known good one in gbpvr dir?
ahh,it's probably dotnot at work...i'll just stick a delete cmd in somewhere..
thanx for helping me figure it out..

[zehd]

yep...worked for me....
i think i'll stick a blank, read-only file in system32 to prevent this again...
sorry for hijacking...

EDIT: nope,can't do that...rec service won't start...!!!
is there no way to ignore any config.xml except the known good one in gbpvr dir?
ahh,it's probably dotnot at work...i'll just stick a delete cmd in somewhere..
thanx for helping me figure it out..

I don't understand why another copy of config.xml is stored in the system32 folder on your machine...

[pBS]

i believe it was a previous lockup due to other things, windows looks to write the file somewhere, and my gbpvr\config.xml got corrupted by adding trash at end...
so seems windows losing where to write the file to, and forgetting what to write to the real one , it adds registry info to the end of config.xml, and writes config.xml to %windir%\system32...

maybe a drive error, windows errror or dotnet error, can't tell...
had some lockups due to heat a while back so may have come from that....

i do see it as a problem that any config.xml in the path will hose gbpvr...
apparently dotnet isn't that particular where it gets it settings from...lol
that's how reliable dotnet is, it doesn't even pay attention to you when you say to get config from a certain place..!? it'll just take first one it finds?! geez..

they'll just call it a 'feature' so they won't have to change it to work correctly..lol

[mkenyon2]

I don't have a postprocessing.bat file. Is that why? Is there a sample out there?

[mkenyon2]

Okay, just put Comskip 80.023 in, with NO PostProcessing.bat file. The box for 'Run while recording' is NOT set. Let's see if anything happens.

[sub]

I don't have a postprocessing.bat file. Is that why? Is there a sample out there?

You normally wouldnt have one of these. Its a file that people can optionally create if they want to run jobs after recording. If they do create one, then they also need to run comskip from it if thy want this (since PostProcessing.bat overrides whatever commercial detection settings are specified in the config app)