Chopshop Chopping early

Hey, has anyone else noticed chopshop's auto chop almost always chops too early?

I've try a few different setting for Threshold, Recover & Sensitivy but whatever I try I always have to move the start points forward manually a bit. Anyone else noticed that or am I missing something?

x2k wrote:Hey, has anyone else noticed chopshop's auto chop almost always chops too early?

I've try a few different setting for Threshold, Recover & Sensitivy but whatever I try I always have to move the start points forward manually a bit. Anyone else noticed that or am I missing something?

never tried jet..But I will... IT'S a good question...

...are you trying to chop a mono or a stereo sample? remember that you only see one channel in trim screen and the wave on the other channel might be starting earlier, so the autochop uses this as a start point.
other than that converting to sliced samples will turn the slices to mono - this also can lead to a different sounding startpoint...

peace jo

selecta jo wrote:...are you trying to chop a mono or a stereo sample? remember that you only see one channel in trim screen and the wave on the other channel might be starting earlier, so the autochop uses this as a start point.
other than that converting to sliced samples will turn the slices to mono - this also can lead to a different sounding startpoint...

peace jo

for sure, I had thought of that and to be honest I can't really think back to a time when I was deffo chopping a mono sample but I'm fairly sure I have done....will try it a bit later on and let you know for sure. Thanks.

this was the case with the 1000, too

i think the problem may be that it's not necessarily chopping early, it's that the os adds a TINY little attack at the beginning at each chop - in order to make it so there's always gonna be a zero crossfade. it's a nice thought, but inappropriate for those who want control.

it reminds me of all of the Wizards in Windows XP made for old people/the developmentally disabled - let me help you do this, let me help you do that.

i'm not positive, but this very well may be the case. is the gap really small?

here's a way around it - if possible, leave plenty of room in your slices before the same starts. that way, you can use the sample file itself to dupe your machine FAAAAAAAAR beyond 1/96 ppq - you can use shift timing and even swing via sample silence at the start. i've been doing this recently - nearly all of my notes are on perfect 100% quantise but they swing and shift at rediculous values. the only thing this doesn't work for is shifting stuff early.

it's another interesting way of programming - swinging by file rather than midi.

Antonym, the gap is fairly small but it could be smaller, not sure if I like the idea of the attack being added without giveing me an option to disable it (althought I'm, not convinced thats what happening because when you zoom in on the display it doesn't look like an artificial attack has been put in there).

The rest of you post has some nice info in, cool ideas, thanks

chop samples manually, doesnt take that long, and much more room to work wid. i never used to do this cuz i jus used to rock chopshop All the time, by far the easiest option, but not always the best sounding/feelin

yeah i very rarely use autochop and i NEVER use it without fixing up the start/end points.

as for the attack thing, it didn't really look like an attack in the 1000 either, but it was there. definitely not audible, it was just to make sure there was a zero crosspoint. i didn't like the idea either.

For the record the autochop NEVER chopped the samples the way I wanted it to. I've always had to do it manually, but was always happy with the results.

neveR? not even with a nice, predictable break? i know it's not the same code but same principle in jj os and it works pretty good every now and then

Antonym wrote:neveR? not even with a nice, predictable break? i know it's not the same code but same principle in jj os and it works pretty good every now and then

Close, but it never really gets it as tight as I'd like it. But like I earlier mentioned, it's just my personal preference, it may be adequate enough for other people.

Antonym wrote:neveR? not even with a nice, predictable break? i know it's not the same code but same principle in jj os and it works pretty good every now and then

Close, but it never really gets it as tight as I'd like it. But like I earlier mentioned, it's just my personal preference, it may be adequate enough for other people.

yeah. i honestly think that 9 times out of 10, it takes less time to do it manually using divisions or 1/10 chops. i'm at the point where i feel like i can chop much quicker than in recycle (including file moving/loading) in my mpc just cuz i've done it so many times....

I know auto chop is very unlikely to get it exactly how you want but I find it's normally a good place to start, you just hit auto chop then fix up the start/end points. However, I still think they probably could've got it a bit more accurate.

me i use that all the time now i jus move it in the right place its always early or late sometimes its fine but i could be wrong aint sampled in a min wait to get a hard drive and 128 or should i say 256mb