[Feature Request] Automatic Deletion of Low-Quality Loops

[vpoguru]

Summary

Add a function that automatically deletes loops that exceed (or fall below, depending on definition) a user-defined quality threshold. This would allow users to quickly clean up large loop libraries without manual review.

Proposed Solution

Introduce an automated cleanup feature that evaluates loops against a quality score and removes those that do not meet a user-specified threshold.

Key Functionality

• A configurable quality threshold (e.g., slider or numeric input)
• Automatic identification of loops exceeding the defined low-quality limit
• One-click deletion of all affected loops
• Optional preview list showing which loops will be deleted before confirmation

Example User Flow

1. User opens LoopAuditioneer’s batch processing panel
2. User sets a quality threshold (e.g., “Delete loops below 65% quality”)
3. User clicks “Clean Up Low-Quality Loops”
4. App shows a preview of loops marked for deletion
5. User confirms → loops are deleted automatically

Acceptance Criteria

• Users can define and modify the quality threshold
• The app correctly evaluates loops using the existing quality metric
• Only loops outside the accepted quality range are removed
• User confirmation is required before deletion
• Operation completes without affecting loops above the threshold

Benefits

• Faster library cleanup
• Reduced manual effort
• Improved focus on high-quality material

Optional Enhancements (Future)

• Preset thresholds (e.g., “Aggressive,” “Balanced,” “Conservative”)
• Per-project vs. global threshold settings
• Logging/report of deleted loops

[larspalo]

It shouldn't be too hard to implement this. However, there are a few things in your suggested workflow that I think is a bit outside the normal batch process behaviour.

My suggested implementation of the workflow would be:

1. Open batch process
2. User selects source/target directories and "Remove low quality loops" as process and clicks "Run batch"
3. A new dialog is opened with the current loop search quality set by default, but the user can change the value to actually use in this dialog exactly the same way as the loop search parameter
4. The user can then, in this new dialog, make a "Dry run" to not actually remove any loops but get an output of how many loops would be removed and possibly how many would be left for each file in the progress status textctrl, or just perform the loop removal immediately - which also would present the same output to the progress status textctrl about what was actually done

Again, the numerical loop evaluation is a rather crude tool in my opinion as the human ears are much more sensitive to changes in background noise than the actual waveform matching might suggest. Some loops with clicks/glitches can of course be eliminated by such a process - but many times they could also be fixed by just adding a small crossfade in the ODF if no other problem exists. Other loop "defects" might not be so easily fixed but would require a new search with better search criteria (many times involving setting other parts of the sustain section to do the search in to avoid said background noise changes).