Subject: RE: [linux-audio-dev] LADSPA Plugin Uniqueness
From: Richard W.E. Furse (richard_AT_muse.demon.co.uk)
Date: Wed Mar 22 2000 - 20:15:31 EET
The problem with this is that different developers will need different
numbers of plugins - most will probably want about 5, a few (e.g. big
system developers) might need hundreds. These requirements pack far better
into 24bits if we don't break the bits up into a 'developer' and 'plugin'
part.
And to answer your other email, I agree - I was planning that IDs 1-1000
would not be allocated so there was a range for people to 'play around'
with, particularly for development. Claims for 1001+ are welcome now - I
don't think it would be fair for me to take them...
I know this isn't as nice as could be, but it's simple and compatible with
everything. These can be mapped into a 64bit scheme (perhaps in MuCoS?) by
reserving a single developer ID.
-- Richard
-----Original Message-----
From: David Olofson [SMTP:david_AT_gardena.net]
Sent: Wednesday, March 22, 2000 12:42 AM
To: linux-audio-dev_AT_ginette.musique.umontreal.ca
Subject: RE: [linux-audio-dev] LADSPA Plugin Uniqueness
On Mon, 20 Mar 2000, Richard W.E. Furse wrote:
> I'd prefer for us to play by ear. If 24bits really proves to be too
little
> then MN (and I'm sure other hosts) could introduce different encoding
> schemes and we could increase the range. (Perhaps we'll have 64bit+ home
> computers by then anyway.) If every developer uses 1000 plugin IDs this
> gives us capacity for 16777 developers. Personally I think these are
> practical limits that can be policed at least initially by manual
> distribution of IDs.
How about fitting that range into the low bits of the two 32 bit
words (developer and plugin ID), and keep the other bits all zero
for now?
That way, we get away with IDs that can easily be cut down to smaller
word sizes, but there's still no need to change the API if/when
bigger IDs are needed - native hosts, and hosts that use the full 64
bits get away with no changes whatsoever, and old plugins will still
work without any special treatment.
Obviously, the developer IDs have to be managed carefully as long as
the ID size restriction is an official part of the API. Any guesses
for how long this restriction will make sense?
//David
.- M u C o S --------------------------------. .- David Olofson ------.
| A Free/Open Multimedia | | Audio Hacker |
| Plugin and Integration Standard | | Linux Advocate |
`------------> http://www.linuxdj.com/mucos -' | Open Source Advocate |
.- A u d i a l i t y ------------------------. | Singer |
| Rock Solid Low Latency Signal Processing | | Songwriter |
`---> http://www.angelfire.com/or/audiality -' `-> david_AT_linuxdj.com -'
This archive was generated by hypermail 2b28 : Wed Mar 22 2000 - 19:10:43 EET