By Tubedigga
Fri Mar 30, 2018 12:37 am
TUBEDIGGA: 20 Min Live MPCX Drum & Bass Set:
HAPPY EASTER
In this video I'll take you on a little journey for nearly 20 minutes.
Ok, so of course the sequences are mostly programmed but that is what you have to do first, then decide what gets triggered live along with pad mutes, sequence switches and note repeats/XY etc. I've tried to design this project so it's interchangeable and evolves over time.
This project used 1 program on one track (Program 001) and it spawned all other programs - and sequences, still all on track one..
Literally just a case of copying sequences, duplicating programs, switching them up with other sounds, interchanging basically - and spawning new patterns and ideas for samples and how best to perform break downs and transitions. Lots of pad muting and sequence switching which need a lot of refinement from me, not the machine.
Lots of flattening pads, resampling, using samples in different banks but morphing them with all there is available.
All programs are using pad bank A only, which is easier to navigate/pad mutes etc. I feel it can evolve into a super set, a massive pallet of sonic material that I can just duplicate to programs and then manipulate and recycle to construct new kits upon kits- adding small samples on the way like a collage.
Memory is barely 20% and CPU is at 13%
There's a fair few minor mess ups in here but nothing I couldn't rescue because of the way this is set up - at least you can see it was live
The XY needs to be handled with discipline otherwise it just turns into silliness, which I was guilty of a couple of times here.
My workflow is really coming together as a result of thinking long and hard about ways to use the X in a live situation, and also economy regarding the MPCX RAM to avoid glitches. I've literally had no glitches whatsoever whilst producing all these beats (2 days work mining my sample library for old breaks). It's been rock solid.
I really do think you have to treat it with respect, be gentle at first and work with it in a way that it recognises, rather than making (understandable and often unavoidable) errors by pressing conflicting buttons simultaneously - this has always crashed MPCs for me. Then you get quicker and more domineering with it and it becomes the willing and able android servant you spent your hard earned $$$ on.
HAPPY EASTER
In this video I'll take you on a little journey for nearly 20 minutes.
Ok, so of course the sequences are mostly programmed but that is what you have to do first, then decide what gets triggered live along with pad mutes, sequence switches and note repeats/XY etc. I've tried to design this project so it's interchangeable and evolves over time.
This project used 1 program on one track (Program 001) and it spawned all other programs - and sequences, still all on track one..
Literally just a case of copying sequences, duplicating programs, switching them up with other sounds, interchanging basically - and spawning new patterns and ideas for samples and how best to perform break downs and transitions. Lots of pad muting and sequence switching which need a lot of refinement from me, not the machine.
Lots of flattening pads, resampling, using samples in different banks but morphing them with all there is available.
All programs are using pad bank A only, which is easier to navigate/pad mutes etc. I feel it can evolve into a super set, a massive pallet of sonic material that I can just duplicate to programs and then manipulate and recycle to construct new kits upon kits- adding small samples on the way like a collage.
Memory is barely 20% and CPU is at 13%
There's a fair few minor mess ups in here but nothing I couldn't rescue because of the way this is set up - at least you can see it was live
The XY needs to be handled with discipline otherwise it just turns into silliness, which I was guilty of a couple of times here.My workflow is really coming together as a result of thinking long and hard about ways to use the X in a live situation, and also economy regarding the MPCX RAM to avoid glitches. I've literally had no glitches whatsoever whilst producing all these beats (2 days work mining my sample library for old breaks). It's been rock solid.
I really do think you have to treat it with respect, be gentle at first and work with it in a way that it recognises, rather than making (understandable and often unavoidable) errors by pressing conflicting buttons simultaneously - this has always crashed MPCs for me. Then you get quicker and more domineering with it and it becomes the willing and able android servant you spent your hard earned $$$ on.
