[mythtv-users] 0.27.1 stores wrong length in SD mpeg2 recordings

[Stephen Worthington]

On Sun, 22 Jun 2014 02:15:40 +0200, you wrote:

>Hoi Hika,
>
>Sunday, June 22, 2014, 2:03:40 AM, you wrote:
>
>> Hoi Mark,
>
>> Sunday, June 22, 2014, 1:46:51 AM, you wrote:
>
>
>
>>>> On 22 Jun 2014, at 8:21 am, "Hika van den Hoven" <hikavdh at gmail.com> wrote:
>>>> 
>>>> Hoi Mark,
>>>> 
>>>> Sunday, June 22, 2014, 12:15:50 AM, you wrote:
>>>> 
>>>> 
>>>>>> mythcommflag --rebuild -f %FILE% works. I tested a file at the command
>>>>>> line and it now shows the correct duration. It however gave a decoding
>>>>>> error after finnishing: Unknown Error 541478725.
>>>> 
>>>>> I believe the error can be ignored. I always get the same / similar
>>>>> error message after every Mythcommflag run with no issues.
>>>>> _______________________________________________
>>>> 
>>>> Thanks I changed all my rules and templates to exclude transcoding and
>>>> to include the seektable rebuild job.
>>>> I'm now wondering ik commflagging will work correctly, for I have it
>>>> starting directly. Future will tell.
>>>> I'm also thinking of replacing the transcode command with a script
>>>> that first does a seektable rebuild before the transcoding and that
>>>> outputs the errorcode from the transcoding.
>>>> Something like:
>>>> 
>>>> #!/bin/bash
>>>> declare Filename=$1
>>>> if [ "$FileName" == "" ]; then
>>>>   exit 1
>>>> fi
>>>> /usr/bin/mythcommflag --rebuild -f $FileName
>>>> 
>>>> /usr/bin/transcode $FileName
>>>> exit $?
>>>> 
>>>> Do I have to add more? I'm not familiar with what transcode passes on
>>>> to the commandline.
>>>> 
>>>> Tot mails,
>>>>  Hika                            mailto:hikavdh at gmail.com
>>>> 
>>>> "Zonder hoop kun je niet leven
>>>> Zonder leven is er geen hoop
>>>> Het eeuwige dilemma
>>>> Zeker als je hoop moet vernietigen om te kunnen overleven!"
>>>> 
>>>> De lerende Mens
>>>> 
>>>> _______________________________________________
>
>>> I don't use the inbuilt transcode functions, so don't recall off
>>> the top of my head what parameters, if any, they need.
>
>>> But the first thing that occurs to me is that I believe that
>>> rebuilding the seek table will invalidate commflag markers and
>>> cutlist markers, so if you were transcoding to remove commercials
>>> and pre / post padding you may need to rerun your commflag detection
>>> and rebuild your cutlist after rebuilding the seek table and before transcoding.
>
>>> I think the parameters passed to the inbuilt transcode can be seen
>>> from mythtv-setup on one of the screens near where you setup the
>>> user jobs. Under General somewhere I think.
>>> _______________________________________________
>
>> Thanks, it there just says the default 'mythtranscode' but obviously
>> parameters will be added like the filename, but maybe others. So to
>> catch that proper I might have to add a test routine. Unless I know it
>> will only be the filename.
>> Also I'm concerned with syntax. My example uses shell syntax, for it
>> is a shell script. The usercommand Stephen gave uses a slightly
>> different syntax %FILE% in stead of $FILE. Could anybody comment on
>> that. I seem to remember those commands normally are run without
>> shell. therefore the different syntax???
>
>> Tot mails,
>>   Hika                            mailto:hikavdh at gmail.com
>
>Nice by the way, the user job 'Rebuild Seek Table' Also shows on the
>frontend menu. So I can easily run it on a recording at need. I don't
>need to run it on all recordings of the past month.

Yes, the User Jobs are well integrated into MythTV.  They also show up
in the Job Queue on the frontend (Information Centre > System Status >
Job Queue).

The %FILE% syntax is MythTV syntax for parameters it is passing to
external programs.  The $FILE syntax is for parameters inside a Bash
script (nothing to do with MythTV).  There is a list of MythTV
parameters in the User Jobs section of the MythTV documentation:

  http://www.mythtv.org/wiki/MythTV-HOWTO

The parameters that are available to be used depend on the context,
and if you pass one that is not available in the context it was used,
you get no substitution for that parameter.  For example, if you put
%PLAYGROUP% and it was the wrong context, you would get that
%PLAYGROUP% text passed to your external program.  The same syntax is
used for programs you attach to MythTV System Events.

The seek table data is stored in the mythconverg database in the
recordedseek table.  That is the largest table in the database by far
- its size is normally such that the rest of the database together is
well less that one quarter the size of the recordedseek table.  If you
are using commercial flagging, then when you rebuild the seek table,
you will need to do a full run of mythcommflag and have it re-do the
commercial flagging as well as the seek data, rather than run it with
the --rebuild flag.  I do not normally use commercial flagging, so
when I rebuild a seek table, I prefer to use --rebuild so the job
completes quickly.  Re-running the commercial flagging would take
quite a long time.  I have never done it, but I believe re-running
commercial flagging would be done by the same command, but just
leaving out the --rebuild option.

If you get an error at the end of a mythcommflag run (with --rebuild
anyway), you can just ignore it.  The problem happens after all the
valid data has been stored in recordedseek and does not affect
anything.  I do not always get that error, but I have had it fairly
frequently.