1.bpm detection, 2.beat tapping, 3.display contrast

[hemskoc]

forgot to answer you, hemskoc.

No, it did not work to set the BPM range to "None 40 - 240"...
... Imagination's Just An Illusion remains on 139.2 BPM ;-)

Thank you

Even manually tapping it out with the none option selected?
Cheers

[Support@MixVibes]

I have this track in my batch test, and yes the bpm is wrong from start (arround 140).
What I did :
- play it @ 0 pitch
- tap it 2 bars
- the border become white
- flashing in white on the tempo

At this stage if the flashing is not sync with the sound then tap again.

If it is ok, then wait until you see the ok box : click ok. Done.

[barren fell]

thank you both.

hello hemskoc, yes tried with "None" setting (which is 40-240) and it didn't work :-(

hello Support, yes I do exactly this all the time
- play it @ 0 pitch
OK
- tap it 2 bars
OK
- the border become white
OK
- flashing in white on the tempo
yes, it flashes in white, but constantly with exact the wrong value (in this case 139.2 BPM). tested this with a dozen files...

- no matter how long I'm tapping (I did it up to 2 minutes multiple times and with multiple files) the flashing value is not even slightly changed to another value - it flashes EXACTLY on the wrong value analysed by Cross.
When I finally stop tapping the old, wrong BPM is waiting for my OK (a red button below the BPM digits) displaying 139.2

The only thing I noticed is that sometimes for a "millisecond" a lower BPM value is displayed during tapping, but to short to tell you a value.

In short: everything is working as it should except that the tapped BPM is not recognized/accepted... and believe me, I'm counting, drumming, and tapping tight like a clock work for more than 30 years ;-)

Thank you both again and best regards,
barry

[Support@MixVibes]

The dev told me that only 1 bar is needed.

[Stealthii]

Possibly offtopic, why can't we manually enter a BPM value to two decimal places? It rounds the value I type off to 0 decimal places (ie. 178.82 becomes 178.00bpm). It's important for looping

[hemskoc]

Possibly offtopic, why can't we manually enter a BPM value to two decimal places? It rounds the value I type off to 0 decimal places (ie. 178.82 becomes 178.00bpm). It's important for looping

yeah off topic, but that was my sugestion when the extra
decimal was added!
BTW Barren, when you tapped out the new BPM, the new value in decimals is NOT DISPLAYED UNTIL YOU PRESS OK! The old value will be displayed UNTIL you press OK! You just have to make sure the outer of the bpm box is flashing as close as possible to the BPM that you can hear from the track.
Cheers

[barren fell]

A little addendum for your information:

the BPM tapping issue only occurs when working in Vinyl mode!!

Last week I tried the first time to tap tempo in internal mode and was suprised that the BPM value followed my tapping...
The tapped tempo is displayed and wating for "OK"

In vinyl mode tempo does not change and Cross asks to give an "OK" to the wrong (old) tempo. When clicking OK the tapped (new) tempo is displayed and accepted.

Therefore > I will switch to internal sync when tapping tempo... this is a workaround I can live with

[barren fell]

p.s. hemskoc put me on the right track, thanks

[Support@MixVibes]

You're right there is a bug there.

[Stealthii]

I thought something wasn't right there.. never noticed it outright though. Nice barren fell