It's not clear to me the difference between Event Graph Editor and Automation Sub-Track.
If I'm not missing something, both allow to define variations of MIDI CC, module parameters, aftertouch and pitch bend (only Velocity is different being available in the E.G.E. but not in the A.S.T, a convenient choice by the way since a strong visual correlation with notes is required in this case).
Since the point-based manipulation of A.S.T. panels is more practical and precise, I tend to ignore the E.G.E. except for the velocity view. The drawing mode of E.G.E. is a bit strange instead.
Besides subjective feeling and preferences, is there a special reason for such kind of apparently duplicated feature for same tasks with different interaction and visual modes ?
If not, in the spirit of MuLab simplicity (that I appreciate a lot) it could be maybe possible to rethink the approach with a more unified solution.
Just a comment and suggestion of course.
Duplicated functionality?
-
- KVRist
- 58 posts since 31 Oct, 2006
-
- KVRAF
- 13864 posts since 24 Jun, 2008 from Europe
The Event Graph Editor was first, then came the Automation Tracks. There indeed is an overlap but currently thing is that when you record automation it can only be recorded as events and these can only be edited in the Event Graph Editor. It's on the wishlist to further finetune these things so that automation can directly be recorded as breakpoint envelopes.
-
- KVRist
- Topic Starter
- 58 posts since 31 Oct, 2006
Ok, understood. Looking forward for this future enhancement.mutools wrote:The Event Graph Editor was first, then came the Automation Tracks. There indeed is an overlap but currently thing is that when you record automation it can only be recorded as events and these can only be edited in the Event Graph Editor. It's on the wishlist to further finetune these things so that automation can directly be recorded as breakpoint envelopes.