From a3670594c5a3c5a7053dd8bd8280b7c2b20cefbe Mon Sep 17 00:00:00 2001 From: Florian Jung Date: Sun, 8 May 2011 14:38:10 +0000 Subject: the proper AL::raster quantisation functions are used in the scoreeditor --- muse2/muse/midiedit/scoreedit.cpp | 7 +++---- 1 file changed, 3 insertions(+), 4 deletions(-) diff --git a/muse2/muse/midiedit/scoreedit.cpp b/muse2/muse/midiedit/scoreedit.cpp index cb37c382..9534abf9 100644 --- a/muse2/muse/midiedit/scoreedit.cpp +++ b/muse2/muse/midiedit/scoreedit.cpp @@ -1315,15 +1315,15 @@ bool operator< (const note_pos_t& a, const note_pos_t& b) } - + int flo_quantize(int tick, int quant_ticks) { - return int(nearbyint((float)tick / quant_ticks))*quant_ticks; + return AL::sigmap.raster(tick, quant_ticks); } int flo_quantize_floor(int tick, int quant_ticks) { - return int(tick / quant_ticks) * quant_ticks; + return AL::sigmap.raster1(tick, quant_ticks); } @@ -3927,7 +3927,6 @@ set staff_t::parts_at_tick(unsigned tick) /* BUGS and potential bugs - * o the proper quantize functions must be used! yes, really! * o when the keymap is not used, this will probably lead to a bug * same when mastertrack is disabled * o tied notes don't work properly when there's a key-change in -- cgit v1.2.3