[MPlayer-users] shrink a movie

[Rocky Hetherington]

On Sat, 2002-07-27 at 21:24, Moritz Bunkus wrote:

> > The only differences are that in the first clip audio is at 48000Hz with
> > the video stream coming first in the Ogg file, while the second clip is
> > resampled to 44100Hz with the audio stream before the video.
> 
> Interesting bug.

Not so sure it's a bug with ogmmerge.  The files produced appear to be
fine (although i'm no expert), so i'm thinking it might be a problem
with the OGM DS filters.

The errors the files throw up are something to do with Vorbis.dll rather
than an Ogg problem, so i think that the DS filters might be expecting
Vorbis to be in the first stream and it chokes when it isn't.

Or maybe the DS filters just can't deal with 48000Hz Vorbis?

> I've been working a lot on ogmmerge over the last four
> days and am close to release a (nearly completely rewritten) version
> 0.6 which should also fix a lot of bugs.

Look forward to it.  The current version is a damn fine piece of work
though.  The only problem i've experienced is the above one.  Oh and
mplayer sometimes exits or restarts the file if you attempt to seek
forwards a lot.

> I'll let you know explicitely once I release that version so that you
> can check if the new ogmmerge version does also produce files not
> playable under Windows.

If it's the stream order that's the problem then simply changing the
command in the readme to "ogmmerge -o output.ogg audio.ogg video.avi"
will put them in the right order, if it's the 48000Hz audio that's the
problem then resampling will solve it (which is a good idea anyway).

If you want to look at the problem/non-problem files yourself they are
the *.mpeg4.ogg ones at
http://www.hetherington.co.uk/files/experimental  It may be that the
problems were at the users end (although the second file worked for both
of them).
-- 
Rocky Hetherington
Web    | http://www.hetherington.co.uk
News   | news://nntp.hetherington.co.uk
Jabber | jabber.hetherington.co.uk