[mythtv-users] mythvidexport problems

[Raymond Wagner]

On 4/5/2012 12:50, Tapani Tarvainen wrote:
> On Mar 27 21:39, Michael T. Dean (mtdean at thirdcontact.com) wrote:
>
>> there's little reason with current MythTV not to
>> put recordings (TV and/or movies) into Video Library.
> * It apparently cannot handle recordings with non-ASCII
>    characters in their title at all ("ERROR: ascii").
>    Being in Finland, that's like half of all my recordings.

Python 2.x and Unicode have a long running animosity towards each 
other.  Ascii is handled independently from unicode and other encoded 
text, however there are tons of methods that require ascii strings and 
cannot operate using non-ascii text.  My use of Unicode tends to be 
limited to the occasional stylized character in a name, so I tend to 
make changes that silently break Unicode operation and never notice.

> * Commercial detection data is lost (despite --skiplist option) -
>    everything becomes "Not flagged" (and there seems to be no
>    way of detecting commercials in Video Library).

The script merely passes the data into the bindings.  Chances are the 
bindings are storing those values against the wrong `filename` in the 
database.

> * Screenshot is lost in the process, which makes browsing
>    less convenient.

Assuming the metadata lookup is performed properly, it is supposed to 
pull a new screenshot, as well as other artwork, from the matching entry 
on TheTVDB.com.  The fallthrough behavior for when this data is not 
available needs to be improved.

> * It is cumbersome to use: You have to start the job,
>    wait for it to complete, check the recording is OK
>    in the Video library, then delete it from recordings.
>    (Presumably this could be automated, IF it were
>    reliable enough.)

This version adds three options, --delete, --safe, and --really-safe.  
--safe checks the destination filesize against the source to make sure 
some data wasn't lost somewhere in the transfer, and causes the user job 
to fail if they don't match. --really-safe performs an SHA1 hash of both 
source and destination instead.  --delete will delete the source file, 
enforcing the use of --safe if neither are manually defined on the 
command line.  I've not yet pushed it to the wiki as it uses methods in 
the bindings only available in 0.25.

https://github.com/wagnerrp/mythtv-scripts/blob/master/python/mythvidexport.py