On Fri, 2004-01-02 at 14:28, Steven M. Schultz wrote: > cvs update works wonders ;)
Indeed, if you have the time to manage software in such a manner.
> I put the stuff into MP4 containers with AAC audio and MPEG4 video.
MP4 containers huh? I will have to take a look. Do they overcome 2G
file limitations?
> Not only useable with mplayer but ALSO with Apple's Quicktime player.
> The couple things you'll need are the AAC encoder ("faac" from
> www.audiocoding.com I believe) and 'mp4creator' (a small part of
> the rather large MPEG4IP project).
Thanx!
> No, a set-top box is the DVD player that John Q. Public gets at
> Best Buy or Fry's or whatever. A computer is not considered a STB.
Yeah, but I am not talking about semantics here. Why is a "STB/DVD"
player more suited to MPEG2 than a computer? Or are you just reflecting
the current status in the STB market?
> I thought ffmpeg's mpeg4 encoding was interlaced aware.
I am not sure to tell the truth. My results sure do look interlaced. I
just don't know how well suited to field based encoding mpeg4 is. I had
always understood that mpeg2 was more suited to field based encoding
like television destined material.
> With mpeg4 though you can cut the bitrate down considerably below
> what mpeg2 requires. ~2000 kbits/sec is more than enough for general
> mpeg4 use
I use 2500 kbits/sec on full frame (i.e. no cropping, no
inverse-telecining), and reduce appropriately from there (i.e. 2000
kbits/sec when inverse-telecined).
> and that's a _long_ movie at 2GB
1 full hour is slightly more than 1GB, so anything 2+ hours blows the
2GB limitations.
b.
--
My other computer is your Microsoft Windows server.
Brian J. Murrell
signature.asc
Description: This is a digitally signed message part
