No, if I want to play a song, I load it, beatmatch it (or have sync on), and see how it sounds. If it doesn’t sound messed up, I play it. If it does, that’s when I look at the BPM and pitch adjustment to see what would need to happen for it to sound less messed up and I either adjust accordingly or pick a different song.
It’s really not as complicated as you’re making it as long as you have ears and know how to use them. You’re a DJ. Your ears are supposed to be more sensitive to this kind of thing than anyone listening, and your headphones are supposed to be higher-quality than basically any of the sound systems you’re playing on so you can hear these things.
They’re pretty damn good. Traktor’s Hi-Quality version, Ableton’s Complex Pro mode, and Pitch’n’time for Serato can go plenty far for any halfway normal DJ set, and even Pioneer’s old algorithms can do 118 to 125 over the course of a set…that whole set is only a 6% change, which is less than 1 semitone of adjustment at any point.
If a song is really far off the BPM I want to play it at (say, a trance song at 140 that fits better with the trancey house sound at 124ish, which would be like 12%), I use offline pitch conversion to make a 120-something BPM version and save it, since those sound even cleaner. I use Pro Tools to do it, but Audacity can do it in 2 steps (tempo change first, then pitch shifting) and be nearly inaudible.
Yeah…I was about to say, the easiest way is to give the pitch fader a little nudge at basically any point (or a knob if you don’t have pitch faders). If you’re using keylock, you can do it basically anywhere. If you’re not, you have to be more sneaky.
This is actually 100% of the reason my turntables & DVS are setup right now…I wanted to have faders there in my face to remind me to do it. But, really, it doesn’t matter. As long as you pay attention to what you’re doing, just about any way to do it works.