[mythtv-users] orphaned videos and orphaned recordings that really are matches
Jeremy Jones
jeremy.dwain.jones at gmail.com
Fri Feb 3 20:49:56 UTC 2012
I had an issue that may or may not be common, if it is or happens to
someone else, I have a solution in place, and would like to share it,
if it is not going to have the potential to screw up something else:
The problem:
I have a userjob transcoding my recorded tv and I messed somthing up
in it. By the time I noticed my mistake I had 20-30 recordings with
the extension .mpeg (which my userjob created) that did not have a
matching database entry. Conversely I also had the same number of
database recording entries that did not have a matching video file
with the same name and a .mpg extension.
The repair of the database:
I did a hack job on find_orphans.py to match up those two sets of
orphans and 'fix' the recorded table to match. Would this type of
addition be something of value?
The fix:
Of course the first fix was to take out the error in the userjob that
made the script bomb. The second change I made may be of value to the
group:
I made a change to my transcode script to update the recording table
immediately after the original file is deleted. That way doing
something stupid later in the script like I did won't mess up a bunch
of recording entries. Since my script is based on the
transcode_wrapper_stub.py, I thought the change may be relevant there
as well.
Side note:
Before posting here, I attempted to contact a dev directly by email to
see if this would be an acceptable addition to find_orphans.py, but I
did not get a response. I assume that my email was filtered out and
he never read it, since that is probably what I would do if I were
him. :-)
If I breached a rule of etiquette with this post or with my direct
email, please forgive me, but more importantly, please let me know.
Thanks,
Jeremy
More information about the mythtv-users
mailing list