If you click on the bpm field of a particular track the decimal will show up.

But the integer value (110 instead of 109.7) will be written back to the file and overwrites the original value!

Yes.. and then you click on the bpm field for that particular track again and you will then see the decimal point.

We changed how SSL reads decimal points after taking a consensus. Most users do not want to see a decimal point so we made it so that if you do want to see the decimal point you have to double click on the bpm field for that particular track.

Don't understand the logic - sorry.

In Tag & Rename I have saved "113.7".

=> Hex-View:

03d71350h: 69 00 73 00 63 00 6F 00 54 42 50 4D 00 00 00 0D ; i.s.c.o.TBPM....
03d71360h: 00 00 01 FF FE 31 00 31 00 33 00 2E 00 37 00 43 ; ...ÿþ1.1.3...7.C
03d71370h: 4F 4D 4D 00 00 00 30 00 00 01 65 6E 67 FF FE 43 ; OMM...0...engÿþC

I import the file in Serato. The column BPM shows "114". After a double click it shows "114.00".

Then I update the artist value.

Re-Check a Hex-View:

03d71310h: 00 0A 00 00 00 10 00 00 00 00 00 00 00 00 54 42 ; ..............TB
03d71320h: 50 4D 00 00 00 04 00 00 00 31 31 34 43 4F 4D 4D ; PM.......114COMM
03d71330h: 00 00 00 12 00 00 00 65 6E 67 00 61 74 61 6C 6F ; .......eng.atalo
03d71340h: 67 20 4E 75 6D 62 65 72 47 45 4F 42 00 00 00 40 ; g NumberGEOB...@

=> BPM is "114"

and not "113.7".

Please don't forget to check the example above. The update of the BPM happens - as you can see!

Thx!

pueblofunky,

I am asking for some information from Serato regarding this.

In the meantime, I think its important for you to know that just because a particular bpm analyzer tells you that the bpm of a particular track is exactly 113.7 bpm doesn't mean that that track is exactly 113.7 bpm.
If you took that same track and ran it through five different bpming programs you would, more than likely, come up with different bpms.

With that said, there is no reason to rely on decimal points to match up your songs.
Not only that but you will often experience what were refer to as "wow and flutter" which is describing a small delay that you would get from the rotation of a turntable which would definitely knock any .1 of a decimal off.
You could still experience this when using cd players if the original file was recorded off of vinyl.

My point is is that using a .1 of a beat to mix your files together is simply useless and is never going to give you the exact bpm.
This is why SSL does not show decimal points.

I know the problem about BPM that all programs have a different logic (I've programmed one in the late eighties).

I've no problem that Serato shows an integer.

My problem is that Serato makes an update (with the rounded value)! And you only need to play a track - you needn't change another value.

And the follow up - regarding to
scratchlive.net

is that other values are destroyed too - as confirmed by Rane Support.

Also when the data have been read in Unicode format but only iso-8859-1 will be used - Serato writes back in iso-8859-1.

=> The next SYNC with my backup copies ALL THE UPDATED BIG WAV files! That's a problem.

So - currently I can only use Serato in protect library mode - but then I'm not able to delete a track from a list/crate. I always have to click setup, ...

PS: The only one solution in the meantime is that before I go djing I set all files to READ-ONLY. Then Serato makes no update but I can still delete a track from a crate.