<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000001">
On 11/17/2013 8:57 AM, John Pilkington wrote:<br>
<blockquote cite="mid:5288D96F.7040203@tesco.net" type="cite">On
17/11/13 14:14, Paul Harrison wrote:
<br>
<blockquote type="cite">On 17/11/13 13:47, Zig wrote:
<br>
<blockquote type="cite">
On 11/17/2013 5:29 AM, Paul Harrison wrote:
<br>
<blockquote 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
<br>
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
<br>
to test.
<br>
<br>
Please report back if it fixed the problem for you.
<br>
</blockquote>
I don't understand exactly, the commit system. Is it possible
to
<br>
briefly explain to a novice how to figure out when this commit
will
<br>
show up in my particular distribution?
<br>
I'm currently running v0.27-89-g4ca9300 Branch: fixes/0.27.
I have
<br>
looked at the ticket and see the extremely long commit number
as well
<br>
at the changeset number, but I don't know how to follow those
numbers
<br>
down to what release they first show up in.
<br>
<br>
If this is beyond the scope of explaining to a novice, I
understand.
<br>
Thanks,
<br>
Ziggy
<br>
<br>
</blockquote>
<br>
The easiest way to tell if you have the commit is to look at the
number
<br>
after v0.27 in the version you have it is 89 which means there
have been
<br>
89 commits to the 0.27 branch since it was tagged. The commit
you want
<br>
the number is 92 so when that number is >= 92 in the version
you have
<br>
then you know you have the commit.
<br>
<br>
Paul H.
<br>
</blockquote>
<br>
You can get the version of mythburn.py after this commit here.
Because it's python, provided nothing has changed in its links to
the rest of the system, you should be able to drop it into yours
without waiting for a fresh system build.
<br>
<br>
IIRC you found that you had to apply a different patch, based on
this one, to get your system to create a DVD :-)
<br>
<br>
I got here from the fixes branch, but I see nothing on the page
that confirms that's what it is.
<br>
<br>
<a class="moz-txt-link-freetext" href="https://github.com/MythTV/mythtv/blob/fa94c154c79d0752eb0eb59e579e1985ccf26532/mythplugins/mytharchive/mythburn/scripts/mythburn.py">https://github.com/MythTV/mythtv/blob/fa94c154c79d0752eb0eb59e579e1985ccf26532/mythplugins/mytharchive/mythburn/scripts/mythburn.py</a>
<br>
<br>
John P
<br>
<br>
</blockquote>
Using the mythburn.py you referenced above (with your addition to
output the mythtranscode command line to the log) I still get the
error - see failedlog.txt that is attached.<br>
<br>
If I change line 1429 from:<br>
data.starttime = rec.starttime.isoformat()<br>
to:<br>
data.starttime = rec.starttime.utcisoformat()<br>
then mythtranscode completes - see successlog.txt that is attached.<br>
<br>
On the frontend archive setup screens I have "always use
mythtranscode" checked and "use projectX" unchecked.<br>
Ziggy<br>
<br>
<br>
<br>
<br>
</body>
</html>