[MPlayer-dev-eng] [PATCH] Real Audio/Video support for Mac OS X

[Diego Biurrun]

Donnie Smith writes:
> On Sat, Jun 19, 2004 at 11:07:33 +0200, Diego Biurrun wrote:
> > Yes, we'll put a codecs package up for download.  Could you prepare
> > and upload it to incoming, please?
> MacOSXRealPlayerCodecs.zip e03314e26479068a6e90f3f0bda60ef1, 988 kB.
> Includes what was in my codecs folder, so there might be some
> unnecessary files, but it's pretty small anyhow so to avoid any
> potential cross-reference problems I left it as is. Note that it's an
> Apple-flavoured ZIP-file, which is necessary to include the resource
> forks (it's not too well supported for system <10.3, but at least
> everyone can see what's in the file).

OK

> I haven't included any instructions, but I guess anyone compiling the
> source should be able to figure out that 
> {,~}/Library/Application\ Support might be a suitable place to put
> them. Btw, configure only checks where RealOne installs them (in it's
> own Application bundle), so one would have to specify a custom
> location with --with-reallibdir.

Hmm, dunno how this is handled in OS X, but the codecs should go in
$_libdir/codecs, which usually maps to /usr/local/lib/codecs.

While we are at it: There is a PPC Real codecs package..  Does it work
for you or not?

http://www1.mplayerhq.hu/MPlayer/releases/codecs/

> > > +<command>GetDiskFragment() failed with error -2804: &lt;&lt;Unknown disk fragment&gt;&gt;&lt;&lt;Unknown disk
> > > +fragment&gt;&gt;&lt;pncrt.Shlb&gt;&lt;&gt;</command>
> > 
> > This should also be in <screen> tags and you should insert a linebreak
> > at the point where the original message is wrapped, <screen> does not
> > wrap lines automatically (similar to <pre> in HTML).
> There's no line break (except at the end, of course) in the message
> mplayer spits out, so I removed the one that was there. Is this what
> you mean? (The message after ":" is returned by the system, so it's
> impossible to know for certain what it will be.)

OK, if MPlayer does not output a linebreak after the ":" then you
should preserve this.  I thought maybe it did.  <screen> not inserting
linebreaks on its own sometimes confuses people, that's all.

Diego