auto chop on mpc 2000 classic

http://www.youtube.com/watch?v=QFXVl4BW ... annel_page

hey guys i watched this and tried everything step for step but still i get the whole sample on every pad not the 'chops' that it says u get ...yes i made it mono and then i tried note off (didnt have it on poly) I have gone through the process four times and turned it off in between everytime still...no dice..please help as i really wanna get this shit working

The key ingredient here is the 16 levels key.

You need to have full level off, and 16 levels on, set to velocity.

Then, as he showed, you have Velocity->Start set at 100.

My guess is you are either skipping the 16 levels part, or you have 'full level' on.

turned it off in between everytime

Totally unnecessary ;]

Good luck.

^^^^

Tons of ways to chop. Just a couple of things I like to do w/ the 2KXL is use the Q-link slider to select arbitrary points points of your loop. Gives you a real feel of how your chops and you never know what you'll here.

The video he is referring to is about the 16 levels function with Velocity assigned to Start.

Sure everybody does it different, but the OP was asking about this particular way.

Zn edit with a calculator sometimes.

nogginj wrote:The key ingredient here is the 16 levels key.

You need to have full level off, and 16 levels on, set to velocity.

Then, as he showed, you have Velocity->Start set at 100.

My guess is you are either skipping the 16 levels part, or you have 'full level' on.

turned it off in between everytime

Totally unnecessary ;]

Good luck.

hey mate, thanks for the reply. I have done everything in the video just as he did. I actually came home on lunch today and checked again to make sure I was doing it right. In respect to the full level/16 levels, I did it right with the full levels off then pressing '16 levels' on and making velocity the option, this is why I am confused because he says in the video 'do it this way and it'll work' but i have tried and cannot figure it out. If for whatever reason i cannot do it his way is there in fact another way to 'auto chop' the sample over the pads as i am finding cutting down a single sample quite a long process. I just want dilla chops lol

I don't know, but it's not like feature is going to 'broken' on you mpc. If you do it correctly, it has to work.

Maybe you are not making the setting on the correct pad?

Maybe your sample is too long / not long enough?

Are you sure you are in the right bank before you hit the 16 levels? After? (Not sure if that makes a difference).

Does your velocity work at all?

You have to be sure that Velocity->Level is at 0, and Velocity->Start is at 100 (he does not actually show that step).

I have done everything in the video just as he did.

If you do that it won't work cause he doesn't show that step ;]...it's already set in his vid.

Also, do you have your sample properly trimmed in the TRIM page? Does the original start happen at a useful spot (no silence)? Is there a ton of silence at the end of the sample? Trim off ALL the silence! That could be having an effect.

