<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000001">
<br>
<div class="moz-cite-prefix">On 9/26/2013 3:44 AM, John Pilkington
wrote:<br>
</div>
<blockquote cite="mid:5243F3EA.3010207@tesco.net" type="cite">On
25/09/13 19:21, Zig wrote:
<br>
<blockquote type="cite">Mytharchive calls mythtranscode (from
mythburn.py) with incorrect
<br>
starttime, resulting in mythtranscode not finding the recording
and
<br>
erroring out.
<br>
<br>
The actual recording start time of this example is 13:36:00
local time,
<br>
Chicago Time Zone (-5 hours from UTC)
<br>
The mythconverge database entry is 18:36:00 (that's the UTC
time)
<br>
<br>
<br>
mythtranscode reports, via mythburn.log"
<br>
******************************************
<br>
*"Couldn't find recording for chanid 1211 @
2013-09-24T13:36:00Z"
<br>
*"Failed while running mythtranscode to cut commercials and/or
clean up
<br>
an mpeg2 file."
<br>
*"Result: 146, Command was mythtranscode --mpeg2 --chanid 1211
<br>
--starttime 2013-09-24T13:36:00-05:00 --outfile
<br>
"/var/lib/mytharchive/temp/work/1/newfile.mpg""
<br>
*"Failed to run mythtranscode to fix any errors"
<br>
******************************************
<br>
If I run mythtranscode from the command line this works:
<br>
mythtranscode --mpeg2 --chanid 1211 --starttime
<br>
2013-09-24T18:36:00-05:00 --outfile
<br>
"/var/lib/mytharchive/temp/work/1/newfile.mpg"
<br>
<br>
and, oddly enough, this command line works too:
<br>
mythtranscode --mpeg2 --chanid 1211 --starttime
2013-09-24T18:36:00
<br>
--outfile "/var/lib/mytharchive/temp/work/1/newfile.mpg
<br>
<br>
So there are two problems.
<br>
1) The -05:00 at the end of --starttime seems to be ignored
<br>
2) The command line that is passed to mythtranscode has the
local
<br>
--starttime in it, not the UTC starttime, which is what is in
the
<br>
database and what mythtranscode seems to like.
<br>
<br>
This worked fine under 0.25, but fails consistently after
upgrading
<br>
0.27. I also tried a clean install of the latest Mythbuntu,
upgraded it
<br>
to 0.27, then installed mytharchive via the Mythbunutu control
center
<br>
and still get the same failure. It is consistent and
repeatable.
<br>
<br>
Mythtv Revision: v.027-9-gb6a6574 branch: fixes/0.27
<br>
Mythbuntu 12.04.3 LTS
<br>
<br>
I have attached the complete mythburn.log
<br>
<br>
Any advice on what I might be doing wrong or a fix would be
appreciated.
<br>
Thanks,
<br>
Ziggy
<br>
<br>
</blockquote>
<br>
There was a flurry of patches to MythArchive before 0.27 release
but it looks as if this one didn't make it. Raymond asked for
test results :-)
<br>
<br>
<a class="moz-txt-link-freetext" href="http://code.mythtv.org/trac/attachment/ticket/11758/mythburn.patch">http://code.mythtv.org/trac/attachment/ticket/11758/mythburn.patch</a>
<br>
<br>
John P
<br>
<br>
</blockquote>
Thanks John, I tried the patch and got the exact same error and
logs as before the patch. After reviewing the patch, it looks like
it might fix the case where projectX is being used but not
mythtranscode. I don't know anything about projectX so I can't
verify that.<br>
<br>
I do not really understand perl very well, but looking at the patch
gave me some ideas, and after hacking around a bit I came up with
this patch (attached) that works in my situation of using
mythtranscode on a TV recording. It only changes one line. It
works when applied after Raymond's patch and it also works (in my
case) when it is the only patch applied to the stock mythburn.py.<br>
<br>
Thanks,<br>
Ziggy<br>
<br>
<br>
<br>
<br>
<br>
<br>
</body>
</html>