Deprecated: mysql_connect(): The mysql extension is deprecated and will be removed in the future: use mysqli or PDO instead in /storage/content/49/145849/famitracker.com/public_html/forum/classes/dbHandler.php on line 29
FamiTracker
So I've been referencing a few threads on here in regard to syncing up the .wavs ive exported from famitracker to my DAW (fl studio in my case). I want to make my dilemma as clear as possible because I would very much like to put this to bed, ive been using fami for years now without being able to execute this and I'm slowly going insane. So heres a good example of my problem.
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.
in spite of trimming the silences at the beginning and end of the wav files, timestretching and restretching, i just cant seem to get the wavs synced to metronome for more than a minute.
i posted in this thread back in the summer for reference: http://famitracker.com/forum/posts.php?id=4715
in spite of all the info, i never really saw a conclusive method, put in simple terms, of how to correct this issue. there was a lot of math involved, playback rates, etc, but in the end i remained confused.
so with your help, im hoping we can figure this out. and if the results are conclusive, maybe we can sticky this thread for future users who run into this issue.
The tempo in famitracker is a slave to the output clockrate, which doesn't want to do anything but 150, 120, 100, and a few others. 4/190 is not actually possible by the tracker, and it needs to modulate frames per row (the speed number), but famitracker is horrible at this, and even if it were good at it, it's impossible to get a sync with a song that doesn't follow a speed measurable to what the famicom can do (100, 120, 150, 225, etc.).
One thing you can do is rewrite all versions of the song that you have to follow suit with the tracker. Another thing you can do is just bend over and let the limitations fuck you violently. Or, you can move the cover to another tracker that isn't limited by this limitation, though that is the longest of all possibilities, and is unnecessary work.
[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.[/quote]
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.
There are some notes on Famitracker's BPM accuracy here:
[url=http://famitracker.com/forum/posts.php?id=4715]http://famitracker.com/forum/posts.php?id=4715
Long story short is that it tends to round down, so if you need accurate tempo you should keep it at 150 or other tempo that doesn't require rounding.
[quote=Slimeball][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.[/quote]
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.[/quote]
just to clarify, 256hz is not normally the engine speed i use. it was an exception in this case because i wanted a faster vibrato effect.
normally i compose all my songs at 60hz.
so with that, if i made a song at a speed of 7 and tempo of 128, famitracker calculates a bpm of 109.71 would the same math above still apply? how would a song like that work?
