My Quantize shortcut key "Q" doesn't work. Not sure why?

My SonarX1 installation is a fresh installation on a brand new machine with all the default SonarX1 settings.  When I go to Preferences-Customization-KeyBindings it says "Q" should be Quantize.  But when I press "Q", nothing happens.  Am I doing something wrong?  "P" works fine and brings up the Preferences, but "Q" doesn't.  Any help would be appreciated.  Thank you
 
Geno

Have you selected something (like a clip) to quantize?
 
I ask because I just tested it on a MIDI drum clip.
 
"Q" brought up the Quantize dialog.  After reviewing the settings, I pressed the "OK" button and it worked.

Positively Charged


Have you selected something (like a clip) to quantize?
 
I ask because I just tested it on a MIDI drum clip.
 
"Q" brought up the Quantize dialog.  After reviewing the settings, I pressed the "OK" button and it worked.

Positively - OK - It works on a MIDI clip just like you said.  What I was doing was in the PRV - selecting a group of notes - It doesn't work here.  Try selecting notes in the PRV and hit Q.  This must be a bug.

Testing it in PRV now guys...

Positively - wow - Mine doesn't work and neither does Keni but yours does.  Let me trying closing and re-opening, or a different project.  Did you test in Sonar32 or Sonar64?  I'm in 64.

Keni


It seems that the letter shortcuts don't work in PRV... only in TV...

So in PRV you have to use the old alt-P followed by Q to open the process menu, then select quantize...

I've brought this up a few times.  "Q" simply does NOT work in the PRV.  A glaring omission indeed.
 
 

But mine does work, Billy.  Surely there is some explanation?

I went into key bindings and in global options I found Process|Quantize. I bound Q  to That.

It now works in both PRV and TV.

Don't be afraid to customize key bindings!

They should have had it like this already, but still...

You can always save export import key bindings and also return to default key bindings.

Positively Charged


But mine does work, Billy.  Surely there is some explanation?

Interesting.   But previously "Q" was a default for "Mute clip".  I never changed that.  It worked.
Now "Q" is changed to Quantize.
 
No matter what I've tried - when I select a clip in the clips pane, double click it to bring it into the PRV, select some notes and hit "Q -- NOTHING happens.
 
I've checked the keybindings.  Even re-entered it as it wants to be.  Nada.
 
So I find it interesting you can actually hit Q with notes selected in the PRV and it works?
 
Are you really sure of this?
 
 
BTW, it definitely DOES work in the track/clip pane.  That is, if I select a clip there and hit Q, it works.  Just NOT in the PRV at all (for me and others).
 
 

Positively Charged


Lance, that's what I said in my prior post.  Mine was ALREADY bound to Quantize in global options.

I know I did not do it; it was already like that.

So I think there's got to be SOME explanation for why some of us have different default key bindings?

See my post above.  "Q" is not (new with X1) the default for Quantize.  In prior versions it defaulted to Mute Clip.
 
SO you didn't have to change it -- X1 did it for you.
 
 

Okay.  It is messed up, I'll admit that, and I still don't know why our systems would be different in this regard. 

But at least it works if you assign it.

Oh crap - Now my project is having a problem playing - it's stuck.  I think I just corrupted it.  Could be Trilian, could be Sonar.  Crap.

Billy, that's what I said.  I just took some literary license.  (?)

Would you like to report it on the bug contact form?  It isn't reproducible on my system, so it would make more sense if you (or somebody else having the problem) did.

There you go, you have homework now.  HAH!

guitartrek


Oh crap - Now my project is having a problem playing - it's stuck.  I think I just corrupted it.  Could be Trilian, could be Sonar.  Crap.

I don't know if you've seen what I've said elsewhere about a similar thing, but ...
 
I started a TOTALLY new/fresh project.  I was in the creative mood.   Long story short...  I had to stop working in X1 and bring the project back to 8.5.3 (which took some adjustments as well -- quite a mood killer actually).
 
I just kept hitting bugs.  And then at one point no matter what I tried, X1 would crash every time I 'saved' the project (which I do often).
 
NONE of those issues happened with the same project in 8.5.3.  So I just kept going with it.
 
Strange, but true.    And what should I have done?  There was NO choice really.   So I just think there are some non-visible bugs (memory leaks perhaps, or other similar issues) that MAY creep up when least expected.
 
This is why we need a serious major bug fix patch asap, in my humble opinion.  X1A was not that.
 
 

Positively Charged


Billy, that's what I said.  I just took some literary license.  (?)

Would you like to report it on the bug contact form?  It isn't reproducible on my system, so it would make more sense if you (or somebody else having the problem) did.

There you go, you have homework now.  HAH!

I suspect they knew or know about this. It's too obvious and glaring, and enough users apparently have the issue.
 
But, while I don't mind entering bug reports, I also feel just a teeny weeny itsy bitsy upset that this has turned into a public beta test.  I want to make music.   Reporting bugs that are not so obvious is one thing.  It makes sense to help find those esoteric ones, and probably does require a large user base to find those.
But basic functionality shouldn't be the users responsbility in general.  I bought a program to use.  To work with.  I don't mind helping them out, and do and will; but it is a bit over the top unless they explicitly release a true public beta.
 
But ok, I'll report it - and I bet it's been reported already anyway ;)