perfect loop on pc isnt so perfect in the xl

i was just reminded about this "issue" when collabing with a fruity user. how come when you perfectly trim and/or loop something on a wav editor & throw it in the xl it's never right?

you can always use the zoom function on the mpc. thats why its there to get an accurate cut. i use an audio editor cause im more accurate with a mouse then with the wheel, but i used to use the mpc. its the same thing, you just gotta use your PLAY X: feature and the zoom feature. you'll be straight.

its good to use the PLAY X:AfterZn function. that will let you hear whats AFTER your selected zone. Play after zone and listen to see if it starts right on beat. if its cut off a little, the you know your chop will be off. if it starts right on beat, then you have a good chop. also check PLAY X:ZONE to listen to your selected area.

hope that helps

i think the answer is that the timing is never exactly the same.
noticed it when syncin mpc to cubase, i had originally the same tempo on mpc and cubase, had some audio loops on cubase synced to the tempo, then synced cubase to the mpc and the audio loops were slightly off-time.

this happens also with machines: we did some NO-MIDI rock n roll jams with machines from different brands, (eg: korg+akai+yamaha) all set to the same tempo, they stayed in time for some bars then loose timing, because of slight differences in clock.

also noticed when exporting a loop from mpc, loadin it in melodyne, the tempo on mpc was 102, in melodyne (which is accurate) the tempo showed like 102.3 or something like that.

import your loop in the mpc then use the bpm timestretch function.
it works for me and given that the difference is minimal, u got no artifacts on the stretched sample.

well thats why you have to actually sync the clocks of the different machines...im not too hip on this subject of synching different devices. but maybe when you synced cubase you were having some latency issues? when I used to sync to cubase, everything was on time and cool.

peace

well, i explained myself bad:
i have no problems syncin to cubase:
fact is:
i was workin separetly(not synced) on both cubase and mpc

on cubase i timestretched some audioloop to (say) 102 bpm
and on the mpc i was workin at the exact same tempo (102 bpm)

when i synced em the sync was perfect, but now the audioloopz are off time because the 102 bpm of cubase are not the same 102 bpm of the mpc

so the drumhits and isolate samples on cubase are perfectly syncd to the mpc and even the start of the audioloopz, but their duration is slghtly wrong for the above mentioned reason.

a bit contorted but thats it!!!

gotcha. THAT method never worked for me. I've tried it before but it never works. I dont know how the mpc is counting those beats per minute, but it isnt the same as my computer. or maybe we're doing something wrong?

but thats basically what the sync is for. so you can keep everything on time. otherwise the clocks will just run on and do what they do.

The 2000 truncated the last 30ms of your perfect loop.

good input from all. thanks!