Looking for velocity recurver and CC remapper

[atomota]

I'm looking for a VST plugin that can recurve the velocity levels from my keyboard, and/or remap multiple hardware CC controllers to different CCs. I've Googled and checked kvr and www.midiplugins.com and have found some things that will do this, but they seem like major overkill for what I want to do:

nF_MC23 will remap velocity, but it's also got all kinds of virtual sliders that I don't need taking up most of the GUI space. Maybe it will remap CCs and I'm just missing it.

nF_ControlFront will remap 8 CCs and their values very nicely, but it's got a bunch of LFOs I don't need and a munger I don't know how to use, and the GUI is so large it won't all fit on my screen.

Are there any simple and to-the-point effects that will do what I'm looking for?

Thanks.

[robenestobenz]

http://www.devilswhisper.com/ There's veloremap and controller remap plugins on the right hand side.

I'd really recommend getting familiar with the munger plugins, I've found them useful many times after initially being totally baffled.

[Lagrange]

Man i tried those nf-plugs but found you gotta be really carefull of midi feedback whoahoa!!! Plus I did not like the fact that when it said cc it meant everything but that cc... shit like that can really turn a person off they could be a little more self explanitory..

C

[atomota]

http://www.devilswhisper.com/ There's veloremap and controller remap plugins on the right hand side.

Bingo. Drawing the curves freehand on VeloRemap is rather fiddly, but I imagine I can come up with some curves that match my style and keyboard using nF_MC23 and copy them into a VeloRemap .fxp file (the VeloRemap format looks pretty straight forward).

I'd really recommend getting familiar with the munger plugins, I've found them useful many times after initially being totally baffled.

Some day . . .

[robenestobenz]

It's the slew of commas that really threw me off.

Wow, fxp files formats depend on the VST plugin? Makes sense I guess, but I'd never of thought it. Often wondered about this... so they are sometimes quite transparent to edit then?

[atomota]

It's the slew of commas that really threw me off.

Wow, fxp files formats depend on the VST plugin?

After thinking about this, I guess not, they've just got to have a value for each parameter and they seem to have some other stuff like probably the id of the vst they belong to, I have no idea what the rest is, but I don't think I need to know. Someone writing a host would need to know since it's the host that reads and writes the files.

Makes sense I guess, but I'd never of thought it. Often wondered about this... so they are sometimes quite transparent to edit then?

That probably depends on your background. When I look at it I see 128 32-bit floating point numbers at the end of the file which would be the curve values (divided by 127), to me that's transparent enough to script something up that can create a new curve based on breakpoints or whatever. But I work with this kind of stuff for a living.