Chris Grigg wrote:
David said:
Steve said: [...]
I think its clear that we need timestamps for note events, but they are a different beast.
Why are note events different? Does that imply that (other) controls are only meant for "slow" operations that aren't as time critical as triggering notes?
I think such assumptions lead to designs that force users to resort to destructive audio editing where automation *should* be able to do the job.
Obviously, there are many cases where it doesn't make sense to implement fully sample accurate controls, accurate ramping and stuff, but that's plugin implementation dependent. It's not something we can decide on here and hardwire into the API.
Seems like for simplicity it would be way better to have a single event timing model, and treat all event types the same way. Since timestamping is clearly needed for at least one of these (notes) then you'd get that for free for all the other event types. I guess the question is whether the group believes that any performance boost from supporting non-timestamped control-setting events would outweigh the burden of supporting two different kinds of event timing models.
and I even wonder what performance boost that might be! In VST the missing timestamps are more of a burden.....
---------------------------------------------------------------------- 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
