bpmcalc is an Amarok script that calculates BPM on song change and update Amarok's database.
This is my first amaroK script which calculate the BPM of the currently playing file. I wrote it after the recent patch which add a BPM field in the playlist. It isn't really useful, but I think it's cool; plus it can make conversations: "Hey! did you know tha this tune is 130BPM!..."
Don't forget to add the BPM column to the playlist (right-click on the column titles->show columns->BPM)
Note the detection is sometimes bad for some music styles or when the bass drum isn't loud enough. However, in those cases the BPM is often a multiple of what has been detected. If you don't agree with what is detected, you can right click the playlist -> bpm -> check manually and press spacebar.
Feel free to modify it or to mail me your
comments/requests/favorite tune!
Requirements:
· Amarok
· Python
· ffmpeg (to convert a music chunk in something readable)
· libSoundTouch (the package is soundstretch on debian)
· permission to write some bytes to /tmp
What's New in This Release:
· fixed so that the script works with filenames containing shell characters such as '
· increased reliabity of "stop"
· do not clobber existing BPM (MP3 only, if eyeD3 is installed)
· do not automatically double measurements that are lower than threshold. It's more likely that the real BPM is 4X measured rate, but we cannot know for sure.
· vastly improve manual BPM, using itjBPM as example for onehanded operation
· . (period): tap
· enter: set BPM
· [ : divide BPM by 2 (by 3 if triple time selected)
· ] : multiply BPM by 2 (by 3 if triple time selected)
· ' (single quote): next song
· / (slash): advance 30 seconds
· 0-9: set rating
· measure counter: click to switch between square and waltz measures
· TODO once http://bugs.kde.org/show_bug.cgi?id=142750 is fixed
· do not clobber BPM on non-MP3 files
· allow comment updating
Product's homepage