[gmpi] Re: Shared resources
- From: Steve Harris <S.W.Harris@xxxxxxxxxxxxxxx>
- To: gmpi@xxxxxxxxxxxxx
- Date: Sun, 16 Nov 2003 18:23:09 +0000
On Sat, Nov 15, 2003 at 07:00:53 +0100, Marco Ballini wrote:
> One issue I didn't see considered is "SHARED RESOURCES".
> With "resource" I mean: a wave (i.e. a sample), a song (i.e. a
> sequence), a graph (of plugins, for graph plugins), etc...
> With "shared" I mean that a resource may be accesed by more than one
> plugin.
> Specifying a mechanism for shared resources you may allow for example
> two plugins sharing the same waveform or the same envelope. This is
> quite common in trackers.
> This could be done via "static ports" where you specify a pointer (and
> the size) to a buffer of data. Plugin developers may decide not to use
> shared resources, but with shared resources you have an common interface
> for some operation (thus easier to implement in a GUI created by a
> host): load/save a resource means load/save a song for a sequencer,
> load/save a sample for a sampler, etc...
At least on Linux/OSX you can do this with shared memory, which means that
the data will be shared between hosts, bot just between plugins on one
host, and theres a POSIX api, so its portable.
- Steve
----------------------------------------------------------------------
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:
