Closed mixxxbot closed 2 years ago
mixxxbot
commented
2 years ago Commented by: pwhelan Date: 2010-10-17T11:21:32Z
This will definitely get looked at when working on the aubio and beat jumping code. I already have quantization of loops working, I believe. This just involves setting loops up on a beat boundary.
I still have not worked on triggering things on a beat, but it should be doable. It will most likely require working with the looping engine and/or the engine scalers.
mixxxbot
commented
2 years ago mixxxbot
commented
2 years ago Commented by: esbrandt Date: 2011-10-26T20:37:39Z
I wonder if mouse clicks really support quantization as stated in the original bug description. If i activate quantization, pause the playback and click on the waveform overview , the playposition is not set on a beat.
mixxxbot
commented
2 years ago Commented by: rryan Date: 2011-10-26T20:49:51Z
Ah, true. Our mouse doesn't really do anything other than let you drag the waveform, so maybe it doesn't make sense? Maybe it originally meant mouse clicks on GUI hotcue/loop buttons?
On Wed, Oct 26, 2011 at 4:37 PM, jus
I wonder if mouse clicks really support quantization as stated in the original bug description. If i activate quantization, pause the playback and click on the waveform overview , the playposition is not set on a beat.
-- You received this bug notification because you are a member of Mixxx Development Team, which is subscribed to Mixxx. https://bugs.launchpad.net/bugs/661884
Title: Support quantization of loops, mouse clicks, and cues/hotcues
To manage notifications about this bug go to: https://bugs.launchpad.net/mixxx/+bug/661884/+subscriptions
mixxxbot
commented
2 years ago Issue closed with status Fix Released.
Reported by: rryan Date: 2010-10-16T20:15:35Z Status: Fix Released Importance: Wishlist Launchpad Issue: lp661884 Tags: bpm, engine
We should allow a 'quantization' mode to be enabled which makes all beats, hotcues, cues, and moues-clicks act as if the user exactly set them on a beat.