Here's a 'MPC programs' workaround: 1. load up as many kits as you want to check out 2. create an empty drum track 3. in the main mode tap the left-side panel (vu meters) 4. use 'send to' to select the kits. Delete and Purge what you don't need, keep what you do; the empty drum track acts like a clone for others, it even responds to 16 levels and other midi e.g. it can be sequenced, automated. Hope that helps.
@@mpchead Kinda. I don't like to edit stuff there. I use the clips-matrix in more Ableton style. This video & the the description breaks that down in detailed way: th-cam.com/video/Ankzrt01JZ4/w-d-xo.htmlsi=mT9yZMGX4H2dlvOT But I do most the song making in the matrix & only use the arranger to record the scenes & automations. I wish there were more arranger seqs than just 1, but my clip-Bank method that I linked to kinda makes up for that. I wish there was a "Convert Arranger Tracks to Clips" so I didn't have copy & paste each arranger track to clip so I could clear it & reuse it. I'm glad you made this for the MPC dudes. Once they adjust to this system, most will be cool with it in long-run. Peace!
@@wirklich_niemandThe existing workflow is way faster than linear editing. Duplicate a sequence 10 times takes 5 seconds. Record track mutes to 10 sequences maybe 10 minutes total. Chain together in Song mode takes seconds and the full beat is programmed. It takes longer to chop samples than to program a song. There is no way to work that fast in a linear daw.
@@UGHeatyes but song mode still exists with 3.0 so you can still use that if you so choose. I think the benefit is that you can get more granular with song composition with this new arranger.
I just got into the MPC world last year after over a decade of using Maschine. This new way seems to make more sense to me than the way it is currently.
Maschine has some workflow advantages that 3.0 bridges. But it seems to have lost a few things that, while making it easier for new people, takes away power from experienced users.
It's astonishing how such a simple change can throw off and trick somebodies mind, if you are used to a specific method of doing something for a longer period of time. To me it feels quite intuitive how 3.0 works. And it all relates. We all wanted disc-streaming and now we get it. The old mindset tries to load everything into RAM, new logic just links available samples to a track, without the need to utilize RAM, simple and nice! All those samples which got left behind in the RAM which you had to delete all the time to keep the project clean was horrendous overhead work. No more needed, nice! it feels hard to see Marlow struggle with discovering this, but I was always a fan of his video style and I have high hopes that he will soon begin to love the new methods. :)
I don’t think people realize that MPC 3 actually makes keygroups useable. Unlike plug-ins, keygroups programs have no limit. Can load as many as you like. I avoided them in MPC2, because I didn’t want to delete all the keygroups I didn’t use and purge the unused samples to keep my projects from taking 5 min to load.
@@matthewjswiderI will try my best On regular Daws like ableton or reason or what not When you load the instrument , it just goes to the track When you load a drum kit it goes to the track as it is linked But In older MPC, you can load instruments/drum tracks/ keygroups and they could work within multiple tracks Because of this, we usually just load a bunch of everything which causes ram to decrease With this new method you only pull the instrument needed for the track
To be honest, I think it's an improvement. I read a lot of people are complaining, but that happens every time something, they are used to, changes. People don't like change. I think, it is way easier now especially for people new to the mpc, but for me as well. A few years back as I started learning the mpc, I still remember, how confused I have been especially about programs. Sequences make sense, tracks make sense, but programs? What is that? That were my initial thoughts. To simplify that is the way to go and I would like to see that for other aspects of the mpc as well. Simplicity is where magic happens at least for me.😉
Programs were the heart of the MPCs. A bunch of friends I tried to get on the MPC, over the years, got insanely confused by Programs. I learned to make electronic music on a 500 so it was just how it was to me, and I built some crazy programs as a teenager. The workflow is dead, there’s no going back. All I wanted was mf disk streaming
@Marlow Digs I so appreciate you for explaining that "Programs" are now "Tracks" in MPC 3.0, however that's not alot of people workflow on their MPC's. Especially not the legacy MPC users. @AkaiProVideo better add another ✅ checkbox in the "Audition" to "Play the MIDI data from the selected track" or something as a workaround. Until they do I'm deciding to stay put in the MPC 2.
Yup, I tried working around this by just hitting duplicate track on my drum program tracks, but it was doubling them in memory. Now someone is in the forums saying this isn't the case, but I'm on 3.4. Can anyone confirm this?
The point to me is the workflow was already a pain. So for ppl who have used the 2.0 flow for years and have a quick 2.0 muscle memory, they will have a period of time where theres a high risk of accidentally deleting their work. Akai shouldve put a message like "This will delete blah blah, Are you sure? Yes No Cancel" This would save a lot of learning curve pain. Just my opinion.
Listening to while you experienced MPC guys figure out all the Shortcuts makes me realize why guys like me could never wrap our heads around MPC workflow. I feel version three is going to make things way more useable for guys like me.
The way I see it is this : the old school way is so deep in our DnA it was always gonna be painful when progress comes calling. But it’s nessecary for what’s coming down the line. We need this and we have to adapt. It’s not gonna take as long as people think. BUT I’m still gonna have one of my MPC’s running 2.0 just in case. However I can see how I’m gonna end up flipping everything to 3 after the fine tuning and muscle memory happens.
After having the Force since 2021, the best feature that most are sleeping on, is the macros. Once you set them up & make some templates things get super quick!
Muscle memory doesn't work the same on a touch screen, especially the ones on the Live. Going in and destructively deleting sounds out of a piano roll is never going to be better than muting tracks you don't want to hear on a particular sequence. Pad Mute doesn't replace this either.
I sold my MPC One because I just couldn’t get around the MPC workflow. I would think I “got it” and eventually I would hit a wall that had my head scratching for hours. It was really frustrating. This feels like a welcomed change. Pick one up again??
I wish you could have a Program (track now) and have sub tracks with in it. Call it lanes Then you could have the old track mute by including Lane Mute. Lol won’t happen
The question is will the duplicate tracks created have ALL the samples of the original track, or paired down only to the one exploded out? I assume that the samples aren't duplicated with the track, so each track would have a duplicate of the entire sample set.
Hey Marlow, when you tap the save button and it went to the save menu screen, I saw an icon that had drum program and it had the 16 pads in red on the screen. Isn’t that also another option to save drum programs as well instead of having to save the track with the drum program on that track?
About "resuing" a program in multiple tracks, I believe you can have a midi track sending notes and other messages to the program in another track. If that's the case, I guess you still get a similar workflow as before, though the Program Edit button will open the midi program instead, and the sample edit button probably doesn't do anything.
Yes and no, yes you can send midi but from what I understand you can only send to one track, maybe there's more to it but it does not compare to having the same program in multiple tracks sharing effects and polyphony.
Hey Marlow (or anyone else who knows…), is it possible to revert back to 2.0 from 3.0 when you’ve installed 3.0 on standalone? All of the 3.0 talk has given me a whole new appreciation for 2.0… I don’t want to install 3.0 if I can’t go back.
Will it also delete the midi data of the track when you load a certain drum program into the track. So if you want to change the drum sounds on an existing track is that still working, Marlow?
I miss being able to master in the MPC. It used to be you could just master it. Like a wav. On one program. Now you have to do it individually. At least for now
Thanks for the video, to bad your MPC screen only fills 1/4 of my screen. It makes it really hard for me to see your screen + reflection. I assume it's specifically for people who own your MPC model so they can see what buttons you push. Same with the "Mpc 3 comparison with Mpc 2.0 Screens" I wish they'd be the center, so I can see the little details of the video, which now is harder to see. Regardless I am looking forward to go through your you tube channel tutorials again just like I did with MPC 2, thank you!
This is exactly where clips came in handy on the Force, and why it’s weird that they just ripped 3.0 software from Force instead of thinking through something a bit more custom to the MPC
It's still in the beta stage so I'm holding judgement until it's official released and if need be I'll just have to adapt to the new changes or just stay in 2.0 🤷🏿♂️
man, I bought an MP' 'cuz I wanted to keep me off on the FL Style and the computer screen. Since I introduce myself into the Legacy Workflow I done more beats than in a Daw and quickly. Lets say 1 Beat per day. It took me more than a week to finish a Beat in FL, and I gotta say that I hate this (beta)update, and I will keep it real the Legacy workflow…
Wait, if i see that right, this actually disables MIDI-Mapping.. When i work with a MIDI-Mixer like the Launch Control XL, i could make a template where i do 8 basic programs and every program is linked to a fader, a mute and solo button. So for every new program i used that template. The disadventage of this was, that i have to load all new samples in that programs - so a workflow like yours with the crop programs wasnt possible. (without re-mapping every MIDI button to the new program) But same here now - iam bound to create new Tracks/Programs so i would have to MIDI-map all over again and again. That sucks.
Thanks for the video Marlow. This is super helpful. I have a question - I have always played live sets using a 1 sequence + 1 program method. Seq 1 and Program 1 make up the whole song, Seq 2 and Program 2 is song 2, etc. It was easy to load, let's say, 25 Sequence+Programs into RAM and then you have 25 beats in a project to play live. Can this still be done easily on MPC 3?
Yes, you can do this but the set up will look a little different. So basically, your set project would have 25 tracks. Each track will have a program associated with it. Seq 1, Track 1, will have Program 1 and the sequenced beat, with all the other tracks in this sequence blank. Seq 2, Track 2, will have Program 2 and the sequenced beat, with all the other tracks in this sequence blank. Seq 3, Track 3, will have Program 3 and the sequenced beat, with all the other tracks in this sequence blank. And so on…
@@Kano88_beats Sorry, I didn’t explain that part very well. Those “blank” tracks will still be drum program tracks containing a program, but they won’t contain any recorded midi data. In a given sequence, only one drum track will contain recorded midi data (i.e., your song created using the program on that drum track) and the other 24 drum program tracks will not contain any recorded midi data. So you will end up having one song per sequence.
So you can't save a "drum track" and use it in two different projects. If you put a lot of work into a certain drum track program and you like to keep it and use it in different project?
I try and keep every track in every sequence the same program this seemed to make sense. So now when you duplicate tracks iit carrys the program with it???if so this is short cut for me.
someone mentioned that you could control a dum track with several midi tracks to work around the tracks and programs being one is that possible and is it still gonna be in the final version thanks for all your videos very helpful
Hi there, between yesterday and today I was using the new firmware. I understand that there is a big conceptual change and a big discussion around this topic. But my question is: what about the workflow for the live set? I understand that now it is more dynamic to produce a track in the studio. No discussion! It is much easier but I insist what happens when I want to create a live set? how should I think about the structure/architecture of the machine? If I load my live set from the MPC 2 it reads and plays it without problems but each sequence was a different song with its own tracks. This is no longer the case now. If each sequence had let’s say 5 tracks each. Now it looks all together, there is no way to discriminate which tracks each sequence contains. So now I have to see all the tracks of all the sequences in a sequence, which is very chaotic. I’m not trying to start a debate, I’m trying to get someone to help me understand. I have the feeling that MPC3 is more like a DAW: Logic, Sonar, Protools, Cubase, etc and therefore it is not ready to build a live set. So sorry, but I can't agree with you that it's exactly the same. Thanks
@@mpchead sorry but in minute 14:33 you say: ...but the workflow is essentially the same... and you didn't mention nothing about this BIG CHANGE on the concept of the workflow to do live sets. In fact is a big discussion in this moment. They changed the essence of the machine's architecture. please don't misunderstand me. I don't want to criticise you. You have done a great video and a great job. I really like your channel. But this topic I mention is a big discussion at the moment, it has a lot of frustrated users on the forum. Maybe you already have it in mind but you could make a video about this topic. Thank you very much and congratulations for your great job!
yeah even with the clarifications about mutes and the song -> arrangement potential you highlighted in the earlier video, this still seens to break too much of what i've been doing with this machine since i've had it. automatically deleting programs because i try to switch between a few i'm auditioning? ayfkm? so i need a bunch of duplicate tracks in my project structure? like, i wouldn't be the least bit sour if this were a new device or an alternate Force-for-MPCs fork while they continued bug fixes and workflow improvements on the pre-3 platform. but this is not an upgrade to me, a person who already owned a current gen MPC. yes you can do most of the same things but that is true about Ableton vs FL Studio and yet no one wants to have to switch suddenly because the developer they'd invested years of their creative life with suddenly decided that actually the other company's DAW is sexier. i do not understand declaring "the workflow hasn't changed" and "everything is pretty much the same" while you detail structural level changes to projects. i also don't feel like i can trust the backward compatibility with older projects as being much more than theoretical when it is effectively converting them to a new format. being able to touch up songs in arrangement and create better transitions is cool in theory, but ultimately will still be part of what i'd use a computer DAW for even if i **do** transition to MPC 3. beyond that, reordering effects is the only part that has really tempted me and it's like... i've been used to that stupid needless limitation for almost 5 years since I bought an MPC (specifically an MPC not a Force I must note...) so i think i'll be able to continue surviving around it. 4-5 years of semi-regular semi-decent updates was... semi-alright for a product support lifetime. i don't mind some of the DAW features but i recognize that i'm in a tiny percentage of the reaction out here (and the fact that even ONE of us is less than euphoric seems to bother some people more than these issues actually bother us!) and it's okay that this will probably be my last MPC from date of manufacture. it's plain to see that they're going to ride this $$$ train as far as they can, and i can't even really blame the developers for it.
You don't need to delete the track/program if you don't want to, you can just load the new program to a new track, and yes you'll have a bunch of different track in the end. I don't think the compatibility will be there at all between 2.0 and 3.0. Good on you to speak out and express your thoughts.
Over the years I’ve seen tons of new MPC users struggle with the mental model behind Sequences, Tracks and Programs. While this new approach may limit the creativity of a few, it makes a ton of more sense to the many. Plus I’ve always run into problems when I start mixing programs and tracks around. Song mode doesn’t work anymore once you do that. So the decision to bind them into one makes a ton of sense to me, sorry.
What you said is all correct. But some of us prefer the other way. Why can't people just accept that. We are not all alike, you have your preferences and I have mine.
It's going to be easier for less experienced people and is probably fine for everyone else, as long as they didn't take away the functionality of the programs themselves (eg. Program level effects). My issue is that Akai probably did take away things. For example, track mutes per sequence is gone, which makes song mode useless.
So it sounds like MPCs just moved away from people who used them for live gigs and creative jamming, and became more of a "production only" machine. That's too bad. I hate losing old, trusted features to make way for new. Can't we have both?
@mpchead Hey Marlow, great video thank you for that. Now imagine my workflow regarding stem separations. After separating the stems from my main sample, I start creating my beat with the original sample. Once the first tracks are up, I often love it to change the original sample within my tracks to the programs 'Other' or 'Bass' to hear how it sounds and with the benefit that my grid events stay intact. Hope this makes sense somehow. How should i do this right now? is this even possible? And is it possible to choose programs from my project pool instead of browsing thru my whole sample library all the time? thanx alot for clarification.
@@PeteOnTheBeat This is how i would do that: Go to sample edit mode and select your sample. Then select "Create Stems" and activate all options (Vox, Bass, Drums, Other). Make sure that both "Assign to a Pad" and "Use Trimmed Samples" are selected. Once you have done this, save the sample as a program. Then switch to program edit mode, select your sample and you can now lower the volume of the drums to zero. Then select "Flatten Pad" and you will get your sample without drums. I know, i know.. but it just sounds more complicated than it actually is! ;) If someone know a better way to do this on a mpc, feel free to share!
I created a pad with 3 layers - all but the drums. But in program edit,to chop,it only chop the pad,for example,the bass. Totally ignores that it has 2 more layers in the same pad. Thats why I was thinking about resampling and shit. All would be just a sample,in a pad,without the drums. Does your method allow to chop all the stems at the same time?
I haven't tried it but seeing you can change a program you would have to select "all" inside the program and change the slices to "other" or "Bass". this might work. Honestly it would be something to try and see if there's a workaround.
No, this is a restriction that Akai currently has in the OS. This is similarly done for audio tracks. I assume this keeps the cpu/ram from being taxed. Explore keygroups, you can load as many you like. With the linking of tracks to one program at a time, using keygroups makes a lot more sense than they did in the past. And there are a lot of good keygroups libraries available, or make you own by auto sampling.
I don't like that. Most of the time I use a template with drum programs I created previously (Kicks, snares, percussion..) so that I can immediately start. Furthermore I like to use one drum program in different tracks and have every time the same effects on it.
But you can still use that template, nothing changed that way. That second thing you mentioned yeah that's probably not gonna happen unless you use submixes or returns to send the different tracks/programs to it.
What would be great is if later on they did an update where you could select to link or synch tracks. So if you duplicate or copy the same track 3 times the one which is on top in the order can be synched to others and whatever effects or changes you make will happen to the others synched. If I select track 1 & 2 and make changes on track one it does the same on track 2. If I then deselect track 2 but select track 1 & 3. The changes will remain on track 2 but new changes will be on 1 & 3 when I edit anything on track 1.
@@mpchead Also without having each of them linked to a track? I want to have them in my "inventory" so that I can pick any of them if I want. So that I don't need to load any during production when I decide that I need them.
@@mpchead th-cam.com/video/8B9rU7zs4a8/w-d-xo.htmlsi=mzUB6KNw-zjis6C_. I thought I sent the link a week ago but I just realized it didn’t go through. Sorry for the late reply.
Cooy program? So I have to copy ALL the samples every time i want a different drum sound on a different track? So my drum program has to be copied 4 times just to have kick, snare, hat, toms on separate tracks? Dang. Thats gonna unnecessarily clog up my SD card with duplicate samples.. i used to get by with 1 drum program and only 1 of each sample. Seems inefficient..
I don't like that you can accidently delete an entire program and all its samples so easily. If you just switch to another type of track and then back again - all your samples are gone. Seems like a lock function or something similar would be beneficial on the tracks
Can you demonstrate in a future video on how to duplicate a track and copy events and apply a filter effect on the duplicated sample? Hope this makes sense thanks. great video by the way.
So, I just started a fresh project - I'll have a drum track. I load a drum loop to a pad and chop it. Hopefully I can still chop into a new program as we did before. But now,where's that program? I want to find it to load it into track 1,so I can then duplicate it twice so I have a kick track, a snare track and a hats track. But then, wait, I need some extras that weren't on the drum loop. So I create another program/track to add them,but wait so are heavier on the low end than other and it will mess with the mix,so I now have to duplicate that other program,or just make another. Then the sample,that I usually added to the same program where I had my dloop. Feels like a lot of work,but it's basically what I end up doing in Ableton,with the difference that my computer has a faster cpu than the MPC and I have way more ram... Very curious about all this... especially the converting the sample to another program. And Marlow, can we duplicate the whole sequence as before? To create a chorus for example.
I think an easier way would be to just work within one drum track. Duplicate the low end heavier hits to other pads for additional processing. Then when you’re done sequencing the drums, just explode the drum track and rearrange the exploded tracks in the order you prefer. I agree, the old way is slightly quicker, but this way might work, too.
I am really curious to see the people's reaction towards that massive change. To me, that approach throws a lot of the classic program workflow out the window and makes everything harder to mix. If you are working like me , which is all samples in a single program and each pad having its own track, you will have a hard time mixing. The solution of having empty drum tracks sending notes to a track program is not intuitive as you don't get the names of samples as you normally see in a program. + Changing the midi track volume does nothing for the sample / automations need to be done on the track that has the sample. Exploding the sequence will create multiple programs with a single sample. This is how you can work in the arranger and have everything laid out as i previously said, but that means you will have one sample per program. So you either do the whole sequence on a single track then explode after, or if you have multiple programs (I almost always load a 909 program and create a second one with synth bounces, samples etc) you will end up having two tracks on the arranger and do your mixing process in the pad mixer.
Agreed. They really need to make these options customizable settings, rather than completely change the “CLASSIC” MPC paradigm. Somebody get Roger Lynn on the phone!
I don't understand why it will be hard mixing specially now with the new mixer window. Just go to the mixer and mix all the sounds there. Each track will be the same with an individual sound. You won't be able to have an overall effect section for the same program as before but maybe you can use sbmixes and returns to share effects. That being said I do prefer the 2.0 workflow.
I can already see what's going to happen to a lot of people including my self. Loading a new program should automatically load it to the next AVALIABLE track instead of overwriting ones that are already there. Is there a set number of track that can be loaded or is it based on memory? They should also give an option for call it "Associate Tracks" giving us back the option of keeping what we have now but just with different verbiage for people who want to continue the older workflow. Like Track 2 and it associate Track 2a. Track 2a would essentially be everything Track 2 is but without the sequence data. The track option could just be added in the same location as the Track type creation screen.
It will load to a new track if you want, will not erase the other track unless you want it to. I don't know about any set number of tracks, don't believe there is any limit.
Now, why will you have to load up 50 programs? Show me in what scenario you’ll have to load up 50 programs… looking for problems that aren’t there… sheesh
@@ArthurBlue-i1v yeah Sure… 50 programs load up with 2gb of Ram? Unless every sample on those programs are 5kb ain’t no way you’re loading up to 50 programs with 2GB Ram.. With what memory your gonna run a smooth live show. Your “what if” scenario is BS.
Linking tracks to programs doesn't make any sense, how many sounds are you going to use in one track. Why would I keep loading the same program over and over for every track. They totally changed up the entire workflow and made it slower. I like some of the new features but this ain't it.
I see what you’re saying, but to be honest, this is a workflow enhancement, especially when dealing with loading a lot of kits and/or keygroups. In MPC 2 and earlier, projects can become huge and take a while to load because you loaded up a lot of programs and forgot to delete the programs you didn’t use in your project and purge the unused samples before you saved the project. In MPC 3, if you’re dealing with a single drum program, sequence your drum on one track and then explode the track.
the normal MPC ..."one sequence one song "... liveset style is over. this is really not good.......in 2.0 the program workflow was perfect and now we have to prepare a lot more and we search early in the morning on stage for the bassdrums on track 79 or 57 or .....before it was in every sequence always on track 1( that was the easy mpc way) new is not always better . in 2.0 the only thing to do, to have it streamlined (if you want) is to use the same programs on the same tracks in every sequence (could be easy i think ) and now everybody is talking about workflow better better and maybe i am the only one who is not convinced. i have fear for preparing a liveset and bring songs together and change something quickly in the last minute..
I hope that they will change it in future builds. There was a new build for the closed beta testers that fixed some bugs and such so it is still very much being worked on. But having all sequences sharing the same tracks and removing the clip programs is a big hit at the live aspect of the mpc.
I understand what you’re saying, but most people use the MPC for production and song creation. This workflow seems to be aimed at making the workflow more intuitive and streamlined for that audience. I think the intricate user q link mapping is aimed at the live performance crowd. What would be convenient is if MPC 2 and MPC 3 could be dual booted. This feature might be on the nerdy/techy end of the spectrum and something we would most likely never see, but, it still would be cool.
I think you need to better explain the flaws with them "merging" programs with tracks. 1) you can't assign the same program to more than one track. Duplicating a track to get a copy of that program does not "fix" this problem. If you "duplicate" a program for 5 tracks and want to make a change to a pad, you'd have to do it 5 times. Same if you wanted to add a sample, you'd have to do it on 5 different tracks. 2) if you spend time sampling to pads and build a program, then you mistakenly change the track type to MIDI, you've now lost the program you just created as well as all the samples. This is just poor design. I really hope they bring back the ability to assign the same program to multiple tracks.
That is true and more, much more. this change is a big blow on programs control. You can always undo, that is not that something I would worry about but I understand your point, it is bad design.
I get what you’re saying, but the MPC(60, 60ii, 3000, 2000, 4000, 2500, and so on) has always been somewhat a of simple Daw. On a MPC, I create a track, load a program, and record midi. I create another track, load a program, and record midi. And so on. I then copy sequences, and arrange my beat in song mode. I do the same thing on the computer in Ableton. Create a loop with multiple tracks, copy the loop multiple times and arrange. Obviously, you can do more on the computer, but the basic daw features are similar between the two. The end result being a sequenced beat/song.
@@brianpinkins6218 I feel that. I think it's just becoming more computer like, With the touch screen and all the new features... A computer with a pad controller is basically a mpc X with bigger screen and with all the benefits of a computer....I don't buy the computer is to distracing argument but hey just make music on whatever, that's all what counts
![[#2024MAMA] G-DRAGON - 무제(Untitled, 2014)+POWER+HOME SWEET HOME+뱅뱅뱅+FANTASTIC BABY | Mnet 241123 방송](http://i.ytimg.com/vi/Ox29z5Nf1Uk/mqdefault.jpg)
I share Drum Programs since 2017 on my Patreon www.patreon.com/mpchead
Sample packs mpchead.com/collections/sample-packs/Drum-kits+sample-packs
I like the new way of 3.0. Thanks
Here's a 'MPC programs' workaround: 1. load up as many kits as you want to check out 2. create an empty drum track 3. in the main mode tap the left-side panel (vu meters) 4. use 'send to' to select the kits. Delete and Purge what you don't need, keep what you do; the empty drum track acts like a clone for others, it even responds to 16 levels and other midi e.g. it can be sequenced, automated. Hope that helps.
I can read your comment here, but putting it in a video is more better. Some people are visual learners.
As a Force users this breakdown was like a Force for MPC-Heads tutorial. Keep walk over to the Darkside!
Nice Job breaking this down.
You like the arrangement view on the Force?
@@mpchead Kinda. I don't like to edit stuff there. I use the clips-matrix in more Ableton style. This video & the the description breaks that down in detailed way: th-cam.com/video/Ankzrt01JZ4/w-d-xo.htmlsi=mT9yZMGX4H2dlvOT
But I do most the song making in the matrix & only use the arranger to record the scenes & automations.
I wish there were more arranger seqs than just 1, but my clip-Bank method that I linked to kinda makes up for that. I wish there was a "Convert Arranger Tracks to Clips" so I didn't have copy & paste each arranger track to clip so I could clear it & reuse it.
I'm glad you made this for the MPC dudes. Once they adjust to this system, most will be cool with it in long-run. Peace!
So glad this isn’t confusing at all and that’s not a Dig at you Marlow
its actually very streamlined and behaves now like daws and other samplers. I'm glad they finally get rid of their dusted workflow.
@@wirklich_niemand having to menu dive to create a new track and add tracks/programs is not an improvement. I’m all for improvements.
@@wirklich_niemandThe existing workflow is way faster than linear editing. Duplicate a sequence 10 times takes 5 seconds. Record track mutes to 10 sequences maybe 10 minutes total. Chain together in Song mode takes seconds and the full beat is programmed. It takes longer to chop samples than to program a song. There is no way to work that fast in a linear daw.
@@UGHeatyes but song mode still exists with 3.0 so you can still use that if you so choose. I think the benefit is that you can get more granular with song composition with this new arranger.
@@filmingkey But you can't have different track mutes per sequence which kills that workflow. Slow way or no way.
I just got into the MPC world last year after over a decade of using Maschine. This new way seems to make more sense to me than the way it is currently.
Maschine has some workflow advantages that 3.0 bridges. But it seems to have lost a few things that, while making it easier for new people, takes away power from experienced users.
@@s.gharavi1614Man I wound up going back to 2.15.1. I may upgrade again later.
@@leogolive did you go back because the issues with the changes with programs? I'm dreading losing that.
It's astonishing how such a simple change can throw off and trick somebodies mind, if you are used to a specific method of doing something for a longer period of time. To me it feels quite intuitive how 3.0 works. And it all relates. We all wanted disc-streaming and now we get it. The old mindset tries to load everything into RAM, new logic just links available samples to a track, without the need to utilize RAM, simple and nice! All those samples which got left behind in the RAM which you had to delete all the time to keep the project clean was horrendous overhead work. No more needed, nice! it feels hard to see Marlow struggle with discovering this, but I was always a fan of his video style and I have high hopes that he will soon begin to love the new methods. :)
I don’t think people realize that MPC 3 actually makes keygroups useable. Unlike plug-ins, keygroups programs have no limit. Can load as many as you like. I avoided them in MPC2, because I didn’t want to delete all the keygroups I didn’t use and purge the unused samples to keep my projects from taking 5 min to load.
Guys, how do I understand anything you just said as a new user?
@@matthewjswiderI will try my best
On regular Daws like ableton or reason or what not
When you load the instrument , it just goes to the track
When you load a drum kit it goes to the track as it is linked
But In older MPC, you can load instruments/drum tracks/ keygroups and they could work within multiple tracks
Because of this, we usually just load a bunch of everything which causes ram to decrease
With this new method you only pull the instrument needed for the track
@@matthewjswider Just use the new system naturally. Without knowing the old processes it should fall into place for you without to much hassle.
To be honest, I think it's an improvement. I read a lot of people are complaining, but that happens every time something, they are used to, changes. People don't like change. I think, it is way easier now especially for people new to the mpc, but for me as well. A few years back as I started learning the mpc, I still remember, how confused I have been especially about programs. Sequences make sense, tracks make sense, but programs? What is that? That were my initial thoughts. To simplify that is the way to go and I would like to see that for other aspects of the mpc as well. Simplicity is where magic happens at least for me.😉
I agree that is simplifies things, but for people that are comfortable with programs it does take away some level of control (not much but some)
Programs were the heart of the MPCs. A bunch of friends I tried to get on the MPC, over the years, got insanely confused by Programs. I learned to make electronic music on a 500 so it was just how it was to me, and I built some crazy programs as a teenager. The workflow is dead, there’s no going back. All I wanted was mf disk streaming
@Marlow Digs I so appreciate you for explaining that "Programs" are now "Tracks" in MPC 3.0, however that's not alot of people workflow on their MPC's. Especially not the legacy MPC users. @AkaiProVideo better add another ✅ checkbox in the "Audition" to "Play the MIDI data from the selected track" or something as a workaround. Until they do I'm deciding to stay put in the MPC 2.
Yup, I tried working around this by just hitting duplicate track on my drum program tracks, but it was doubling them in memory. Now someone is in the forums saying this isn't the case, but I'm on 3.4. Can anyone confirm this?
This is a great walkthrough. Really helped break down the smaller details of new workflow changes. Thanks!
The point to me is the workflow was already a pain. So for ppl who have used the 2.0 flow for years and have a quick 2.0 muscle memory, they will have a period of time where theres a high risk of accidentally deleting their work. Akai shouldve put a message like "This will delete blah blah, Are you sure? Yes No Cancel" This would save a lot of learning curve pain. Just my opinion.
Just press undo. It works
Listening to while you experienced MPC guys figure out all the Shortcuts makes me realize why guys like me could never wrap our heads around MPC workflow. I feel version three is going to make things way more useable for guys like me.
I’ve bought and sold a few mpcs because the workflow was too different from daws. V3 has me coming back and I might never leave! 🙌🏾
Just wanted to say thank you for saying you don’t know yet about clips. Saves me asking!
Many thanks for teaching us all of that! Very appreciated!
These are great instructions, and the way I do it now
The way I see it is this : the old school way is so deep in our DnA it was always gonna be painful when progress comes calling. But it’s nessecary for what’s coming down the line. We need this and we have to adapt. It’s not gonna take as long as people think. BUT I’m still gonna have one of my MPC’s running 2.0 just in case. However I can see how I’m gonna end up flipping everything to 3 after the fine tuning and muscle memory happens.
After having the Force since 2021, the best feature that most are sleeping on, is the macros. Once you set them up & make some templates things get super quick!
Muscle memory doesn't work the same on a touch screen, especially the ones on the Live. Going in and destructively deleting sounds out of a piano roll is never going to be better than muting tracks you don't want to hear on a particular sequence. Pad Mute doesn't replace this either.
I sold my MPC One because I just couldn’t get around the MPC workflow. I would think I “got it” and eventually I would hit a wall that had my head scratching for hours. It was really frustrating. This feels like a welcomed change. Pick one up again??
thanks for your explanation much appreciated... Question...can you load an old project into the 3.0 ??
You can but it might not play the same way because of track mutes being different for now.
I wish you could have a Program (track now) and have sub tracks with in it. Call it lanes Then you could have the old track mute by including Lane Mute. Lol won’t happen
Does exploding tracks still allow for multiple tracks with a single program? Or is it duplicating programs for each sample?
Good question
I didn't see that but I assume it will create new tracks/programs. Mpc3 does not have identical programs. It will always be a copy.
The question is will the duplicate tracks created have ALL the samples of the original track, or paired down only to the one exploded out? I assume that the samples aren't duplicated with the track, so each track would have a duplicate of the entire sample set.
Right. Will it duplicate the whole program multiple times, or just create a new program with a single sample for each track. Good question.
Hey Marlow, when you tap the save button and it went to the save menu screen, I saw an icon that had drum program and it had the 16 pads in red on the screen. Isn’t that also another option to save drum programs as well instead of having to save the track with the drum program on that track?
About "resuing" a program in multiple tracks, I believe you can have a midi track sending notes and other messages to the program in another track.
If that's the case, I guess you still get a similar workflow as before, though the Program Edit button will open the midi program instead, and the sample edit button probably doesn't do anything.
Yes and no, yes you can send midi but from what I understand you can only send to one track, maybe there's more to it but it does not compare to having the same program in multiple tracks sharing effects and polyphony.
@@mpchead it's also just a pain to open a midi track.
Bro, in the save menu there is an option for saving drum programs. That same option is in MPC 2 right now.
@@chopsDT thanks I missed that
I can’t wait to get 3.0 I think it’s gonna be a game changer for me I’m so used to using Reason
Hey Marlow (or anyone else who knows…), is it possible to revert back to 2.0 from 3.0 when you’ve installed 3.0 on standalone?
All of the 3.0 talk has given me a whole new appreciation for 2.0… I don’t want to install 3.0 if I can’t go back.
You have an option during the beta to switch back to 2.0
Maybe a vid just diving into the arranger and it's functions?
Will it also delete the midi data of the track when you load a certain drum program into the track. So if you want to change the drum sounds on an existing track is that still working, Marlow?
No, it doesn't delete the midi if you load a different program into the track.
@@mpchead@mpchead ❤❤❤ Ok. That is a plus then. But I got your points. Thanks so much Marlow... you are one of the best MPC heads out there.
I miss being able to master in the MPC. It used to be you could just master it. Like a wav. On one program. Now you have to do it individually. At least for now
certainly a lot cleaner to work with. tidy !
Thanks for the video, to bad your MPC screen only fills 1/4 of my screen. It makes it really hard for me to see your screen + reflection. I assume it's specifically for people who own your MPC model so they can see what buttons you push. Same with the "Mpc 3 comparison with Mpc 2.0 Screens" I wish they'd be the center, so I can see the little details of the video, which now is harder to see. Regardless I am looking forward to go through your you tube channel tutorials again just like I did with MPC 2, thank you!
This is exactly where clips came in handy on the Force, and why it’s weird that they just ripped 3.0 software from Force instead of thinking through something a bit more custom to the MPC
Exactly.... that's it 💯
It's still in the beta stage so I'm holding judgement until it's official released and if need be I'll just have to adapt to the new changes or just stay in 2.0 🤷🏿♂️
man, I bought an MP' 'cuz I wanted to keep me off on the FL Style and the computer screen. Since I introduce myself into the Legacy Workflow I done more beats than in a Daw and quickly. Lets say 1 Beat per day. It took me more than a week to finish a Beat in FL, and I gotta say that I hate this (beta)update, and I will keep it real the Legacy workflow…
very good video - well done
Ive never used an mpc and this shit is so damn confusing 😂 i sometimes think about buying one to make music elsewhere out of my house tho
Wait, if i see that right, this actually disables MIDI-Mapping..
When i work with a MIDI-Mixer like the Launch Control XL, i could make a template where i do 8 basic programs and every program is linked to a fader, a mute and solo button. So for every new program i used that template. The disadventage of this was, that i have to load all new samples in that programs - so a workflow like yours with the crop programs wasnt possible. (without re-mapping every MIDI button to the new program)
But same here now - iam bound to create new Tracks/Programs so i would have to MIDI-map all over again and again.
That sucks.
Thanks for the video Marlow. This is super helpful. I have a question - I have always played live sets using a 1 sequence + 1 program method. Seq 1 and Program 1 make up the whole song, Seq 2 and Program 2 is song 2, etc. It was easy to load, let's say, 25 Sequence+Programs into RAM and then you have 25 beats in a project to play live. Can this still be done easily on MPC 3?
Yes, you can do this but the set up will look a little different. So basically, your set project would have 25 tracks. Each track will have a program associated with it.
Seq 1, Track 1, will have Program 1 and the sequenced beat, with all the other tracks in this sequence blank. Seq 2, Track 2, will have Program 2 and the sequenced beat, with all the other tracks in this sequence blank. Seq 3, Track 3, will have Program 3 and the sequenced beat, with all the other tracks in this sequence blank. And so on…
Yes it can be done very easily from what you explained.
@@brianpinkins6218 thanks for the reply. Are all the other tracks blank because they are now midi tracks?
@@mpchead Thanks for the reply 🙏🏼
@@Kano88_beats Sorry, I didn’t explain that part very well. Those “blank” tracks will still be drum program tracks containing a program, but they won’t contain any recorded midi data. In a given sequence, only one drum track will contain recorded midi data (i.e., your song created using the program on that drum track) and the other 24 drum program tracks will not contain any recorded midi data. So you will end up having one song per sequence.
So you can't save a "drum track" and use it in two different projects. If you put a lot of work into a certain drum track program and you like to keep it and use it in different project?
You can save the program/track and load to new projects.
I try and keep every track in every sequence the same program this seemed to make sense. So now when you duplicate tracks iit carrys the program with it???if so this is short cut for me.
Yes it duplicates the program to a new track.
That's the best thing about 3.0 (including the ability to easily move tracks).
someone mentioned that you could control a dum track with several midi tracks to work around the tracks and programs being one is that possible and is it still gonna be in the final version thanks for all your videos very helpful
You can do that but it sounds like such a hard work to do
Hi there,
between yesterday and today I was using the new firmware. I understand that there is a big conceptual change and a big discussion around this topic. But my question is: what about the workflow for the live set? I understand that now it is more dynamic to produce a track in the studio. No discussion! It is much easier but I insist what happens when I want to create a live set? how should I think about the structure/architecture of the machine? If I load my live set from the MPC 2 it reads and plays it without problems but each sequence was a different song with its own tracks. This is no longer the case now. If each sequence had let’s say 5 tracks each. Now it looks all together, there is no way to discriminate which tracks each sequence contains. So now I have to see all the tracks of all the sequences in a sequence, which is very chaotic. I’m not trying to start a debate, I’m trying to get someone to help me understand. I have the feeling that MPC3 is more like a DAW: Logic, Sonar, Protools, Cubase, etc and therefore it is not ready to build a live set.
So sorry, but I can't agree with you that it's exactly the same.
Thanks
Where did I say it is not exactly the same? Watch my video on end of a legacy workflow. Thanks for sharing
@@mpchead sorry but in minute 14:33 you say: ...but the workflow is essentially the same... and you didn't mention nothing about this BIG CHANGE on the concept of the workflow to do live sets. In fact is a big discussion in this moment. They changed the essence of the machine's architecture. please don't misunderstand me. I don't want to criticise you. You have done a great video and a great job. I really like your channel. But this topic I mention is a big discussion at the moment, it has a lot of frustrated users on the forum. Maybe you already have it in mind but you could make a video about this topic. Thank you very much and congratulations for your great job!
yeah even with the clarifications about mutes and the song -> arrangement potential you highlighted in the earlier video, this still seens to break too much of what i've been doing with this machine since i've had it. automatically deleting programs because i try to switch between a few i'm auditioning? ayfkm? so i need a bunch of duplicate tracks in my project structure? like, i wouldn't be the least bit sour if this were a new device or an alternate Force-for-MPCs fork while they continued bug fixes and workflow improvements on the pre-3 platform. but this is not an upgrade to me, a person who already owned a current gen MPC. yes you can do most of the same things but that is true about Ableton vs FL Studio and yet no one wants to have to switch suddenly because the developer they'd invested years of their creative life with suddenly decided that actually the other company's DAW is sexier. i do not understand declaring "the workflow hasn't changed" and "everything is pretty much the same" while you detail structural level changes to projects. i also don't feel like i can trust the backward compatibility with older projects as being much more than theoretical when it is effectively converting them to a new format. being able to touch up songs in arrangement and create better transitions is cool in theory, but ultimately will still be part of what i'd use a computer DAW for even if i **do** transition to MPC 3. beyond that, reordering effects is the only part that has really tempted me and it's like... i've been used to that stupid needless limitation for almost 5 years since I bought an MPC (specifically an MPC not a Force I must note...) so i think i'll be able to continue surviving around it. 4-5 years of semi-regular semi-decent updates was... semi-alright for a product support lifetime. i don't mind some of the DAW features but i recognize that i'm in a tiny percentage of the reaction out here (and the fact that even ONE of us is less than euphoric seems to bother some people more than these issues actually bother us!) and it's okay that this will probably be my last MPC from date of manufacture. it's plain to see that they're going to ride this $$$ train as far as they can, and i can't even really blame the developers for it.
You don't need to delete the track/program if you don't want to, you can just load the new program to a new track, and yes you'll have a bunch of different track in the end. I don't think the compatibility will be there at all between 2.0 and 3.0. Good on you to speak out and express your thoughts.
Edit: Ahhh nevermind I commented too soon, you answered my question 👍
Over the years I’ve seen tons of new MPC users struggle with the mental model behind Sequences, Tracks and Programs. While this new approach may limit the creativity of a few, it makes a ton of more sense to the many.
Plus I’ve always run into problems when I start mixing programs and tracks around. Song mode doesn’t work anymore once you do that. So the decision to bind them into one makes a ton of sense to me, sorry.
What you said is all correct. But some of us prefer the other way. Why can't people just accept that. We are not all alike, you have your preferences and I have mine.
It's going to be easier for less experienced people and is probably fine for everyone else, as long as they didn't take away the functionality of the programs themselves (eg. Program level effects). My issue is that Akai probably did take away things. For example, track mutes per sequence is gone, which makes song mode useless.
@@s.gharavi1614 it’s been confirmed that Akai have fixed that issue now.
Yes, I heard they added back track mutes! I'm so glad!
So it sounds like MPCs just moved away from people who used them for live gigs and creative jamming, and became more of a "production only" machine. That's too bad. I hate losing old, trusted features to make way for new. Can't we have both?
Why can't they just build a new sampler with all this new features. I don't get it
@@mpchead well they did, it's force akai, is that functionality brought over the mpc. this makes even less sense
I think there's workarounds for the programs, but the deletion of independent track mutes per sequence is a deal killer.
they mess uo w the natural mpc workflow ☹️
@mpchead Hey Marlow, great video thank you for that.
Now imagine my workflow regarding stem separations.
After separating the stems from my main sample, I start creating my beat with the original sample. Once the first tracks are up, I often love it to change the original sample within my tracks to the programs 'Other' or 'Bass' to hear how it sounds and with the benefit that my grid events stay intact. Hope this makes sense somehow. How should i do this right now? is this even possible? And is it possible to choose programs from my project pool instead of browsing thru my whole sample library all the time? thanx alot for clarification.
Interesting. Do you know an easy way to remove just the drums from a sample using the Stems? I was thinking about just resampling. Will that work?
@@PeteOnTheBeat This is how i would do that: Go to sample edit mode and select your sample. Then select "Create Stems" and activate all options (Vox, Bass, Drums, Other). Make sure that both "Assign to a Pad" and "Use Trimmed Samples" are selected.
Once you have done this, save the sample as a program. Then switch to program edit mode, select your sample and you can now lower the volume of the drums to zero. Then select "Flatten Pad" and you will get your sample without drums. I know, i know.. but it just sounds more complicated than it actually is! ;) If someone know a better way to do this on a mpc, feel free to share!
I created a pad with 3 layers - all but the drums. But in program edit,to chop,it only chop the pad,for example,the bass. Totally ignores that it has 2 more layers in the same pad. Thats why I was thinking about resampling and shit. All would be just a sample,in a pad,without the drums.
Does your method allow to chop all the stems at the same time?
I haven't tried it but seeing you can change a program you would have to select "all" inside the program and change the slices to "other" or "Bass". this might work. Honestly it would be something to try and see if there's a workaround.
So, in that case, can we have more than 8 plugin tracks?
No, this is a restriction that Akai currently has in the OS. This is similarly done for audio tracks. I assume this keeps the cpu/ram from being taxed. Explore keygroups, you can load as many you like. With the linking of tracks to one program at a time, using keygroups makes a lot more sense than they did in the past. And there are a lot of good keygroups libraries available, or make you own by auto sampling.
I don't like that. Most of the time I use a template with drum programs I created previously (Kicks, snares, percussion..) so that I can immediately start. Furthermore I like to use one drum program in different tracks and have every time the same effects on it.
But you can still use that template, nothing changed that way. That second thing you mentioned yeah that's probably not gonna happen unless you use submixes or returns to send the different tracks/programs to it.
What would be great is if later on they did an update where you could select to link or synch tracks. So if you duplicate or copy the same track 3 times the one which is on top in the order can be synched to others and whatever effects or changes you make will happen to the others synched.
If I select track 1 & 2 and make changes on track one it does the same on track 2. If I then deselect track 2 but select track 1 & 3. The changes will remain on track 2 but new changes will be on 1 & 3 when I edit anything on track 1.
@@mpchead Also without having each of them linked to a track? I want to have them in my "inventory" so that I can pick any of them if I want. So that I don't need to load any during production when I decide that I need them.
Its more complicated.
More buttons pressing to work with programs.
Actually Malo just shows you can swap a drum program even as it plays from the brow screen, you have to use the plus and minus buttons.
Link me up
@@mpchead.
th-cam.com/video/8B9rU7zs4a8/w-d-xo.htmlsi=-VmHLcbad29PT-to
@@mpchead th-cam.com/video/8B9rU7zs4a8/w-d-xo.htmlsi=mzUB6KNw-zjis6C_. I thought I sent the link a week ago but I just realized it didn’t go through. Sorry for the late reply.
Cooy program? So I have to copy ALL the samples every time i want a different drum sound on a different track? So my drum program has to be copied 4 times just to have kick, snare, hat, toms on separate tracks? Dang. Thats gonna unnecessarily clog up my SD card with duplicate samples.. i used to get by with 1 drum program and only 1 of each sample. Seems inefficient..
The copying of a program does not copy samples, it only copies the program settings. Samples are the same.
@@mpchead Ok thanks. That's a relief!
I don't like that you can accidently delete an entire program and all its samples so easily. If you just switch to another type of track and then back again - all your samples are gone. Seems like a lock function or something similar would be beneficial on the tracks
Can you demonstrate in a future video on how to duplicate a track and copy events and apply a filter effect on the duplicated sample? Hope this makes sense thanks. great video by the way.
11:32 I show how to duplicate a Track/program. After you duplicate just apply the new effects to the new track.
I just got an mpc and all the recent talk about tracks/programs has me so fuckin confused. I do not get it
If you are new, just disregard all this and learn the new 3.0
@@mpchead thanks for the reply 🙏🏼
So, I just started a fresh project - I'll have a drum track. I load a drum loop to a pad and chop it. Hopefully I can still chop into a new program as we did before. But now,where's that program? I want to find it to load it into track 1,so I can then duplicate it twice so I have a kick track, a snare track and a hats track. But then, wait, I need some extras that weren't on the drum loop. So I create another program/track to add them,but wait so are heavier on the low end than other and it will mess with the mix,so I now have to duplicate that other program,or just make another. Then the sample,that I usually added to the same program where I had my dloop.
Feels like a lot of work,but it's basically what I end up doing in Ableton,with the difference that my computer has a faster cpu than the MPC and I have way more ram...
Very curious about all this... especially the converting the sample to another program.
And Marlow, can we duplicate the whole sequence as before? To create a chorus for example.
I think an easier way would be to just work within one drum track. Duplicate the low end heavier hits to other pads for additional processing. Then when you’re done sequencing the drums, just explode the drum track and rearrange the exploded tracks in the order you prefer. I agree, the old way is slightly quicker, but this way might work, too.
I am really curious to see the people's reaction towards that massive change. To me, that approach throws a lot of the classic program workflow out the window and makes everything harder to mix.
If you are working like me , which is all samples in a single program and each pad having its own track, you will have a hard time mixing.
The solution of having empty drum tracks sending notes to a track program is not intuitive as you don't get the names of samples as you normally see in a program. + Changing the midi track volume does nothing for the sample / automations need to be done on the track that has the sample.
Exploding the sequence will create multiple programs with a single sample. This is how you can work in the arranger and have everything laid out as i previously said, but that means you will have one sample per program.
So you either do the whole sequence on a single track then explode after, or if you have multiple programs (I almost always load a 909 program and create a second one with synth bounces, samples etc) you will end up having two tracks on the arranger and do your mixing process in the pad mixer.
Agreed. They really need to make these options customizable settings, rather than completely change the “CLASSIC” MPC paradigm. Somebody get Roger Lynn on the phone!
I don't understand why it will be hard mixing specially now with the new mixer window. Just go to the mixer and mix all the sounds there. Each track will be the same with an individual sound. You won't be able to have an overall effect section for the same program as before but maybe you can use sbmixes and returns to share effects. That being said I do prefer the 2.0 workflow.
I can already see what's going to happen to a lot of people including my self. Loading a new program should automatically load it to the next AVALIABLE track instead of overwriting ones that are already there.
Is there a set number of track that can be loaded or is it based on memory?
They should also give an option for call it "Associate Tracks" giving us back the option of keeping what we have now but just with different verbiage for people who want to continue the older workflow. Like Track 2 and it associate Track 2a. Track 2a would essentially be everything Track 2 is but without the sequence data. The track option could just be added in the same location as the Track type creation screen.
It will load to a new track if you want, will not erase the other track unless you want it to. I don't know about any set number of tracks, don't believe there is any limit.
I can't be bothered with that new interface 5 years on my live ain't happening.
To me 3 is far superior. One track one program - makes sense.
It definitely makes things simpler
MPC 3 method is more simple and effective
So I can no longer if I like a drum from on kit and bass from another put it on the same track Ok that sucks
You can load any sample you want to a track/program load bass samples and drum samples to the same program if you want.
so if I load up 50 programs I will have 50 tracks? this is no good Akai
Yes
Now, why will you have to load up 50 programs? Show me in what scenario you’ll have to load up 50 programs… looking for problems that aren’t there… sheesh
@@Ruben4554 I load up mad programs
@@Ruben4554 live on stage ...easy 50 pgrms
@@ArthurBlue-i1v yeah Sure… 50 programs load up with 2gb of Ram? Unless every sample on those programs are 5kb ain’t no way you’re loading up to 50 programs with 2GB Ram.. With what memory your gonna run a smooth live show. Your “what if” scenario is BS.
Linking tracks to programs doesn't make any sense, how many sounds are you going to use in one track. Why would I keep loading the same program over and over for every track. They totally changed up the entire workflow and made it slower. I like some of the new features but this ain't it.
I see what you’re saying, but to be honest, this is a workflow enhancement, especially when dealing with loading a lot of kits and/or keygroups. In MPC 2 and earlier, projects can become huge and take a while to load because you loaded up a lot of programs and forgot to delete the programs you didn’t use in your project and purge the unused samples before you saved the project. In MPC 3, if you’re dealing with a single drum program, sequence your drum on one track and then explode the track.
I think the underlying samples are the same, it's just a duplicate of the program. So it isn't that different.
Why Ave sound like a hater when it comes to your opinion? 🤔
He cleared it up, stop it man.
@ricardomilice2470 stop what? Stop being so sensitive. I didn't know he "cleared it up"
@ricardomilice2470 what do u mean "cleared it up"? You mean he apologized for kinda sounded like a ass? Maybe you can clear this up for me lol
@@RAWDILLZ I don’t mind controversy from time to time, but these 2 channels I rock with.
@@RAWDILLZ 🙄😂😂 I wish I had the energy to go back and forth.
the normal MPC ..."one sequence one song "... liveset style is over. this is really not good.......in 2.0 the program workflow was perfect and now we have to prepare a lot more and we search early in the morning on stage for the bassdrums on track 79 or 57 or .....before it was in every sequence always on track 1( that was the easy mpc way)
new is not always better .
in 2.0 the only thing to do, to have it streamlined (if you want) is to use the same programs on the same tracks in every sequence (could be easy i think ) and now everybody is talking about workflow better better and maybe i am the only one who is not convinced. i have fear for preparing a liveset and bring songs together and change something quickly in the last minute..
I hope that they will change it in future builds. There was a new build for the closed beta testers that fixed some bugs and such so it is still very much being worked on. But having all sequences sharing the same tracks and removing the clip programs is a big hit at the live aspect of the mpc.
@@MGoolas and in the past the mpc was a beast on stage
Same like you. I Will stay in 2.0
Nowhere did it say this was a forced update nobody making you do nothing stop crying
I understand what you’re saying, but most people use the MPC for production and song creation. This workflow seems to be aimed at making the workflow more intuitive and streamlined for that audience. I think the intricate user q link mapping is aimed at the live performance crowd. What would be convenient is if MPC 2 and MPC 3 could be dual booted. This feature might be on the nerdy/techy end of the spectrum and something we would most likely never see, but, it still would be cool.
Kind of bullshit is that
akai u are confused in the head
I think you need to better explain the flaws with them "merging" programs with tracks.
1) you can't assign the same program to more than one track. Duplicating a track to get a copy of that program does not "fix" this problem. If you "duplicate" a program for 5 tracks and want to make a change to a pad, you'd have to do it 5 times. Same if you wanted to add a sample, you'd have to do it on 5 different tracks.
2) if you spend time sampling to pads and build a program, then you mistakenly change the track type to MIDI, you've now lost the program you just created as well as all the samples. This is just poor design.
I really hope they bring back the ability to assign the same program to multiple tracks.
That is true and more, much more. this change is a big blow on programs control.
You can always undo, that is not that something I would worry about but I understand your point, it is bad design.
fk the MPC, Its just a daw in a box now. and a shtty one. if you are going to use a daw just use a real one.
I get what you’re saying, but the MPC(60, 60ii, 3000, 2000, 4000, 2500, and so on) has always been somewhat a of simple Daw. On a MPC, I create a track, load a program, and record midi. I create another track, load a program, and record midi. And so on. I then copy sequences, and arrange my beat in song mode. I do the same thing on the computer in Ableton. Create a loop with multiple tracks, copy the loop multiple times and arrange. Obviously, you can do more on the computer, but the basic daw features are similar between the two. The end result being a sequenced beat/song.
@@brianpinkins6218 I feel that. I think it's just becoming more computer like, With the touch screen and all the new features... A computer with a pad controller is basically a mpc X with bigger screen and with all the benefits of a computer....I don't buy the computer is to distracing argument but hey just make music on whatever, that's all what counts
MPC... The very name basically means a DAW