rvense wrote:I might not be understanding the procedure, but why not just sample a bunch of sounds, assign them sequentially into a drum programme and then save that? You'd get all the individual sample files in a folder.
That is the point. To diddle around with programs and assign samples and so on, requires additional effort with no purpose. All I am doing is sampling or organizing sample material. I don't want to also do this with Programs which will be of no use to me. They're actually in the way.
I have a rather large library (closing in on a TB) and I rather not keep my sample files tainted by particular technologies (like MPC files). Those Program files would just be extra clutter without utility.
I obviously realize that this is not how all people keep their stuff, but I fail to see how being able to treat a Sample file just like any other file, e.g. a Program, Pattern or Sequence, would be a negative thing. The option to save a sample is already available, so the function is recognized as needed. Just make it also work the MPC way, the way the other types (sequence, track/pattern, program, etc.) work.
In a Program (using the pen), the option 'SAVE *CURRENT* SAMPLE' does not make sense to most people. There are lots of threads asking how to save samples, and most seem to look under the sample edit for it. I say this situation speaks for itself. We shouldn't even have to ask for it, it should've already been filed under 'to fix' as 'inconsistent behavior'.