[mythtv-users] mythtrascode --inversecut

Anthony Giggins seven at seven.dorksville.net
Tue Feb 21 11:53:02 UTC 2017


On 21 February 2017 at 19:40, John Pilkington <J.Pilk at tesco.net> wrote:

> On 20/02/17 23:57, Anthony Giggins wrote:
>
>>
>>
>> On 18 February 2017 at 03:24, John Pilkington <J.Pilk at tesco.net
>> <mailto:J.Pilk at tesco.net>> wrote:
>>
>>     On 17/02/17 16:26, Mike Perkins wrote:
>>
>>         On 17/02/17 12:52, John Pilkington wrote:
>>
>>             On 17/02/17 01:52, Anthony Giggins wrote:
>>
>>                 Is anyone successfully using this option?
>>
>>                 When ever I specify --inversecut the transcode fails
>>
>>                 This Works
>>                 mythtranscode --infile
>>                 /storage2/recordings/4093_20160403201000.mpg
>>                 --mpeg2 --honorcutlist "18778 35040" --outfile
>>                 "/storage2/recordings/test2.mp <http://test2.mp>g"
>>
>>                 This Fails
>>                 mythtranscode --infile
>>                 /storage2/recordings/4093_20160403201000.mpg
>>                 --mpeg2 --inversecut --honorcutlist "18778 35040"
>> --outfile
>>                 "/storage2/recordings/test2.mp <http://test2.mp>g"
>>
>>
>>             It's a long time since I used mythtranscode, and I don't
>>             think I've
>>             ever used it with the cutlist
>>             defined like that on the control line  - but perhaps " 0
>>             18778 35040 "
>>             would do what you want.
>>
>>         I think I would give the two output files different names, too.
>>         I'm not
>>         sure if mythtranscode deletes any existing files before creating
>>         a new
>>         one, but different names will help avoid confusion.
>>
>>
>>     I don't know how the command line is parsed, but it could perhaps be
>>     inverting the cutlist before it has one.   Does '--honorcutlist " mm
>>     nn" --inversecut'...  work?
>>
>>     John P
>>
>>
>> OK I found the Secret Sauce
>> mythtranscode --infile
>> /storage2/recordings/4093_20160403201000.mpg --mpeg2 --honorcutlist
>> "18778-35040" --outfile "/storage2/recordings/test2.mp <http://test2.mp
>> >g"
>>
>> mythtranscode --infile
>> /storage2/recordings/4093_20160403201000.mpg --mpeg2 --honorcutlist
>> "18778-35040" --inversecut --outfile "/storage2/recordings/test3.mp
>> <http://test3.mp>g"
>>
>> looks like it requires the dash between the external cutlist I thought
>> from what I read it needed to be a space.
>>
>> Thanks everyone for the suggestions.
>>
>> Cheers,
>>
>> Anthony
>>
>
> Glad you got it going.  FWIW here's a section of a recent mythDVBcut log
> file.  Looks as if I thought mythutil --setcutlist needed commas too.
>
> chanid 1003   starttime 2017-02-19 20:58:00  recordedid 12844
> Reformatted starttime 20170219205800
> Running: mythutil --getcutlist --chanid 1003 --starttime 20170219205800 -q
> Cutlist: 0-5520,5700-6124,22264-28684,45517-51933,66187-72636,94206-98946
>
> If you want to reset this cutlist, after restoring the .old file
> and resetting the DB with mythcommflag --rebuild, you could try:
>
> mythutil --setcutlist 0-5520,5700-6124,22264-28684,4
> 5517-51933,66187-72636,94206-98946 --chanid  1003 --starttime
> 20170219205800
>
> -but seektables from different tools have differed in the past :-)
>
> Cutframe list from editor:
>   0 5520 5700 6124 22264 28684 45517 51933 66187 72636 94206 98946
>
> Passframe (reversed cutframe) list from editor:
> 5520 5700 6124 22264 28684 45517 51933 66187 72636 94206 98946
>
> Active keyframe passlist via DB.  First is a cut-in:
> 5519 5699 6123 22263 28683 45516 51932 66186 72635 94205
>
> John
>
> Thanks John,

I'll really only be expecting a single cut for this use case but its a good
reference to have if needed again.

Cheers,

Anthony
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mythtv.org/pipermail/mythtv-users/attachments/20170221/1813cb47/attachment-0001.html>


More information about the mythtv-users mailing list