The main problem is still there.
If iQ is OFF, ‘non quantize’ is still ON ( if set to anything but 0 ).
So there’s no way, to easily use Hard Quantize and Iterative Quantize,
with two different shortcuts, as it was possible in Cubase VST32.
The workslow in V6 is as follows :
Choose a quantize preset via drop down menu
( presets can be stored with and without ‘Non Quantize’ )
This menu can get very long, as the self made presets are added after the standard presets.
disable / enable iQ ( iterative Quantize ) via shortcut
do the actual quantizing via shortcut
( yep, Bo’s macro will ease the last two steps )
After all, it’s a small improvement over V5, where you need to open the Quantize Settings dialog.
Still, it would be great to simplify the use of the 2 different quantize modes, again.
( Sadly CinStudios’ idea, Shortcuts for Quantize Presets, would not help, as ‘Non Quantize’ is not part of a quantize preset. )
Wouldn’t a keybind to a preset % of 0 accomplish that? Just curious.
I’ve always wondered why hard quantize didn’t work without turning iterative to 0. Just seems odd as they seem like either/or options. It’s kind of like the Monty Python SPAM skit.
Eric: I don’t like ‘Itertative Quantize’. I just want to hard quantize.
Waitress: Well 10% doesn’t have much quantize in it
Eric: I don’t want any quantize
Waitress: You can Hard Quantize.
Eric: Does it have iQ?
Waitress: Of course, but you can set it to %5 and it won’t have much iQ
…
Picture vikings marching around “Grid, Grid, Grid, Grid …”
Hmmm … I have to check that again, I think ‘non quantize’ IS actually a part of a quantize preset …
Anyway … guess quantize preset shortcuts are difficult to implement.
Indeed ! And it was working like expected, in pre-SX versions.
Er… Getting TO it is not the title of the thread. I presume you can get to it if you know it’s “not working as expected”.
My statement still stands. “Fiddle” is a highly technical term among us pros.
I think you’ll find that after a little study the new way will get clearer. Looks good to me. I may start using it but never on drums, makes them sound lumpy to my ears.
To Dada.
I still find, looking at it, that any unselected notes stay put and selected notes that have iterative, or other quantise applied behave like I always expected. They move closer to the nearest quantise (magnetic) point.
I think that the range setting has been altered (removed?) to “streamline” the process which is ok for the way I work but not so for you. If that’s the case then I’d lobby for an option for the behaviour.
the quanitiz have taken a quantum leap forward and … a quantum leap backwards! +1 + -1 = 0
Feature re-request for C6.5
separate hard Q and interative Q commands
AND
Reintroduce the position and velocity SLIDERS and the percentage SLIDERS.
I want to be able to set the Q to auto exec and then drag the sliders until it sounds right!
That crap they are replace with is a total unintuitive headache !!!
But the inspector stuff in the Key Editor is BRILLIANT! The Quanitize tool and the others where you need where!
Having that said, you can’t have separate Q commands and you can’t have no sliders.
Jan,
When using Iterative Quantize, do you often vary the value for “non-quantize”?
If not (i.e. you have a “regular” non-quantize value preference), you might consider building a Logical Editor preset that selects only notes that are outside a given range, then, with “Non-Quantize” fixed at zero (which is what you want when doing hard quantizing) apply Iterative Quantize only to the selected notes. (Could add that preset to the beginning of Bo’s macro )
Just for fun (o.k. a bit perverted ), I have built such a preset (attached here also). It is based on a PPQbase of 960 (i.e. 240 ticks per 16th), with an effective “non-quantize” range of outside ±40 ticks on a 16ths grid.
Here’s a screenshot of part of it (because the LE preset cannot be seen in its entirety without scrolling the upper section of the LE window…
wow Vic, although that is quite impressive, wouldn’t it be easier if turning off iQ disabled non-quantize? Think of the number of scripts you’d have to write to support the various grid sizes, tempos and tick depth.
Ha … thanks Vic …
I need the following NonQuantize ranges : ± 3, 4, 5, 8, 10
If You would be so kind …
No ! … just joking
Thanks again for the effort ( ± 40 is way too high for me, though )
This is indeed a workaround, as I rarely change the NonQuantize value.
But I don’t have any shorcuts left, for the different NonQuantize settings.
Also will this work for audio events ? Now that we finally have iQ for audio ??
The simplest solution is still, to automatically turn off NonQuantize, when turning off iQ.
You’d have to build a similar preset in the Project Logical Editor.
Anyways, for your “ideal” Hard Quantize situation, there are other things to take into account…
Should it also override the “Catch Range” parameter?
What about “Swing”?
It’s interesting that you post that. I’ve always wanted the presets to save the entire set of quantize dialog values and assign those to the Quantize key commands. That way I could have the 4 or 5 configurations I use the most as keys.
The thing with swing is, I only use it interactively. I’m not saying everyone should, just that that’s how I use it. So, it is always off unless I’m twiddling the knob. I pop back and forth between Q and iQ constantly. I’ve just got in the habit of turning iQ and magnetic to 0 before closing the dialog. So, iQ for me is always an interactive process like swing even though it doesn’t need to be (and I wish it wasn’t).
Just found this link. I have to say that after using Cubase for roughly the 20 years its existed (average use 8 hours a day) its taken this crazy update (no direct key command for Iterative or hard quantize) for me to finally join the forum. Please Steinberg - I love Cubase to bits - but this function is driving me, and any other cubase user I know of, nuts - please do an update and give us the choice.
)
