So I tend to make some massive recordings, like 12 hours to record a certain sport. Com skip then runs, and understandibly it takes awhile on a recording that size. The issue I have is that if I delete a bunch of shows in channels to make space once com skip has already has started, I have to wait until comskip is done for the pc to actually delete the shows and free up the space. This creates a problem when I'm running low on space and looking to free up space quick, because I never know how long comskip will be and I can't free up space until comskip finishes. Is there anyway to allow show deletion while comskip is running? Or pause it briefly to allow show deletion? Or something else? Thanks.
Could always kill the process from the task manager and redo commercial detection once done deleting- no harm.
This sounds like a problem with the OS and filesystem, rather than specific to Channels itself. As stated above, killing the comskip process ought to release the file handles; also, a sync after deletion (depending upon the OS/FS) should ensure that all cached disk writes—including deletions—are completed.
IIRC, it used to terminate comskip when you deleted a recording before they implemented TRASH last year.
Now selecting DELETE or TRASH on a recording just marks it for delayed (1 day default) deletion from the file system.
I don't think so.
Maybe you're thinking of recording being stopped (tuner released) when deleted. That broke briefly when trash was introduced but still works now.
A long running comskip can currently delay the pruner which deletes old episodes. This is a known issue.
Yes, so I didn't (IIRC that is)
How difficult is it to terminate a running comskip when the user deletes/trashes the recording being comskipped?
If a user killed the process themself, would that cause any issues?