-
-
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
UI freezes when applying actions on multiple/many tracks #8480
Comments
Commented by: uklotzde Sorry, Sebastien, that I didn't notice this earlier! |
Commented by: uklotzde This is not a duplicate, but a known issue! In fact the new issue recently reported by Sean is a duplicate of this issue: |
Commented by: uklotzde We don't need a separate worker thread. I already have an idea in my mind how such a reactive, event-loop-driven TrackActionScheduler can be implemented efficiently:
Some parts of the new TrackAnalysisScheduler might be reusable. |
Commented by: uklotzde Unassigning myself, because I don't plan any major changes on the current software design of the UI. Even the mentioned reactive and multi-threaded redesign of the analysis has not been merged, yet. Instead we should think about decoupling the backend from the frontend and eventually replace the frontend with QML components. |
Commented by: uklotzde The workaround is in place. Further improvements would require substantial changes to the architecture. |
Issue closed with status Fix Released. |
Reported by: sblaisot
Date: 2016-02-20T17:11:24Z
Status: Fix Released
Importance: High
Launchpad Issue: lp1547916
Tags: gui, library, metadata
I just discovered a bug in Mixxx 2.0.0 (64 bits on win 10 64b).
If you select a (rather) large number of tracks in the library, open right-click menu and select BPM->Reset tempo and beatgrid, the interface freezes until mixxx has finish resetting tempo and beatgrid on all these tracks.
I've just seen that with 1000 tracks selected.
This should probably be done in another low-priority thread.
The text was updated successfully, but these errors were encountered: