u-he

Nig · Post by **Nig** » Wed Apr 04, 2012 7:06 pm

Was just remapping my keyboard with Diva and was looking for a way to Midi Unlearn all but could not seem to find it. Does it exist or is it possible?

Urs · Post by **Urs** » Wed Apr 04, 2012 9:28 pm

Close your host software and delete this file:

com.u-he.Diva.midimap.txt (in Diva.data/Support/ or ~/Library/App..Supp../u-he/)

and soon this file is called

com.u-he.Diva.midiassign.txt

Nig · Post by **Nig** » Thu Apr 05, 2012 9:59 pm

It's that easy

and I see all the other midimap files in there too, good to know. Thank Urs

bmrzycki · Post by **bmrzycki** » Thu Apr 05, 2012 10:37 pm

Nig wrote:It's that easy and I see all the other midimap files in there too, good to know. Thank Urs

Sneaky secret unsupported tip: If you can figure out the name of a parameter (even if it doesn't allow right-click midi learn) it usually can be added to the file for midi learning.

Fun to do things like change the size of each arp mod step with a controller...

Urs · Post by **Urs** » Fri Apr 06, 2012 12:47 pm

bmrzycki wrote:
Nig wrote:It's that easy and I see all the other midimap files in there too, good to know. Thank Urs
Sneaky secret unsupported tip: If you can figure out the name of a parameter (even if it doesn't allow right-click midi learn) it usually can be added to the file for midi learning. Fun to do things like change the size of each arp mod step with a controller...

The update to MIDI Learn we've been working on will let you learn these things from right inside the ui

tectonica · Post by **tectonica** » Fri Apr 06, 2012 12:56 pm

Urs wrote:
bmrzycki wrote:
Nig wrote:It's that easy and I see all the other midimap files in there too, good to know. Thank Urs
Sneaky secret unsupported tip: If you can figure out the name of a parameter (even if it doesn't allow right-click midi learn) it usually can be added to the file for midi learning. Fun to do things like change the size of each arp mod step with a controller...
The update to MIDI Learn we've been working on will let you learn these things from right inside the ui

Hello Urs,

will you also extend the automation-capabilities in view of these new MIDI-learn-functionality? Will for example also the LFO-, Waveform-panels etc. be selectable by Automap, for example?

Bronto Scorpio · Post by **Bronto Scorpio** » Fri Apr 06, 2012 12:59 pm

Urs wrote:
bmrzycki wrote:
Nig wrote:It's that easy and I see all the other midimap files in there too, good to know. Thank Urs
Sneaky secret unsupported tip: If you can figure out the name of a parameter (even if it doesn't allow right-click midi learn) it usually can be added to the file for midi learning. Fun to do things like change the size of each arp mod step with a controller...
The update to MIDI Learn we've been working on will let you learn these things from right inside the ui

That's cool! Will be fun with my BCR2000

Cheers
Dennis

Urs · Post by **Urs** » Fri Apr 06, 2012 1:24 pm

tectonica wrote:will you also extend the automation-capabilities in view of these new MIDI-learn-functionality? Will for example also the LFO-, Waveform-panels etc. be selectable by Automap, for example?

That's a different story. We have "hidden" a lot of parameters for historical reasons. Now we're in a dilemma: There's no technical need to hide them anymore. But if we make them visible, it'll break a lot of existing project files with automation tracks.

Therefore we need to come up with a new system that adds all of those parameters to the end of the list.

Which we might get into, maybe some time later this year. I hope.

tectonica · Post by **tectonica** » Fri Apr 06, 2012 1:36 pm

Urs wrote:
tectonica wrote:will you also extend the automation-capabilities in view of these new MIDI-learn-functionality? Will for example also the LFO-, Waveform-panels etc. be selectable by Automap, for example?
That's a different story. We have "hidden" a lot of parameters for historical reasons. Now we're in a dilemma: There's no technical need to hide them anymore. But if we make them visible, it'll break a lot of existing project files with automation tracks.

Therefore we need to come up with a new system that adds all of those parameters to the end of the list.

Which we might get into, maybe some time later this year. I hope.

Thank you, for the info, Urs!

So now I get a slight understanding on the possible problems. I hope you manage to handle it, I really love Zebra and would really like to have more hardware-controlling-capabilities for it! In each case I wish you all the best, for making a big approach on this.

Besides this, I also have the problem, that Presonus Studio One doesn't allow me to address any of the LFO-parameters via the conventional Midi-learn-funcitonality... the internal control-link only allows me to control automatable parameters. And obviously Presonus doesn't allow ordinary Midi-learn-functionality besides the control-link.
So at the moment I have to spin certain knobs with the mouse only, what it makes a bit confusing, when I also use a hardware Midi-controller-device.

u-he

KVR Audio

Midi Unlearn All?