View Single Post
Old 09-22-2017, 04:42 AM  
mccrabney
Human being with feelings
 
mccrabney's Avatar
 
Join Date: Aug 2015
Location: Buckett, Kentucky
Posts: 1,064
Default

Quote:
Originally Posted by schwa View Post
We can add support for chasing the last automation item when moving the edit cursor, but if there is no automation item at the start of the project, there is no defined parameter value there, so things are non-deterministic again.
edited wording for clarification

chase last point in last AI when moving edit cursor after/in between AIs is good.
chase next point in next AI if there is no automation item before edit cursor is my recommendation for the 2nd issue.

Quote:
Maybe we could always ensure there is a small automation item at timeline position zero? That would address both of these issues.
it would, but surely making a "create AI for last touched param at edit cursor/time selection" action (that obeys TCP vol/pan controls etc unlike MPL's script would result in less mousing to the beginning of the project to ctrl-drag an AI elsewhere in the project.
__________________
we would benefit from the ability to "select most recently recorded midi" ... would reference midi recorded in last rec/overdub cycle. use case: easily selectively quantize most recently recorded notes
mccrabney is offline   Reply With Quote