Is there a way to quantize with more resolution than 1/32 triplet

Cause i wish i had even 1/64 and 1/128 if there are quick transitions of notes
1/32 will be to low resolution

the transport bar has snap settings all the way to 1/128

i need the 1/64 or 1/128 to to Quantize this Demo 

Just did this quick, just to point out that higher resolution is needed
if i Quantize it with 1/32 or 1/32 triplet, it will come out way to bad. 

Yes, you can type in the value in ticks. Check out the Quantize Duration video on my site...
http://www.garrigus.com/
 
Scott

--
Scott R. Garrigus - http://garrigus.com - SONAR X3 Power! - http://garrigus.com/?SonarX3Power
* Author of the Cakewalk Sonar and Sony Sound Forge Power book series: http://garrigus.com/?PowerBooks
* Author of the Cakewalk Sonar ProAudioTutor video tutorial series: http://garrigus.com/?ProAudioTutor
* Publisher of the DigiFreq free music technology newsletter: http://www.digifreq.com/
* Publisher of the NewTechReview free consumer technology newsletter: http://www.newtechreview.com/

Seems you might have your tempo set at half what it should be; those sound like 16th triplets to me.

The tempo is all fine, this was just to try and show that if i should
Quantize it i would need higher resolution.

Anyway it is not important it was just to demo
just hope they will add 1/64 and 1/128 resolution, then all will be good.
 

Sonar, as a matter of fact, do already Quantize at 1/64 & 1/128.
The "INPUT" Quantize has values to engage to 1/128 dotted-1/128 triplet as per 'midi tracking'
'Post Quantize' aka "Edit Mode" shows values only to 1/32, but as already pointed out by Scott, you can achieve finer resolutions by entering 'tick values'
 
Then there is the world of ' audio quantize'----The options being "Audio Snap", "Melodyne", "V-Vocal", "Loop Construction"----as having the tools for 'edit quantize'.  I don't know if its possible to do "input audio quantizing" 

Most people cannot consistently perform tightly enough to make quantizing to 128ths work well. At 125 BPM, there are two ticks per millisecond. A 128th is thus 15 milliseconds, and anything over 7.5 milliseconds off the intended time (i.e. over half way to the next/previous gridline) is going to get moved the wrong direction. At much lower tempos, it might be useful, but low-tempo music doesn't usually have a lot of 128ths in it. And anyone who can consistently perform to ± 7.5ms doesn't need to quantize.
 
In any case, as Scott pointed out you can set the quantize resolution in ticks. A 64th is 60 ticks, and 128th is 30.
 
 

brundlefly
...And anyone who can consistently perform to ± 7.5ms doesn't need to quantize....
 

Notable quotable!

A funny quantize resolution story for you from the days of the Mac Plus...
 
Passport Designs had a MIDI sequencer with 240 ppqn resolution, which was considered pretty much the norm. Then Logic was updated to something like 1000 ppqn, and a guy called up Passport demanding a refund because he had just brought their sequencer, the Logic update came out a couple days later, and he felt 240 ppqn was not sufficient to reproduce the nuances of his playing. They actually gave him a refund, and he later had the nerve to call them back and berate them for putting out such an inferior product, and how Logic was so much more accurate.
 
Except for one thing...the jitter on the Mac Plus scaled to the resolution. In other words, there was twice the jitter at 480 ppqn and four times the jitter at 960 ppqn. So the bottom line with the Mac Plus was that ALL sequencers had the same accuracy regardless of the stated PPQN. Even the guys at Passport didn't know this and apparently, neither did any marketing departments 
 
I wrote up the results of my tests for Keyboard magazine , and people were able to duplicate the results so it wasn't just my system.

What I find is that the notes that are below even 1/16 get moved to places they don't need to be. For my work, I would like to select a bunch of midi notes then select the start note and end note and have them re-aligned to an 1/8th or something moving all the notes in between so they still sound musical. 
 
Hope that makes sense.. What usually happens in my world is musicians rush or lag a section with fast notes in it. It all sounds musical but doesn't line up with the timing well. Tweaking the entire section, stretching or compressing or sliding makes it line up better but the relationship between the faster notes needs to remain the same, it's critical to make it sound musical. 
 
It's almost impossible to do that with the quantize the way it works now. You just have to edit every note and or select a few notes and nudge them here or there. 
 
Interestingly you can do this with audio by splitting the audio at the right place and quantizing the start times, which moves the entire section.
 
But I don't know of a way to do that with midi notes.
 
gbow

gbowling
What I find is that the notes that are below even 1/16 get moved to places they don't need to be. For my work, I would like to select a bunch of midi notes then select the start note and end note and have them re-aligned to an 1/8th or something moving all the notes in between so they still sound musical.
 

Fit Time will expand or compress a selection of MIDI notes. For example this screen shot shows a sequence as recorded, then copied with Fit Time applied to shorten the overall duration while retaining the timing of the individual notes in between the start and end notes of the selection.
 

 
Between this and the quantization strength and window parameters, you should be able to do what you want if I understand you correctly.