The picture I uploaded shows what I mean

What does the picture you posted show? Seems like way too many Velocity events for just five notes.

Why is this posted under reface?

Sorry not sure I posted in the correct spot. I can repost if I need to? The picture is notes laid out in 1/128 quantization so there's a lot of them. I do a lot of trap style stuff with very quick snare and high hat rolls that fade in and out and what not, basically that picture is a random layout of notes fading into a higher velocity. However the velocity does not change. It stays at 127 or whatever the default velocity is, even on the notes that are very low. However it seems to do it randomly (which I know isn't the case) on different performances. Typically I have no problems changing note velocity through cubase on instrument voices, but when I try to change the velocity on drum voices (which is 80% of what i need the feature for) It doesn't change at all on any of the drum performances I have created from wav files, and seems hit or miss on the factory drum performances. Not sure why. I've tried to go through and troubleshoot the midi set up but I believe I have it set up properly. Any thoughts?

I don't understand - that screenshot looks like 5 MIDI notes. Which says to me that the items along the bottom do not represent Velocity. 5 Notes would have 5 independent vertical lines, one for each Note. A note-on can have only 1 Velocity value.

Please explain or show a better screenshot.

It wasn't five notes, it was possibly 70 or more notes, it was just an example of the velocity fade in as I typically use it. I've taken a different screenshot to be more clear.

It wasn't five notes, it was possibly 70 or more notes, it was just an example of the velocity fade in as I typically use it. I've taken a different screenshot to be more clear.

It wasn't five

I see four sets of six notes each, is that correct?

I apologize for the multiple messages phone is being weird, yes correct. This is just an example, but basically the velocity should fade into a higher velocity, but although the note parameters on the key editor screen on cubase are set to fade in, there is no change to the sound coming out. However, it only seems to do this with drum voices. If I adjust the velocity on instrument voices I don't seem to have that problem.

I'm sorry, what "Voice" are you talking about? Please be specific. You also mention "default Velocity", in your initial post, which is not a term I'm aware of... what default velocity?

You mention you're using a Montage, what Drum Performance are you triggering? We'll try to duplicate what your seeing, because it doesn't sound right.

I will basically lay out how I have things set up.

Cubase is loaded with 16 MIDI tracks with the channel number set to ANY. At times to create fast rolls containing multiple notes I will set the channel number in Cubase to whatever corresponding Montage track contains the drum performance I am using. For example, track 1 in the Montage contains Metal Bits, so I will set the channel number in Cubase to channel one. This allows me to use the paint tool to draw multiple notes quickly instead of using the keyboard. The velocity issue arises whether the channel is set to ANY or if it is assigned to a specific Montage track.

My Montage 7 is properly set up to transmit MIDI data to be recorded in Cubase

The drum performance I am using is a performance I created with .wav files, loading each .wav file to a key and saving it in the Montage as a library file.

Everything works as it should as far as I can tell, I just don't understand why velocity adjustments performed inside cubase will not function properly when I'm using my created performances. When using instrument performances there doesn't seemean to be a problem

Your answer, again, is a bit cryptic... but if these are YOUR custom waves, did you take the time to make them velocity sensitive.

The problem with a raw .wav is it Audio designed to always playback at a fixed volume. A .wav does not include things like a Note number or a Velocity Sensitivity... these are parameters applied in the synthesizer and are part of what makes a Montage "Waveform" different from a raw .wav.

Confusing is your claim normal sounds Play with velocity, but you failed to mention whether those Normal sounds are Montage sounds. This is the first time you thought to mention it is YOUR OWN data (welll, that's an important clue, no? 🙂

Check the LEVEL/VELOCITY setting for the Key to which you have assigned your custom Wave

Press [EDIT]
Press [PART SELECT x] to select the Part containing the Kit
Touch "Osc/Tune"
In the screen activate the "Keyboard Select" function (green)
Touch the Key on the keyboard to recall the Waveform parameters
Make sure it shows your Waveform name
Touch "Level/Pan"

You want to check that the "LEVEL/VELOCITY" parameter is set to a positive value. +32 for example, would create a linear curve where for each increase in Velocity effort in, there is a unit increase in Level result out.

A Level/Vel = 0 means no change in velocity
+32 = linear response
+63 = means only maximum effort yields results, low velocities are ignored
Negative values reverse the velocity response.

You can also assign a standard drum PART (preset) instead of using your custom/user data to validate (hear) if the problem is with drum PARTs, in general - as you seem to imply, or just something wrong with your custom PART. Seems like a programming error (if dynamics are desired) instead of any general deficiency in drums responding to velocity.

Worked like a charm. Don't know why I didn't think abut the velocity settings when I loaded the wav file in. One quick question, is there a way to apply velocity settings over the entire performance instead of manually doing it for each wav file? Thank you again for the umpteenth time Phil.

No worries! The joke I always make in the Master Classes, there are two categories of musicians, normal and drummers!
Normal program Parts use a Waveform mapped horizontally (and/or vertically) across the keep board, so things like Velocity could be assigned to many at once. There can be eight Elements per AWM2 Part. Each Element references a Waveform.

But then there are those non-normal drums. A Drum program Part uses one Waveform per each Key. So the multiple samples are not horizontal, they are stacked vertically. This completely changes how you deal with them. When you think about it, each Key in a Drum Part is a different instrument. Each has a separate volume, pan position, Tuning, Envelope, each has its own filters, its autonomous - it's a separate instrument on each Key. Each can be routed to its own Audio output. This is why Drums are unique... it's actually 73 Elements. Each mapped a Key C0-C6.