Forum to discuss all matters relating to the MPC1000 and MPC2500 operating systems created by 'JJ' (all versions).
User avatar

By jahrome Fri Jul 06, 2007 11:29 pm
Yes, time stretching on the XL is un-useable for me. For large samples, it can take 20 plus minutes. When I purchased the MPC 2500, this was the first function I tested. It took the MPC 2500 no time at all to process the same sample. I posted my results when the MPC 2500 forum was created.
User avatar

By Jacpot Fri Jul 06, 2007 11:50 pm
The trick is to use bpm match. Its much faster then time stretch
User avatar

By jahrome Fri Jul 06, 2007 11:57 pm
I posted this thread almost 2 years ago:
http://www.mpc-forums.com/viewtopic.php ... sc&start=0:


The MPC 2500 has the sample slice feature or recycle where it will chop samples according to the amplitude of instruments in a track. It will create a program with these chopped samples. You can also choose to convert these chopped samples to a patched Phrase. Then you can use real-time tempo control that doesn't affect pitch.


The MPC 2500 also has a timestretch function in the sample editing menu. I loaded a 3 minute Camp Lo song, the classic 'This is it'. The original tempo was around 90 and I changed it to 120. It took about 15 seconds and sounding great. It didn't effect the quality of the song at all. So next, I did the same thing but slowed the tempo to 40. This 3 minute sample took 1 minute to process. When I played it back..the song was just creeping along..slow as heck. The vocals in the track were pretty good..the beat stuttered..but thats what happens when you take this feature to the extreme. It easily passed that test. Attempting this test on the 2000XL can take up to 10-20 minutes! This feature rivals the timestretch function of the MPC 4000. It is at least equal in this term.



Now I am fully aware of what the MPC 2000XL can do. I owned/used the MPC 2000XL since it was released. I got rid of it the same week my MPC 2500 arrived.

By el tripps Wed Jul 11, 2007 3:43 am
doesn't the 2500 only detect tempo for 1 bar loops though? My biggest issue is that I can't take a sample that is 2 bars long and use the sample detection accurately. It assumes all loops are 1 bar. This is the only thing that keeps me from going straightforward with the mpc 2500 exclusively. On certain beats I like to take a sample that is maybe 2 bars long and 76 bpm's and then time stretch it to somewhere around maybe 88 bpm's, then chop it. This doesn't work on the 2500 machine because with the akai OS I can't tell the machine how many beats the loop is.
User avatar

By coles_brandon Wed Jul 11, 2007 10:07 pm
el tripps wrote:doesn't the 2500 only detect tempo for 1 bar loops though? My biggest issue is that I can't take a sample that is 2 bars long and use the sample detection accurately. It assumes all loops are 1 bar. This is the only thing that keeps me from going straightforward with the mpc 2500 exclusively. On certain beats I like to take a sample that is maybe 2 bars long and 76 bpm's and then time stretch it to somewhere around maybe 88 bpm's, then chop it. This doesn't work on the 2500 machine because with the akai OS I can't tell the machine how many beats the loop is.


In essence a 2 bar loop doesnt exist. It all depends on your time signature. If you consider one bar 4/4 then a 2 bar loop is 8/4 timing. If your loop is 8/4 then your 2bar loop is 16/4 and so on and so forth. You can make damn near ANYTHING happen if you know your timing.
By el tripps Thu Jul 12, 2007 3:16 am
first thing I tested was the tempo detect and time stretching. i looped up a 2 bar drum loop, the time signature was 1/4 and the loops was 8 beats long. it detected 110.2 bpm's and I converted it to 96 bpm's. when i set my sequence to 96 bpm's it did not loop properly. i made sure i assigned the new sample to the right pad. the loops seemed a little slow. what did i do wrong?
User avatar

By synthburn Thu Jul 12, 2007 7:21 pm
its better becuase of the pad 11 mode