[mythtv-users] Share your transcode settings!

[Paul Gardiner]

On 11/01/2012 16:47, Tim Draper wrote:
> On 11 January 2012 16:26, Josh Rosenberg<mythtv at desh.info>  wrote:
>> All,
>>
>> I'm still struggling a lot with setting up transcoding.  But rather
>> than ask for specific help, I'm going to try a different approach.
>>
>> Those of you who do any sort of lossy or format-converting transcoding
>> beyond just stripping commercials, share how you do it!  Built-in
>> transcoding, a user job, or what?  If you use a script someone posted
>> online, have you modified it?  If you use a standard utility like
>> ffmpeg, or a script with multiple modes, what options do you call it
>> with?  Also, how long does the conversion take and how well does it
>> work for you (that is, how much space does it save and how is the
>> quality impacted)?
>>
>> Bonus points for explaining why you chose what you chose, or what
>> alternatives you've discarded along the way.
>>
>> Google searching for transcode help seems to mostly reveal people who
>> are struggling, and I'd like to hear some examples from people who are
>> succeeding!  Regardless of whether your use case exactly matches mine
>> or not.
>>
>> Thanks!
>>
> i too am having issues with this.
> i've found handbrake CLI and an mencode h.264 scripts - neither work.
> mencode did work, now it seems broken and myth will error.
> the handbrake task doesnt even start, as it just gets stuck in the list
> _______________________________________________
> mythtv-users mailing list
> mythtv-users at mythtv.org
> http://www.mythtv.org/mailman/listinfo/mythtv-users

I really like the results obtained by running mythtranscode, used in
fifodir mode into ffmpeg. You still get to cut adverts out, plus
you get full control of recompression. You can maintain interlace, or
deinterlace and double the frame rate. My script is linked to from
the mythtranscode wiki page: http://www.mythtv.org/wiki/Mythtranscode.
May not do exactly what you want, but should be easy to alter.

If you want to use the --passthrough option, then you need to be
on master or JYA backports.

There's also, an option --cleancut I use here, but not in the publicised
script. That avoids certain problems with cut points, but you need
to be using JYA backports from my git fork for that to work.

Cheers,
	Paul.