BPM wrong imported if decimal point is used


bpmanalyzer creates exact bpm tag entries, e.g. 120,01. Which is imported as 12001. Which is obviously wrong.

file attachments


InneHo wrote Oct 16, 2013 at 8:48 AM

According to the documentation IDv3 documentation the BPM value is an integer value (decimal places aren't allowed). Therefore I have to implement a "workaround" to handle these "special" values.

=> Will be fixed in Verion 124.14 (soon)

wrote Oct 16, 2013 at 8:49 AM

alexrjs wrote Oct 16, 2013 at 3:01 PM

I made temporary fix in an older source code version... I just use a division by 100 if the value of the bpm is bigger then 250... Guess that's a dirty hack, but it worked... Anyway my uneducated guess is, that the bpmanalyser is storing an integer, but it presents it as an exact bpm value on the front end... So I guess it is up to the user of the bpm field to make sense out of the bpm value...

Anyway, many thanks for the fix, I appreciate it... Like your Player...

Some ideas (I wanted to try but I have no time, cause I work on another project):
  • Saving the visual state; so I don't have to hide the frequency displays all the time
  • A "Key" field for Harmonic mixing -> Have a look... Mixed In Key... Rapid Evolution 3
  • Harmonic Mixing feature according to the "Key" and "BPM"

InneHo wrote Oct 16, 2013 at 4:37 PM

Hi Alex,

yes you implemented the "hack" that I had in mind. I think's this is the best way ...

I found on some web pages that the common value for dividing is 501 instead of 250.
Tomorrow the latest version will be ready for download ..

And something about your ideas:
You're welcome to improve the player!
Feel free to implement your ideas. (As far as you share your code. I like Open Source ;-)

Regards, InneHo

InneHo wrote Oct 16, 2013 at 4:44 PM

Hi Alex (again),

I forgot something to say: The visual state should be saved already.

In the DJP.AppConfig.cfg file (simple text file) you will find the key "PlayerWaveForm" (Section "Player Setting").
The DJP.WPFFrontEnd.PlayerBoards.PlayerAreaPresenter handles this ..

Maybe you find a bug ? Please let me know ...

(Again) regards, InneHo

wrote Oct 17, 2013 at 6:46 AM