Just be super careful when doing this and pay attention to what you are doing so you dont maybe accidentally hit another pad.
Hit the pad with the sample on it the whole time so you can hear the changes.
Hit the pad...did you hear the sample start at the beginning? (NO SILENCE).
Turn OFF full level.
Hit the pad (keep tapping it...you should still be hearing the sample from the beginning).
Go into PGM edit (keep tapping the pad, make sure it's the correct pad).
Hit OPEN WINDOW on the attack or decay param (keep tapping that pad...just so you know you are affecting the proper sample...is your sample responding to velocity...getting quieter with softer taps?).
Now set Velocity->Level = 0 (keep tapping that pad...it should now be 'full volume' no matter how hard you hit it)
Now set Velocity->Start = 100 (as you tap lighter / harder now, you should hear the sample start from different points...the harder you hit the EARLIER the sample starts...if you hit it real hard, it should start from the beginning).

That's how you do it.

Those steps might seem a bit excessive but there's obviously some part of it you are missing, so do them all. I am saying to keep tapping it over and over so you can hear the changes as they take place.

is there in fact another way to 'auto chop' the sample over the pads as i am finding cutting down a single sample quite a long process

Not that I know of on a classic (some people made suggestions above). But get used to doing the sample cutting, it's work you just have to do. Also, keep in mind that this 'auto-chop' way of using the velocity -> start is not always going to give you the chops you want...I don't know the intricacies of how it works, but it's not really an 'autochop'...it's just a clever hack of a function that was meant for something else, and it's not very tweakable...you basically set it to the different, static, values, and either take what it gives you or try a different setting.

If you get it work, here is an xtra info:

prepare your sample so it is 5 seconds. this will spread the whole sample over the 127 steps. It doesnt matter how long it is after pitch it inside the MPC but after sampling and trim it should be 5 seconds (original tune).

If it is shorter than 5 seconds, the resolution will be not as fine as with 5 seconds. it wont be spread over 127 steps but ...lets say 100 steps or less (depends on the length of the sample). some pads will be empty then.

If its longer than 5 seconds you wont be able to have a pad that really play the end of the sample (the longer the sample the longer the samplepart of pad 16 will be)

If a pad doesnt hit exactly where you want it (for example: left a bit of the attack on a snare) use step edit and edit the velocity value till you like it. Also the step edit is the place to go when the sample is something that is time related (like a drumloop).

Still. I dont find this technique very useful or rather say its not a very pleasing workflow IMO.

peace

peterpiper you wonderful man, I've always wondered what the 'magic' number was for length of samples vs velocity->start offset.

Have you tested that 5 second thing, or found it somewhere, or is this from experience?

So it's true then, the start offset is an absolute value, irregardless of the sample length?

Makes me wonder how sample-tune affects this...is it strictly tied to global 'time' in some way, or is it tied to number of samples (which might vary, I imagine, with tune setting, depending on where they do offset calculations vs resample calculations)

I tried this by myself when I saw that the samplestart could be modulated by velocity but I didnt find it useful enough to integrate in my workflow.
The post above was written just from memories without testing it again but by reading your last post I thought I should try it right now. So....

I cant explain what exactly is goin on in this machine (its a bit confusing ) but here are some infos.

I just found out that you dont need to actually trim the sample to 5 sec BUT

1. The startpoint that you set in trim settings is always represented by the velocity value(s) 127-124 or 123 (dont aks me why there is no change on these values )

2. The velocity value 1 represent a samplestart 5 seconds after the startpoint setting (TRIM SCREEN) Tuning settings inside the MPC have no influence on that.

3. the steps in velocity value doesnt represent linear steps in time. I dont know the reason for that but if the steps would have the same size in time 2,5 seconds would mean a value around 63 (half of the time should mean half of the velocity value) In my test the 2,5 seconds mark was at 39 or 38.

4. If the sample is longer than 5 seconds the velocity value 1 will still play from that 5 seconds till the end of the sample.

5. If you have a sample shorter than 5 seconds it wont fill up all 127 steps. You can sample it slower to increase the "velocity-value-to-sample-start- resolution". Hint: 5 seconds

And here are some values

The velocity values of the 16 Level functions and the time that it represents are:

Pad01 -> 007 -> 4,513
Pad02 -> 015 -> 3,872
Pad03 -> 025 -> 3,281
Pad04 -> 031 -> 2,888
Pad05 -> 039 -> 2,450
Pad06 -> 047 -> 1,985
Pad07 -> 055 -> 1,625
Pad08 -> 063 -> 1,301
Pad09 -> 071 -> 0,968
Pad10 -> 079 -> 0,722
Pad11 -> 087 -> 0.512
Pad12 -> 095 -> 0,313
Pad13 -> 103 -> 0,181
Pad14 -> 111 -> 0,085
Pad15 -> 119 -> 0,025
Pad16 -> 127 -> 0,000

I'm sorry for the english. When it goes too deep in technical stuff I have a hard time to find the right words.


Just another though I just had:

Using a MIDI keyboard (most of us have 61 or maybe 76 keys) to get direct access to 61 or 76 velocity values. Of course you'll need to transform note number to a velocity value but with the help of cubase input transformer it should be no problem Lucky are those of us that have a full piano keyboard (88 keys)

peace

peterpiper wrote:The velocity values of the 16 Level functions and the time that it represents are:

Pad01 -> 007 -> 4,513
Pad02 -> 015 -> 3,872
Pad03 -> 025 -> 3,281
Pad04 -> 031 -> 2,888
Pad05 -> 039 -> 2,450
Pad06 -> 047 -> 1,985
Pad07 -> 055 -> 1,625
Pad08 -> 063 -> 1,301
Pad09 -> 071 -> 0,968
Pad10 -> 079 -> 0,722
Pad11 -> 087 -> 0.512
Pad12 -> 095 -> 0,313
Pad13 -> 103 -> 0,181
Pad14 -> 111 -> 0,085
Pad15 -> 119 -> 0,025
Pad16 -> 127 -> 0,000

Amazing work. This is something I've always wanted to know, but was complicating things thinking I'd be analysing sine sweeps, etc.

Thank you for this.

And ps...your english is great...better than most native speakers around here.

hey it's nice seeing this on paper... that is the easiest way to explain what that technique is actually doing.

peterpiper wrote:If you get it work, here is an xtra info:

prepare your sample so it is 5 seconds. this will spread the whole sample over the 127 steps. It doesnt matter how long it is after pitch it inside the MPC but after sampling and trim it should be 5 seconds (original tune).

If it is shorter than 5 seconds, the resolution will be not as fine as with 5 seconds. it wont be spread over 127 steps but ...lets say 100 steps or less (depends on the length of the sample). some pads will be empty then.

If its longer than 5 seconds you wont be able to have a pad that really play the end of the sample (the longer the sample the longer the samplepart of pad 16 will be)

If a pad doesnt hit exactly where you want it (for example: left a bit of the attack on a snare) use step edit and edit the velocity value till you like it. Also the step edit is the place to go when the sample is something that is time related (like a drumloop).

Still. I dont find this technique very useful or rather say its not a very pleasing workflow IMO.

peace

here are some interesting informations
thanks a lot
the technique is not very useful, but the trick is fine

its weird its like it kinda half worked, i now have some short chops and some longer ones that can be cut off by the shorter ones..not exactly how it worked for him but it worked for me and so far i am very happy with the results..thanks to all involved who helped me get this shit, cheers