-
-
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
Add Slicer mode with visual feedback #9660
Comments
I would also like to see this feature added, as there are lots of controllers with a 'Slicer' pad mode that would benefit from being supported without janky ComponentsJS work-arounds. |
Would love to see a slicer mode too, though this is probably dependent on having downbeat detection (which includes questions like how to handle 3/4, 5/4, changing measures etc.): |
Most slicer modes I've seen rely on multiples of 4 beats, even if the tracks themselves are not in 4/4 time signature. Maybe slicer mode could be implemented without downbeat detection for now? Obviously not for release, it would need to be a bit more reliable than that, but maybe as a POC? Where initiating slicer mode will just initiate it at the beat closest to the current playhead's position? |
I use slicer a lot. For simplicity we can implement in mixxx slicer counting length in beats, not bars. I am not sure, do we detect already if song is 4/4, 6/4 or something else? if we detect just plain song bpm then do slicer in beats, not bars. |
Reported by: Holzhaus
Date: 2019-05-13T19:51:31Z
Status: Confirmed
Importance: Wishlist
Launchpad Issue: lp1828886
It would be nice to have a "Slicer Mode" similar to that found in Serato. An mapping for the DJ-202 that is currently in-development already implements it, but is missing visual feedback in the waveform display:
https://gist.github.com/upCASE/88fb258e85546092af18bc3ff924f752#file-roland_dj-202-scripts-js-L1225
Thus, it would be nice to have something like that in Mixxx natively.
More information about Serato's Slicer Mode:
The text was updated successfully, but these errors were encountered: