[vorbis-dev] Parallelism

[Monty]

Again, majordomo rejects messages with 'which' on a line by itself (it's an 
admin command).

Monty

------- Forwarded Message

From: "Timothy Wayper" <timmy at r3.co.nz>
To: <vorbis-dev at xiph.org>
References: <Pine.GSO.4.21.0008180843130.758-100000 at general2.asu.edu>
Subject: Re: [vorbis-dev] Parallelism
Date: Fri, 18 Aug 2000 13:02:46 -0500
MIME-Version: 1.0
Content-Type: text/plain;
        charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2314.1300
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300

Note: I've since found that David Burnett has already got vorbis supported
under BeOS in the form of a plugin for CL-Amp and a couple of command line
tools. (Thanks David!)

> Are you thinking GUI or command line utility?  In the command line
department,
> oggenc should work, or be very easy to fix.  As for playback, I'm still
trying
> to beat ogg123 into shape.  Next I need to fix byte ordering, but after
that I
> would love to have someone do a BeOS driver for the libao output library
we're
> using.

Ultimately, I would like to see vorbis supported as media add-on under BeOS,
allowing any application to encode and decode vorbis streams as easily WAV's
and MP3's are currently supported :-) (And without the royalties that force
Be to only include MP3 encoding in the Pro version of BeOS.) The user justs
selects Ogg as their output format, the application plugs the appropriate
nodes together, and away we go! I'm sure Be themselves would love this level
of integration.

Having an BeOS driver for libao would certainly be possible, too.

> That brings me to a general question I have about BeOS:  ogg123 and libao
are
> both C.  Can audio output on a BeOS computer be done with C code, or is
C++
> required?  If C++ is required, what are the issues involved in integrating
C
> and C++ code?  (I have no experience in this area.)

The use of C++ is is required to play audio under BeOS (except  for a system
beep function).

Interfacing the code itself should be fairly easy, there's no reason the C++
BeOS code can't have a pure C API. Where there might be complications is in
dealing with the Be application model. POSIX code can be directly compiled
to command-line apps under BeOS, but interfacing to the App server requires
a C++ application object to be created... but anyway, I'm sure us BeOS guys
can sort out these issues.

Cheers,
Tim W.

------- End of Forwarded Message

--- >8 ----
List archives:  http://www.xiph.org/archives/
Ogg project homepage: http://www.xiph.org/ogg/