© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
35a32c5
(Get the code!)
Sorry Sean -- I was wrong. There were a couple places here and there where we were losing precision by casting the BPM to a single-precision float. Fixed in lp:mixxx/1.11 r3696 by always treating the BPM as a double. Confirmed that the value maintains its full precision across restarts so it's correct in the DB as well.