[mythtv-users] mythtranscode cutlist argument?

[John Pilkington]

On 14/07/10 03:38, jlistspam wrote:
> On 7/9/2010 5:00 PM, Christopher Meredith wrote:
>> According to the help output, mythtranscode can be used with the
>> --infile and --honorcutlist flags and the latter "Optionally takes a
>> cutlist as an argument when used with --infile." Can anyone tell me
>> what format this argument should be? I've tried creating a plaintext
>> file with this:
>>
>> 1836,13700-18207,29554-36778,50077-54307,55801-
>>
>> and passing the text file as an argument, and I've tried passing that
>> whole string as an argument. In both cases, the file is transcoded but
>> no cuts are honored. How should this argument be formatted?
>>
>> Thanks!
>> _______________________________________________
>> mythtv-users mailing list
>> mythtv-users at mythtv.org
>> http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
>>
> I use getcustlist to get the cut list: mythcommflag --getcutlist -f
> /video/2054_20100124170000.mpg
>
> with the output of: Cutlist:
> 0-163,9630-18820,28905-37340,50045-58484,74368-82668
>
> I then pass it to mythtranscode as: --honorcutlist "0-163 9630-18820
> 28905-37340 50045-58484 74368-82668" replacing the commas with spaces.
>
> John
>

Hi: I saw an earlier very similar post from you about this, although 
they don't appear in the same thread in my reader.  I'm not clear why 
you would want to do this if you are getting the cutlist from 
mythcommflag, because mythtranscode --honorcutlist  ought to use the 
internal cutlist as default anyway.  Is it just an example or do you 
actually use it like this?  - and if so, why?  Just curious.

John P