It doesn't work in 4.0.7 for me. Yes, the screen comes up, and the [TAP] button records the timing of your taps, but when I click on [Save] nothing happens. BPM is not written to the database nor the file tag.

Any hope of getting this updated for 4.0.7?

It doesn't work in 4.0.7 for me. Yes, the screen comes up, and the [TAP] button records the timing of your taps, but when I click on [Save] nothing happens. BPM is not written to the database nor the file tag.

BPMtapper does not work on a fresh install of MM 3.1 an a new winXP sp3.

But also on my old PC BPMtapper does not work with MM 3.1 when i delete from the harddisk the older version of MM 3.05:
originally i had the script working in MM 3.0.5. Afterwords i installed the new version of MM 3.1 into a different directory and did not uninstall MM 3.0.5.
I istalled BPNtapper to the new MM 3.1 as well and it is working with MM 3.1 without problems but only when the old directory of MM 3.0.5 is still there. When i delete it the BPMtapper panel is not shown anymore in the new MM 3.1. i get an error instead: "the web seite cannot be shown".

The same error nstead of the panel shows on the new PC with only the new MM 3.1.

I have a strange issue wit the this script:

BPMtapper does not work on a fresh install of MM 3.1 an a new winXP sp3.

But also on my old PC BPMtapper does not work with MM 3.1 when i delete from the harddisk the older version of MM 3.05:originally i had the script working in MM 3.0.5. Afterwords i installed the new version of MM 3.1 into a different directory and did [u]not[/u] uninstall MM 3.0.5. I istalled BPNtapper to the new MM 3.1 as well and it is working with MM 3.1 without problems but only when the old directory of MM 3.0.5 is still there. When i delete it the BPMtapper panel is not shown anymore in the new MM 3.1. i get an error instead: "the web seite cannot be shown".

The same error nstead of the panel shows on the new PC with only the new MM 3.1.

mistresso wrote:
What I've seen with some integrated tappers though - ie, ones accompanying apps that did BPM analysis - was that they would actually look at the "original" BPM field, assume if you were tapping it out that it was inaccurate, and then try to contextually determine if you were hitting a fractional value of the stored value. IE, say the track was set to 120 incorrectly. The tapper will then "see" any tapped average of 60bpm +/- 10 beats as 60, and lock onto that value.

I like that idea.
good one, I will try and incorporate it.

Yes, it's very often so that BPM software like "Mixmeister BPM Analyser" finds a BPM value half or double of the correct one.

An option like that suggested by mistresso would be exactly the thing to "round up" the BPM.tapper and make it a "perfect thing"

[quote]mistresso wrote:What I've seen with some integrated tappers though - ie, ones accompanying apps that did BPM analysis - was that they would actually look at the "original" BPM field, assume if you were tapping it out that it was inaccurate, and then try to contextually determine if you were hitting a fractional value of the stored value. IE, say the track was set to 120 incorrectly. The tapper will then "see" any tapped average of 60bpm +/- 10 beats as 60, and lock onto that value.

I like that idea.good one, I will try and incorporate it.[/quote]

Yes, it's very often so that BPM software like "Mixmeister BPM Analyser" finds a BPM value half or double of the correct one.

An option like that suggested by mistresso would be exactly the thing to "round up" the BPM.tapper and make it a "perfect thing" :-)

DaledeSilva wrote:
I will give it a background image that you can replace.

Thanks!

I believe there are several scripts like this that were written a while ago which are very useful but get "lost" unless you stumble across them. Just the fact that we are discussing it now will bring this script to the attention of a whole group of users.

Keep up the good work.

Jim

[quote="DaledeSilva"]

I will give it a background image that you can replace.

[/quote]

Thanks!

I believe there are several scripts like this that were written a while ago which are very useful but get "lost" unless you stumble across them. Just the fact that we are discussing it now will bring this script to the attention of a whole group of users.

Heh, well the search is still on for a seasoned BPM analyzer that actually does everything we want without making a big mess or running off the Itunes library. It's funny that with all the music apps we have for the PC, there is simply nothing out there that writes to the ID3 tag and isn't totally half-assed. Heck, most of the apps haven't even been updated since 2005.

I think most people look at the calculus required to actually figure out BPM's - which is still only 60% accurate at best - and flee in terror.

I just wish some of the audio engineers out there would put their heads together and come out with an open source library that could be shared.I can't blame the folks who want to make a buck off their hard work, but the fact is that the science still does not work reliably - which seems to scream for a cooperative and not capitalistic solution at this point.

Heh, well the search is still on for a seasoned BPM analyzer that actually does everything we want without making a big mess or running off the Itunes library. It's funny that with all the music apps we have for the PC, there is simply nothing out there that writes to the ID3 tag and isn't totally half-assed. Heck, most of the apps haven't even been updated since 2005.

I think most people look at the calculus required to actually figure out BPM's - which is still only 60% accurate at best - and flee in terror.

I just wish some of the audio engineers out there would put their heads together and come out with an open source library that could be shared.I can't blame the folks who want to make a buck off their hard work, but the fact is that the science still does not work reliably - which seems to scream for a cooperative and not capitalistic solution at this point.

mistresso wrote:What I've seen with some integrated tappers though - ie, ones accompanying apps that did BPM analysis - was that they would actually look at the "original" BPM field, assume if you were tapping it out that it was inaccurate, and then try to contextually determine if you were hitting a fractional value of the stored value. IE, say the track was set to 120 incorrectly. The tapper will then "see" any tapped average of 60bpm +/- 10 beats as 60, and lock onto that value.

