Pete/Dan: CHOP SHOP improvements for v1.4

Dan/Pete,

for me personally these two are really BIG:

please consider the following improvements to the CHOP SHOP:

1) Re-Chop button, located between Chop and Trim

Function:

Allow to Re-Chop a previously created region:

I would like to chop a sample by region first, i.e. take a 32 bar sample and slice it into 4 regions. Then select first region by pressing the relevant pad, hit re-chop, and re-chop it by transients. Go to the next original region and re-chop it by lets say BPM.-- and so on and so forth....

The result should all be mapped to 1 program, when done I woud convert the program. re-chop should work on any already existing region, it basically treats the selected region as a sample but does not disregard other regions in the sample. In theory i should be able to Re-Chop until all my pads are filled up.

2) Loop in chop mode

in Chop to Region mode, allow the region to be looped, so when i hit the play it loops that region rather than just playing to end of sample, maybe using a modifier key such a shift and mpc pad

e9000k wrote:2) Loop in chop mode

in Chop to Region mode, allow the region to be looped, maybe using a modifier key such a shift: so when i hit the play it loops that region rather than just playing to end of sample

I like this one.

JAH wrote:

e9000k wrote:2) Loop in chop mode

in Chop to Region mode, allow the region to be looped, maybe using a modifier key such a shift: so when i hit the play it loops that region rather than just playing to end of sample

I like this one.

you are fast lol

updated my demo and this update is big! The chop shop is not there yet, we had a convo around re-chop before you may recall. Can you see why I need that re-chop button, or do i need to explain it again to make it more clear?

e9000k wrote:

JAH wrote:

e9000k wrote:2) Loop in chop mode

in Chop to Region mode, allow the region to be looped, maybe using a modifier key such a shift: so when i hit the play it loops that region rather than just playing to end of sample

I like this one.

you are fast lol

updated my demo and this update is big! The chop shop is not there yet, we had a convo around re-chop before you may recall. Can you see why I need that re-chop button, or do i need to explain it again to make it more clear?

Sample Edit/Sample Record are the most import modes for me. There are quite a few functions that I would like to see added. I wrote an entire thread about it.

However, I have a new MPC Forum resolution. I will only comment on things I really like to avoid some of the back-n-forth between Ren users that has been going on. I respect everyone's feature requests whether or not I agree or have a need for it.

Agreed, hope they keep working on it. I really hope they continue updating at this pace, if so we will see 1.4 in april...

JAH wrote:

e9000k wrote:2) Loop in chop mode

in Chop to Region mode, allow the region to be looped, maybe using a modifier key such a shift: so when i hit the play it loops that region rather than just playing to end of sample

I like this one.

I like this one too

e9000k wrote:2) Loop in chop mode

in Chop to Region mode, allow the region to be looped, maybe using a modifier key such a shift: so when i hit the play it loops that region rather than just playing to end of sample

It'd cool if it allowed the region to be reversed play if it dont already

peteblues wrote:

JAH wrote:

e9000k wrote:2) Loop in chop mode

in Chop to Region mode, allow the region to be looped, maybe using a modifier key such a shift: so when i hit the play it loops that region rather than just playing to end of sample

I like this one.

I like this one too

does that mean, we could possibly see this in 1.4? what about any incremental updates like 1.3.1...etc? like take some of the issues with 1.3 and make minor adjustments to the code and send that back out. by the time we get to 1.4, there wouldn't be that much of a delay.

sparq wrote:
does that mean, we could possibly see this in 1.4? what about any incremental updates like 1.3.1...etc? like take some of the issues with 1.3 and make minor adjustments to the code and send that back out. by the time we get to 1.4, there wouldn't be that much of a delay.

unlikely for 1.4. It's a matter of setting priorities. We'll see. Can't make any promises.

peteblues wrote:

sparq wrote:
does that mean, we could possibly see this in 1.4? what about any incremental updates like 1.3.1...etc? like take some of the issues with 1.3 and make minor adjustments to the code and send that back out. by the time we get to 1.4, there wouldn't be that much of a delay.

unlikely for 1.4. It's a matter of setting priorities. We'll see. Can't make any promises.

Pete, please, please put the re-chop feature forward, on the 5000 you can chop, divide equally by lets say into 8 regions, then select region and hit Edit and divide again.... I still don't understand why the chop shop functionality was not matched.

JJOS does this:

http://www.youtube.com/watch?feature=pl ... K3sfXO6ySY

Make it 1.5 but please include it, the chop shop was only in 1.3 improved before it wasn't even a chop shop. Please send it forward to Dan and just get it sorted for us.

The loop one i suggested is a no brainer.. must have

peteblues wrote:

sparq wrote:
does that mean, we could possibly see this in 1.4? what about any incremental updates like 1.3.1...etc? like take some of the issues with 1.3 and make minor adjustments to the code and send that back out. by the time we get to 1.4, there wouldn't be that much of a delay.

unlikely for 1.4. It's a matter of setting priorities. We'll see. Can't make any promises.

I promise to send you a bar of the finest Finnish chocolate if you can make the pingpong/alternate loop happen.
This is a promise. Just give me your address.

Pete, careful with your adress, people will run up in your place and hold you ransom for some mpc soft features

If we are going for feature request then Pete please implement Non destructive chop exactly like machine.
Picture
You have a Drum sample program with three different sample set to oneshot.
Let say for example stringloop1 , stringloop2 and stringloop3

Whilst composing you make the musical decision that you would like to have another pad with stringloop1 on but this time starting from the third musical event.

On maschine I hold down duplicate and tap the pad with stringloop1 on and then any free pad I press sampling and simply move the start point to the third musical event easy. I can do this in seconds and this doesn't interrupt the creative flow. As everything is non destructive and the implementation is so fast these decisions can be made on a whim, this is good.

With the MPC Ren when you are working in an existing program that already contains multiple samples this requires the extra set of duplicating the sample each time. It starts to add up to quite alot of extra button presses and menu navigation when you are adjusting start end points of multiple samples with multiple copies within a REN program.

Please implement something where by the default behaviour for the Ren is NON destructive chopping i.e. I am only prompted to make a destructive chop if I am applying a destructive operation such as normalisation.

I would like to be able to duplicate a pad and then simply go to sample edit and set the start point without affecting any other pad. Why would the normal mode of operation be that if you change the start point of one pad it changes the other pad too. I can think of almost no situation where this behaviour is desirable. I wish this was behaviour was removed from all MPC's forever as it has always been the slowest way of accomplishing this type of editing.

Also why is reversing a sample a destructive operation? When you are just reading the sample from the end point back to the start point.

Note length quantisation would also be a significant enhancement.

Those three are bread and butter requests for me.

Good job on 1.3 its significantly better than 1.2 and I can compose on the Ren now.
Geoff

Fanu wrote:

peteblues wrote:

sparq wrote:
does that mean, we could possibly see this in 1.4? what about any incremental updates like 1.3.1...etc? like take some of the issues with 1.3 and make minor adjustments to the code and send that back out. by the time we get to 1.4, there wouldn't be that much of a delay.

unlikely for 1.4. It's a matter of setting priorities. We'll see. Can't make any promises.

I promise to send you a bar of the finest Finnish chocolate if you can make the pingpong/alternate loop happen.
This is a promise. Just give me your address.

Nice! How did you know I take chocolate bribes?

pete, we need to be able to select (current, multiple, all) pads from the hardware, not just software! Def need this in 1.4