-
-
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
prioritize tracks with stored analysis in analysis queue #6753
Comments
Commented by: daschuer the attached patch works like described. It it includes the changes from Bug #1088071. |
Commented by: rryan Hm, my only worry is that we throw away partially completed analysis of a
|
Commented by: daschuer Hi RJ, Thank you fro review!
Commit to lp:mixxx/1.11? |
Commented by: rryan Thanks -- I didn't read closely enough. In most of the analyzers from initialize() you call loadStored() and return false if the track initialized. I don't see this in AnalyserBeats. Is there a particular reason for that? Otherwise looks good to commit. The patch also includes the fix from Bug #1088071, right? |
Commented by: rryan I plan to tag beta2 tomorrow and would definitely like this to be included so we can get it tested. Thanks! |
Commented by: daschuer Committed to lp:mixxx/1.11 #3626. |
Issue closed with status Fix Released. |
Reported by: daschuer
Date: 2012-12-08T15:09:15Z
Status: Fix Released
Importance: Low
Launchpad Issue: lp1087995
Attachments: prioritize_analysis.patch
Currently, If you load a already analysed track to a deck, the waveform is displayed after a possible running analysis on an other track is finished.
I will prepare a patch which instantly loads the analysis data for already processed tracks.
The text was updated successfully, but these errors were encountered: