MPC1000 OS2XL Ver2.10 10-FEB-2011

I retracted my last statement, just not before you replied. wasn't thinking clearly. IF there was a 'Loop until release' setting for the loop this would work. It is a common setting on many samplers. This way, The sample loops as long as you hold a pad/key and plays out post loop after you release. Wouldn't work with the current implementation of xfade loops as it would need to put a xfade from the loop to the post loop as well. As it is, when you enable or commit an xfade loop, anything after the loops sounds out of place as the sample has been changed to much.

patchen wrote:I retracted my last statement, just not before you replied. wasn't thinking clearly. IF there was a 'Loop until release' setting for the loop this would work. It is a common setting on many samplers. This way, The sample loops as long as you hold a pad/key and plays out post loop after you release. Wouldn't work with the current implementation of xfade loops as it would need to put a xfade from the loop to the post loop as well. As it is, when you enable or commit an xfade loop, anything after the loops sounds out of place as the sample has been changed to much.

Deleted last part of what u wrote

Yeah, traditionally sustain loops are the norm. I just checked and yes, there is a click after the 'commited' x-fade loop when you turn loop off.

Yeah figured if I caught my mistake soon enough....
Perhaps a "loop until release" mode is in order for a feature request. That will give you exactly the functionality you are looking for.

BTW, just playing around and using the x-fade commit function can be really cool if you use it recursively. You can get really cool long sustaining samples from short choppy ones if you apply the x-fade over and over again. Just keep moving the start point to the left to increase the size of the loop each time. Sound very similar to Wavelab's 'loop tone equalizer' or even Infinity (the program Korg uses to process all of their looping sounds)

Can be really cool for certain sounds if you are experimentally minded....

Coz wrote:I still wish he'd enable your currently loaded project to be the default location when saving.

If you've been navigating through a bunch of nested folders on your hard drive for samples, then hit save at the end of your session, it takes you back to that nested samples folder. You then have to hit load and navigate back to your project folder (sometimes 20 button presses!) and then press save again... Why??!

It's also too easy to mess up and accidentally hit 'do it' (in load) instead of switching to save... I know because I did it last night and lost several hours work!!!

You can navigate to your folder in save mode. you don't have to switch to load mode to navigate folders.

patchen wrote:Yeah figured if I caught my mistake soon enough....
Perhaps a "loop until release" mode is in order for a feature request. That will give you exactly the functionality you are looking for.

BTW, just playing around and using the x-fade commit function can be really cool if you use it recursively. You can get really cool long sustaining samples from short choppy ones if you apply the x-fade over and over again. Just keep moving the start point to the left to increase the size of the loop each time. Sound very similar to Wavelab's 'loop tone equalizer' or even Infinity (the program Korg uses to process all of their looping sounds)

Can be really cool for certain sounds if you are experimentally minded....

That's a great idea actually! Maybe it will give similar results to the ASR-10's Synthesize Loop function, you can make a loop out of anything with that.

wow, nice. there are NO CLICKS when retuning converted xfade loops. this is excellent. polyphony headroom!

also patchen, excellent tip regarding recursive loop conversion to get a longer sample, i tried this and it worked wonderfully.

mp3 wrote:

Coz wrote:I still wish he'd enable your currently loaded project to be the default location when saving.

If you've been navigating through a bunch of nested folders on your hard drive for samples, then hit save at the end of your session, it takes you back to that nested samples folder. You then have to hit load and navigate back to your project folder (sometimes 20 button presses!) and then press save again... Why??!

It's also too easy to mess up and accidentally hit 'do it' (in load) instead of switching to save... I know because I did it last night and lost several hours work!!!

You can navigate to your folder in save mode. you don't have to switch to load mode to navigate folders.

Ok, major schoolboy error on my part ... Although in my defense, the manual makes no mention of backing out of nested folders using the ^ cursor.

My point still stands about the current way of saving being convoluted though.

jimmie wrote:One thing I'd really, really like is to be able to use the loop as only the sustain portion of your amp env, then when you release the pad the sample doesn't loop anymore but plays to the end.

