[gmpi] Re: MIDI: Proposed Reqs (try #2)
- From: Chris Grigg <gmpi-public@xxxxxxxxxxxxxx>
- To: gmpi@xxxxxxxxxxxxx
- Date: Wed, 7 Jul 2004 14:07:44 -0700
Mike B. said:
Chris G. said:
3. Not sure, but it feels like there are some assumptions in there
about what the Actor reports back to the host, i.e. that the host
could somehow extract the map from the Actor... if so, can you
amplify?
The host could, potentially, use the actor as its map. When
it receives MIDI, it translates it to GMPI and sends it to the
actor, which then does the map translation. I like this model better
than publishing a map and then somehow having the plugin notify that
the map is stale. This way, the map always lives inside the plugin.
Sure, the Actor can map a MIDI message to a parameter, but I don't
think that's what the map's for. The map tells the host, for a given
thing in the plug, what MIDI message you send to the plug to target
that thing. So the arrow flows in the opposite direction.
-- Chris G.
----------------------------------------------------------------------
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: MIDI: Proposed Reqs (try #2)
- From: Tim Hockin
- References:
- [gmpi] MIDI: Proposed Reqs (try #2)
- From: Chris Grigg
- [gmpi] Re: MIDI: Proposed Reqs (try #2)
- From: Mike Berry
- [gmpi] Re: MIDI: Proposed Reqs (try #2)
- From: Chris Grigg
- [gmpi] Re: MIDI: Proposed Reqs (try #2)
- From: Mike Berry
Other related posts:
- » [gmpi] MIDI: Proposed Reqs (try #2)
- » [gmpi] Re: MIDI: Proposed Reqs (try #2)
- » [gmpi] Re: MIDI: Proposed Reqs (try #2)
- » [gmpi] Re: MIDI: Proposed Reqs (try #2)
- » [gmpi] Re: MIDI: Proposed Reqs (try #2)
- » [gmpi] Re: MIDI: Proposed Reqs (try #2)
- » [gmpi] Re: MIDI: Proposed Reqs (try #2)
- » [gmpi] Re: MIDI: Proposed Reqs (try #2)
- » [gmpi] Re: MIDI: Proposed Reqs (try #2)
- » [gmpi] Re: MIDI: Proposed Reqs (try #2)
- » [gmpi] Re: MIDI: Proposed Reqs (try #2)
- » [gmpi] Re: MIDI: Proposed Reqs (try #2)
- » [gmpi] Re: MIDI: Proposed Reqs (try #2)
- » [gmpi] Re: MIDI: Proposed Reqs (try #2)
- » [gmpi] Re: MIDI: Proposed Reqs (try #2)
- » [gmpi] Re: MIDI: Proposed Reqs (try #2)
- » [gmpi] Re: MIDI: Proposed Reqs (try #2)
- » [gmpi] Re: MIDI: Proposed Reqs (try #2)
- » [gmpi] Re: MIDI: Proposed Reqs (try #2)
3. Not sure, but it feels like there are some assumptions in there about what the Actor reports back to the host, i.e. that the host could somehow extract the map from the Actor... if so, can you amplify?
The host could, potentially, use the actor as its map. When it receives MIDI, it translates it to GMPI and sends it to the actor, which then does the map translation. I like this model better than publishing a map and then somehow having the plugin notify that the map is stale. This way, the map always lives inside the plugin.
- [gmpi] Re: MIDI: Proposed Reqs (try #2)
- From: Tim Hockin
- [gmpi] MIDI: Proposed Reqs (try #2)
- From: Chris Grigg
- [gmpi] Re: MIDI: Proposed Reqs (try #2)
- From: Mike Berry
- [gmpi] Re: MIDI: Proposed Reqs (try #2)
- From: Chris Grigg
- [gmpi] Re: MIDI: Proposed Reqs (try #2)
- From: Mike Berry