[gmpi] Re: Req 76,78
- From: "Angus F. Hewlett" <angus@xxxxxxxxxxxxx>
- To: gmpi@xxxxxxxxxxxxx
- Date: Tue, 08 Feb 2005 11:32:16 +0000
Didier Dambrin wrote:
But what for audio? Plugins (effects or generators) that can show &
play waveforms are not that rare.
As a percentage, they're still pretty small..
The GUI would need the waveform data to display it, and the process to
play it. Both can't share the same data, unless it's in an ugly
memory-mapped file. Will you be passing huge amounts of audio data
through the host?
No... just pass the pixels you need. Could do it with very little data -
less than 1KB for a typical waveform display.
IMHO, if we're going to expose all parameters to the host, might as
well try and push most developers in to using markup for the UI
rather than writing it in C(++). However, it's an open question as to
whether to make this an API thing (i.e. plug-ins expose their GUI in
the form of markup; we provide a rendering library for host
developers to use) or an SDK thing (plug-ins expose their GUI via a
C(++) interface, but we provide a library which plug-in developers
can include allowing them to write the GUI in markup, but for it to
be exposed to the host as C(++)).
what's 'markup'?
A markup language is, to put it loosely, something like XML or HTML,
text-based and parsed at runtime.
Best regards,
Angus.
--
=========================================================
Angus F. Hewlett, Managing Director (CEO)
FXpansion Audio UK Ltd - http://www.fxpansion.com
Registered in the UK - #4455834 - VAT: GB 798 7782 33
=========================================================
----------------------------------------------------------------------
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
Other related posts:
- » [gmpi] Req 76,78
- » [gmpi] Re: Req 76,78
- » [gmpi] Re: Req 76,78
- » [gmpi] Re: Req 76,78
- » [gmpi] Re: Req 76,78
- » [gmpi] Re: Req 76,78
- » [gmpi] Re: Req 76,78
- » [gmpi] Re: Req 76,78
- » [gmpi] Re: Req 76,78
- » [gmpi] Re: Req 76,78
- » [gmpi] Re: Req 76,78
- » [gmpi] Re: Req 76,78
- » [gmpi] Re: Req 76,78
- » [gmpi] Re: Req 76,78
- » [gmpi] Re: Req 76,78
- » [gmpi] Re: Req 76,78
- » [gmpi] Re: Req 76,78
- » [gmpi] Re: Req 76,78
- » [gmpi] Re: Req 76,78
- » [gmpi] Re: Req 76,78
- » [gmpi] Re: Req 76,78
- » [gmpi] Re: Req 76,78
- » [gmpi] Re: Req 76,78
- » [gmpi] Re: Req 76,78
- » [gmpi] Re: Req 76,78
- » [gmpi] Re: Req 76,78
- » [gmpi] Re: Req 76,78
- » [gmpi] Re: Req 76,78
- » [gmpi] Re: Req 76,78
- » [gmpi] Re: Req 76,78
- » [gmpi] Re: Req 76,78
- » [gmpi] Re: Req 76,78
- » [gmpi] Re: Req 76,78
- » [gmpi] Re: Req 76,78
- » [gmpi] Re: Req 76,78
- » [gmpi] Re: Req 76,78
- » [gmpi] Re: Req 76,78
- » [gmpi] Re: Req 76,78
- » [gmpi] Re: Req 76,78
- » [gmpi] Re: Req 76,78