<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000001">
On 11/17/2013 5:29 AM, Paul Harrison wrote:<br>
<blockquote cite="mid:5288A87C.10701@sky.com" type="cite">On
17/11/13 10:17, John Pilkington wrote:
<br>
<blockquote type="cite">
<br>
However, I have a confession to make. My instructions for
patching mythburn.py were incomplete; they didn't follow RW's
patch. Try that.
<br>
<br>
<a class="moz-txt-link-freetext" href="http://code.mythtv.org/trac/ticket/11758#comment:2">http://code.mythtv.org/trac/ticket/11758#comment:2</a>
<br>
<br>
</blockquote>
<br>
I've committed the patch to both master and fixes to make it
easier to test.
<br>
<br>
Please report back if it fixed the problem for you.
<br>
<br>
Thanks,
<br>
<br>
Paul H.
<br>
<br>
</blockquote>
Hi Paul, I'm now running v0.27-93-gb0c1c97. I still get the same
error, mythtranscode cannot find the recording. If I patch the new
mythburn.py with this patch it works fine:<br>
______________________________________________<br>
--- mythburn.py 2013-09-23 18:09:40.000000000 -0500<br>
+++ mythburn.py.zig 2013-09-26 07:50:53.479406824 -0500<br>
@@ -1426,7 +1426,7 @@<br>
data.description = rec.description<br>
data.rating = str(rec.stars)<br>
data.chanid = rec.chanid<br>
- data.starttime = rec.starttime.isoformat()<br>
+ data.starttime = rec.starttime.utcisoformat()<br>
<br>
cutlist = rec.markup.getcutlist()<br>
if len(cutlist):<br>
______________________________________________<br>
I also put in the following patch which writes to the log file, to
see how mythtranscode was being called during a successful run:<br>
***********************************************************************<br>
--- mythburn.py 2013-09-26 08:29:36.864946340 -0500<br>
+++ mythburn.py.logCommand 2013-10-12 09:15:08.081108196 -0500<br>
@@ -1755,6 +1755,9 @@<br>
write("Failed while running mythtranscode to cut
commercials and/or clean up an mpeg2 file.\n"<br>
"Result: %d, Command was %s" % (result, command))<br>
return False;<br>
+ else:<br>
+ write("Successful run of mythtranscode to cut commercials
and/or clean up an mpeg2 file.\n"<br>
+ "Result: %d, Command was %s" % (result, command))<br>
<br>
return True<br>
**********************************************************************<br>
<br>
This is the desired file to be processed:<br>
Processing recording 1:
'/var/lib/mythtv/recordings/1571_20131117160300.mpg'<br>
<br>
This is the mythtranscode command line generated by the current
unpatched mythburn.py which fails:<br>
mythtranscode --mpeg2 --chanid 1571 --starttime
2013-11-17T10:03:00-06:00 --outfile
"/var/lib/mytharchive/temp/work/1/newfile.mpg"<br>
<br>
This is the mythtranscode command line generated after applying the
first patch listed above which then succeeds:<br>
mythtranscode --mpeg2 --chanid 1571 --starttime 2013-11-17T16:03:00
--outfile "/var/lib/mytharchive/temp/work/1/newfile.mpg"<br>
<br>
In the case of failure, mythtranscode does not understand time zone
offsets. After applying the patch, the timezone offset is computed
into the the starttime before it is handed to mythtranscode.<br>
<br>
As an aside, the new mythburn.py (92) is different from the old
mythburn.py (pre 92) but the version number in the mythburn.py file
has stayed the same. So that's a bit confusing.<br>
<br>
Thanks for looking into this,<br>
Ziggy<br>
<br>
<br>
<br>
<br>
<br>
</body>
</html>