[mythtv-users] mythexport or nuvexport

[Martin Moores]

On 8 October 2012 17:17, Bill Meek <keemllib at gmail.com> wrote:

> On 10/08/2012 03:31 AM, Paul Gardiner wrote:
>
>> On 07/10/2012 20:15, Martin Moores wrote:
>>
> ...
>
>  So I looked into the possibility that the recording did not exist in the
>>> database.  The filename in /var/lib/mythtv/recordings matches what is
>>> going into the script:
>>>
>>> 1004_20120429205500.mpg
>>>
>>> But in the database, the start time is listed as:
>>>
>>> 2012-04-29 19:55:00
>>>
>>> Which I imagine is due to the UTC time conversion in 0.26 and me being
>>> in the UK, with daylight savings etc
>>>
>> ...
>
>  What happens if you try 20120429195500? What value appears as
>> %STARTTIME% if you run the user job?
>>
> ...
>
> Hi;
>
> Did you upgrade to 0.26 after that program was recorded? You're correct,
> recorded.starttime was one of the columns changed to UTC by the upgrade
> process.
>
> The upgrade did not convert the filenames to UTC, but the filnames of new
> recordings will be in UTC.
>
> Can your script use --infile %FILE% rather than %STARTTIME% (or
> %STARTTIMEUTC%.)
>
> When you look in the database, compare the starttime and basename:
>
>   select title,chanid,starttime,**basename from recorded order by
> starttime;
>
> That is not, in any way, a suggestion to change the database entries!
>
> --
> Bill
>

Thanks both for the replies, been on a course this week, so just looking at
this again now

Bill,

Paul's script does not use "--infile", just chanid and starttime, so can't
try that at the moment

Running the mysql you suggested (thanks for that) shows "starttime" and
"basename" matching since I did the upgrade, but 1 hour off before I did
the upgrade.

The program I was trying to run through the script was recorded before the
upgrade, but running the script as a user job on brand new recordings, I
get the same error and it shows as failed in mythweb.

Looking in the logs:

Oct 11 19:38:12 MYTHTV1 mythlogserver: mythbackend[5274]: I UserJob_1483
jobqueue.cpp:2409 (DoUserJobThread) JobQueue: Started MythTranscode for
Breakfast recorded from channel 1001 at 2012-10-11T04:55:00Z
Oct 11 19:38:12 MYTHTV1 mythlogserver: mythbackend[5274]: E UserJob_1483
jobqueue.cpp:2444 (DoUserJobThread) JobQueue: User Job
'/home/user/mythtranscode.sh --chanid "1001" --starttime "20121011055500"
--title "Breakfast" --subtitle "" --outdir
/media/media/Videos/Other/Transcoded --passthrough' failed.

This shows that myth is looking for a recording starting at 04:55, the
script is looking for 05:55, it actually started at 05:55, but still failed

The filename and basename are both 04:55, which is correct for UTC

Paul,

Manually running with the script "correct" time (04:55) works, on this new
recording anyway.  Running it on the old recording:

Oct 11 19:40:17 MYTHTV1 mythlogserver: mythbackend[5274]: I UserJob_1484
jobqueue.cpp:2409 (DoUserJobThread) JobQueue: Started MythTranscode for
Homeland:"The Vest" recorded from channel 1004 at 2012-04-29T19:55:00Z
Oct 11 19:40:17 MYTHTV1 mythlogserver: mythbackend[5274]: E UserJob_1484
jobqueue.cpp:2444 (DoUserJobThread) JobQueue: User Job
'/home/user/mythtranscode.sh --chanid "1004" --starttime "20120429205500"
--title "Homeland" --subtitle "The Vest" --outdir
/media/media/Videos/Other/Transcoded --passthrough' failed.

Still 1 hour difference between the myth jobqueue line and the script

Recording actually started at 20:55, basename shows 19:55 and filename
shows 20:55

Running the script manually with 19:55 works.

So:

Old recording - basename 04:55 - filename 04:55 - script looks for 05:55
(fail) - manual script run 04:55 (works)
New recording - basename 19:55 - filename 20:55 - script looks for 20:55
(fail - manual script run 19:55 (works)

I am thoroughly confused.  It does seem that if the basename is matched, it
works

Cheers

Martin
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.mythtv.org/pipermail/mythtv-users/attachments/20121011/de39d9db/attachment.html>