slice mode sample overlaps

so in my research of the 2kxl, i have found that when you chop sample in it, it takes a few samples from the part before or after to make up for an attack or decay setting like the 1k has when you export your chops.

can you turn this off? or are all your chops gonna sound not exactly the way you chopped them on the waveform view?

say i sampled kick into the 2kxl from an external source, would it add a couple miliseconds of silence before the chop that i made, thus rendering the kick a little bit off when played?

also one more question, regaurding mute groups, i understand that the og 2000 didnt really have them, but had something similar that could mute up to 2 other pads, did the 2000xl have them put in?
can i assign my samples--say i have 48 of them--to the pads, then set all of those to mute group one, and when i play any pad, it will cut any other pad in that program off?

thanks

damien907 wrote:so in my research of the 2kxl, i have found that when you chop sample in it, it takes a few samples from the part before or after to make up for an attack or decay setting like the 1k has when you export your chops.

can you turn this off? or are all your chops gonna sound not exactly the way you chopped them on the waveform view?

Are you talking about pre-rec in the record screen? You can set that to be whatever you want. The default is 100ms. You can also set the MPC to auto-rec at a certain vol level. You must still set the pre-rec value to zero though.

If you are talking about the decay value, you can just set that to zero for any sample in program mode as well. Now when you are in program mode/main screen, the sample will play as it sounds in trim mode.

You almost always have to truncate your sample, Ive been living with this "problem" for 12 years now, lol. A perfectly chopped and trimmed sample is much easier to achieve with an SP303/404. MPC's usually take some work to tailor the sample, the record function isnt as exacting, but it is more robust.

Lamp dropping knowledge, get to reading, lol. Damn lamp.....back to giving out page #'s. I missed those days ,

@ lamp
from the 2000xl manual
"While either note set in the Note: field in the lower half of the display is generated, the note is
muted when a note displayed in the upper half of the display is generated. This is convenient
when you want to stop the sound of an open hi-hat with a closed hi-hat.
To turn this function off, select the Mutes off: Note: field and select --/OFF by
rotating the DATA wheel to the left."

does this mean that you can only mute out one other pad instead of have any pad mute any other pad.
so i could set pad a1 to mute pad a2, but then pad a1 couldent ever mute pad a3 through d16?

@ jonestown i think what im talking about refers to the trim screen (mode +pad 5.)

from what i understand, if you go to a zero crossing, it will add a few extra samples before or after your chop point, so it pretty much negates your zero crossings.

someone on a different thread said this (dont remember which one) and also tutor says it in his mpc 1000 vs mpc 2000xl comparison.

he says this reffering to the improved slicing of the 1k.

#19. Improved slicing feature - now you can add a timestretched decay on the end of each chop (like recycle) rather than the old XL method which just 'borrowed' a few samples from the slice in front of it (leading to clicks). You can also chop up to 64 slices.

have you used a 1k with jjos? i would say that i can get accurate chops according to the zero crossings on it, is this gonna be near impossible on the 2kxl? or can yo make it so it doesnt "borrow a few samples from the previous slice."

thanks

The trim mode does not add samples, afaik. I use trim mode, loop, zone, etc. to chop loops at zero crossings all the time, no issues. Just set the decay value to zero in the program mode.

As far as what the manual says, You can have one pad mute 2 other pads.

ah cool, thanks for clearin that up.

In "Slice sound" the mpc2000xl will add extra ' borrowed ' samples. If you don't want it to do that, just set the END MARGIN to 0



In MUTE ASSIGN . Any pad can be set to mute up to two other pads. But any number of pads can be set to mute any two others.
This was really only designed to mute open and partially open hi hats, hence the limited practicality.

ah cool, ok, thats good enough then, that is kinda wack it doesnt have full mute groups though.

damien907 wrote:ah cool, ok, thats good enough then, that is kinda wack it doesnt have full mute groups though.

yeah, it sucks .. but at least it doesn't prevent you from doing what you need to do...

it's still cool though because you can have pad 1 mute pad 2... without having pad 2 mute pad 1... this sometimes is nice to have. You can set up the blank pads trick to take care of further muting. Also, coming from older models... it's sweet not HAVING to rely on note off to cut samples short.... or on the 60... it doesn't have shit on the older OS as far as note off, or mutes of any kind so you have no choice but to trim exactly... (not that you have bucket loads of ram to spare anyhow... you would be trimming every millisecond off a sample anyways)

ah, that just opened my eyes, thanks debauch. so in essence it could behave at least similar my 1k, if i just set them all to mute to 1 silent pad. thats awesome.

damien907 wrote:ah, that just opened my eyes, thanks debauch. so in essence it could behave at least similar my 1k, if i just set them all to mute to 1 silent pad. thats awesome.

well.. you could go to the D bank and assign a sample you already have like a high hat to D pad 1 (D1) .. I suggest you pitch it up to the max and put the filter to 0 so you cant hear it anymore...

make pad D1 mute pads A1 and A2 (or what ever...) then do the same by making D2 mute A3 and A4.. assign a simulti on D1 so when pressed it always triggers D2 as well...

or.. you can just figure the order you will bang in your sample pattern ... make each sample mute the one before it ..

I had this problem when using zone mode.

I had the margin set to high put it to 0 and the slices I cut exactly how measured them to be

mr_debauch wrote:. I suggest you pitch it up to the max and put the filter to 0 so you cant hear it anymore.....

This works but depending on the sample you can still have audible data, I personally just turn down the pads volume to 0 in the mixer. It's still behaves the same but generates no sound whatsoever.

m56p87 wrote:

mr_debauch wrote:. I suggest you pitch it up to the max and put the filter to 0 so you cant hear it anymore.....

This works but depending on the sample you can still have audible data, I personally just turn down the pads volume to 0 in the mixer. It's still behaves the same but generates no sound whatsoever.

yeah I do that too.. it's just that sometimes I have had issues with doing that (not every time).. it stopped doing the muting.. that may have been a bug

mr_debauch wrote:yeah I do that too.. it's just that sometimes I have had issues with doing that (not every time).. it stopped doing the muting.. that may have been a bug

Definitely sounds like a bug! Even if the volume is 0 the program still has a sound in it! Gotta love the personality of older hardware