Sorry for the simple question, but what is the best way to save a project, especially when you are doing fine tunings in an old project. Changing patterns among the same kit without saving the kit each time I switch to a new pattern (even when I set to reload the kit in pattern change) make my project a bit messy. Do I have to p. Lock every change I make while switching to same kits’ patterns?
Being a newbie I am sure that I am doing something wrong.
Thanx.
This could clarify your question … hopefully …
If you are changing paramters generally, you change the parameters of the kit.
If you are p-locking something, those paramters will be part of the pattern.
We have 128 kits for a project. That should cover very complex performances. If I have a basic kit and want to change some parts to be more than p-locks only, I copy the kit, assign the kit to the pattern that shall make use of it, and make changes to the copy. It is also convenient to name the kits in a way that makes me remember, what the purpose or speciality of this kit was.
Well, I end up with some kits that might only be different by using other kicks, HH or different tuning, but this prevents me from changing something in pattern B and later makes me wonder, why pattern A generates strange sounds.
If I save my project, all those things will be saved too.
thank you for your reply.
What about the kit reload setting (in sequencer settings i think), how does this work? I thought that everytime i was about to change a pattern the kit will automatically reload.
Yes, you are right
in this can be checked. But this feature is more important to live performing and might be confusing when editing kits.
If you are performing live and use live paramter changes, you might need to go back to the unedited kit quickly or by changing a pattern using the same kit. But the manual is not clear.
It says “…KIT RELOAD ON CHG will cause kits to reload to their saved state automatically as soon as a new kit becomes active. This is useful if you for example play live, have tweaked a kit extensively and want it to return to its saved state automatically next time it becomes active again. This behavior will be familiar to all who are used to the MachineDrum and the MonoMachine.” (manual p. 53)