Paul Davis wrote:
c) 1-or-more named bundles of streams with defined, enumerated formats. The format defines (either as flags, multiple fields, whatever) the data type (int, float, double...), the number of channels (1, 2, 6..), the encoding (mono, stereo, 5.1...), and the storage (normal, interleaved...). Each port of a plugin needs to list, in order of preference (or somehow wieghted), the formats it can handle.
you know, this is heading toward the exact same conceptual
disagreement that we've had between ALSA and JACK. ALSA represents
every possible audio hardware format you can come up, and a few more
to just to be sure. JACK by contrast enforces mono, normalized
32 bit floating point.
which one do you think most people like working with? which one has the least scope for obscure format handling bugs?
(sorry to repeat myself for long-time LAD readers) i think we should
be learning the lessons that SGI learnt from their video APIs. come up
with a simple API that handles 90% of what people want to do, which is
normally very straightforward. then figure out clever ways to support
the remaining 10% without destroying the simplicity of the basic API. SGI did the almost-opposite: come up with a simple API then keep
extending and extending it until it supported everything. it ended
being almost unusable without spending months studying the API.
--p
-- Mike Berry Adobe Systems
---------------------------------------------------------------------- Generalized Music Plugin Interface (GMPI) public discussion list Participation in this list is contingent upon your abiding by the following rules: Please stay on topic. You are responsible for your own words. Please respect your fellow subscribers. Please do not redistribute anyone else's words without their permission.
Archive: //www.freelists.org/archives/gmpi Email gmpi-request@xxxxxxxxxxxxx w/ subject "unsubscribe" to unsubscribe
