[gmpi] Re: Decision Time: 7.1.2

>Is it really weighing down EVERYONE?  Most hosts will just not load a plugin
>that is not Float32.  I don't see that as any weight at all.

what is the point in writing a new API to try to overcome the current
plethora of equivalent-yet-incompatible APIs, only to introduce a new
category of incompatibility. "sorry, that host doesn't support our
plugin's datatype". what is the point? what is the difference for the
user (or the plugin author or the host author) with "that host doesn't
support our plugin API" ?

>So I think we really are agreeing on one fundamental:  Float32 is not the
>only datatype for sample I/O.  Is that correct?  If for no other reason than
>"we agreed to support hand-helds".

if we did in fact agree to support non-IEEE float 32 capable systems,
then i think thats true, yes. but if and only if. the mail archive
should reveal the answer.

>> *** BUT *** not in the same host and not in the same plugin package. 
>
>This is an arbitrary decision.  Allowing a host to support multiple
>datatypes certainly complicates the hosts which choose to do so, I do not
>deny that.  But hosts that choose NOT to support multiple datatypes get no
>added complexity. Plugins do not have any added complexity either way.
>
>So where is the harm in allowing it?

see my first paragraph.

----------------------------------------------------------------------
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: http://www.freelists.org/archives/gmpi
Email gmpi-request@xxxxxxxxxxxxx w/ subject "unsubscribe" to unsubscribe

Other related posts: