Forum to discuss all matters relating to the MPC1000 and MPC2500 operating systems created by 'JJ' (all versions).
By manman Thu Nov 27, 2014 10:39 pm
I recently got my password for os2xl and have started messing around with non-destructive chopping. I have a sample that I chopped up and created a new program from, then I went to mode->save, and saved the program (with sample). It saved the original sample, and nothing else which I was confused about for a second, then I realized- of course, because it's using nd-chop. The next day I loaded the program/sample, but noticed that when I try to use the program I got no sounds from the pads.

I thought I had lost all the chops I set, but when I went to mode->trim and selected the sample, all the chops were exactly as I had saved them last. I created a new program from it and everything worked as it did the other day.

I guess I'm confused about how this all works in terms of saving/loading. I figured that with nd-chop instead of saving a bunch of new chopped sample files and pointing pad->sample wav in the pgm file, it now points pad-> original sample wav + start/end reference data for chop. But if that's true, it seems like loading the program/sample should have worked fine. Is there something else I need to do to save an nd-chop based program so it can be loaded in one step later, or would I have to rebuild the program every time?
User avatar
By le rat Thu Nov 27, 2014 11:11 pm
Hi,

As you've noticed in os2xl there are two different levels when it comes to NDC :
- one in TRIM mode where you create your non-destructive chops
- the other one in PROGRAM mode where you can assign chops to pads thanks to this column :

Image

So basically you need to save the sample and the program. You can also do blank programs with your favorite ndc assignments.

To avoid issues the best is to SAVE ENTIRE MEMORY.

If it's still not clear for you, you can purchase The JJOSXL Sampling Bible from MPC-TUTOR on this black friday. It's worth reading it. I don't think OS3 and OS128XL non destructive slice are mentioned though. But that's another story ;)
By manman Thu Nov 27, 2014 11:29 pm
Thanks for the reply. I think I might be missing something, because I'm pretty sure I DID make sure both the program and sample got saved. here is basically what I did:

-load up my sample
-go to [mode]->trim
-Set 'chop' to ON for nd-chop, slice my samples the way I wanted for each pad
-select 'new program' and create a new program

The last step I did above is what should have assigned the chops to the pads, so I never needed to go into program mode to do that part (and it seems like it did do that, because the pads were playing my chops just as I expected).

Then I went to [mode]->save and selected the program. When i selected it I made sure "with sample" was also selected. I saw that both a sample wav and program file were created (I'm not sure if it always creates a new sample file I think it only did that because I did a slight edit and extract on the original sample I started with, so the chops were based on that)

So if it's a question of saving both the program and sample, I'm *think* I did that part right. Otherwise, it seems like it wouldn't make sense that when I selected that saved sample and went to [mode]->trim, all my original chops WERE there...for some reason the program just didn't have them assigned to the pads anymore.

EDIT:
yeah, so I just did an experiment to try this again. After I created a new program and re-assigned those chops as described above, I went to the program menu to make sure I saw the chops assigned (and had changed to play to Mono). Saved the program (''with sample' set, but sample was already saved). When I turned the mpc off/back on, and loaded the program/sample, go to program menu and all pad assignments gone/ play set to Poly. Saving all memory is probably what I should be doing, but just for the sake of understanding I want to figure out what I'm missing here...
By manman Fri Nov 28, 2014 10:34 am
Ah, ok got it. No, I just went straight from free to os2xl, no factory reset. I'm not sure if I need to format the CF card with the new OS again too, but I guess I will try both.

So it sounds like the way I was trying to do it at least should work, but the OS install just might be buggy. That's good to know at least, thanks.
User avatar
By le rat Sat Nov 29, 2014 9:08 am
And in os2xl you can save the "system setup". After erasing you can reload your own settings.

So yeah do a factory reset and then when you use your MPC just name everything properly (samples, programs..etc). Then, SAVE ENTIRE MEMORY in a new folder each time. Should work fine.