Looping not in keyboard map.

[RJ Skerry-Ryan]

In lp:mixxx/1.8, hotcues and loops are a major new feature so we should incorporate them into the keymap.

There is tons of cruft in our current keyboard maps. Currently I've added hotcues 1-4 to zxcv and m,./ for channel 1 and 2 respectively. I also made Shift+ the key clear the hotcue. I moved the BPM tap buttons to q and u because they were originally in the bottom row. I'm at a loss for where to cram in looping though. Comments?

If we merged the BPM tap buttons into the beat sync button (by making one a Shift+ modifier) then that would free up two keys on each side in the QWERTYUIOP row. But we really need 3 keys for looping to make sense.

Also, we could use a handy cheat-sheet diagram for new users.

[Sean M. Pappalardo (pegasus-renegadetech)]

What about using the numeric keypad? Use +, Enter, and 0 on it for Loop in, Loop out, and Reloop/Exit respectively, since they're all double-size keys. Then 1-9 can be used for stored loops in a future version.
Or how about using PrtScrn/Sysreq, Scroll lock, and Pause/Break since they're all together?

[RJ Skerry-Ryan (rryan)]

Yea that works fine for full-sized keyboards, but it won't help laptop
users.

On Sat, Jun 26, 2010 at 6:10 AM, Pegasus <email address hidden> wrote:

> What about using the numeric keypad? Use +, Enter, and 0 on it for Loop in,
> Loop out, and Reloop/Exit respectively, since they're all double-size keys.
> Then 1-9 can be used for stored loops in a future version.
> Or how about using PrtScrn/Sysreq, Scroll lock, and Pause/Break since
> they're all together?
>
> --
> Looping and hotcues not in keyboard map.
> https://bugs.launchpad.net/bugs/596131
> You received this bug notification because you are a direct subscriber
> of the bug.
>

[Swiftb0y (swiftb0y)]

Mixxx now uses GitHub for bug tracking. This bug has been migrated to:
https://github.com/mixxxdj/mixxx/issues/5424