Expose floating-point BPM in MediaFile or normalize floats to ints in database

[Julf]

Running "beet write" causes updates of bpm values from integer to float (bpm: 113 -> 113.145) despite multiple runs of "beet write". "beet update -p" suggests same changes the other way around (bpm: 113.145 -> 113).

[sampsyo]

Currently, MediaFile exposes the bpm field as an integer. We could consider trying to expose a floating-point value instead. In this case, we would also want to change the field in library.py accordingly. If we do this, we'd have to live with some formats being unable to store non-integer numbers, but that's probably fine.

Alternatively, we could ensure that the database always stores integers. Currently, the field (via the Integer type in dbcore.types) does not attempt to round fractional numbers to integers in the normalize method.

[Julf]

Hi!

I guess this was never resolved? It is somewhat annoying that "beet update"
and "beet write" keep updating every single file that has a bpm field,
as "beet update" insists on converting floats to ints, and "beet write"
on converting ints to floats...

Is there any way to tell "write" and "update" to ignore the bpm field?

Julf

[sampsyo]

Is there any way to tell "write" and "update" to ignore the bpm field?

Not currently; sorry.