Track restrictions across sequences

I just joined a new band. In the last one, I was using the one song per project model; I am considering trying the one song per sequence model instead so as to eliminate load times.

I know that there are restrictions on what a track can do from one sequence to the next; in experimenting with this it seems that the restrictions are even tighter than I imagined. For instance :

- A track that uses a plugin must use the same plugin for all sequences, though the program can be changed
- A track that uses a keygroup must use the same keygroup in all sequences.

I am starting to think that the second model is too restrictive for practical use. Any thoughts on this? Is anyone getting multiple songs into the MPC's memory, and what compromises have you made to do so?

Live OG, 1.11.7

jamos wrote:- A track that uses a plugin must use the same plugin for all sequences, though the program can be changed
- A track that uses a keygroup must use the same keygroup in all sequences.

Maybe I'm mis-understanding you, but you can have a different keygroup program (or plugin) on the same track number across sequences. Each sequence is independent of all other sequences. The moment you switch to another sequence you can have whatever track and program set up you want entirely for that sequence. Other sequence contents have no bearing on this.

In what way are you encountering a restriction in this scenario?

MPC-Tutor wrote:

jamos wrote:
Maybe I'm mis-understanding you, but you can have a different keygroup program (or plugin) on the same track number across sequences. Each sequence is independent of all other sequences. The moment you switch to another sequence you can have whatever track and program set up you want entirely for that sequence. Other sequence contents have no bearing on this.

In what way are you encountering a restriction in this scenario?

What I'm finding is that if I assign a plugin on sequence A, and then a different plugin on sequence B - sequence A will have the Sequence B plugin when I switch back. Similarly with keygroups. HOWEVER - now I think this must be, at least in part, a display bug... for keygroups, the display shows Piano, but when I hit the pads it plays Choir; and when I leave the main screen and come back, everything is good. So I have some experimentation to do.

Thx for the help. You wrote an article on this if I am correct, I remember seeing it once - what was the name?

Yep. Display only. No problem, I feel good again.

With plugins you must create a unique program for each plugin or preset you wish to use. So if seq A has a tubesynth preset on program002, on seq b (e.g. an odyssey preset), set a plugin track then press the '+' icon on the PROGRAM row to create a new plugin program, program003 (rename accordingly). you can now assign an odyssey preset to this program. seq A is unaffected as it runs a different, separate program. Remember you are limited to 8 plugin programs though (no limit on keygroups). And if you wish to have multiple presets from the same plugin, the same rules apply; new plugin program for each preset.

And that's exactly why I can't understand that we can't send or write PROGRAM CHANGE to the internal plugs and FX !!!

Akai make a big miss on it .. you could have 8 plugins, any number of presets in it, giving you a full power in one project.


( Context : I use my Live 1 on gig with differents bands, always making one big project containing everything to chain songs and make transition) It is the only way I can rely on my MPC to go on stage One big project that i did check and that doesn't fail ... if i need extra sample memory, or FX or RAM or anything... I sometimes make a second one but It's scaring me on stage when it come to loading and checking that your mappings and everything works

Calcaire, I definitely want to pick your brain on this... how you use the MPC that is. Looking at your Jawohl Mi Amor vids now.

In the last band I was using the MPC controlling two Nord G2s and a tablet running Emulator X. Each song in one project. The MPC would call up programs on the other instruments when a project is loaded. This would take a few seconds (10?), but that was OK because our frontman/guitarist had to fiddle with his pedal board between songs; I was always ready to go before he was. The Emulator had memory for thousands of sounds so there was no load time there. I did not make much use of the plugin synths on the MPC,

The next group will be a bit more professional so I want to be able to segue between songs quickly. I have dropped the Emulator and replaced one G2 with a Hydrasynth Deluxe. This means I will need to rely more heavily on keygroups, which means longer load times and/or fewer unique sounds. Still trying to find a balance.

So - I see you are using the MPC for drums, a Moog of some sort, and some other things. Do you use lots of keygroups? Plugins? How many songs per set? Etc.

TIA

i didn't know EMU X would/could work with tablet, nice find

jamos wrote:Calcaire, I definitely want to pick your brain on this... how you use the MPC that is. Looking at your Jawohl Mi Amor vids now

So - I see you are using the MPC for drums, a Moog of some sort, and some other things. Do you use lots of keygroups? Plugins? How many songs per set? Etc.

TIA

In this Jawohl mi Amor project I was using MPC for drums/ percussions + external sequencing of moog and clavia NS2.
Also using a few internal plugins program as Electric and Tube synth. Also sending program change on every device at start or in transition between sequences, very useful also when a song structure needed a change of synth patchs, while keeping hands on the keys...

But he NS 2 and the Subsequent really did the job of sound design and performance, so no need of keygroups program, only for a few "background" or ponctual sounds sequenced internally from the MPC. So memory wise it was really ok and I could use quite any drum sound or sample loop I would like to use.. One sequence was even made of a 64 bars real drums+FX looop stereo sample I could'nt emulate so good not to depend too much on keygroups.

Project MPC : 100 sequences used, sometimes working in one sequence with track mute, sometimes chaining manually 8 to 16 sequences when needed ( one next sequences bank) . Sometimes One long sequence playing back ( when i was sure the singer could'nt miss the count

Effects on sends an returns, and master, assigned to QLINKS "project mode" ...
The aim was to keeps hands on the 2 synths and touch the MPC only for sequence chaining and FX, .. So everything assigned for every sequence.. big big job.


In "CUMBIA CHICHARRA" band, i use a one project full of keygroups and 8 plugins program , RAM quite full , making my MPC a very good expander + FX Box, controlled by a Midi keyboard = knobs faders and pads ( Excellent NOVATION SL MK3) . everything is played live with controller splitted in 1 2 or 3 parts depending on the song.. One song per sequence, but no sequencing involved I've sampled my Synths so i've got my own Hohner clavinet sound in a box

With a a Ssh enabled version of MPC firmware , I made a very useful global mapping on MPC software and transfer it to the MPC standalone, really opening the controllers possibilities ( like having 16 Q links on my keyboard and hanging Qlink mode between project and Program with a button... ) ... Again... Kikkgen did something great with this for controlling MPC on stage. Hail to him !

https://github.com/TheKikGen/MPC-LiveXp ... ode-how-to

Hope it helps.

Yes it certainly is helpful. Thank you !