First, sorry if I'm missing a preference/option somewhere (wouldn't be the first time..)
Just wondering, to make sure: are MIDI learn parameters in u-he instruments global and persistent on purpose? Testing this on Windows (64bit), both in Live 10 and Reaper, with two instances of a given instrument (trying it out with both the Repros and Zebra).
When ever I assign a parameter via MIDI learn in one instance, the other instance of the same instrument "listens to" the assignment I made and changes accordingly.
So it's not possible, for example, to have two Repro 1 instances running at the same time, make the first one learn something like filter env attack at CC3, and then learn the same parameter on the other instance at CC4, and have each of them respond to different CCs for the same parameter. (So that, if I wanted, I could then have them both MIDI armed at the same time, and simultaneously control that parameter on both instances independently, CC3 on the other and CC4 on the other...)
To recap, when ever you MIDI learn a parameter on either instance, the other instance changes its MIDI mapping as well.
Testing with Zebra, also, and not only do the MIDI mappings transmit on the fly like this, they are also persistent. Meaning that they are still mapped to the same CCs even after closing the DAW, opening a completely different DAW and instantiating Zebra there and loading a random patch.
Apologies if I'm missing a setting which allows MIDI learn assignments to be instance specific.
MIDI learn global and persistent in instruments, not saved with project?
-
- KVRAF
- Topic Starter
- 1950 posts since 17 Jun, 2005
Aagh, replying myself here: it's pretty terrible at the moment, and probably isn't on purpose? Projects do break from this. I just loaded an older project that has CC assignments for specific parameters, and contains expression data recorded in clips using those parameters -- and now that I have used MIDI learn after that (in a completely different project and DAW, even) to assign different parameters, the project doesn't sound at all what it's supposed to sound like, as the CCs control entirely different stuff. By default these should surely save with the project file, stored per instance.
-
- KVRAF
- Topic Starter
- 1950 posts since 17 Jun, 2005
Replying myself another time: I googled the issue and turns out it's by design.
In other words, when using u-he instruments, you need to decide from all the available instrument parameters which ones you want to control via CC, assign those to CCs of your choosing, and if you have CC data recorded into relevant clips in your projects, never change the assignments after that again
I almost always use direct parameter automation on the DAW level, so I was this late in realizing how u-he MIDI learn has worked since... from the start, I suppose
(Still think it's weird not to have an option for assignments per instance, though. Like, use the global ones by default, fine, and I see the point
, but allow flicking a switch and learning unique ones per particular instance, and save those with the project. That would rock.)
In other words, when using u-he instruments, you need to decide from all the available instrument parameters which ones you want to control via CC, assign those to CCs of your choosing, and if you have CC data recorded into relevant clips in your projects, never change the assignments after that again
I almost always use direct parameter automation on the DAW level, so I was this late in realizing how u-he MIDI learn has worked since... from the start, I suppose
(Still think it's weird not to have an option for assignments per instance, though. Like, use the global ones by default, fine, and I see the point
, but allow flicking a switch and learning unique ones per particular instance, and save those with the project. That would rock.)