The incorrect BPM might already be written to the tags of some files. I would highlight various tracks and delete the BPM completely from them. Then select the range and re analyze the files - the correct BPM should then be calculated.

Rafael, I submitted a bug report while 2.0 was in test phase about this same issue. It is not doubling or halveing like some people are claiming (you can just set your range to fix that); in my case the BPM are being calculated are usually off by 10 bpm or for some odd reason analyzed at 128 where they are at around 85-95 range.

Maybe you guys can look into it cause once I open 1.9.2 and analyze the same files that I'm having issues with on 2.0.0, they come up waaay more accurate than 2.0

Yes, I am deletingthe BPM field and selecting the right BPM range before analyzing

Here's how to do it:

PC Users - before installing, find the ScratchLIVE executable (by default it is in C:\Program files\Serato\ScratchLIVE, and rename it - for example call it ScratchLIVE 1.9.2.exe. When you install the new version, the old executable will not be deleted, and you can choose which you want to run by going into that folder and double clicking on the executable. You can still do this if you have already installed the 2.0 Beta - just rename the executable to ScratchLIVE 2.0 Beta.exe, and then reinstall the version you were previously running.

Mac users - before installing, rename the existing application file as above (like "Scratch LIVE 1.9.2") - you have to be admin to rename it. (If you aren't admin, you can copy it to another location, and then rename it.) Even though the 2.0 Beta version is already named to indicate which version it is, you need to change the name to stop it being overwritten by the next version you install, for example by changing "Beta_1" to "2.0B1".