WaxAegis wrote:Playing back all layers simultaneously, as well as reflecting tuning settings, would be an in-depth task to program. However, I'll note that request because it's a good idea. I can't promise that will be implemented, though.
'Note On' is a setting in a pad's layer, so that's why I grouped it together with layer settings. For example, to set Note On on Layer 1 in all pads, set it in Layer 1 on one pad, then Apply Layer to Pads and choose All Pads.
Also, maybe an insight into your expected workflow for the sample range assignment would help me out as well.
Regardless as to whether I can preview the samples on the computer, it's the functionality that's most important to me.
I realize Note On is a setting per layer, I'm not questioning that. However, once I've used the "Apply Layer to Pads" function, every single aspect of the pad that was the source of the change is copied to all other pads, and any changes made to that pad also are reflected in the other pads.
What is the set of steps you recommend for creating a multisampled program (or a chromatic program with a single sample, to be more precise in this case)?
My initial thought was it should be this:
1) Set the program to Chromatic using the Tools->Make Pads Chromatic option
2) Assign the original sample to the associated pad based on its info in the MIDI Trigger box, assigned it to cover pads no wider than -36/+36 tuning respectively. (though I wish the program would simply assign it across any excess pads at the value of -36 or +36 rather than showing me an error and requiring me to recalculate which pads to assign the tuned sample to)
3) Set the initial pad to Note On and right click the Note On box to bring up the context menu, selecting Apply Layer to Pads. This, I thought, would assign this particular parameter from this layer to all pads on the same layer.
I also tried without step 1 (still not clear how the auto-setting of tuned samples across pads modifies note #s of pads) and with steps 2 and 3 reversed, thinking if I first set everything to Note On and then assign the tuned samples, there's no way they would accidentally copy all parameters from the one pad to all in step 3.
But it seems no matter the order of the steps (or which steps I leave out), my efforts always end up in one of two ways: The same sample assigned to all pads set to Note On but all tuned to 0, or all the sample tuned across all appropriate pads but without the Note On setting engaged.
Perhaps some examples of operation in the Readme file, or an associated hlp or HTML help file would prove beneficial.
To me, assigning parameters on the screen such as filter and tuning from the computer is a little unnecessary since I perform all of these settings mostly by ear and the numbers are of little relevency to me. However, if I were to familiarize myself with the numbers and their relation to the functions, bulk-editing would of course be easier on the computer.
But for now, any PC-based MPC editor I use is mostly a time saver for putting together good collections of pre-recorded drum sounds and phrases into MPC kits to be further tweaked on the machine, rather than a tool to replace/augment the timbre-programming functions on the MPC.
Cheers again on the work so far!
-tank.
