[mythtv-users] H.264 Encoding - Need for a Command Line Tool for Analyzing Video Sources

[Willy Boyd]

I see... great.  That's close to what I figured and makes perfect
sense.  I just got a new TV, so soon (like when I get a HDhomerun)
I'll be fiddling with this sort of stuff.  ;-)  I'll probably test the
scripts on a few encodes, figure out a good avg bitrate that looks
good to my eyes, then run with it like that, as you suggested.  For me
it will be more about just shrinking the size down from multiple gigs,
not necessarily to an arbitrary limit.

On 11/29/06, Steven Adeff <adeffs.mythtv at gmail.com> wrote:
> On 11/29/06, Willy Boyd <willyboyd at gmail.com> wrote:
> > On 11/28/06, Steven Adeff <adeffs.mythtv at gmail.com> wrote:
> > > On 11/28/06, Joel Turner <jturner421 at aol.com> wrote:
> > > > On Nov 28, 2006, at 3:48 PM, Steven Adeff wrote:
> > > > > check gossamer for the script I posted to convert to "HR.HDTV". It has
> > > > > mplayer commands for getting most of that information. original
> > > > > bitrate can be tricky due to variable bitrate, your best bet for this
> > > > > if you want an average is to take the file size and movie length and
> > > > > do some math. As for progressive/interlaced, this is even trickier,
> > > > > though you can make some assumptions like 1280x720=720p=progressive,
> > > > > 1920x1080=1080i=interlaced, PVR content is interlaced, etc.
> > > >
> > > > Thanks Steve.  This is a great help.  The mencoder manual has a lot
> > > > of good information on how to determine interlaced vs progressive and
> > > > tecline.  I will need to figure out a way to deal with mixed
> > > > material.  A good example is one of the Star Wars movies that were on
> > > > Cinemax recently which switches between 30000/1001 fps NTSC and
> > > > 24000/1001 fps progressive.
> > >
> > > Cinemax is 1080i, so it sounds like a mixed telecine process(their way
> > > of screwing with these filters, and of course it looks bad on the tv
> > > too if taken too far), my scripts 1080i filtering should handle that
> > > decently.
> >
> > Just out of curiousity, why the size limitations in the script?  It
> > looks like the 350MB and 700MB sizes are for half hour and full hour
> > shows, and running it on say a movie or a 61 minute recording isn't
> > supported?  If I wanted to extend that for myself would it just be a
> > matter of adding more time/size rules for longer recordings, or is
> > there some reason I'm overlooking for doing it that way?
>
> It's to match the hr.hdtv "guidelines" setup by "the scene". Which
> base their encodes on being able to burn a "1 hour" show to a CDR.
> I've taken this script and modified it for various other purposes,
> x264, 1080p and 720p xvid, etc. changing those sizes as I felt
> appropriate.
>
> As for odd sized shows, yea, in the basic form they are not supported,
> but again, it wouldn't take much to add more if statements to catch
> for other sizes, or to just create a separate script or option that
> uses a desired average bitrate.
>
> I just didn't feel it deserved much more work than I had already put
> into it, otherwise I would have written it in PERL. Though, if I
> understand correctly, MythArchive is based on ffmpeg, which should
> support all the filters, etc in mplayer, making it the ideal solution
> for doing any of this stuff.
>
> --
> Steve
> Before you ask, read the FAQ!
> http://www.mythtv.org/wiki/index.php/Frequently_Asked_Questions
> then search the Wiki, and this list,
> http://www.gossamer-threads.com/lists/mythtv/
> Mailinglist etiquette -
> http://www.mythtv.org/wiki/index.php/Mailing_List_etiquette
> _______________________________________________
> mythtv-users mailing list
> mythtv-users at mythtv.org
> http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
>