I like that idea.
good one, I will try and incorporate it.

Just JP wrote:One thing I find myself wishing for is the ability to skin the script. I use the Eclipse skin which is a dark skin and BPM.Tapper is very white.
Jim

I will give it a background image that you can replace.

I guess the reason that I haven't fixed / worked on this script is because i've always got another script in int he back of my mind that will incorporate this into it. However, that script also hasn't been addressed yet.
I will see what I can do to get these small edits happening.

thanks for commenting on my script!

[quote="mistresso"]What I've seen with some integrated tappers though - ie, ones accompanying apps that did BPM analysis - was that they would actually look at the "original" BPM field, assume if you were tapping it out that it was inaccurate, and then try to contextually determine if you were hitting a fractional value of the stored value. IE, say the track was set to 120 incorrectly. The tapper will then "see" any tapped average of 60bpm +/- 10 beats as 60, and lock onto that value.[/quote]I like that idea.good one, I will try and incorporate it.

[quote="Just JP"]One thing I find myself wishing for is the ability to skin the script. I use the Eclipse skin which is a dark skin and BPM.Tapper is very white.Jim[/quote]I will give it a background image that you can replace.

I guess the reason that I haven't fixed / worked on this script is because i've always got another script in int he back of my mind that will incorporate this into it. However, that script also hasn't been addressed yet.I will see what I can do to get these small edits happening.

The script works great for my needs in MM 3.1 also. I don't use the "save" button but it would be nice if I could.

I use it either manually check a BPM value determined by MixMeister or when I'm to lazy to open MixMeister for an individual tracks. One thing I find myself wishing for is the ability to skin the script. I use the Eclipse skin which is a dark skin and BPM.Tapper is very white.

Jim

The script works great for my needs in MM 3.1 also. I don't use the "save" button but it would be nice if I could.

I use it either manually check a BPM value determined by MixMeister or when I'm to lazy to open MixMeister for an individual tracks. One thing I find myself wishing for is the ability to skin the script. I use the Eclipse skin which is a dark skin and BPM.Tapper is very white.

Hrm, maybe what we need then is just a simple script to rewrite existing BPM's that are selected. It wouldn't make as much sense in combination with the BPM tapper.

What I've seen with some integrated tappers though - ie, ones accompanying apps that did BPM analysis - was that they would actually look at the "original" BPM field, assume if you were tapping it out that it was inaccurate, and then try to contextually determine if you were hitting a fractional value of the stored value. IE, say the track was set to 120 incorrectly. The tapper will then "see" any tapped average of 60bpm +/- 10 beats as 60, and lock onto that value. Really helps for some of us rhythmically-challeneged people.

Hrm, maybe what we need then is just a simple script to rewrite existing BPM's that are selected. It wouldn't make as much sense in combination with the BPM tapper.

What I've seen with some integrated tappers though - ie, ones accompanying apps that did BPM analysis - was that they would actually look at the "original" BPM field, assume if you were tapping it out that it was inaccurate, and then try to contextually determine if you were hitting a fractional value of the stored value. IE, say the track was set to 120 incorrectly. The tapper will then "see" any tapped average of 60bpm +/- 10 beats as 60, and lock onto that value. Really helps for some of us rhythmically-challeneged people.

Just wondering on the current status of this script, as the last poster said it wasn't working on MM3 very well.

External programs still seem to be the way to go - due to all the math that goes into guesstimating beats - but with the ever present doubling/halving issue with BPM calculations, having a batchable button to quickly override the false calcs would be very useful. To date I think I've only seen it in ONE app, (beaTunes?), even though it's requested numerous times on forums.

Still though, no one has even written a good external app that works well enough for us non-DJ's. Beatunes seems to have the most features, but like Rapid Evolution and most other apps, it works only off playlists and Itunes databases. Other apps are Mac-only (the main OS used by DJ's and musicians), or write to the comments field and hork up tags in other ways.

I'd use MixMeister but it's TOO simple, and its speed means it reports a lot of the doubled/halved figures - but with no easy way to correct them save manual editing.

Just wondering on the current status of this script, as the last poster said it wasn't working on MM3 very well.

External programs still seem to be the way to go - due to all the math that goes into guesstimating beats - but with the ever present doubling/halving issue with BPM calculations, having a batchable button to quickly override the false calcs would be very useful. To date I think I've only seen it in ONE app, (beaTunes?), even though it's requested numerous times on forums.

Still though, no one has even written a good external app that works well enough for us non-DJ's. Beatunes seems to have the most features, but like Rapid Evolution and most other apps, it works only off playlists and Itunes databases. Other apps are Mac-only (the main OS used by DJ's and musicians), or write to the comments field and hork up tags in other ways.

I'd use MixMeister but it's TOO simple, and its speed means it reports a lot of the doubled/halved figures - but with no easy way to correct them save manual editing.

you're right.. if you music get's acurate bpms from that program, it's alot more efficient to use that.

however, the reason I created this script is that while that program can return an 'acurate' bpm, with slower music, it's usually not the beat we're interested in that mixmeister uses...
eg. for a song which we'd want to know is 60bpm, it would probably return 120bpm

so the timing is acurate.. but doesn't give any indication of the "speed" of the song.

Dale.

you're right.. if you music get's acurate bpms from that program, it's alot more efficient to use that.

however, the reason I created this script is that while that program can return an 'acurate' bpm, with slower music, it's usually not the beat we're interested in that mixmeister uses...eg. for a song which we'd want to know is 60bpm, it would probably return 120bpm

so the timing is acurate.. but doesn't give any indication of the "speed" of the song.