MOTUnation.com

I have a particular patch that I am using which has a wide range of sounds depending on the velocity level. I'm using the Change Velocity MIDI plugin on the channel right now to set everything to 127, but sometimes I want it at a steady 100, or a steady 60. Just got me wonder if there is a way to assign one of my keyboard controllers to control the constant velocity of this instrument? Would be great if I could assign a fader to the "Set all velo to" field in the plugin window. This might really be a Kontakt question.... but I would rather do it in DP so that I can use it in other places also.

Any ideas out there?

thanks!

Couldn't that be achieved from your controller? If it's programmable, I'd get into the manual on it because I know even my POS USB KB has all kinds of filtering tools that you can assign to knobs and such but I don't use it... I just go into the data and highlight it and change the velocity levels while looping and listen, but today, most controllers can do this by themselves.

I looked through the manual several times (I have a CME 88), but didn't see anything except how to change the velocity curve. All of the MIDI controllers need to be assigned a CC#, and velocity doesn't use a MIDI CC message.

I remember reading years back of how Stewart Copeland would use the pressure pad on a LinnDrum or Akai MPC (can't recall which) to alter velocity in a stream of pre-programmed hit hat-triggering MIDI notes. It sounded like a cool way to bring some real expression into the often challenging job of programming great-feeling hit hat parts. I never figured out how to implement the CC to velocity translation... could it be done in Custom Consoles?

What say you Shooshie?

The custom console is a good idea. I've never actually used one for anything, but I gave it a shot. I have a console set up with my keyboard as the source, and my target being the MIDI track I want to control the velocity of. The console is receiving Mod Wheel, and sending Velocities as a Slider, Value Box. This is almost what I need. It displays the velocity value in the box as I move my mod wheel, but it also shows what ever actual velocity I am playing on the keyboard. If I move the mod wheel, it overides the track velocity, but just for a moment, and then the keyboard velocity takes over again............... very close.

thanks for the help with this!

Some thoughts…
You could also use the 'Change Velocity' function …
e.g. , highlight what you want changed in the T.O. window , memorize the key command to call it up
and punch in the values that you want - done !

Additionally , if you purchased 'Quickeys' , you could setup a macro to change all velocities
to 100 or 60 or whatever and put it all under 1 key. …Highlight > QK key > done

HTH - Schweats

Tripi wrote:The custom console is a good idea. I've never actually used one for anything, but I gave it a shot. I have a console set up with my keyboard as the source, and my target being the MIDI track I want to control the velocity of. The console is receiving Mod Wheel, and sending Velocities as a Slider, Value Box. This is almost what I need. It displays the velocity value in the box as I move my mod wheel, but it also shows what ever actual velocity I am playing on the keyboard. If I move the mod wheel, it overides the track velocity, but just for a moment, and then the keyboard velocity takes over again............... very close.

thanks for the help with this!

Sure, but is it useable? I'd like to give it a whirl sometime, maybe using my Motif's touch strip, or keyboard aftertouch.

I have in the past been able to do this very thing with Custom Consoles. It was not easy, and I cannot begin to remember why. But I did it.

Shooshie

Schweats wrote:Some thoughts…
You could also use the 'Change Velocity' function …
e.g. , highlight what you want changed in the T.O. window , memorize the key command to call it up
and punch in the values that you want - done !

Additionally , if you purchased 'Quickeys' , you could setup a macro to change all velocities
to 100 or 60 or whatever and put it all under 1 key. …Highlight > QK key > done

HTH - Schweats

I actually have a quickeys macro that brings up the change velocity command and enters 80 in it. But this is more for MIDI editing. What I'm looking for now is more of a perfomance thing, so I need to have a way to alter the velocity of what I am playing.... not what I've already played.

I'm going to keep playing with the custom console I started to make. I think that is the right direction, but I need to find a way to filter out the incoming velocity from my keyboard.

I would appreciate it you would keep us posted on your results, Tripi. Thanks!

For DP to process it in a custom console there would be even more added latency because it has to have the input before it can process an output if this is a real time thing... I'd do it from the source or if your using an actual MIDI cable (not usb) there are boxes out there to do this exact thing and they have dip switches in there to manipulate any type of data in any way. DP is for post production not performance stuff. I don't see how a sequencer could do that... that's not a post process... it's a pre process so to speak otherwise, highlight the data and change velocity.
Something like the old MIDI octopus where you can program each MIDI channel with it's own special settings and save it as a preset and switch between them would be a better solution IMO.
The only other thing I could think of is use MAX/MSP or something like that to use IAC to send it to DP after you do what you want to the MIDI information.

Bidule can do this task.

http://www.plogue.com/?page_id=274

Use "CC to Params" and map the desired controller to both lowest and highest velocity of the "Velocity Scaler"

reedman wrote:Bidule can do this task.

http://www.plogue.com/?page_id=274

Use "CC to Params" and map the desired controller to both lowest and highest velocity of the "Velocity Scaler"

You are so right. My entire template is in bidule, so this would be one solution. Only thing is, I think it would affect all of the instruments loaded in one particular instance of kontakt. Looks like the change velocity plugin in DP is still the best bet or having something inside of DP to do this.

Thanks for all the good advice.

Tripi wrote:

reedman wrote:Bidule can do this task.

http://www.plogue.com/?page_id=274

Use "CC to Params" and map the desired controller to both lowest and highest velocity of the "Velocity Scaler"

You are so right. My entire template is in bidule, so this would be one solution. Only thing is, I think it would affect all of the instruments loaded in one particular instance of kontakt. Looks like the change velocity plugin in DP is still the best bet or having something inside of DP to do this.

Thanks for all the good advice.

You could also load an instance of Bidule as an AU plugin in DP and create the same graph with the velocity mapping and save this as a preset. This would be like a custom MIDI plugin for this purpose and you could leave your rewire template alone.