KVR Audio

Jarlath · Post by **Jarlath** » Wed May 10, 2006 4:51 pm

Hi,
I never liked the way FL Studio handled this for third party plugs - too fiddly!

However I found this brilliant workaround - and yes it works:
http://www.flipside.singingcrane.com/FL ... opic=636.0

x

aMUSEd · Post by **aMUSEd** » Wed May 10, 2006 6:17 pm

Might be useful - if you want to sum it up in a few steps (its a bit on the wordy side at the moment) I could add it to the Wiki - thanks

Jarlath · Post by **Jarlath** » Wed May 10, 2006 9:32 pm

Here's a step-by-step...

1. Open an empty FLStudio project
2. Open an instance of any synth that accepts midi CCs
3. In the wrapper menu go to 'Link all parameters'
4. From the top drop-down box, select the synth parameter corresponding to MIDI cc #0
5. In the dialogue under 'MIDI Controllers', select controller 0, disable Auto detect, and enable omni
6 Click Accept. The controller in the top drop-down box will autincrement to cc #1
7. Repeat steps 5 and 6, selecting controller 1. You need to do this 127 times (once for each cc#). ALWAYS select OMNI! Ok, this seems like a lot of work, but you only need to do it only once, and it's worth it.
8. Once all 127 MIDI CCs have been mapped, save the project as a template. You can now delete the vst synth. Any synth you use subsequently will recognize MIDI learn on vsts that support it.

I've tested this and MIDI learn functionality works flawlessly for Zeta, PentagonI, Rhino2. The only midi-learn enable vst it hasn't worked for is Kubik.

Cheers!

aMUSEd · Post by **aMUSEd** » Wed May 10, 2006 10:08 pm

Thanks - I'll add it if thats OK.

Jarlath · Post by **Jarlath** » Thu May 11, 2006 5:43 am

cool, thanx

aMUSEd · Post by **aMUSEd** » Thu May 11, 2006 11:06 am

Updated - still waiting for Sonar and Cubase SX/Nuendo (or any others - e.g. Samplitude??)

aMUSEd · Post by **aMUSEd** » Fri May 12, 2006 5:31 pm

Any takers?

Ultimate Midi learn "how to" list