Comment 7 for bug 1156868
Revision history for this message
| Stéphane Guillou (stephane-guillou) wrote | #7 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
73416ba
(Get the code!)
Hi all
Yes, this is something that would really help people mixing with large and/or diverse libraries.
I agree with cies that just storing the BPM is already helping a lot just to narrow down a collection in order to beat-match. The user can directly see what the BPM are, and even though they would have to wait again for the analysis to find where the beats actually are, at least the user does not have to lose time analysing dozens of track to find the one that could fit. I do not think the beat grid issue actually blocks the problem described here. Maybe fixing this would just lead to a different bug report about the beat grid not being saved as well.
I would extend on the proposition here with what I guess is a feature request that fits nicely in here: having the option in the preferences to either always save the analysed BPM or only saved them when "validated" by the user (with the little check-box).
Cheers