Auto note map?

Official support for: mutools.com
Post Reply New Topic
RELATED
PRODUCTS

Post

It seems that each new clip has a unique personality regarding its note mapping.
Eg. I create a clip, map a note to play. The clip triggers. I then drag a new midi file over that clip. The clip no long triggers. (The auto created name 'Sequence (1)' changes to 'Sequence (2)' when new content is dragged into that clip)
That leaves no real path to having note mapping pre-configured and then dragging new clips in or creating new ones.

Could we have a preference, or a key modifier, that allows a clip just to have its contents changed rather than create a new clip. Or that its note mapping is retaine?
Thanks.

Post

I understand your point and have taken note on the wishlist to have a look at this.
Can't yet estimate when though as i'm currently working on CLAP support.

Post

Hi, new user! Decided to pull the trigger after a few days of demoing the plugin version, and I'm really admiring all of your work, feel like I have barely scratched the surface!

I'm in search of a similar solution/have a similar FR. It would be nice if instead of being linked to the clip itself in the matrix, the MIDI trigger could be linked to the matrix slot permenately, just so things remain somewhat static for particular controller setups and would be easy to fabricate/duplicate. Along those lines, if each slot in the matrix had it's own trigger, it could allow for things like recording to a particular slot on the fly, overdubbing, maybe even undo functionality; essentially each slot in the matrix could be it's own little looper track.

I get there are bigger things than that in the todo list, especially in a one person show, but just wanted to piggy back and add to the wishlist. Thanks for such a great musical tool, looking forward to all the ways it will inspire!

Post

I'll get back on this topic soon later. Will first focus on consolidating and finalizing CLAP plugin support and releasing MuLab 9.2. I've taken note to get back on this topic afterwards.

Post

Thanks so much for taking the time to respond/consider! And I totally agree with those priorities; support of an open standard plugin format is paramount, much more important than refining niche use cases. Appreciate all of your work!

Post Reply

Return to “MuTools”