#beets

sampsyo: ok, that should be an easy fix then. But just looking at the other option, is there anything that would prevent the value to be a float everywhere?

I don't think so -- staying a float should be fine.

that's what I thought. I had a look at the id3v2 spec and didn't see anything that would require it to be float, but I didn't check further

so, is it fine if I check on making it a float everywhere?

the id3 spec is actually pretty clear that "The BPM is an integer"

Mineo: hmm, interesting. Do you have a link maybe?

http://id3.org/id3v2.4.0-frames section 4.2.3

thanks. That makes things clearer

though other tag standards might allow it to be float, id3 is not the only one :)

well, mp4 says it should be int as well. VorbisComment has no specific tag for bpm

or at least, I couldn"t find any

Oh, I believe it should be coerced to an int before writing those tags (just not in the db).

well, if it's different in the db then in the file, comparing both will alwazs yield a difference, which is what I want to get rid of mainly

Ah, true. A forthcoming coercion system is probably the right solution.