• SONAR
  • Programming Exact Velocities In Step Sequencer?
2014/05/09 13:22:43
aglewis723
Hello,
 
I know by default, if you plug in a step, it uses velocity at 100, and then you can use the draw tool to roughly change it, but I want to plug in an exact value of "64", how can I do this in the step sequencer view?  The draw tool is not accurate enough.
 
Thank You,

Adam
2014/05/09 15:34:00
brundlefly
I find it pretty easy to hit 64 with the mouse, but I just checked the User Guide and Shift+Enter with focus on the step in the notes pane will allow you to enter a numeric value.
2014/05/09 17:10:38
aglewis723
brundlefly
I find it pretty easy to hit 64 with the mouse, but I just checked the User Guide and Shift+Enter with focus on the step in the notes pane will allow you to enter a numeric value.


How exactly does one "hit 64 with the mouse"?   You can click somewhat around 64, but are you at 64?   

Shift+Enter would be very tedious as you have to do it on each step.  I want to default to 64 instead of 100 every time I click on a step.
 
 
2014/05/09 17:16:51
Anderton
aglewis723
 
Shift+Enter would be very tedious as you have to do it on each step.  I want to default to 64 instead of 100 every time I click on a step.



I don't understand the problem. Why isn't "Set Default Velocity for Steps" under the Step Sequencer's Options menu not good enough?
2014/05/09 17:21:16
aglewis723
Anderton
aglewis723
 
Shift+Enter would be very tedious as you have to do it on each step.  I want to default to 64 instead of 100 every time I click on a step.



I don't understand the problem. Why isn't "Set Default Velocity for Steps" under the Step Sequencer's Options menu not good enough?


Ahhh, Anderton, again I run into you.  I know what you like doing, you like to try and troll people for not reading the manual and not searching the forums.   Last time you answered a post of mine in a nasty way, I proved you wrong by actually showing you a screen cap of the 15 minutes worth of internet searching I did before posting.

I did the same here, unfortunately the manual for Sonar is quite big and not the most easy to search and find exactly what one is looking for, hence that is why we turn to the forums, correct?

Technically, EVERYTHING you want to do should be in the manual, but this is a place to help each other out without being talked down to.  You tend always assume one hasn't done their work.  What a terrible approach to life.
 
But thank you for the answer :)
 
-Adam
2014/05/09 17:36:59
Anderton
It wasn't "nasty," I was thrown off by your saying you wanted to "plug in" a value of 64. It seemed to me that implied you wanted to do something AFTER entering velocities, like set all step sequencer velocities after recording to 64 or something (I don't know of any way to do that, by the way, so if that had been your question my response would have been I didn't have an answer).
 
Setting a default doesn't let you "plug in" anything, the step starts with that value automatically. I was also thrown off because you said "I know by default, if you plug in a step, it uses velocity at 100" which didn't make sense to me because I thought that using Options to change the default would have taken care of what you wanted but apparently it didn't or wouldn't have started this thread. So of course I thought you were trying to do something else.
 
I'm not trolling anybody, you had a question. Before I was going to assume the answer was obvious and say "do this," I wanted to make sure I understood what you wanted to do because what you wanted to do wasn't clear. So I asked you to explain why the existing option didn't work. Now I realize you simply didn't know that Option existed.
 
P.S. if I recall correctly, in the previous answer you thought was "nasty" I didn't fully understand what the issue was, which is why I needed the screen cap. As soon as I saw it, then I understood what you were talking about. I try to helpful but if I don't fully grasp what the issue is, the answer will be flawed. This is why I try to make sure things are as clear as possible. This is something I do with everyone, not just you. I don't just assume I'm right and everyone else is wrong, I ask questions to make sure I fully understand what an issue is.
 
2014/05/09 17:45:22
aglewis723
OK then, my apologies.  Your name keeps popping up in my head as someone who keeps telling me to "read the manual" or "do some research first".
 
If I am mistaken, then please forgive me.  I try and help people on here too when I can even if it's something simple, you know, you can't just ask the instruction manual a question.
 
Anyway, my apologies if I had you wrong.
 
Anderton
It wasn't "nasty," I was thrown off by your saying you wanted to "plug in" a value of 64. It seemed to me that implied you wanted to do something AFTER entering velocities, like set all step sequencer velocities after recording to 64 or something (I don't know of any way to do that, by the way, so if that had been your question my response would have been I didn't have an answer).
 
Setting a default doesn't let you "plug in" anything, the step starts with that value automatically. I was also thrown off because you said "I know by default, if you plug in a step, it uses velocity at 100" which didn't make sense to me because I thought that using Options to change the default would have taken care of what you wanted but apparently it didn't or wouldn't have started this thread, so of course I thought you were trying to do something else.
 
I'm not trolling anybody, you had a question. Before I was going to assume the answer was obvious and say "do this," I wanted to make sure I understood what you wanted to do because what you wanted to do wasn't clear. So I asked you to explain why the existing option didn't work. Now I realize you simply didn't know that Option existed.
 
P.S. if I recall correctly, in the previous answer you thought was "nasty" I didn't fully understand what the issue was, which is why I needed the screen cap. As soon as I saw it, then I understood what you were talking about. I try to helpful but if I don't fully grasp what the issue is, the answer will be flawed. This is why I try to make sure things are as clear as possible. This is something I do with everyone, not just you. I don't just assume I'm right and everyone else is wrong, I ask questions to make sure I fully understand what an issue is.
 




2014/05/09 17:53:02
brundlefly
For the record I, too, read "I want to plug in an exact value of "64"" as "I want change the velocity of a step by entering "64" from my keyboard".
 
Dave
2014/05/09 17:58:30
Anderton
No need for an apology, but I don't think I've ever told anyone to "read the manual." If you started reading the manual today, you'd still be reading it after X4 appeared. However, I often reference parts in the manual (if I know what they are) so I don't have to take the time explaining something that already exists.
 
What I HIGHLY recommend is using the search and index function to look up topics. I constantly have situations where I once knew how to do something esoteric but can't quite remember how I did it. Index and Search will take care of me almost all the time, but not always...I'm still not quite sure what the little triangle sandwiched between the MIDI jack and grid in the upper right corner of the PRV does, and there's no tooltip. It may relate to how the pyramids were constructed.
 
The other advice I'd give is that when asking questions, be EXTREMELY specific. It's like the guy who couldn't use the Solo button on a track being processed via sidechain without killing the sidechain effect. That's simply not possible if the send is pre-fader. We went back and forth and back and forth, and finally, he put up a screen capture that indeed exhibited the impossible behavior. I was totally mystified and could not reproduce the issue, nor could anyone else.
 
Finally he added an offhand comment about using a virtual instrument as the sound source...aha! The solo button was cutting off the MIDI track driving the soft synth (which by definition can't be pre-fader), hence no audio to drive the sidechain. Had the virtual instrument aspect been mentioned in the first post, it would have been solved in the second one.
2014/05/09 18:11:52
Anderton
BTW - let me clarify the X4 reference was a figure of speech, not foreshadowing!
12
© 2026 APG vNext Commercial Version 5.1

Use My Existing Forum Account

Use My Social Media Account