On 21 Oct 2003, Florin Andrei wrote:

> The problem is, what happens if it's still too big? (larger than the
> space available on the destination DVD)
> Sometimes you need to shrink the m2v part. Is there a way to shrink it
> without actually extracting it?

        No, I do not believe there is a way to do that "in place".

        It did not occur to me that was what you were attempting to do.
        Looking at the examples gave me the idea you were primarily
        interesting in removing the unwanted streams to reduce the size -
        for that 'vstrip' is the perfect tool for the job.

> For the moment, i extract the M2V and the AC3 and, if the M2V is still
> too humongously big, i requantize it with tcrequant (part of the current

        There is at least one other tool that does that - I forget where
        I came across "repackmpeg2".   I'm still not sure how those tools
        work without decoding and recoding the data though.

> >     The use 'vstrip' to remove/retain the desired audio tracks.
> >     http://www.maven.de/

> Cool, added to the bookmarks. Thanks!

        The command syntax is strange.   Here's a good example (from a
        session I had yesterday).   The DVD has 3 audio tracks - LPCM
        (huge at ~1.5Mb/s), 5.1 AC3 (448Kkb/s), and DTS (I forget the
        rate - probably 448K also) as well as a high rate video stream.

        What I wanted was just the video and the AC3 stream.   So after
        getting the concert to a 'stream.dump' using mplayer I ran
        vstrip:

                vstrip stream.dump -!ox.vob 0xe0 0xbd 0x81

        and that left me with a x.vob containing only stream 0xe0 (the
        video) and substream 0x81 (AC3 audio) in a VOB format file. 

        Nice thing about vstrip is that is retains the VOB structure - no
        mplex run necessary.

> Someone suggested (based on the mplex debug messages that i posted) that
> the problem might be that the AC3 stream is shorter than the M2V stream,
> so it erroneously triggers the split somehow.

        I don't think that's the cause.   A shorter audio stream will just
        leave silence - at least that's what happened the last time I used
        the wrong audio file in a mplex run.

> I'm not sure whether that's the explanation or not. I erased the files
> that were causing the issue.

        Next time you run into the problem try using a '%d' in the output
        file name and seeing how much data actually gets written to the
        second file after the split.   

> >     Try the lastest cvs version? ;)
> 
> <sigh> I wish i had time...

        cvs update
        ./autogen.sh
        make

        doesn't take that long ;)

        Cheers,
        Steven Schultz



-------------------------------------------------------
This SF.net email is sponsored by OSDN developer relations
Here's your chance to show off your extensive product knowledge
We want to know what you know. Tell us and you have a chance to win $100
http://www.zoomerang.com/survey.zgi?HRPT1X3RYQNC5V4MLNSV3E54
_______________________________________________
Mjpeg-users mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/mjpeg-users

Reply via email to