Logic + 2000XL clipping samples (popping/cracking on 1st bea

So, i just got Fast Track Pro for recording (tracking out) to logic from my 2000XL. I think I have everything sync'd up right, which took some research, but for bass heavy samples, i get popping at the very start of the bar.

For example, my bass drum hits on the first beat, when i play it back, i hear the clip on that first beat and the rest is fine for the 4 bars, but then when looped, on that first beat, it clicks. This is the same for my basslines, assuming they drop on the first beat.

Any Logic (or other DAW) users experienced this? Am i missing something simple?

Thanks so much!!

play around with buffer settings in logics preferences

clipping in my mpc 2kxl sounds kinda 'poppy'.. try lowering the 'pre-DA' gain in the mpc mix screen somewhere

Okay, this is driving me crazy. I've messed with with the "delay transmission by" setting in logic. This has helped for most all tracks recoding in. However, the kick drum is still having problems.

I took screens shots to explain...

Here you see I've tweaked the midi settings to start the recording right on time (if left at "0" I can see a delay in recording the first kick drum)


BUT, even though I timed the start perfectly (by messing with the delay setting) the tail end is cut off, and this (I believe) is why I get the click and popping when the track is looped


here is my delay setting currently


Any advice? the BPMs are matched on the MPC and Logic and Logic and the MPC seem to be sync'd correctly. This minor timing issue is only really heard in things like the kick drum right before the beginning of the next bar. So, the samples and stuff sound okay (although everything is probably slightly off).

Do you hear the pops/clicks on the recording from your DAW, or when you play the loop directly from the MPC?? If your loop isn't chopped to a proper zero-crossing, it will pop and click, and no amount of delay compensation in your DAW is going to change that.

I only hear it when playing back from the DAW, MPC itself sounds fine. I think it's fine on the MPC, just no idea why I can't get it to match in Logic.

Also, it only pops/clicks on the first beat. Audio itself is fine. It's because of that tail end being cut-off that does it (i think). And I can't simply extend the marker in Logic because it extends the time overall and won't match up to the set BPM

If you've synced your MPC and logic with Midi Time Code, note this: "When using MTC, it is recommended to add 1 or 2 bars of pre-roll to allow reliable sync-up of software and device."

It could be the sync glitch you're hearing there.

m:t:c wrote:If you've synced your MPC and logic with Midi Time Code, note this: "When using MTC, it is recommended to add 1 or 2 bars of pre-roll to allow reliable sync-up of software and device."

It could be the sync glitch you're hearing there.

I'm not familiar with the "pre-roll" term, does that mean i should add to the current count-in (which is set at 1 bar)?

I'm using "Midi Clock" not "Midi Time Code".

When I tried to use MTC, I couldn't get it to sync right.

I found the "pre-roll" setting, but it's in seconds, I tried 5 and 10 and it yielded the same results,

I can't quite see, you'd have to zoom in a little more on the sample but does it start on a zero crossing? otherwise you will certainly hear a click at the beginning. You can just add a short attack, ~20 ms will do.

the.dude wrote:I can't quite see, you'd have to zoom in a little more on the sample but does it start on a zero crossing? otherwise you will certainly hear a click at the beginning. You can just add a short attack, ~20 ms will do.

thanks for your response. would you mind explaining this a but more? i am total noob to Logic and am trying to go through tutorials, but i don't quite get what you're recommending. in particular, what zero crossing means and how to add attack.

thanks

Hello…

Check out this wiki article for an explanation of zero crossing.

http://en.wikipedia.org/wiki/Zero_crossing

If your sample doesn't start at a zero crossing the drivers in your speakers are essentially jumping from a rest state (zero) to whatever value your sample starts at so quickly it produces a click.

You can fix it by adding a very fast volume fade in, 20 milliseconds will do, at the beginning of the sample.