Skip to content

make beatjump moving active loop optional#16099

Draft
ronso0 wants to merge 2 commits intomixxxdj:mainfrom
ronso0:beatjump-loopmove-option
Draft

make beatjump moving active loop optional#16099
ronso0 wants to merge 2 commits intomixxxdj:mainfrom
ronso0:beatjump-loopmove-option

Conversation

@ronso0
Copy link
Copy Markdown
Member

@ronso0 ronso0 commented Mar 4, 2026

Previously beatjump did always move the active loop.
I'm aware this is by design (#1187) to simplify handling and save screen space -- but it has been bugging me for years, admittedly only rarely, but still: to move inside a loop I'd have to disable it, beatjump quickly, an re-enable it. Cumbersome and stressing, especially with short loops.
(also mentioned in #10811, but that's mainly about beatgrids)

Now at least controller mappings can use both beatjump and loopmove controls independently.

Further details are in #16150

I'd be okay with making this a draft until we come to conclusion wrt the skins UX.

Previously beatjump did always move the active loop.
Now controller mappings can use both beatjump and loopmove controls.

Note: official skins still only provide beatjump controls, no loopmove controls
@ronso0 ronso0 marked this pull request as draft March 9, 2026 15:36
@ronso0
Copy link
Copy Markdown
Member Author

ronso0 commented Mar 9, 2026

Just noticed that there is no loopmove_size and no loopmove_forward/backward controls (only controls with explicit beat sizes) -- which are required for proper GUI/mapping integration.

Will eventually try to implement those.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant