[mythtv-users] Mythtranscode starttime

[Mark]

> -----Original Message-----
> From: mythtv-users [mailto:mythtv-users-bounces at mythtv.org] On Behalf
> Of Michael Wisniewski
> Sent: Saturday, 12 March 2016 6:29 AM
> To: Discussion about MythTV
> Subject: [mythtv-users] Mythtranscode starttime
> 
> Hi!  I'm starting to go crazy over here.  :)  I'm trying to debug a userjob that's a
> shell script to transcode the video using ffmpeg.  Unfortunately, the job is
> failing on mythtranscode.  Looking at the backend logs, I can see it's getting
> executed with:
> 
> Mar 11 13:41:33,snoopy,3,23,mythbackend:, mythbackend[32236]: E
> UserJob_1846 jobqueue.cpp:2444 (DoUserJobThread) JobQueue: User Job
> '/mnt/mythtv/scripts/mythtv-transcode-x264-high.sh
> "/mnt/mythtv/default/1189_20160311193900.mpg" "/mnt/mythtv/default/2
> (WBBMDT) - 20160311133900.mkv" "1189" "20160311133900"' failed.
> 
> 
> When I run mythtranscode by hand with:
> 
> $ mythtranscode --chanid 1189 --starttime 20160311133900 --mpeg2
> 
> 
> It errors out with this:
> 
> 2016-03-11 13:47:12.815803 E  Couldn't find recording for chanid 1189 @ 2016-
> 03-11T13:39:00Z
> 
> 
> However, if I run mythtranscode with the date in a different format like this:
> 
> $ mythtranscode --chanid 1189 --starttime "2016-03-11 19:39:00" --mpeg2
> 
> 
> It works fine.  So unfortunately, the %STARTTIME% in the job is putting the
> date in as just the numbers while mythtranscode likes the date in the full
> format.
> 
> Is there something that I'm doing wrong since it seems to be failing?  Thanks!

I note that in your first command that errors out you use "20160311133900", whereas in the second command that works you use a different starttime number, not just a different format. Ie "2016-03-11 19:39:00" has the hour as 19 whereas the first command has the hour as 13. Depending on which version of MythTV you are using (I don't recall, I apologise if you already said) but older versions took %STARTTIME% as the input whereas later versions take %STARTTIMEUTC% as the input, so might be worth checking that the correct start time is being used. Can be more of an issue if older third party scripts are used on newer installations but my guess is that the issue is the wrong starttime parameter is being used.