Saving Parts

I’ve literally just started to try experimenting with parts, I’ve been using Merlins tutorial which is quite helpful.

I’ve just saved a ‘part’ in a project I’ve been working on and the pattern has now been completely messed up, the trigs have been moved.

Anyone know why this would have happened? Thanks.

What do you mean the trigs have moved? I can tell you this much: parts are totally unrelated to trigs, so your saving a part is not the cause.

1 Like

It seems the sample trigs on one of the tracks all moved a step or two down the sequencer, this happened literally as I just hit save part. Is it possible I have hit something else to cause this?

In grid record mode, pressing func+left or right moves rhe trigs accordingly. I’m guessing this might have happened by accident.

1 Like

Ah yes, that’s exactly whats happened. Thanks!

Sorry for bumping this topic, my question is quite different from the original, but fits well with the topic title.

Anyway, here is my random OT question of the day :
What is the point of saving parts ? Only to use the “Reload” function ? Or is there any other reason ?

Parts are saved when project is saved, depending on what you are doing saving parts separately has some uses, for example if you tweak some parameters but did not want to keep them, then reloading the part (that you previously saved) will restore your part without undoing any other changes you since made to the project. I see saving parts as a way of allowing the autosave to take care of other project settings, whilst allowing parts to be saved separately if needed.

So in summary, if you are happy with how your project sounds save the parts, then you are free to tweak away, safe in the knowledge if you want to revert to the saved parts you can.


Noob here - I’ve read multiple comments where people say if want to save everything they save the project first, and then also save the parts.

So you are saying that is unnecessary?

That’s an error : in that case, if you reload the project, saved parts are not reloaded! :content:
So you should save parts first.

Anyway parts settings are stored with banks when you save the project. No need to save them. It is usefull only if you mess with parameters and want to reload settings in live conditions, but a project reload suffice.
It’s another store level I don’t use, but some people may prefer to do it. It’s not a bad thing, but it requires more time. Maybe depends on how you use OT.
Other caveat : you can accidentally reload a part and loose new settings.

You can also save banks, hence save all its parts, patterns.

I know what parameters I mess with. :pl:


Thanks. So, in short, the answer of my question is yes :grin:

Kind of, :laughing: you can save a single part independently though, so if you change a few different parts it can be handy to have the option.

Yes but no :joy:

God only knows what happens when you use parts of different machine types and your pattern has sample locks (well God, and maybe @sezare56 :smiley: ? )


Should be in patterns, like all plocks (except scenes).

Yeah but I’m thinking what happens if you have a part with flex and sample locks, but you change to a part with static? I never tried it.

I might see what happens next time I get a chance.

My guess would be it locks to the same slot number, but from the static slot list in this case.

Or maybe the sample lock turns into a normal trig… :thinking:


My guess too.
But what if locked sample is a recording? :pl:

1 Like

Hang on, how do you save banks? Is it faster than saving a project?

Also adding that parts allow you to change sample slots. So part 1 could be samples 1-8, then part 2 can be 9-16 etc. Great for techno cause you can have 4 sample sets in one bank giving you essentially 4 patterns per “song” with 4 of those songs in 1 bank.

1 Like

In the project menu. Theoretically faster.
Not sure how it can be usefull. Maybe if you have a corrupted bank in a project?

I recommend it for really paranoid people :
Save sample settings, parts, banks, project, and use SAVE AS NEW to be really sure.
Then use PURGE/COLLECT SAMPLES and upload the project to a cloud, copy it to several memory stuff. 10 CF cards should suffice.

Tons of explanations and exemples in the manual :

SAVE CURRENT BANK works like the save project command, but on a per bank basis. The command will save the settings and assignments of the currently active bank. RELOAD CURRENT BANK works like the reload project command, but on a per bank basis. The command will revert the currently active bank to the previously saved state

1 Like

Do you save them? :content:

Per track, in a bank, 4 sample slots with parts vs 128 with sample locks…:thinking:

For me it’s really problematic to change part in a song just for samples assignments : if you change parameters common to all parts, you have to set these parameters again on all parts, and save them again if you always save parts. Time consuming in the end.