MPC Renaissance Video Compilation Thread!

xparis001 wrote:

b-righteous wrote:Good one.

So will this also work after slicing? Another words, does slice create a new sample restricted to the slice region(truncated) or can you expand the regions to the original sample? Both ways have an advantage but just trying to see.

it copies the pad parameters, but uses the same samples. you can, however, extract individual slices directly to pads, and decide if you want it destructive, or non-destructive. nondestructive, you can adjust the start / end after the fact, but it takes more ram.

This is real nice!!! PROPS

Some questions doh...

I can understand that non-destructive will take more ram than to truncate every slice. But if it only copies the parameters. and not the sample, why does it take more ram? its still just one sample file with diffent start and end points right? u have this in the ASR10 like u probably know. and how much ram does that have compared to a computer? just confuesd

Luigi wrote:

xparis001 wrote:

b-righteous wrote:Good one.

So will this also work after slicing? Another words, does slice create a new sample restricted to the slice region(truncated) or can you expand the regions to the original sample? Both ways have an advantage but just trying to see.

it copies the pad parameters, but uses the same samples. you can, however, extract individual slices directly to pads, and decide if you want it destructive, or non-destructive. nondestructive, you can adjust the start / end after the fact, but it takes more ram.

This is real nice!!! PROPS

Some questions doh...

I can understand that non-destructive will take more ram than to truncate every slice. But if it only copies the parameters. and not the sample, why does it take more ram? its still just one sample file with diffent start and end points right? u have this in the ASR10 like u probably know. and how much ram does that have compared to a computer? just confuesd

copy pad copies the parameters of the pad and uses the same sample.

when you chop a sample non-destructively, you get multiple copies of the same sample.

I was talking about two different functions.

copy pad copies the parameters of the pad and uses the same sample.

is this like filter, pan, velocity etc? or the sample start and end point?

when you chop a sample non-destructively, you get multiple copies of the same sample.

I know nothing about programing but whuldent it be less power consuming having just one sample, but using multiple and diffrent start and end points, instead of 16 samples of the same thing?

Luigi wrote:

copy pad copies the parameters of the pad and uses the same sample.

is this like filter, pan, velocity etc? or the sample start and end point?

when you chop a sample non-destructively, you get multiple copies of the same sample.

I know nothing about programing but whuldent it be less power consuming having just one sample, but using multiple and diffrent start and end points, instead of 16 samples of the same thing?

1. yes, exactly

2. multiple start / end points dont work if you want to, say, normalize one part, pitch it down, do a fade out, or whatever. this way, if you want to edit the sample of just one pad, you can.

Makes sense. Great you guys are offering different approaches.

It looks like the current system applies destructive edits to the original sample so chopping needs to create new samples so each chop can be edited separate without affecting others.

Another way to do it, is just have sample start end offsets for chopping and make destructive edits always create a new sample.

Either way, with most systems at least 4 GB of RAM these days, A couple dozen audio files won't be a big issue.

@xparis001

Ok makes sense! thx.

Not a Ren vid, but a vid of the new Max49. Would be nice if this thing could be used as a controller for VMPC!:

DJ Hellfire wrote:Not a Ren vid, but a vid of the new Max49. Would be nice if this thing could be used as a controller for VMPC!:

I'm on the right! God I wanted to take that prophet home. It belongs to our QA Assistant Manager. He wont sell it. :/

I bet that thing has some CRAZY bass sounds! I heard you sweep through some for about a second!

DJ Hellfire wrote:I bet that thing has some CRAZY bass sounds! I heard you sweep through some for about a second!

Believe it or not, the Pro One's bass is even more awesome. I want to do a max49 video with it, but its a matter of finding time.

Andy wrote:So if I want to do timestretch...which....nobody else has within their controllers...in an MPC environment. So this is one feature that every user needs. And anybody that can't support this type of feature is really going to run into a lot of problems.

Taking them not so subtle jabs at NI for not having timestretching on Maschine. NI said two years ago they will add real-time time stretching to Maschine in an update.

Sounds like fighting words.

jpeg wrote:

Great video , but once again im always noticiing when in the sample edit mode when andy cuts the loop ect... He uses the qlinks and not the jog wheel. It looks like the jog wheel is only for scrolling and navigating threw differnt things on the os. I could be wrong thou..
Hey XParis r we gonna be able to play say our timestrentched sample up and down the keyoard in diffrent pitches?

ddanielsbeats wrote: Great video , but once again im always noticiing when in the sample edit mode when andy cuts the loop ect... He uses the qlinks and not the jog wheel. It looks like the jog wheel is only for scrolling and navigating threw differnt things on the os. I could be wrong thou..

If its like the MPC 5000, then using the Qlinks or Jog/data wheel should be able to edit a sample...

ddanielsbeats wrote:

jpeg wrote:

Great video , but once again im always noticiing when in the sample edit mode when andy cuts the loop ect... He uses the qlinks and not the jog wheel. It looks like the jog wheel is only for scrolling and navigating threw differnt things on the os. I could be wrong thou..
Hey XParis r we gonna be able to play say our timestrentched sample up and down the keyoard in diffrent pitches?

It's because the q-links are faster due to the smaller turning radius of the knobs. I'm sure it's much more efficient than the data wheel!