-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Change between Grid and raw beats without re-analyze. #7127
Comments
Commented by: daschuer Yes, this puzzled me for a time. Why is "Assume Constant Tempo" Recommended? Here is a discussion but without a conclusion: Bug #1114643 A checkbox per track looks locks like a good workaround. Could it be possible to drop the checkbox and let Mixxx decide? Can you explain what is the advantage of a constant beat grid? What are your typical use cases? I am not an expert, but is it to skip short parts of track like vocal solos or temporary tempo shifts? In addition we need an indicator in the library, if the track has const tempo or not. |
Commented by: ferranpujolcamins If I have to be honest, I don't really know what are the real advantages of I've read the comments on the bug you mention. In my opinion, dealing with At the moment I mostly play at my college's parties where I play all kind
-- |
Reported by: ferranpujolcamins
Date: 2013-07-31T21:43:42Z
Status: Confirmed
Importance: Wishlist
Launchpad Issue: lp1207096
Tags: beatgrid, bpm
Mixxx should allow to toggle between beat-grid and raw beats once the song is already analyzed without the need of re-analyze the song.
When dealing with songs with a loose tempo, I have to comment the songs I need to re-analyze, and then go to the analyze view to redo the job. Just checking / unchecking a check-box on the track's properties dialog seems much more practical to me.
Then, we could also remove the "assume constant tempo" option in preferences. Again, when dealing with collections of tracks with a tight tempo and tracks with loose tempo, it is just not easy to check / uncheck this every time.
The text was updated successfully, but these errors were encountered: