Quantize - Default to Preset?

For example, I like to quantize to 16th notes w/ 80% strength.

I've defined a preset (and saved it).

However, the first time I use quantize for a session, I need to load my quantize preset. After that, it defaults to my preset.

But as soon as I restart Sonar, the quantize window goes back to the 100% default...

How can I get Sonar to use my preset by default instead of 100%?

I am wondering if perhaps you could set that parameter in a new project, and then save the whole thing as a new Project Template or overwrite an existing one.
 
Wouldn't that result in you having that setting persist for new projects moving forward?
 
Bob Bone
 

am wondering if perhaps you could set that parameter in a new project, and then save the whole thing as a new Project Template or overwrite an existing one.

When I save a project, and then reload it, the quantize settings go back to the default (which is 100%).  In other words, it forgets what preset I was using before I saved.
 
So, I don't think a Project Template would behave any differently.

I'll give project templates a try later tomorrow. Bet it works.

To clarify, this topic not about the parameters *inside* a preset, it's about which preset is loaded by default when you start Sonar:
 

Is there any way to get the Quantize window to default to a preset rather than 100% ?

 

First of all, it turns out my earlier thought was never going to work, because until I had midi data entered it wouldn't even let me at the quantize settings, so please forget my earlier idea.
 
Second of all, I just launched Sonar Platinum, and recorded some random drum hits on a midi track using Battery 3 and one of my midi controllers - just wiping across a bunch of keys to get midi data.
 
I THEN was able to get to the Quantize dialog box, and once there I noticed something I had not noticed in the past.  Just to the right of that text box in the upper part of the Quantize dialog box, there is an icon for doing a Save.  When I hit F1 to get the handy dandy context-sensitive help, it informed me I could actually save any number of presets with commonly used settings.
 
Sooooooo, that seems to me to be good news for you, as you can create and recall your frequently used settings and that to me looks like it addresses this problem in a pretty nifty way.
 
I will also add that they have indeed added a whole bunch of context-sensitive help documentation throughout this latest release, that makes it easy to see what choices there are or are not as you move to different areas of the program, and if it works throughout as really helpfully as it did for me here, this will be VERY helpful to lots of folks.
 
I urge you to try creating a few quantize presets for your settings, and see if that takes care of this issue for you.
 
Bob Bone
 

Pretty sure most dialogs like Quantize have a default setting stored in the registry. I have never bothered with setting them though.

scook
Pretty sure most dialogs like Quantize have a default setting stored in the registry. I have never bothered with setting them though.

It looks like I have the couple of presets I just created for quantize settings groups stored in the Registry at:
 
Computer\HKEY_CURRENT_USER\Software\Cakewalk Music Software\SONAR\Platinum\Presets\{23E18F60-FCEC-11CF-953F-00AA00A76449}
 
And then each of my presets is contained as a single entry by my preset name and then its associated data values.
 
If I wanted to have a default group of quantize settings, I would simply name it so it showed up first, since it does display the list alphabetically.  I also checked in the registry, and it actually stores them alphabetically there as well, not that it matters there - just so the displayed list is alphabetized.
 
So, when I load that project, or any project, and I want to have that one particular group of quantize settings get applied, it currently does not load any default, HOWEVER I merely have to click on that arrow to the right of the preset select box and literally click on the first one in the list, and I am good to go.
 
I personally don't see having to do that to apply a common set of quantize parameter values as ANY sort of roadblock to my work flow.  It LITERALLY takes about 1 SECOND to do this.
 
I have much more to deal with in MY life than the minuscule amount of organizational effort needed to come up with a name for my wonder list of default quantize parameters that sorts alphabetically first in a displayed list of such presets, and the 1 second it takes to select that 1st preset from the displayed list.
 
But that's just me, 
 
Bob Bone
 

Before doing your final save on a project, call up the quantization preset you want. Then whatever you open next, old project or new, will default to that preset. IOW, SONAR remembers what you used last.

Sorry, I missed the part where you said you re-started SONAR. Of course as soon as you close SONAR, it will forget anything that doesn't persist.
 
I'm surprised anyone would find this an onerous limitation, but to each his own. If you're really that freaked out about it, put a MIDI track in your normal template, insert the Quantize MFX, and set the parameters to whatever you want. Save the template. Then when you open your template, not only will you have the quantization you want, you'll have a MIDI track open and ready to record. If you want to record another MIDI track, then just ctrl+drag the MFX into that track.

Okay, I get it...you're upset that SONAR doesn't do something automatically, so therefore you have to remember to do it. In that case, use the MFX as suggested previously. If you save the template with the UI open, you can even have that open when you open the project so you can see a visual confirmation that it has the right settings. AND, it's non-destructive so even if you forget the MFX is in there or what it's set to, you can always just change the settings and re-apply it - no need to undo. AND, you can save MFX presets so you're literally one click+select to any preset you want the instant you open the project, even after re-starting.

MFX are way underrated. My pet peeve is that Cakewalk doesn't do more of them, but given that the current ones seem to fly under the radar, they probably don't feel they have much incentive to add more.

Anderton
MFX are way underrated. My pet peeve is that Cakewalk doesn't do more of them, but given that the current ones seem to fly under the radar, they probably don't feel they have much incentive to add more.

+1 for MFX love!

And for the OP, unlike the quantize function, the quantize mfx is non destructive and can be adjusted or removed later in the project on the off chance you discover something you played doesn't need quantizing.
 
FWIW I doubt that Cakewalk or many Sonar users would see this non persistence as erroneous behaviour. Quantizing is something that is generally used sparingly and with contextual precision if the results are to be musically pleasing. In this light the idea of preloading a single frequently used preset is somewhat of a moot point. Just an opinion of course - YMMV.
 

AutoHotKey is one way to customize any application. It can be used to create keyboard shortcuts to drive objects like the Quantize dialog,

Tripecac
Do you add a separate quantizing MFX to each track in your project?  Or is there a way to get multiple (or even all) MIDI tracks routed through the same quantizing MFX instance?
 

Quantizing is something that is generally used sparingly

Not with me!  My playing is very sloppy, so I quantize everything.  However, I never quantize to 100%; I always leave it at around 80% so it feels a tad bit human.
 
 

Haha - fair enough! The MFX plugin is track specific, so you would need to insert an instance on each midi track. You could do this on your track or project templates though, and the quantize settings will stick.