BPM Issues - Recycle vs. MPC 2000XL

I'm having BPM issues when using Recycle to create simple 1 bar, 4/4 drum loops for use in my MPC 2000XL.

Using Recycle, I'll simply crop a basic drum sample to create a perfect 1 bar, 4/4 drum loop. In this particular situation Recycle tells me that the BPM of the sample is 93.701. At this point, I export my drum loop as a .WAV file to a 1GB Flash Memory Card for use in my MPC 2000XL.

The issue is, when I open the drum loop file in my MPC 2000XL and examine the parameters of the file, the BPM is totally different then what it was in Recycle. Why is this happening? In short, I just want the BPM of the file I created in Recycle to be the same when I open it up in my MPC 2000XL.

Any help is much appreciated.

do you have recycle in preview mode? check to make sure you aren't changing the tempo in recycle.

you're opening a .mid right?

Make the loop 93.7. The MPC can't handle the extra decimals.

or just 93 bpm

To answer mQueue's question, I'm just working with .WAV files at this point.

I've taken Lord Toranaga's advice to modify the BPM of the sample in Recyle to the
nearest whole number (e.g. 93) for use in my MPC. In order to modify the BPM in Recycle, I've set my desired slice points and adjusted the Stretch % in the Envelope to 100% to achieve the best sounding result. I then export as one sample in .WAV format.

When I reopen the edited .WAV file in Recyle to view my changes, I set the correct number of bars, and I can see that the BPM has changed to 93, which is what I want. However, now I'm noticing that a small portion of my .WAV file is now outside of the right locator. Why is this happening? When I move the right locator all the way to the right to include the entire .WAV file, the BPM decreases to a differant rate, this is what I don't want, so I revert back.

When I open this same file in my MPC and view the .WAV file in the Trim screen, it appears as if the same thing is happening. The start and end points highlight the entire .WAV file except for a small snippet at the end. The BPM checks out @ 97 in params, but in order to sequence a perfect sounding loop @ 93 BPM, I need the entire .WAV selected in the Trim screen or elso it sounds choppy. When I select the entire loop in the Trim screen to achive this, the BPM in params decreases to a differnt rate. Why is this happening?

What am I overlooking in my process here?

Thanks for any advice.

trust you ears, not anything else.


you are wasting time trying to be so precise.

just make some music

isnt the nearest number 94?

As Lord Toranaga said...

you dont need anything else than to trust your ears...

So what if your MP says it is 290 BPM? who cares
as long as in the main screen you set the BPM's to 93
and you've maid the sample at 93 BPM
then when you try to sequence it it will be perfect.
You can even use the 93.701 file in 93.7 BPM as this will not make a difference for 1 bar

Dont try to match the numbers up
it is pointless and useless...

Make some music...
And IMO you should take the seperate sounds and sequence them on your MPC... DRUM MACHINE

You're doing something very wrong here. Why would you want to apply stretch to the LOOP??? The point of the stretch in recycle is to stretch single HITS so you can play around with the tempo of the original loop. You add stretch to that loop, and surprise surprise, your loop is longer = the BPM gets f'd up.

Furthermore, you have absolutely no use for a midi file (or for Recycle, for that matter!) if all you want to do is loop one single .wav in your MPC. The only data that midi file contains is the tempo and that the loop starts at 001.01.00. Your whole process seems overly complicated to me.

stinktank wrote:You're doing something very wrong here. Why would you want to apply stretch to the LOOP??? The point of the stretch in recycle is to stretch single HITS so you can play around with the tempo of the original loop. You add stretch to that loop, and surprise surprise, your loop is longer = the BPM gets f'd up.

Furthermore, you have absolutely no use for a midi file (or for Recycle, for that matter!) if all you want to do is loop one single .wav in your MPC. The only data that midi file contains is the tempo and that the loop starts at 001.01.00. Your whole process seems overly complicated to me.

you are wrong about the midi file it also contains a sequence telling the individual notes when to trigger.

Lord Toranaga wrote:

stinktank wrote:You're doing something very wrong here. Why would you want to apply stretch to the LOOP??? The point of the stretch in recycle is to stretch single HITS so you can play around with the tempo of the original loop. You add stretch to that loop, and surprise surprise, your loop is longer = the BPM gets f'd up.

Furthermore, you have absolutely no use for a midi file (or for Recycle, for that matter!) if all you want to do is loop one single .wav in your MPC. The only data that midi file contains is the tempo and that the loop starts at 001.01.00. Your whole process seems overly complicated to me.

you are wrong about the midi file it also contains a sequence telling the individual notes when to trigger.

Dude only had one "individual note" (i.e. what I refer to "the loop" that "starts at 001.01.00" above) to trigger, so I'm not wrong about anything.

fair enough. I apologize.