2006-06-30, 07:55 PM
It took me awhile to figure out what was happening, but I noticed that I was running out of disk space even after I had culled a lot of recordings. I saw that some recordings were being removed from the Recordings menu, but still physically existed on the hard drive. I finally figured out what was happening. I was removing the recording whist comskip was removing the commercials. So GBPVR removed the recording from the database, but was prevented from deleting the file because it was in use. Thus orphaning the file, taking up my precious disk space.
Is there anyway we can prevent GBPVR from removing the recording if itâs in the process of comskiping? Or, be able to stop the comskip process, and then remove the file along with the database entry.
I have an idea about how this could be done. When comskip starts to work on a file to mark the commercials, could it also create a marker file. Then when itâs finished, remove the marker file. Mean time, GBPVR checks for the marker file when it goes to delete a recording. And if the two bump heads, GBPVR would either tell me I have to wait for comskip to finish, or be able to stop the process and finish its work
Thanks for reading.
Is there anyway we can prevent GBPVR from removing the recording if itâs in the process of comskiping? Or, be able to stop the comskip process, and then remove the file along with the database entry.
I have an idea about how this could be done. When comskip starts to work on a file to mark the commercials, could it also create a marker file. Then when itâs finished, remove the marker file. Mean time, GBPVR checks for the marker file when it goes to delete a recording. And if the two bump heads, GBPVR would either tell me I have to wait for comskip to finish, or be able to stop the process and finish its work
Thanks for reading.