[gmpi] Re: Topic 6: Time representation
- From: Steve Harris <S.W.Harris@xxxxxxxxxxxxxxx>
- To: gmpi@xxxxxxxxxxxxx
- Date: Sat, 3 May 2003 09:20:38 +0100
On Fri, May 02, 2003 at 11:03:09AM -0700, Chris Grigg wrote:
> > >>>
> >Does this means MUSTIME, tempo, & meter can't be stapled to the
> >timeslice struct, since they come in as a param from some other
> >arbitrary source that the host shouldn't need to peek into?
> ><<<
> >
> >Part of the MUSTIME struct could an ID that indicates the musical timeline
> >context. Then the host could refer to this ID when making conversions.
>
> Well -- just thinking out loud here -- if plug S knows it's slaving
> to MUSTIME master M, then if S had a way to directly call a method of
> plug M, there'd be no need to go through the host. Obviously this
> extends the idea of what a plug-in interface is about.
If thats a requirement it makes it a non-starter IMHO, calling code in
other plugins is just a world of pain.
> I hear ya, but MUSTIME routing may be a sort of foundation architectural
> thing.
It is in modular synths. Tempo control is done by clock signals and some
implicit knowledge about the tempo. Clock signals are fine IMHO, but we
would also want to express the tempo and meter that that clock is for, the
users wont stand for setting the ratio, tempo and meter on every plugin in
2003 ;)
- 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:
