[request] Unglobalize pad set assignments

request: Unglobalize Pad Sets

now the Pad Mode Assign List is a global setting, meaning that if you have e.g. Pad Set 1 selected in Sequence 1 it will be the same for all sequences,... i.e. you can't have different sets assigned in different sequences.

you can have multiple sets though. So you mean the sets are dependent on sequence?

I mean to say it is set up as a global function. Just use multiple sets or just use one bank, like bank D. That is what i do. There was a request for being able to change set numbers from main screen to. This would be good for your problem as you could change from main screen. But it is only a few button pushes to get to the set list.

In some ways this way is better because when you are in song mode it means the sets are not changing all over the shop when its converted. It wont now of course, it ignores sequencer and is global

So I like your idea just that it could be messy when you convert songs or it could be its not able to be a feature that the sequencer can do.

Thats what your request would mean! That the MPC sequencer will have a new Data set entry concerning the SETS. So the MPC sequencer would need to recognise sets and set numbers, which then means it can change sets. That is what you really want isnt it

Because thats the next natural progression of your idea, dont you think?
Which means yeah not global.

I reckon it should act like tempo. Tempo is another global function that can be independent of the sequencer. Tempo IS recognised by the sequencer and is a global function that affects every track in sequence no matter what track it is in. Follow me astro.

one of the reasons why I want non-global pad assignments is because I use sequences like projects, i.e. I usually have one project as AUTOLOAD and have different beats, tunes in different sequences instead of different projects.

I do that a bit as well, and have different things in the sequences of a project. So really different sets then would be answer, just change set number. from set screen when you change sequence. You really have to start using a folder for each project and use save all-2... will make things much easier. BUT you can extract sequence from project file, have you tried that at all? so you can make set then load a sequence from other project into your new set up of sets. The sets are saved in the MPC settings file from memory arnt they? not the project file. (looking now), and then save into another folder. This is how you can make sets of songs in one project as well, by loading just one sequence from a project file, not all the sequences. Not much of a work around but with this and MPC set up files you can play around and find a good set up you want. But yeah different set numbers. I think if they could be named, recognised by the sequencer, and changed from footswitch it would be **** amazing live, and so agree but even now, all you do is open set window, change set. takes a few button pushes and you should be quick enough to do that when playing live, so even though it would be killer, it would also be overkill so to speak.

astronaut wrote:one of the reasons why I want non-global pad assignments is because I use sequences like projects, i.e. I usually have one project as AUTOLOAD and have different beats, tunes in different sequences instead of different projects.

i'll just say i think you are setting yourself up for a lot of pain working this way. as you can see you've already run into one obstacle due to this. there's a lot of problems that can occur from this way of working.

really the best way is to have a new folder for each song you are working on. in this case you would use SAVE MEMORY 2 into the folder. this will save everything (including your pad assignments) into that folder. this keeps everything organized, prevents you from overwritting samples accidentally, keeps all your in/out/fx settings preserved, etc...

Sooty_G wrote:

astronaut wrote:one of the reasons why I want non-global pad assignments is because I use sequences like projects, i.e. I usually have one project as AUTOLOAD and have different beats, tunes in different sequences instead of different projects.

i'll just say i think you are setting yourself up for a lot of pain working this way. as you can see you've already run into one obstacle due to this. there's a lot of problems that can occur from this way of working.

I do save projects to separate folders, but at the same time I save them to a common folder.

---

I reckon that making pad assignments sequence specific won't require a lot of programming.

astronaut wrote:I do save projects to separate folders, but at the same time I save them to a common folder.

why? you do realize that loop info is stored in the sample file itself, right.

so if you have 2 different projects that use the same sample in the same folder, if you change the loop settings in one project and save over the sample, it will screw up your other project that uses that sample.

this is one reason why it is best to save everything in seperate folders.


and even if JJ was going to change this function, i think it woul'd be better to make the pad-assignments PROGRAM specific and not SEQUENCE specific.

Sooty_G wrote:

astronaut wrote:I do save projects to separate folders, but at the same time I save them to a common folder.

why? you do realize that loop info is stored in the sample file itself, right.

Yep I know, but I can use packed programs.

I wish OSXL had the ability to have programs with samples stored in different folders.

and even if JJ was going to change this function, i think it woul'd be better to make the pad-assignments PROGRAM specific and not SEQUENCE specific.

Yep, that's a much better idea, this way you could have different pad assignments on different tracks.