I’m still catching up with current technology (“Snap to zero-crossing” blew me away when first I saw it!), but when the various BPM-detectors in my progs just frustrate me, I’ll take the most likely number as a starting point, open the track w/ Wavelab lite, enter the number into the meter/tempo option, and line up a nice strong peak, like a plosive. Like misterC said, sometimes listening to other remixes is the best plan, especially when it comes to being tripped up by the pella itself. Everything will be on beat, but just a whole lot faster than the original in which case you’ll know to use the lower tempo range to find the BPM. If you have a slow song at 60bpm, it’ll tell you it’s 120bpm. Go for the middle tempo range since most songs are written here. Then again, maybe you don’t want it to sound natural. Just remember not to stray to far from the original tempo or the vocal won’t sound natural. Where it’ll take the vocal and match it to your current tempo. You can also use another feature in it, “Fit to Tempo”.
If it’s an official acapella Fruity Loops will give you the BPM perfectly, DIY’s acapellas it has a little trouble but it gets close. Fruity Loops does its thing, and then you get your BPM.
You’ll be prompted with a window, just select which ever BPM range you think it’s closest to. Then click the little down arrow on the audio file which will give you some options of what to do with it ie, cut, and stutter. Then in your session open up the playlist (can find it in the view tab), click in the lower portion (it’s divided into track loops, and audio files) and load up the vocal. But if you’re wanting to find the bpm to a song that doesn’t tell you, download the demo of Fruity Loops.
0 kommentar(er)
