Mixxx

Bug #898213
Comment #4

Comment 4 for bug 898213

Revision history for this message

RJ Skerry-Ryan (rryan) wrote on 2011-12-17: Re: turn quantization on by default

#4

So there are a few options:

1) Quantize all beatloops regardless of quantize setting and turn quantize off by default.
2) Quantize all beatloops regardless of quantize setting and leave quantize on by default.
3) Quantize beatloops according to quantize setting and turn quantize off by default.
4) Quantize beatloops according to quantize setting and leave quantize on by default.

Option 4 is what we have today.

I'm not in favor of 1 or 2 because it eliminates the ability to use beatloops when the beatgrid isn't perfect. If your beatgrid BPM was perfect but the offset was wrong, then you want to be able to lay a beatloop without having it snap to the grid. Doing 1 or 2 takes away options from the DJ which seems wrong.

Good UX comes from simplicity. I think the simpler the mental model you need to use Mixxx, the better. Having beatloops act differently from loops, hotcues differently from cues, etc. just complicates the mental model you need to keep in your head when using Mixxx. You shouldn't have to go through a flow-chart in your head to understand what's going to happen when you hit a button. (For example: Loop -> follows quantize setting. Beatloop -> always quantized regardless of quantize setting. Cue -> seeks to the quantized cue position on set. Hotcue -> Sets hotcue but doesn't seek to quantized position on set, etc).

Oops, that last paragraph was just a long-winded inelegant way of saying Keep It Simple. Mixxx is already far too complex and we should be working to make things more unified and simple.

Anyway.. between option 3 and 4, I think that these are the pros and cons:

OPTION 3 PRO
============
* Cues/hotcues/loops/beatloops are not badly placed if the beatgrid is inaccurate

OPTION 3 CON
============
* DJs might not ever discover the quantize mode.

OPTION 4 PRO
===========
* Beatlooping experience is much better when quantize is enabled.

OPTION 4 CON
============
* Cues/hotcues/loops/beatloops work badly when the beatgrid is wrong
* DJs might not realize that quantize is a toggle button (the magnet symbol) and might think that mixxx is stuck with this behavior when they would prefer it was disabled.

So there are a few options:

1) Quantize all beatloops regardless of quantize setting and turn quantize off by default.
2) Quantize all beatloops regardless of quantize setting and leave quantize on by default.
3) Quantize beatloops according to quantize setting and turn quantize off by default.
4) Quantize beatloops according to quantize setting and leave quantize on by default.

Option 4 is what we have today.

I'm not in favor of 1 or 2 because it eliminates the ability to use beatloops when the beatgrid isn't perfect. If your beatgrid BPM was perfect but the offset was wrong, then you want to be able to lay a beatloop without having it snap to the grid. Doing 1 or 2 takes away options from the DJ which seems wrong.

Good UX comes from simplicity. I think the simpler the mental model you need to use Mixxx, the better. Having beatloops act differently from loops, hotcues differently from cues, etc. just complicates the mental model you need to keep in your head when using Mixxx. You shouldn't have to go through a flow-chart in your head to understand what's going to happen when you hit a button.  (For example: Loop -> follows quantize setting. Beatloop -> always quantized regardless of quantize setting. Cue -> seeks to the quantized cue position on set. Hotcue -> Sets hotcue but doesn't seek to quantized position on set, etc).

Oops, that last paragraph was just a long-winded inelegant way of saying Keep It Simple. Mixxx is already far too complex and we should be working to make things more unified and simple.

Anyway.. between option 3 and 4, I think that these are the pros and cons:

OPTION 3 PRO
============
* Cues/hotcues/loops/beatloops are not badly placed if the beatgrid is inaccurate

OPTION 3 CON
============
* DJs might not ever discover the quantize mode.

OPTION 4 PRO
===========
* Beatlooping experience is much better when quantize is enabled.

OPTION 4 CON
============
* Cues/hotcues/loops/beatloops work badly when the beatgrid is wrong
* DJs might not realize that quantize is a toggle button (the magnet symbol) and might think that mixxx is stuck with this behavior when they would prefer it was disabled.