Midi learn lost

Hello,
The 3.6 update says "MIDI Learn mappings are no longer lost when loading a drum kit onto an existing drum track.". But that's not happening for me. When i load a different kit i do have the cc previously added but i loose the target, which is then useless since i have to start again. Anyone knows something about this?
Thanks

Cocody wrote:Hello,
The 3.6 update says "MIDI Learn mappings are no longer lost when loading a drum kit onto an existing drum track.". But that's not happening for me. When i load a different kit i do have the cc previously added but i loose the target, which is then useless since i have to start again. Anyone knows something about this?
Thanks

When you upgraded to 3.7 did you do a Preference reset?

Nope, I don't think. Don't remember. Is it asked when doing the update? Or can be done elsewhere?

Cocody wrote:Nope, I don't think. Don't remember. Is it asked when doing the update? Or can be done elsewhere?

It's recommend it after every time you change OS. It fixes many little bugs. You can do it anytime you want. It's in the Preference section somewhere, you may have to press & hold the Shift button. Check the manual for more details. You may want to take note/pics of the settings cause they go back to factory settings.

If it's still acting up send a bug report to Akai:
https://support.akaipro.com/en/support/ ... al_support

Ok. Thank you.

I haven't used midi learns with drum tracks, but I have a template with about 200 midi learns assigned to 6 plug in synths. If I accidently change the synth on a track to a different synth instead of patch, when I put that synth back, All the assignments (typically about 30) are disconnected. And because the midi learn list order is screwed up in 3 onwards, I'm better off just reloading than re-assigning.

The midi learns are so fragile, and without another way to manage them, such as loading in a text file, you really have to tip toe around them. I think they need re-thinking a bit.

Neodymium wrote:I haven't used midi learns with drum tracks, but I have a template with about 200 midi learns assigned to 6 plug in synths. If I accidently change the synth on a track to a different synth instead of patch, when I put that synth back, All the assignments (typically about 30) are disconnected. And because the midi learn list order is screwed up in 3 onwards, I'm better off just reloading than re-assigning.

The midi learns are so fragile, and without another way to manage them, such as loading in a text file, you really have to tip toe around them. I think they need re-thinking a bit.

Akai, Please listen to this message! This something not too many people talk about. This whole need some major level TLC. I wish we could move assigned parameters around in that display list.

It would also be nice to share midi learn lists. My 96 assignments over 3 banks could be really useful for other OPX4 users that have a Launch control style controller. But they need to be editable. If I wanted to have 2 OPX4 in the same session, I have to assign all of them all over again. Instead of edit a file to change the midi channel and load a second set.

Neodymium wrote:It would also be nice to share midi learn lists. My 96 assignments over 3 banks could be really useful for other OPX4 users that have a Launch control style controller. But they need to be editable. If I wanted to have 2 OPX4 in the same session, I have to assign all of them all over again. Instead of edit a file to change the midi channel and load a second set.

We may have to start list for the MIDI/Macro issues.

My track 1 macro setting is always messed up when I load it.

I'm lucky, because two of my q-link encoders need replacing, I don't invest anytime into macros

I haven't used any version 3 OS, but on v2 any midi mapping data was always saved in a project file, for me at least - not sure if that's changed now though..?

Neodymium wrote:It would also be nice to share midi learn lists. My 96 assignments over 3 banks could be really useful for other OPX4 users that have a Launch control style controller. But they need to be editable. If I wanted to have 2 OPX4 in the same session, I have to assign all of them all over again. Instead of edit
file to change the midi channel and load a second set.

Did a feature request about that, export and import of midi mappings. And that mapping should ne stored in a track, not in a project.

Because there are midi learns that are not track specific such as main and submix, the file is project based.