When using quantize on a song in session view, it behaves strangely.
1. When you change the quantize level settings it automatically applies it to the song.
2. When you increase the level of accuracy it adds extra warp markers, but when you decrease the level of accuracy it doesn't remove the extra warp markers (it doesn't remove them if you use quantize from the menu either).
Automatically applying the quantize settings when you change them would make sense if it was a clip independent setting but it isn't - its a global setting. Plus having a separate quantize option shouldn't be necessary if quantize was controlled solely from the settings box.
Personally, I'd say change the quantize settings should have no effect until you quantize the song again. It should also be applying the selected quantize level correctly (its not when you decrease the accuracy).
On a related note, the manual is not very detailed about the quantize feature - it doesn't say what effect the different level settings have for example (no explanation of the T or dual value settings).
[amo] Incorrect behaviour when changing quantize settings
[amo] Incorrect behaviour when changing quantize settings
MacBook Pro 13" Early 2011 - OS X 10.7.4
Hi,jonny72 wrote:1. When you change the quantize level settings it automatically applies it to the song.
Do you mean, Quantize is applied when clicking OK in the Quantize settings dialog? If so, it's as intended. The Quantize settings dialog is a Quantize dialog. The Quantize command is a "Quick quantize" command, using the last set settings.
Do you mean that you expect warp markers to be deleted when you quantize a second time, using a larger grid setting?jonny72 wrote: 2. When you increase the level of accuracy it adds extra warp markers, but when you decrease the level of accuracy it doesn't remove the extra warp markers (it doesn't remove them if you use quantize from the menu either).
We don't want and can't do that. It's near to impossible to detect if you moved warp markers by yourself, and I guess you'd not be happy if your own warping was deleted because you quantize. It's a bit the same as for MIDI notes: quantize is a "destructive" operation.
Regards,
Amaury
Ableton Product Team
It seems a bit pointless having a separate quantize command, would be tidier ifthe quantize option opened up a box from which you can choose the settings with apply / ok / cancel options. But as I said the quantize setting is global, apply it to one song, then change the settings and apply to another, then the new settings show on the first song when you bring up the quantize settings dialog which is confusing to me.Amaury wrote:Hi,jonny72 wrote:1. When you change the quantize level settings it automatically applies it to the song.
Do you mean, Quantize is applied when clicking OK in the Quantize settings dialog? If so, it's as intended. The Quantize settings dialog is a Quantize dialog. The Quantize command is a "Quick quantize" command, using the last set settings.
But why would you want to quantize audio that you had already warped? You wouldn't, quantize should be destructive and remove all existing warp markers and replace them.Amaury wrote:Do you mean that you expect warp markers to be deleted when you quantize a second time, using a larger grid setting?jonny72 wrote: 2. When you increase the level of accuracy it adds extra warp markers, but when you decrease the level of accuracy it doesn't remove the extra warp markers (it doesn't remove them if you use quantize from the menu either).
We don't want and can't do that. It's near to impossible to detect if you moved warp markers by yourself, and I guess you'd not be happy if your own warping was deleted because you quantize. It's a bit the same as for MIDI notes: quantize is a "destructive" operation.
In practice this would make a lot more sense as well. I've been getting very mixed results with different songs - one will quantize well at 1/4 and the next only at 1/32. So being able to switch from one level of quantize to the next quickly and easily to find the best setting (with all existing makers being removed) would be very useful.
Again, in practice the current non destructive quantize doesn't work very well and normally gives very poor results due to the way it handles existing markers.
MacBook Pro 13" Early 2011 - OS X 10.7.4
Re: [amo] Incorrect behaviour when changing quantize settings
Hi,
It's the same as for MIDI: whatever editing you do in the MIDI clip, Quantize would override. And if you quantize many times with different settings, the former quantization is not "undone".
Regards,
Amaury
It's the same as for MIDI: whatever editing you do in the MIDI clip, Quantize would override. And if you quantize many times with different settings, the former quantization is not "undone".
Regards,
Amaury
Ableton Product Team
Re: [amo] Incorrect behaviour when changing quantize settings
Well, I still think its stupid but I would appear to be in the wrong so I'll let it go.
I do think the quantize menu item and dialogue box could be tidied up and improved upon, as well as the manual improved which doesn't have much info especially on the different quantize settings.
Not sure if this needs to stay as a bug report or not, I'll leave that up to you.
I do think the quantize menu item and dialogue box could be tidied up and improved upon, as well as the manual improved which doesn't have much info especially on the different quantize settings.
Not sure if this needs to stay as a bug report or not, I'll leave that up to you.
MacBook Pro 13" Early 2011 - OS X 10.7.4
Re: [amo] Incorrect behaviour when changing quantize settings
Hi,jonny72 wrote:Well, I still think its stupid but I would appear to be in the wrong so I'll let it go.
I do think the quantize menu item and dialogue box could be tidied up and improved upon, as well as the manual improved which doesn't have much info especially on the different quantize settings.
Not sure if this needs to stay as a bug report or not, I'll leave that up to you.
Can you elaborate? Always interesting to hear feedback as well.
Regards,
Amaury
Ableton Product Team