Jump to content

Piano Roll: velocity tool doesn't work correctly


splunk

Recommended Posts

I'm having a problem with the velocity tool in the piano roll of LPX. It works fine when I select individual notes, but if I select all of the notes in a region and try to alter the velocities with the velocity tool, I sometimes am unable to get any movement at all or I get very restricted movement. In other words, the upper or lower movement is restricted even though none of the notes have reached maximum or minimum velocity. The velocity slider in the local inspector works fine, but the velocity tool, which is far more convenient, seems to be broken when there's a multiple note selection. Is anyone else seeing this?
Link to comment
Share on other sites

That works, but has the sometimes undesirable side effect of compressing the entire velocity range if I exceed the minimum or maximum velocity of one of the selected notes. It's just strange that I don't get the same results from the velocity tool and the local inspector velocity slider. The velocity tool has a more restricted range and, in worst cases, no range at all.
Link to comment
Share on other sites

If you can't raise the velocity of a group of selected notes it's because one of them is already at the max velocity.

 

There's no way to raise the velocities of all those notes by the same amount other than compressing their velocity-dynamic.

 

The velocity parameter in the Inspector is an offset but even using that you cannot raise the velocity of a note over its max 127 value, so you'd get the same results as if you were to hold Option and raise the velocity in the Piano Roll as Eric suggested.

Link to comment
Share on other sites

Check that all your MIDI notes are on the same channel. In the piano roll controller lane, click the dropdown and select Channel -> Any and you may see some velocity markers appear that weren't there before.

 

It happens to me all the time because my controller transmits on channel 2 but if I mouse in notes they come in on channel one.

Link to comment
Share on other sites

Hmm. I thought I replied to this, but must have messed up somewhere. The short version is that I tried to make a new project to send to you guys so you could see the problem in action and, naturally, everything worked fine. So for now, it appears that the problem I was having was related to that particular project or regions in that project that were misbehaving. Unless I see this again, I'm going to say this was a project related issue and not something that affects LPX in general.

 

Thanks for all the suggestions and especially to cmrick. I've never had that problem before so I didn't look for it. I'll have to go check.

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...