-
-
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
Decide if "Re-analyse beats" should be ON by default for 1.11 #6803
Comments
Commented by: rryan I agree... we really need an upgrade dialog otherwise people will miss it. I don't want to automatically opt them in. |
Commented by: ywwg Would clicking OK on the dialog actually trigger the analysis or just toggle the checkbox so files are reanalyzed on load? |
Commented by: rryan It would be a one-time question on the first run of 1.11.0 that On Fri, Feb 1, 2013 at 9:22 AM, Owen Williams wrote:
|
Commented by: ywwg I'll bang this out tonight. |
Commented by: rryan Thanks! For reference src/upgrade.cpp is where all the config-upgrade code On Fri, Feb 1, 2013 at 12:43 PM, Owen Williams wrote:
|
Commented by: ywwg Here's the patch. I spent a lot of time on the wording, trying to make it clear that upgrading beatgrids was a good idea, and the default choice, but the user has the option of opting out. |
Commented by: esbrandt Thanks for the patch.
Should we automatically make a backup copy of mixxxdb.sqlite before upgrading just in case? |
Commented by: esbrandt |
Commented by: rryan I played with the wording a little bit here. RE: Jus
I'm against making a backup copy of mixxxdb.sqlite. We didn't get any feedback from someone that was unhappy about us losing their metadata in the beta period which leads me to believe either we warned people well enough via the forum post or they just don't care :). |
Commented by: esbrandt Hmm, i cant't see a window title either in OSX.
|
Commented by: rryan I just removed the bolding. Also, I just discovered the --author flag to bzr commit which looks like it gives Owen credits in the log:
We should use this flag in the future when committing patches from people who don't have commit access so they can get credits in the log. |
Issue closed with status Fix Released. |
Reported by: esbrandt
Date: 2012-12-24T10:54:07Z
Status: Fix Released
Importance: High
Launchpad Issue: lp1093431
Tags: usability
Attachments: upgrade_beats.diff, [OSX 10.8.2](https://bugs.launchpad.net/bugs/1093431/+attachment/3513189/+files/OSX 10.8.2), upgrade.patch
Now we got the praised QM tempo beat detection + improved syncing features in 1.11 there is a catch: All the syncing stuff rises and falls with correct beat detection data for the tracks playing. This correlation is not apparent to the user.
Users upgrading from previous versions won't profit until they discover the "Re-analyse beats" option. Until then we`ll still hear trough the forums and feedback form how much beat detection sucks, that loops and and sync drift .
How about detecting if a user is upgrading and presenting a chooser dialog with additional info message why they should re-analyze the files?
Setting the option to ON dy default could backfire for users who have neatly set beatgrids by hand.
The text was updated successfully, but these errors were encountered: