When commercial detection is in process, and the content is deleted (moved to trash) commercial detection continues, tying up resources for other processes. Would it be possible to exclude items in the trash from commercial detection and stop commercial detection if an item is moved to the trash?
The process is killed after 8 hours. However it would be nice to have a setting that we could specify the duration before comskip is terminated. I have a Linux server running on an 8 core i7. The longest comskip will ever run is like 20min. I'd love to be able to set the max at 1hr.
Usually never a big deal but sometimes I inadvertently delete a program right after it records and forget to wait until comskip is done.
Files that have been trashed before commercial detection starts do not have commercial detection run on them.
We don't have a simple way at the moment to interrupt an in-progress commercial detection run in the case you're describing where you've deleted a file after the detection has started. It's something we can look into in the future.
2 Likes
I'm on a NAS with 4 cores, only 3 used for com skip. sometimes the backlog of pending programs to process gets so long that the program I'm watching never gets processed before I'm done watching. Mainly 1 hours blocks of news, that record back to back.
Thanks would benefit my use case.