Search found 8 matches
- Thu Oct 17, 2013 1:43 am
- Forum: Bugs
- Topic: 81_056 donators live processing quits too early
- Replies: 4
- Views: 9211
Re: 81_056 donators live processing quits too early
Don't know if this matters, I forgot to mention my recording drive is a StableBit Drivepool volume, rather than a normal NTFS volume. 2 recordings started at 8:00 (so really 7:58), one of them still ongoing, but comskip exited very quickly on both, finding no commercials: ###########################...
- Wed Oct 16, 2013 7:45 pm
- Forum: Bugs
- Topic: 81_056 donators live processing quits too early
- Replies: 4
- Views: 9211
Re: 81_056 donators live processing quits too early
Running Windows 7 x64, recordings are made in Windows Media Center using a InfiniTV6 cablecard tuner. 81_050 keeps going until after the recording finishes successfully with the same INI, while 81_056 exits a few minutes after I launch it, catching the commercials that were there up to that point, b...
- Wed Oct 16, 2013 1:28 am
- Forum: Bugs
- Topic: 81_056 donators live processing quits too early
- Replies: 4
- Views: 9211
81_056 donators live processing quits too early
Tried doing live TV processing with the latest version, but it kept quitting long before the recordings completed. I tried launching it from a batch script which waits 10 minutes before running comskip, because I read others had issues if the processing started as soon as the recording did. Didn't s...
- Wed May 23, 2012 5:22 am
- Forum: Support
- Topic: Any Alternative to DTb File Watcher?
- Replies: 95
- Views: 77394
Re: Any Alternative to DTb File Watcher?
How do you make it run as low/idle priority under DirMon2, or are you running it as normal priority?
Also, if you have your recordings and xml files in 2 separate folders, does DirMon2 allow you to specify that the cleanup should check the recording folder for the wtv?
Also, if you have your recordings and xml files in 2 separate folders, does DirMon2 allow you to specify that the cleanup should check the recording folder for the wtv?
- Mon May 21, 2012 5:25 am
- Forum: Feedback
- Topic: File buffering / read sizes
- Replies: 5
- Views: 10157
Re: File buffering / read sizes
I just came across the post about the missing ';' after disable_heuristics=4 in the comskip.ini, which I guess was making some of the settings screwy? After adding the ';' it processes an hour of HD in about 3 minutes even without pre-caching it, which is better than I had gotten it down to before e...
- Sun May 20, 2012 10:34 pm
- Forum: Feedback
- Topic: File buffering / read sizes
- Replies: 5
- Views: 10157
Re: File buffering / read sizes
The filling of cache is done concurrently with comskip processing, and yes, it is many times faster. "before being either CPU or disk limited" was bad wording on my part -- of course it is limited somewhere . Filling the cache keeps it from being disk limited, and even then the CPU isn't p...
- Sun May 20, 2012 7:36 pm
- Forum: Feedback
- Topic: File buffering / read sizes
- Replies: 5
- Views: 10157
Re: File buffering / read sizes
BTW, I threw together a small app that I now run in parallel with comskip, which reads the file throttled to 25MB/s (I haven't made the throttling configurable yet). This allows me to process 2 HD shows simultaneously before being either CPU or disk limited on the Core i7 920. (For some reason even ...
- Thu May 17, 2012 2:03 am
- Forum: Feedback
- Topic: File buffering / read sizes
- Replies: 5
- Views: 10157
File buffering / read sizes
I noticed using procmon that the reads done by comskip are only 32KB, and some are even have the I/O flags "Non-cached, Paging I/O". I'm thinking the non-cached means FILE_FLAG_NO_BUFFERING is set, which means the OS can't choose to do any read-aheads or caching for you on the file. ShowAn...