holy cow!   I'm going to check out this CAL script right now and save it for future use!  I need to learn more CAL scripting!!!
 
 
THANK YOU SCOOK!!!!!  I will update this thread soon!!!

SCOOK!  You are my hero!  Thanks for passing the knowledge along.  I think i gotta get into CAL scripting!  This will come in handy, and I can tell how to edit it for different tasks.
 
You are the man!

Thank you again!!
 

aglewis723
Hello, I DO have a keyboard controller, I played all this stuff by hand.   Just this is a very sensitive patch and the velocities need to be perfect.   It's impossible to play the same velocities over and over.  

 
Is it that the patch has jarring layer changes or too few layers? I try to stay away from synths/patches that do that because it can be difficult to avoid getting unintended timbre changes when velocities are very consistent but are falling randomly on either side of a layer switch by a few values.
 
If a synth has even and predictable response to velocity I find that it isn't usually that critical to have such consistent velocities so long as the dynamic relationship between sequential notes is roughly consistent. Sometime it's enough just to change the range of velocities which can also be done with Find/Replace or the Event Inspector or even just with the Vel+ control, depending on the situation.
 
Anyway, just sharing some thoughts. Only you can know exactly what the part needs.
 
 

You are welcome. There are quite a few cal scripts included with SONAR. Some are well commented. There is a chm of the CAL reference included in CALeditor Keep in mind this stuff is pretty old.

Sonar has a procedure to apply "groove quantize" to existing material. For quantizing, a groove consists of a sequence with notes at specific grid offset times, velocities, and durations. I have not examined precise results myself, but I wonder if you could use your precisely adjusted notes to apply groove quantize to the rest of your notes using a 100% strength to the velocity component (in the groove quantize dialog). If that idea sounds groovy to you, the manual tells how to use the Process > Groove Quantize command. You might have to do a little wading through the manual because groove quantize is heavily documented for use on audio, whereas you just want to apply it to your midi track.

bvideo
I have not examined precise results myself, but I wonder if you could use your precisely adjusted notes to apply groove quantize to the rest of your notes using a 100% strength to the velocity component (in the groove quantize dialog).

Ah, good one, Bill. I forgot that Groove "Quantize" had a velocity parameter.

Aren't quantize functions basically easy access calscripts? I have yet to really dig into all that stuff because up until this point it has been more effort to learn than it's worth for my purposes but it's certainly on the agenda... probably soon.

mettelus
Is the pattern consistent enough that you can use the PRV, and simply copy/paste? Then lasso and drag the notes up/down for the chord changes?
 
Charlie Roy has a nice PRV video for drums that shows what I mean..
http://www.youtube.com/watch?v=ruAnAPR6-hQ

hey thank you very much man :-)
 
@aglewis723, I use the "last touched feature myself.
if you watch that whole vid youll see what im talking about.
it beats switching back and forth trying to find velocity's perfectly.
it also adds flavor to fool the ear in to believing its more human.

I would think quantize functions are compiled code as opposed to scripts. CAL can be very handy but I worry about the long-term viability as it has not been formally supported for a long time and no effort is being made to ensure that its functions continue working, like the status messaging that it used to do. I recently discovered one script I wrote myself was no longer working in X3. I haven't yet taken the time to see if it's fixable.

hmm... weird. I figured it was just a kind of standardized thing to manipulate MIDI. Didn't realize it somehow needed support or updates. Like how I can still use old HTML to build a website if I wanted. Perhaps it has something to do with how the hosts read the info.