No subject


Thu Aug 5 16:39:05 UTC 2010


-----
Getting cutlist...
Cutlist: 390-

Running command mythtranscode --mpeg2 -i
"/home/tdec/dvd/work/1/1006_20110122174200.mpg" -o
/home/tdec/dvd/work/1/newfile3.mpg --honorcutlist "390-"
-----


What my patch does to obtain the cutlist is to run:
mythcommflag --very-quiet --getcutlist -f <flename>

In the case of my log file above, the above command returns:
Cutlist: 25516-32183,42788-49003,57567-64225,72729-78491,93313-100579


Then the code in my patch parses that line into something that
mythtranscode can accept:

+        cutlist = string.replace(result,"Cutlist: ", "")
Remove the string "Cutlist: "

+        cutlist = string.replace(cutlist,",", " ")
Replace "," characters with spaces

+        cutlist = string.replace(cutlist,"\n", "")
Remove the trailing newline


Without needing to go through running mytharchive again, you can
probably troubleshoot this just from a terminal.   From your mythtv
recordings directory, run and post the results of:

mythcommflag --very-quiet --getcutlist -f 1006_20110122174200.mpg

mythcommflag --very-quiet --getcutlist -f 1006_20110122174200.mpg | sed
's/Cutlist: //g'

mythcommflag --very-quiet --getcutlist -f 1006_20110122174200.mpg | sed
's/Cutlist: //g' | sed 's/,/ /g'

mythcommflag --very-quiet --getcutlist -f 1006_20110122174200.mpg | sed
's/Cutlist: //g' | sed 's/,/ /g' | sed 's/\n//g'


Those should do the equivalent of what the patched mythburn.py does to
get the cutlist.  If you end up with "390-" then something is wrong with
the string parsing in the patch.   Perhaps a character set thing?   If
the cutlist does correct, then maybe add some debug write() lines in the
mythburn.py to see exactly what it's doing and where it's failing.


-WD




More information about the mythtv-users mailing list