NON DESTRUCTIVE CHOPPING.....PLEASE!!!!

all ensoniq samplers. eps. eps 16, asr...

oLsen wrote:question: is only the asr-x able to cut nondestructive or also the asr-10/asr-88?

i dunno if this is the same as what you mean but i would love to see the ability to be able to go back to your 16 ( or more ) chops to alter them at any point of time ( so you dont have to start all over again when you cut a slice too short )

Chulukinat wrote:i dunno if this is the same as what you mean but i would love to see the ability to be able to go back to your 16 ( or more ) chops to alter them at any point of time ( so you dont have to start all over again when you cut a slice too short )

roughly that is what non destructive editing would allow! you could always change the start points of each "chop" because the "chops" in this case wouldn't be seperate wave files, but instead each pad would specify a different start point for the ONE same original wav file.

this would be crazy, and it seems VERY possible for this to be implemented into the OS.

THE ADVERSARY wrote:The (asr)X has multiple levels of editing parameters one of the levels actually eidts PAD info so you adjust the Filter/Start/Stop/Loop/Tuning/MODs/ENV/FX routing etc per PAD instead of per sample.
So all 13 PADs per octave have their own set of parameters.
--------------
Not sure if JJ could effectively implemement something like this without creating a special mode for the MPC since it would effect things like the Sample layers, Simult pads and most of the settings in a Program

creating a special mode?? nah nah man. i mean, i guess that might be right if we needed it be EXACLY like the asr-x but no need for all that!

per pad we can already set tune/mod/env/fx/filter.
if we could just set the start point per pad i think that would be a HUGE change in alot of people's workflow.



damn i hope this happens...!

punchdrunk wrote:

THE ADVERSARY wrote:The (asr)X has multiple levels of editing parameters one of the levels actually eidts PAD info so you adjust the Filter/Start/Stop/Loop/Tuning/MODs/ENV/FX routing etc per PAD instead of per sample.
So all 13 PADs per octave have their own set of parameters.
--------------
Not sure if JJ could effectively implemement something like this without creating a special mode for the MPC since it would effect things like the Sample layers, Simult pads and most of the settings in a Program

creating a special mode?? nah nah man. i mean, i guess that might be right if we needed it be EXACLY like the asr-x but no need for all that!

per pad we can already set tune/mod/env/fx/filter.
if we could just set the start point per pad i think that would be a HUGE change in alot of people's workflow.

Yes it would because you would have to change the way too many of the standard MPC functions work and are associated.
It would be similar to how things change when you go into 16-Pads mode.

peezie wrote:all ensoniq samplers. eps. eps 16, asr...

oLsen wrote:question: is only the asr-x able to cut nondestructive or also the asr-10/asr-88?

The only difference was since the X was designed to compete with the MPC it was Pad/octave based which allowed them to make it more directly accessible.
They took what they were already doing with their sampler line of using reference to samples instead of heaving to copy them and built it into a more MPC style box.
Since pads and chopping go hand in hand it was a good look.
if you look at the ASR-x Pro V4 that never got released you can see they were going places with the X.
Too bad Ensoniq was a failing company by then and it never got released.

THE ADVERSARY wrote:Yes it would because you would have to change the way too many of the standard MPC functions work and are associated.
It would be similar to how things change when you go into 16-Pads mode.

can you explain why that would be? i don't think i'm completely understanding you.
why would the behavior act like 16 levels??? are you maybe talking
about changing the start point through something like velocity start?
please explain.

right now i can set Q1 (note on) to alter the start point of all pads on a track.
it works fine.
but instead of using the slider to control the q1 value i'd like to be able to specify that q1 value for each pad as they are hit.

this seems very possible to me unless i am missing something (which is very possible).

punchdrunk wrote:i've postd this before and i've seen other people ask for it too...

IT WOULD BE ILL if you could set different start and end points for each pad!!
since q-links can control start and end points already it would just be
a matter of setting up the pads to input those values.

NON DESTRUCTIVE CHOPPING ON THE 1000 WOULD BE CRAZY!!!
the possibilities and freedom with this would be unbelieveable,
not to mention the memory and disk space you would save...
imagine having ONE WAV of a break and and having all the pads play different
parts of the break that you could readdjust as you wanted, filters, fx, etc...
ALL OFF THAT SAME ONE WAV file.

this would be so dope to have!
anyone else interested in this???
reply or request this....PLEASE!

i support the dream homeboy lets do this

Where do you contact JJ?.....so i can put in my request for this also. Do i just put it in the bug reports?

SELFISH1 wrote:Where do you contact JJ?.....so i can put in my request for this also. Do i just put it in the bug reports?

i put my request in the report a bug page and it works. I suggest u do it like every hour or everyday.

punchdrunk wrote:


can you explain why that would be? i don't think i'm completely understanding you.
why would the behavior act like 16 levels??? are you maybe talking
about changing the start point through something like velocity start?
please explain.

right now i can set Q1 (note on) to alter the start point of all pads on a track.
it works fine.
but instead of using the slider to control the q1 value i'd like to be able to specify that q1 value for each pad as they are hit.

this seems very possible to me unless i am missing something (which is very possible).

First point would be to retain functional compatability, which if you notice JJ tries to do.
Second is because of the way the MPC associates pads and multiple programs.
You would need a mode to edit the pads info in and have it associated to a sequence other wise you would be openning a major doorway to bugs within your sequences.
You keep referring to the Q-links but they also require a mode to use.
The MPC from day one has always been designed to use modes for inputting certain types of data and this would just be another.
You have to go into TRIM now to edit these points (start/stop/loop) how is that not a special mode?

THE ADVERSARY wrote:You have to go into TRIM now to edit these points (start/stop/loop) how is that not a special mode?

why are you bringing up trim mode?
did you even read my last post?

i'm trying to edit the start point through editing a q link value.
the function (or mode) is already there and functioning.
qlink info is already linked to sequences.
i just want the ability to control the qlink value by pad.

if you want to call that another mode then maybe that is where
we are miscommunicating.
i imagine adding another mode to be like adding a huge brand new function.
what i am describing s more like adding another parameter to edit at the program level, rather than a WHOLE new function built from scratch.

punchdrunk wrote:

i'm trying to edit the start point through editing a q link value.
the function (or mode) is already there and functioning.
qlink info is already linked to sequences.
i just want the ability to control the qlink value by pad.

if you want to call that another mode then maybe that is where
we are miscommunicating.

Terminology is one problem but also for it to be really useful for non-destructive chopping a faster way of mapping the pads would be needed to make it useful for chopping.
Otherwise it ends up being more like a modulator for tweaking, if you getr what I'm saying.
So basically a screen that was like a Q-link/Program screen that allowed you to edit the pads is what I am seeing.

THE ADVERSARY wrote:Terminology is one problem but also for it to be really useful for non-destructive chopping a faster way of mapping the pads would be needed to make it useful for chopping.
Otherwise it ends up being more like a modulator for tweaking, if you getr what I'm saying.
So basically a screen that was like a Q-link/Program screen that allowed you to edit the pads is what I am seeing.

word. i see what you are saying.
if i could have it set up anyway then what you are saying would be dope. a seperate screen to edit start and end points etc...but i figured that would be too much code and unrealistic for jj to add.

the way i was describing it was more out of trying to save code space and also hopes that a simpler request would get filled.

either way as long as SOME form of non destructive chopping is added i'd be extremely happy!

yeah I'm just assuming also that there was a reason why he made the Q-link global for the pad bank instead of per pad.
If we are lucky it was an oversight not a force aspect so maybe he can free pads from each other.