On Tue, 26 Oct 2004, Jim Hatfield wrote:

> I've sent this to mjpeg-users and transcode-users, my apologies to
> those who are on both.

        Well, there is, marginally, a mjpegtools connection - looks like
        the mplex command's used after all the transcode processing ;)

> (then using dvdauthor etc etc) but there seems to be a problem which I
> think might be caused by the final mpeg file being over 4 Gb. I fiddle 

        'b' = bits, 'B' = bytes.  4Gb is a 512MB file - not all that big ;)

> with the tcrequant factor to get it a near as possible to 4.5 Gb. 

        If you're using "computer" gigabytes (GB) then the capacity of a DVD
        is 4.38GB.  If you're using "marketing" gigabytes where 1GB is 1000**3
        then a DVD is 4.7GB or 4,700,000,000 bytes.

        Also, there is a small amount of filesystem overhead and any menus
        used take up space as well.

        If you're not generating motion menus, transitions, and the like then
        the overhead of the menus is minimal but  may still need to be 
        taken into account.

> However I have problems playing. I even tried playing the .mpg (using 
> PowerDVD on a Windows box) and it hammered the disk for about 5 mins 
> before play started then the progress bar suggested the movie was only a 
> few minutes long, wierd.

        Don't know about PowerDVD but it could be that it wants the VIDEO_TS
        directory (with the .ifo files, etc) rather than a system stream 
        MPEG-2 file.

        mplex puts in DUMMY/placeholder NAV packets that get computed during
        the authoring process.  It could be that PowerDVD is a bit confused
        by the dummy information.

        Run dvdauthor and get a VIDEO_TS directory and then try playing that -
        perhaps it'll work better than playing the .mpg file.

        Have you tried 'mplayer' on the .mpg file? 

> Do I need to keep the output size below 4Gb, ie is there some 
> architectural issue in the MPEG-PS file format which requires that?

        You need to keep the output size below 4.38GB or 4,700,000,000
        bytes.  I'd consider 4,600,000,000 as a maximum to leave room for
        any menus and filesystem, etc overhead.

        Cheers,
        Steven Schultz



-------------------------------------------------------
This SF.Net email is sponsored by:
Sybase ASE Linux Express Edition - download now for FREE
LinuxWorld Reader's Choice Award Winner for best database on Linux.
http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click
_______________________________________________
Mjpeg-users mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/mjpeg-users

Reply via email to