concurrent library scanning and analysis
Bug #1741665 reported by
Be
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Mixxx |
New
|
Wishlist
|
Unassigned |
Bug Description
It would be nice if there was an easy way to have Mixxx scan the library for new tracks and add them to the analysis queue as it finds new tracks. On first startup with a fresh database and when adding a new library folder, the user should be presented with the option to scan the library, scan and analyze, or neither. This should improve the first run experience considerably.
Changed in mixxx: | |
importance: | Undecided → Wishlist |
milestone: | none → 2.2.0 |
description: | updated |
tags: | added: usability |
Changed in mixxx: | |
milestone: | 2.2.0 → 2.3.0 |
Changed in mixxx: | |
milestone: | 2.3.0 → none |
To post a comment you must log in.
On further thought, I am doubting that we should bother users with the choice between scanning and scanning + analysis. With analysis, scanning, and database transactions each in their own proper threads and not hanging the GUI, I think we could just replace the automatic scan on first start with automatic scan + analysis. If the user wants to cancel analysis part way through, they could click a cancel button in the library GUI.