Bug reports & end-user support for Akai's MPC Software 'controllers' including the new MPC Studio 2, the MPC Touch, MPC Renaissance & original MPC Studio and MPC StudioB lack.
By DannyBmpc Thu Nov 05, 2015 4:21 pm
Hi Guys!

I'm new to renaissance but have used the 2000 for years.

My question is this: How do you guys organize your programs so that they can be used over and over in different projects?

What I have found is that say you make a new program called "chopped drums" and you use that in project #1 and you save this program with the project #1. Then I want to use "chopped drums" in project #2 it has to save all the same samples to project #2 and if I add samples to "chopped drums" on project 2 it will not save the new samples to the same program in project #1. Does this mean I cant have an ongoing sample set that I can add to and use in any program I choose? How do I make a program that will change in every project I make? Also it looks like every program is contained within the project file so I have to go digging in project file to find my programs.

I have tried saving each program in separate folder but then when I go back and upload them it does not have the newest samples that I have added.

Do I just use 1 project and keep all my programs in there? My problem with that is that every time I would save in that project it would take forever to save because it has to save every single sample in every program I have ever used.

In something like logic if I make a sample set I can add that samples set to any project I want and if I add to it then it adds those samples permanently to that sample set to be used in any project I want.

How do you guys organize your programs so you can use them again and again in each project?

Thanks for your help!!
User avatar
By MPC-Tutor Thu Nov 05, 2015 4:55 pm
Programs don't auto update from a 'master' copy, each project and the samples within it remain independant of each other. No workaround, this is just the way it is.

You could add this as a feature suggestion, the ability to create a 'parent' program that when updated changes all instances of it's children in all the projects it's been used in (with some way of 'detaching' individual children to prevent changes to them if need be).

Sounds messy though, I think MPC heads are used to working the independant way.