-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
improve loop_in/_out adjust workflow #10658
Comments
Commented by: ronso0 As far as I understand your request, that requires decoupling the position bar from the actual play head, i.e.
Maybe you noticed that the beatjump controls switch to moving loops as soon as one is activated?
|
Commented by: holopansel Yes, exactly, you understood correctly. What you explained would be the preferred solution. If technically not feasible, also your alternative solution seems to be much better than the way it is currently. Thank you for your support. |
Commented by: ronso0 Alright. Unfortunately I don't see a way to integrate the alternative model into existing mappings. Shift+loop markers is already mapped to loop_in/out_gotoandstop (I think). However, what I described can curently be implemented at the mapping script level, if I'm not mistaking:
This would also allow to move loop_in backwards which is currently not possible (while playing the loop). I doubt someone would simultaneously drag the loop_in marker AND nudge the track with the wheel, so I hope this behaviour doesn't conflict with established use cases. I guess this can also be implemented in the c++ code, though it's probably cumbersome to integrate into the current looping code. Good news is: with Mixxx 2.4 you can prepare and save multiple loops per track. Save and recall works with the hotcue buttons, as well as labeling (and colors IIRC). |
Commented by: daschuer
Is there a video online demonstrating that desired behavior? |
Commented by: holopansel You can see James Hype using this feature here: I also found this: |
Commented by: ronso0 launchpad is still no fun for discussion (@mention, code snippets) so I started https://mixxx.zulipchat.com/#narrow/stream/247619-UI-.26-UX-design/topic/improve.20loop_in.2F_out.20adjustment.20workflow |
UpdateI implemented this in my Reloop TerminalMix mapping, here's the xml and js snippets: @gqzomer did it in a similiar way for the Reloop Mixage #12296 in this commit 9f76150 For controllers this can be integrated into midi-components-js's
For the GUI / keyboard this is a bit more tricky:
|
Just to jump on this issue, see also this nice video with a great interface to change it dynamically (4mn58, link should point there): https://youtu.be/ziZa7aRwYqA?t=298 |
Reported by: holopansel
Date: 2022-02-09T18:53:21Z
Status: Confirmed
Importance: Wishlist
Launchpad Issue: lp1960439
Tags: looping
According to the user manual it should be possible after manual loop set to push loop-in or loop-out again to adjust the in or out point.
When the loop-in is clicked again, the in position moves directly forward in time. And it is possible to set a new position after the old position. The same applies for the loop-out.
Expected behavior would be that when the loop is already set and either button clicked that the loop stays in position until moved by the user and then with a third click confirms the new point.
This is also the behavior of common cd players.
A common scenario or maybe the most common scenario is that loop-in or loop-out is clicked some milliseconds to late and needs to be adjusted to the beginning, so backward in time. This is simply not possible with the current implementation.
I do not think that it matters here, but anyway I'm using Debian 11, Intel evo I7 4 core on a Dell 7420 Laptop. Driver is Alsa,
Hope, I explained the problem well enough, I am available for clarifications if necessary.
Best regards,
John Last
The text was updated successfully, but these errors were encountered: