Quote:
I'm doing a remix of the song "Dead Disco" by Metric. A speed of 4 with a tempo of 190 in the ftm sounds great to my ears. Which according to famitrackers math = a bpm of 285.
After finishing the song i import the wavs into my DAW of choice (fl studio) and then i proceed to use the tap tempo function to tap out the beat. which then gives me a bpm of 142, obviously you can see the gigantic difference here.
If you divide 285 by 2 and round down you get 142. It's the same tempo, just divided by two!
Since the actual tempo is 142.5 BPM, I really hope FL's tempo tap feature recognizes tempos that aren't a whole number and doesn't arbitrarily round up/down. If it always rounds to a whole number, you shouldn't rely on it at all.
Just like you shouldn't rely on famitracker's BPM thingy! It does nothing more than counting 4 rows as one "beat". You shouldn't trust it. :P
I changed the engine speed from 256 to 228. 228Hz aligns with a tempo of 190, just like 60Hz and its multiples align with a tempo of 150. Also I've uploaded an .mp3 with FT's output mixed with a "metronome" playing at 142.5 BPM (I used Audacity's "click track" feature for this). I hope it's enough in sync.
I wouldn't say the maths behind this are particularly hard. You just divide tempo by 2.5 to get the engine speed you need, and multiply the engine speed by a whole number if it's too slow.