major cosign on this! i'm pretty sure JJ could make this happen.

NO CLICKS when retuning converted xfade loops. this is excellent.

Yeah quite impressive. I've just tried it and I could do my own sub-bass with a sine wave easily inside the MPC

seems really cool!! - but not had chance to try it.

it begs the question though - if the xfade to normal loops dont click when the pitch changes, why do normal loops click on pitch change? and why do pefect loops on the computer click when you import them to the mpc?
I messed around trying to make some intsruments using an EMU sample library using jj's automated thing in inst pgm but it was pointless cause there were clicks all over the place.

mikolo wrote:seems really cool!! - but not had chance to try it.

it begs the question though - if the xfade to normal loops dont click when the pitch changes, why do normal loops click on pitch change? and why do pefect loops on the computer click when you import them to the mpc?
I messed around trying to make some intsruments using an EMU sample library using jj's automated thing in inst pgm but it was pointless cause there were clicks all over the place.

The reason the MPC (and many other samplers besides) click when perfect loops are imported from the computer has to do with the different way in which samplers interpret the end point of a loop. As I remember, some samplers read the end point as part of the loop, others read to the end point. This is a common problem when moving samples between formats and is the reason why samplers like Kontakt have a built in function to move the end point one sample to the left or right.

Sooo, to fix imported loops on the MPC, just zoom in close and move the end marker ONE sample to the left or right. One of these should fix the problem.


Now, clicking loops created on the MPC are a different issue entirely, and I must admit I'm confused by them. Most of the time it's click, click, no click, no click, click, click. It clicks sometimes, but not all the time. At some pitch transpositions but not all.... It's weird. It seems to me that in these cases it is not truly a perfect loop and should be clicking all the time but perhaps some quirk of the MPCs pitch resampling engine causes the click to be 'smoothed over' on occasion.

It's a pain because it makes it pretty much impossible to find a perfect loop because the loop does not always click when it should. I imagine if there was a simple fix for this JJ would not have gone to all the trouble of creating his fancy x-fade algorithm....

^ thanks for the clarification.
+1 on unlinking loop end/end of sample so that upon NOTE OFF the rest of the sample plays to the end + release.
i'm sure there's a more concise way of putting this
if anyone knows the technical term for this behavior please tell

also ^ this is all linked in functionality to the awesomeness that is an interpretation of AHDSR that someone came up with in another thread, where DURATION could be specified per pad, ie when you hit a pad, if it's specified to have 48 ticks of duration, that value is automatically entered into the sequencer. this is waaaaay better than having HOLD in your envelope because this way it can be edited after the fact

Nym wrote:^ thanks for the clarification.
+1 on unlinking loop end/end of sample so that upon NOTE OFF the rest of the sample plays to the end + release.
i'm sure there's a more concise way of putting this
if anyone knows the technical term for this behavior please tell...

It is simply called 'loop until release' in most samplers. So, a list of play modes for a common sampler might be; 'Play once', 'Loop until end' and 'Loop until release' (or key up)

Another cool trick, (which is the what I deleted from my earlier post) is to create a release sample that only plays after you release a key/pad by inserting a small bit of silence into the beginning of the sample and having the loop set to this area. If play mode is set to 'loop until release' it will loop this silence until you release the note, then it will play out to the end (if your envelopes are set with a long release time that is).

has this 'loop until release' mode been added to the feature requests yet? If not we should all chime in...

Nym wrote:also ^ this is all linked in functionality to the awesomeness that is an interpretation of AHDSR that someone came up with in another thread, where DURATION could be specified per pad, ie when you hit a pad, if it's specified to have 48 ticks of duration, that value is automatically entered into the sequencer. this is waaaaay better than having HOLD in your envelope because this way it can be edited after the fact

Maybe you are thinking of doing something different, but I usually just go to the sequence edit page and use the DURATION > SET TO VALUE command to get this effect. Off topic, I LOVE the way you can edit note durations using the q-links in the grid edit page. Easier than editing in the DAW in my opinion....

'loop until release' feature request added...