Tap tempo question

[lukas412]

So I really like how the tap tempo functions on the sequencer, but for me I always get results that are way way faster than I feel they should be. I have used tap tempo on tons of devices over the years, and I have even compared tap tempo apps on my phone vs the sequencer, tapping to the same song I am trying to match. Does anyone else see this issue or is it just my bad tapping? On Maschine for example I always get what I feel is pretty close.

Thanks,

Luke

[TK.]

Hi Luke,

I will test the accuracy with a digital pulse generator soon (just added this to my TODO list)

Best Regards, Thorsten.

[dOperator]

hellos,

been testing things on my unfinished midibox seq4 (lpc17) .. and i can confirm that the tempo tap doesn't work as expected, it's a good deal too fast (110 instead of 90 bpm eg) ..

[TK.]

Thanks for the input! This pushes the priority on my TODO list! :)

But I won't have to possibility to check this before next week.

Best Regards, Thorsten.

[TK.]

Question: are you using Wilba's Panel?

And how do you tap the tempo - with MENU+PLAY, or in the BPM page?

Best Regards, Thorsten.

[dOperator]

Not Wilbas here, custom with a dedicated tempo tap button. It's the same with Menu+Play and BPM page for me.

[TK.]

Got it, fixed it!

The tap tempo function was calculating with 5 taps based on the delay measured for 4 taps - therefore the resulting tempo was too high.

In v4.064 it should work very accurately now! :)

Best Regards, Thorsten.

[dOperator]

Thanks, working perfectly now (:

Edited November 4, 2012 by dOperator

[TK.]

Fine! :)

Best Regards, Thorsten.

[EsotericLabs]

Hello,

I still experience too fast tempos with the tap tempo function on my seq4l.068. If I tap along a beat, it speeds up! I have both the newest firmware and the new bootloader. Strange, not?

Edit: found it and solved! The seq4L file seq_ui.c function 3SEQ_UI_Button_TapTempo() still had the old code. I checked in file seq_ui_bpm function SEQ_UI_BPM_TapTempo() of the big seq4. The bpm calculation was different, so I put big seq4's version in and Bingo!

    // original seq4l version: comes up with too high tempo

    // u32 bpm = 60000000 / (accumulated_delay / tap_tempo_beat_ctr);


    // new version copied from the large seq4 seq_ui_bpm.c function SEQ_UI_BPM_TapTempo

    u32 bpm = 60000000 / (accumulated_delay / TAP_DELAY_STORAGE_SIZE);

Edited December 14, 2012 by Martijn

[TK.]

Thank you very much! :)

The change is in the repository now, and it will be available with the next release.

Best Regards, Thorsten.

[TK.]

fixed in V4L.069

 

Best Regards, Thorsten.