On Sunday 15 December 2002 04.57, Tim Hockin wrote:
> > Conclusion:
> > a. The information is there, but you have to *pull*
> >it from the host. Doesn't seem like you're ever
> >notified about tempo changes or transport events.
> >
> > b. Since you're asking the host, and th
> Conclusion:
> a. The information is there, but you have to *pull*
> it from the host. Doesn't seem like you're ever
> notified about tempo changes or transport events.
>
> b. Since you're asking the host, and there are no
> other arguments, there is no way
On Saturday 14 December 2002 18.55, Steve Harris wrote:
> On Sat, Dec 14, 2002 at 06:04:55 +0100, David Olofson wrote:
> [plugin categorisation]
>
> > > This is a classic example of where external metadata is
> > > noticably superiour.
> >
> > Yeah. Especially since users may not agree with the aut
On Sat, Dec 14, 2002 at 06:04:55 +0100, David Olofson wrote:
[plugin categorisation]
> > This is a classic example of where external metadata is noticably
> > superiour.
>
> Yeah. Especially since users may not agree with the authors' choices,
> or may simply want to have plugins categorized base
On Saturday 14 December 2002 11.19, Steve Harris wrote:
> On Sat, Dec 14, 2002 at 06:48:53 +0100, David Olofson wrote:
> > 4. There is a feature that allows plugins to tell the host
> >which "category" they would fit in. (There is some
> >enumeration for that somewhere.) Might be rather han
On Sat, Dec 14, 2002 at 06:48:53 +0100, David Olofson wrote:
> 4. There is a feature that allows plugins to tell the host
>which "category" they would fit in. (There is some
>enumeration for that somewhere.) Might be rather handy
>when you have a large number of plugins installed...
Th
1. getTimeInfo() does *not* take a time argument of any kind;
only a 32 bit filter, to say which fields you actually need.
That is, you can only get the full info for the start of
the buffer. There is a tempoAt() call, that gives you the
tempo at the specified sample frame in the buffe
