On 1/22/07, Stefano D'Angelo <zanga.mail@email-addr-hidden> wrote:
> What I'd like to work on is a sound processing architecture (LADSPA,
> VST, DSSI, etc.) wrapper, which hides the details of a particular
> implementation to audio program developers.
All this architectures have different APIs.
Will your one have an fat API (union of all APIs it hides) or a thin
API (intersection).
What will you do if APIs you wrap are doing the same things very different ways?
You say that if will be possible to compare standards or create a new ones.
If your API wraps them all, then it should automatically be best one.
So, why bother creating new API's if your proposal is in fact that new
API, which is better than any other.
And if it is not better, you can't use more advanced API through your wrapper.
Just some thoughts.
Regards,
Dmitry.
Received on Tue Jan 23 00:15:02 2007
This archive was generated by hypermail 2.1.8 : Tue Jan 23 2007 - 00:15:02 EET