Within library developers the delays are often consistent. Between them, however, is where it turns into a potential nightmare. When I stuck with one or two library devs, these issues were more manageable. I'll have to refer back to dewdman42's detailed examples above.bayswater wrote: ↑Mon Mar 15, 2021 5:42 pm I'm familiar with the reasons why the attack latency has to be addressed. But is it possible to address it comprehensively in the articulation manager? Do the products on offer now deal with it completely? Don't you still have to adjust the timing of note on for a load of other reasons? Maybe not -- I've been playing around with Spitfire stuff recently, and noticed the attacks are very often just where I want them, even for different articulations.
At the least I see that when you want an attack to occur prior to the Note On event, an articulation manager with a look ahead function is useful.
I do believe it's possible to address all that has been requested comprehensively. Examples of powerful and divergent tools covering many of these requests can be found in existing DAWs already. My own abstract vision (not to sound so grandiose) of such implementation doesn't even have to be an articulation manager, per say, but one sandbox-like tool providing, for example, enough object-oriented logical statements and assignments to build whatever controller/action your heart desires. Like the concept of modular synths, but instead of processing and routing sounds, it's directing the DAW's flow of data.
Admittedly my bias in this is that I would like a cuddly GUI solution and not have to learn (or hack through) JavaScript.
