[gmpi] Re: Reqs TODO
- From: Paul Davis <paul@xxxxxxxxxxxxxxxxxxxxx>
- To: gmpi@xxxxxxxxxxxxx
- Date: Wed, 26 Nov 2003 09:25:11 -0500
>>>>
>I would like to see GMPI just do one audio sample format, and I would like
>it to be 64-bit float.
><<<
>
>I strongly disagree... sort of.<g>
>
>I would like GMPI to do a single audio sample format, and it should be
>called "sample_t". If we wind up designing the notion of plugin profiles,
>then one profile can have sample_t be float, and another can have it be
>double.
>
>I object to double as the preferred or nominal format because of memory
>bandwidth considerations. Mundane DSP can get pretty expensive when you
>start requiring each audio data buffer to be twice as big as necessary.
>Double is important for internal state of DSP (such as coeffs in a biquad,
>for example), but for connecting objects float seems pretty robust.
i'm with ron on this one. one sample
format. platform-specific. recompile your plugin with a different
platform header (and presumably a suitable compiler) and it runs on a
different platform. might be 64, might be 32. you don't know, and you
probably shouldn't care.
i see 2 issues though:
first, the arrival of the usual marketing BS, whereby host Foo
proclaims across the pages of Mix, EQ, Sound on Sound, EM and others
"now with 64 bit internal audio data path", instantly labelling all 32
bit plugins for that "platform" as "inferior". the host would simply
have used a new platform file ... not good.
secondly, if you're writing DSP code, there's a good chance that the
way you handle a 64 bit unit will differ from the way you handle a 32
bit one. most ANSI C stuff is double-clean, but at the assembly level,
i am not familiar enough to know the impact ...
--p
----------------------------------------------------------------------
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
- Follow-Ups:
- [gmpi] Re: Reqs TODO
- From: Steve Harris
- [gmpi] Re: Reqs TODO
- From: David Olofson
- References:
- [gmpi] Re: Reqs TODO
- From: RonKuper
Other related posts:
- » [gmpi] Reqs TODO
- » [gmpi] Re: Reqs TODO
- » [gmpi] Re: Reqs TODO
- » [gmpi] Re: Reqs TODO
- » [gmpi] Re: Reqs TODO
- » [gmpi] Re: Reqs TODO
- » [gmpi] Re: Reqs TODO
- » [gmpi] Re: Reqs TODO
- » [gmpi] Re: Reqs TODO
- » [gmpi] Re: Reqs TODO
- » [gmpi] Re: Reqs TODO
- » [gmpi] Re: Reqs TODO
- » [gmpi] Re: Reqs TODO
- » [gmpi] Re: Reqs TODO
- » [gmpi] Re: Reqs TODO
- » [gmpi] Re: Reqs TODO
- » [gmpi] Re: Reqs TODO
- » [gmpi] Re: Reqs TODO
- » [gmpi] Re: Reqs TODO
- » [gmpi] Re: Reqs TODO
- » [gmpi] Re: Reqs TODO
- » [gmpi] Re: Reqs TODO
- » [gmpi] Re: Reqs TODO
- » [gmpi] Re: Reqs TODO
- » [gmpi] Re: Reqs TODO
- » [gmpi] Re: Reqs TODO
- » [gmpi] Re: Reqs TODO
- » [gmpi] Re: Reqs TODO
- » [gmpi] Re: Reqs TODO
- » [gmpi] Re: Reqs TODO
- » [gmpi] Re: Reqs TODO
- » [gmpi] Re: Reqs TODO
- » [gmpi] Re: Reqs TODO
- » [gmpi] Re: Reqs TODO
- » [gmpi] Re: Reqs TODO
- » [gmpi] Re: Reqs TODO
- » [gmpi] Re: Reqs TODO
- » [gmpi] Re: Reqs TODO
- » [gmpi] Re: Reqs TODO
- » [gmpi] Re: Reqs TODO
- » [gmpi] Re: Reqs TODO
- » [gmpi] Re: Reqs TODO
- » [gmpi] Re: Reqs TODO
- [gmpi] Re: Reqs TODO
- From: Steve Harris
- [gmpi] Re: Reqs TODO
- From: David Olofson
- [gmpi] Re: Reqs TODO
- From: RonKuper