concurrent library scanning and analysis

Bug #1741665 reported by Be
This bug affects 2 people
Affects Status Importance Assigned to Milestone

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.

Tags: usability
Be (
Changed in mixxx:
importance: Undecided → Wishlist
milestone: none → 2.2.0
description: updated
tags: added: usability
Revision history for this message
Be ( wrote :

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.

Revision history for this message
Be ( wrote :

Related: Bug #1741676 (add tracks to library as scanner is running)

Be (
Changed in mixxx:
milestone: 2.2.0 → 2.3.0
Revision history for this message
Daniel Schürmann (daschuer) wrote :

We have to consider, that the beatgrid and waveforms took a significant HD space.
So I am in doubt that analyzing by default is a good choice.

The other issue is that analyzing it took sooooo long. We may introduce a strategy to make that unnotable for the user. Something like a maintenance thread that runs only when no other cachingreader is active.

Be (
Changed in mixxx:
milestone: 2.3.0 → none
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Related blueprints