Your comments at 5:30 or so are inaccurate. If you copy a track to a new track, the MPC does not create a new copy of the audio data, it pulls the same audio loaded into memory. Duplicating an audio track does not use more memory. The only problem is, the inability or limit of 4 effects per track. They could easily lift this limit, as well as lifting the limit on the number of VST's in a track and this entire problem goes away. I support the change Akai has made, it is smartly done such that using the same audio track for multiple audio tracks does not use more memory or CPU, and you can test this pretty easily. Load a 5 minute wav file into a track, then check your memory usage, then create a new track and use the same five minute audio track, your memory usage will not change. By the way, disk streaming now exists, so you dont even need to load the audio file into memory, so the entire argument about having audio tracks consuming memory is a moot issue.
Okay, you are so smart, but haven’t been with mpc long enough I guess… what if you need to rearrange some slices? (We always do that) so do that in ALL duplicated tracks What if we need to change attack/ decay/ offset and so on (we always do that) We’ll, again, you need to change it in AALL duplicated tracks Pitch, mute target, simultaneous play Well, it’s seems you are not using sampling as profound as many do, sorry But the process became much worse and much more complicated
@@MastaKraftprod This is not true at all. One big long track. You slice it up. Then export the slices to their own pad in the same track (or hell, a different track if you prefer). Create copies of the tracks with your slices so you have several duplicate tracks of the original slices, make sure you keep one track UNTOUCHED from the original, unless you know the changes you are going to make will be changes you want in all versions of the tracks containing your copied splices. Change each track as you need to. Memory usage will not increase. This was my original statement, you are not consuming more memory by reusing samples in new tracks. The limitation of 8 fx chains (four on the original track and an additional four coming from the sub send bus) is, well, a limitation, but one that should not be much of an issue for most people, especially if you take the time to process the audio beforehand. For example, if you are going to use a stereo widener on all the slices from the track, before you slice the track up, apply the stereo widener to the track so it has the settings you want it to have, export the audio from the modified audio file, then slice it up. You shouldnt need the stereo widener at all on the newly created audio track or the slices. The problem is, you want to complain. You want to work in scenarios where you have no limitations. You want to insult the intelligence of people that are telling you what you are stating is in fact, incorrect. Stand alone MPC's are not your i7 PC with 64 gb of ram. The MPC is really powerful for what it is, because the software has been written to utilize as much of the hardware as possible, but sadly, there are going to be limitations, some artifically created to limit the number of customers that experience issues (I put 12 reverbs on this track and the CPU cant seem to handle it, gee, I wonder why). I have given you a fairly easy way to work around the limitations you talked about, I addressed your incorrect statement about more memory usage for duplicating audio tracks, if you prepare by having one track with your original audio and put your slices in the same track, then simply duplicate that track and only modify the duplicated tracks, you wont be using more memory, and the limitations you describe are not going to be an issue.
I totally agree with you regarding programs. Akai needs to bring back independent programs. I think the decision to remove that ruined the traditional MPC workflow that has been around for years that many producers/beatmakers are familiar with. Why ruin what already has been proven to work? With that said, the arranger view is cool, and so is the new mixer screen. The new mixer screen is dope! I also like what Akai did to the track mute screen regarding the solo function, which makes soloing tracks much more convenient (although there was a bug in 3.0 that wouldn't let me record track solo events, which I hope they fix). Why not just go back to the 2.15 source code and "add" the new arranger view, the new mixer screen, and new track mute/solo screen arrangement (with a bug fix to make track solo events recordable, of course) to the 2.15 workflow instead of redesigning the entire interface and changing the workflow, thus making older projects incompatible in the process?
Cosign I really mis the programs. I usually load up a bunch of drum programs. Then just start playing around with paterns and switch programs to see what sounds cool. Also switching the track type. Hate the way it is now. Normally I would play something via midi. (Motif or whatever) and was able to switch easily between midi, keygroup or plugin track. With the same midi data. Now its just so much work
I kinda see where they’re going with the tracks and plugins since you can easily create a midi track and “send to” whichever program or track. But it still screws up old 2.15 projects and is an absolute pain having to set up all that up to work on old stuff. There is a lot I do like about 3.0 like the arranger and how you can access the track mixer/fx and whatnot. If they can sort out opening older files in 3.0 better then I’m all on board but it ain’t there yet.
I totally agree. I stayed on the mpc 2. The reason I bought the MPC in the first place was that I wanted to get further away from making music on my computer. I feel like this update just tries to bring the computer into the MPC. It needs more touches on the screen instead of buttons which I also don't like. If I wanted to make music that way I would've bought the Koala sampler for ipad for $5 instead of spending a $1000 on an MPC. And the projects on this are at least 30 times heavier than on the previous version. So I'm sticking with what works for me.
Finally, a video answering the big question about the lack of programs. It is really sad. I will stay in v2 until the end. Why AKAI??? makes no sense at all
because I want to keep up with the time. I don't want to end up 10 years later as an old fart saying: oh, 2.15 was great, now your new updates are shit😀
I tried beta 1 and beta 2. Both rendered previous projects created in Song mode broken. If I created a song in Cubase 12 or Ableton Live 11 and Cubase 13 and Ableton Live 12 rendered them broken, I would consider the update as defective. I think he should complain.
@@MastaKraftprod tbh Akai can't even keep their hardware up to date with the software updates. The current MPCs are low-tier PC with a DAW installed. Sure it's "standalone" but you're more than likely producing in your home.
@@MastaKraftprodhonestly you should just delete this video. Too many are switching over to hardware and newcomers are hopping on the Akai train. Too many videos showing how great this update really is even in beta. Then here you are complaining, as if you didn’t even try to learn the update in which takes 10 mins.
@@RealJohnnyHash Your point? Using buttons and pads on a seperate machine is far more satisfying then clicking in, IMO. Controllers have too much of the same problem as well. Learning off the standalone box was the only way for me. Its all preference, you dont gotta yuck someone elses yum tho.
I'm not an Akai Force expert but that is where MPC is going. And Force users seem quite happy with their workflow. So for now, we should await more Force features and trust them to get it right.
thanks for this! i stay in mpc 2 until they release mpc 3 software version. its nonsense to me make standalone beats with mpc 3 and then downgrade when you want to use software also.
Stacked variations of tracks is how I work & MPC3 has pretty much ruined it :( Working with sequences just doesn't work for me. With stacked tracks you can bring in variations of instruments without waiting for the sequence to complete and, using track mutes, you can create songs that sound more fluid and natural.
Just stay on 2.15 and hope they don't release instruments that require 3.xx. People are saying, people don't like change but, the reason I bought MPC was because I was bored using the OLD DAW workflow, now they give us it on MPC, it is the newer generation that has being moaning about wanting an arranger mode so now they gave us this OLD DAW workflow that hasn't changed since the tracker days, it is better suited to a big computer screen, this tiny 7" screen makes everything cramped in the arranger.
MPC 3.0.x is trying to be all things to all people and it fails. Ran both betas. I reported 5 bugs over the course of a week and half and downgraded the first time. The second beta lasted about 20 mins. Most of the broken stuff is still broken. Reported out the bugs and downgraded. I think that I won't upgrade when the time comes. They likely won't be supporting legacy workflows well. The party is over.
No, that's not what's happening when you duplicate a program. It doesn't create extra samples, it refers to that same program sample pool and it it's always been like that. Check your sample pool and you won't see any extra samples. One of purpose of duplicating programs is that you could have your drums sounds on separate tracks and it allows you mix on the program level instead using the pad mixer. If you look at it this way, you'd duplicate the program before you add effects to avoid copying the fx 3 or 4 times. I got this insightful information by an another Master of his Craft...Ski Beats. Akai actually got this right from the get go and it's very effective.
@@MastaKraftprod If you want to keep up with progress, you have to say goodbye to the old workflow in the longterm....it doesn't work like "wash me, but don't make me wet"....it's still a beta by the way.
That’s why I update and will stay in new platform. But when a company make a huge update, I don’t really think they should kill off something extremely important, a cornerstone. Like tomorrow you wake up and a new iOS removes keyboard completely
When I was on an MPC 2000 XL. And the program and sequence structure worked well for that unit. Then I would string up the sequences and create one large song when I was done to overlay more tracks over the entire song. On the NEW MPCs, that I owned this structure never seem to catch on with me. I know I’m not the only one. Which is why I believe a guy is changing it up. So I can understand how people that are used to old this way would be upset. But there really is more than one way to skin a cat. Also, we have to be clear. That resources are not being copied over and over as you describe. But it is definitely a different type of workflow. You have to start using the arranger method believe. Maybe Akai will pull through because I know you’re not the only person that’s complaining about this feature since it was basically a legacy workflow.m. But I feel like Akai is trying to push the MPC forward so we may have to get used to the new workflow for all the great new features that are being added. I think it’s worth it personally. I love innovation. It’s actually made it easier for me so everybody is different. You know how many times I was working on a track. And then I go on a new track and change the drums and then it messed up the drums on my previous track? That’s the downfall of that method. Yes I know I was not doing it right, but it was hard to wrap my head around it. so what is good for one person is not necessarily good for another.
Completely agree. Not enough people appreciate the programs that's why you saw so many track mute videos which were way easier to work around than this. Hopefully they bring them back.
because there i describe it in the video, use the timecode chapters. but if you dont like a snare pattern, for example, you need to go to EVERY sequence and redo this snare pattern my friend. how much time will it take?
@@MastaKraftprod that's why I'd work on one sequences until I have the "full beat" situation with all sounds that I like, and then make copies of patterns for intro, etc. Alternatively, if you like daw workflow, you don't even have to step out of the single pattern - this seems quite popular with the producers on the 3.0 it seems
Being able to create track stacks or nested tracks would be really cool. The way Logic does this is amazing. Create a master drum program track, and be able to create cloned or nested tracks that reference the top level program, to be able to quickly do new performances with that program, but always be able to go back and make tweaks. Really the way the previous Program workflow was setup it was essentially just cloning that program across tracks, I feel like that is definitely something they are working on. I think people should just keep providing feedback through the beta program that they still want access to the program level, or at least an option in settings to expose that. They are obviously listening and taking feedback so I wouldn't be surprised if it happens.
Personally with how I make music, playing all of my own parts on a keyboard or with guitar, this isn't part of my workflow, but I can see how some workflows would be changed negatively by this. My bigger issued with MPC 3 is that they got rid of odd time signatures. That was the main reason why I got rid of the Akai Force, even though I enjoyed pretty much everything else about it.
Id always find boring and not intuitive to the point i never ever bother to grab or once grabbing one, use a mpk or mpc before, but now I really like to work with the 3 Beta, its much more intuitive and daw like, thats an instant win for Akai.
5:50 & 10:39 you would point to a program with a midi track, using 'send to' its same thing as having single program being used by multiple midi tracks. as you said it, midi track weighs nothing but you didnt try use them.
Just recently got a live 2, so not familiar with the original workflow. It actually confused the hell out of me. But, why do the demos still work fine on the mpc3 beta and not your own projects from mpc 2.x?
Yea I like some aspects of it but I’m not sold on the 3.0 beta just yet especially when I load up my previous beats and they play I can’t save them tho
Didn’t really get you… Well, anything that you chop becomes a drum track, yes But drum track IS a program now, they are inseparable. There is a way to rout it through midi track that I showed, but that’s crazy to me:)
@@MastaKraftprod Your chop track is a Drum track, you created a 'MIDI' track and routed that to the original chop track. If you had created a Drum track and routed that to the original track all note mapping will be correct.
@@MastaKraftprod 'But drum track IS a program now' You can add a new drum track that doesn't 'contain' a program, which is the process I just outlined in my previous reply, so that statement is incorrect. A drum track is just a MIDI track (not a 'fake' one lol) mapped in a format to address a drum program. I wrote 'contain' as it doesn't actually contain anything, it routes MIDI to the program as it always has done. In the old OS when you created a drum track on the main page to address an existing program, you still had to point it to the desired program. In the new OS you still need to do that, but you do it in a different place (I/O in mixer). Same with plug ins, only you do that via 'MIDI' tracks now to address an existing plugin. The change as I see it is that to create a sampler program requires you now to create a track to anchor it to, sampler programs can't exist without being assigned to a track, that's it. Once you have that track created, you can point multiple drum tracks to the original via I/O routing. Can't help but think that your view of some literal MIDI tracks as being 'fake' could be a hinderance to your understanding of the architecture/routing. Are there issues? Of course, it's a Beta that is making some pretty fundamental changes to the architecture to try and achieve their intention. There are choices here for Akai and consumers. For consumers, if you want/prefer a more DAW like workflow 3 could be for you. If you prefer legacy MPC workflow maybe stick to the old OS. If you don't want to BETA test don't download 3 until the full version is rolled out.
It is beta. I've been in Akai beta previously and betas were not production ready, and full of unfinished stuff. People should wait for the final version.
The problem with programs is simple. Anyone, and I do mean anyone, please tell me what a program was on pre-3.0 in a way that makes sense to a new user to MPCs. The explanation can involve required knowledge of MIDI on a PC, that is fine, but as a new user to the MPC world, describe a program, and tell me the difference between a program and a track. Im willing to bet, very few of you can. You might even understand in your head what the difference between a program and track is, but can you verbally explain it, using words that make sense to a new user? That was the problem. It took me 6 months to wrap my head around this, coming from writing music in a DAW, because no one, not even Akai had an explanation that made sense. Now, I will give you the explanation in the next paragraph. A PROGRAM is the audio with which the MPC plays the music created in the TRACK, which is the actual notation data. In simple terms, the PROGRAM is the piano, the TRACK is the notes / velocities / key switches that play that piano. It makes zero sense to have these as separate. The real issue comes from the limitations on the number of plugins allowed per track and the number of VST's allowed per song. Lift these limitations, your problem is solved across the board, leave it on the user to deal with the CPU limitations. Now that we have disk streaming, memory usage is practically non-existent, with exception to using things like VST's, and you can always do what we have done in the PC world and bounce VST's to an audio track if you were reaching memory or CPU limitations. One other quick note, if you are needing more than 8 effect chains, maybe you need to bounce your samples to new audio tracks with some effects baked in so you dont need more than 8 fx plugins, because 8 fx plugins is alot for one track, a limitation I rarely come across.
@@joshuagardner894 a program is a container in the sampler that is created to set up samples to be addressed by the sequencer A track contains MIDI data that is sent to the program you have it routed to. It's that simple, nothing has changed in that respect.
@@KM_Mountain Yea sure, and it is a decent explanation that was never provided or explained in Akai documentation, and all of the reviews on recent generation MPC products never explained this adequately, in fact, many reviewers struggled to explain the difference. And your descriptions says nothing about VST's, drum programs, etc. I would argue, it is also an overly complex description, where in very simple terms, the program is the instrument, the track is the sheet music. A track is nothing more than the notation, without the program, it will not do anything, much like staring at sheet music. A program, much like an instrument, wont do anything without knowing what notes to play, hence, the track.
joshuagardner894, It is very simple, IMO. Program is the sound. Track is the notes. You can have the same sound with different notes (in other tracks or other sequences), and you can adjust the sound for ALL of them just setting up the program. Now, as far as I understand, with V3.0, You simply can't
@@elhombredelisboa Not true at all. Just duplicate a track. Theres even a button right at the bottom of the screen of the main page for doing this. It is very common that I write two bass lines using two different bass sounds to create a punchier main section of my tracks. Easy to duplicate the track, which copies the MIDI notation and the sound that will play, then I just change the sound that plays, and make use of the track mute, or, simply delete the MIDI data for the track I dont want to play in that sequence. Oh, but now Im going to hear that youll hit the 128 track limit. Please. My most complex songs dont even have more than 80 tracks, and that is for orchestral music I have written in a DAW on a PC, I cant remember a time where I utilized more than 30-40 tracks on a song in the MPC. It is just not a problem, it is not an issue in the real world. This update is a smart update, it really is. Yes, it makes the MPC more DAW like. Yes, it changes the way you design songs in a very fundamental way. It however does not make things more restrictive. The limitations being described are not real world limitations you will ever hit unless you artificially try, and youd have to REALLY try to hit these limitations. This 3.0 update brings the MPC very close to what a DAW like experience is, and more importantly, allows us to start writing in more complex ways that do not merely involve 8-10 instruments that we duplicate and just mute certain tracks between each sequence. People writing in the MPC world have gotten so lazy. Oh, that drop was "fire"... You mean the one where you muted all the instruments except the percussion for 1 measure and then unmuted everything and blasted the listener with a volume of sound, repeating what the listener already heard for the last three minutes? Every sequence should be truly unique. Even tho a band repeats a chord structure twice for a verse does not mean each verse heard is identical. Even tho they repeat a chord structure for the chorus does not mean each chorus should sound identical. Akai is doing what they should be doing, trying to evolve what people are writing into something more than just muting and unmuting 8-10 tracks. Anyone can write a 4-8 bar loop with 8-10 instruments and unmute / mute tracks as needed. The real art is when someone can write a 60-120 bar piece that is truly unique in each sequence, with subtle but noticeable changes that keep the entire track refreshing, fun, and enjoyable to listen to. Akai is giving us the tools to be more creative and think outside the box, write more creatively, and elevate people that write cool beats into the big boys game of real music writing, because if all you are doing is muting and unmuting tracks, that is just lazy.
@@joshuagardner894 thanks for your answer, but I'm afraid you did not understand what I meant (or I was unable to express it correctly). In short. In V2: -> 4 sequences sharing a drum program . I'm not happy with the quick and I change it in the program. It is changed in ALL the sequence using that program. Is the same case for V3? I guess it is not. You'll have to go across all you sequences and perform the changes in each of them. is that correct?. If so....we have a big issue here
I would have agreed before I actually used it - I come from a 2500 background before that a 1000 so I’m well versed in thier workflows - and tbh I thought there would be more of a change with 3.0 - and Akai alienating thier old school customer base - but nope ! Works like a dream ! And work flow is pretty much the same depending on how you make beats -
Yeah I’m not too keen on the MPC 3.0- I use my MPC X Se everyday and I have no desire to keep up with Jones’s. Perhaps i would get a force for MPC 3.0 but I don’t want my projects messed up. I load a tonne of drum programs especially my own and usually have five or drum tracks with a project. Using track mutes to mess around with what works with what. 2.15 forever! I have a dawless and studio and may the Twain shall not meet unless I’m finishing projects. ❤
No. MPC 2.0 wasn't a DAW, not a PC-like DAW anyway. The MPC 2.0 followed the ALESIS MMT-8 workflow philosophy, but on steroids. And that's why I love version 2.0. I might buy another MPC for 3.0 though... But I will always need ONE MPC with 2.0 software installed.
I have not upgraded to MPC3 Beta nor I don't intend to do so anytime soon. What I see in this video is that somehow you are forced to create a a kind of "Program Track" and the using the MIDI tracks with the MIDI events routed to that "program track". So it's replicating the old 2.0 formula but in a more cumbersome way. I don't like it.
I think Akai is lessening the legacy of the MPC by attempting to make it more like a DAW. Its corky workflow (that we have adapted to) is what makes it an MPC.
We have to be some of the most spoiled mf ever with these machines we have so many capabilities we can do there isn't a Standalone on the market that is fn with mpc just enjoy the beta
Hard to enjoy something that breaks all my previous projects. The logic (or lack there of) that I should "enjoy" having hundreds of my projects broken and about the same amount or more hours of work to repair those projects under 3.0 is foolish at best. I'm so "spoiled" that I only have hundreds of hours to make my old projects compatible with 3.0. It's a defective product thus far. Cubase 13 didn't breaks Cubase 12 projects. How us Cubase users are spoiled. Ableton Live 12 didn't break my Ableton Live 11 files. Spoiled again!
@@MastaKraftprod been using mpcs for a very long time. I am sure they will bring the workflow back to something near. At this point I see how they want you to use them and it is much faster once we old heads understand. One other way is to point midi tracks to the existing tracks. Or use a submix track for FX so that duplicating the track does not cause your fx problem. I place fx on individual pads so this does not matter.
Well you overstand ( more than understand) .Thank you .after 3 days of use I flow away that update this is just a workflow killer and a hungry CPU . The interface is busy ( to many things ) and the mixers man you just lose your brain to understand we’re you are. I don’t ever speak about that stupid linear view on small screen 😂😂😂. Is like looking Facebook On old Nokia phone.Come on The funny things is more and more MPC user just realise how easy is the 2.15 thank to the 3.00 beta .Bless to all
I uninstalled the MPC 3 Beta after one hour, and it wouldn’t save the project. I’ve had my MPC for a year and learnt the work flow, I like it to a point but the song arrange is awful and very unintuitive. The upgrade is an attempt to fix this but instead of making the arrange page more usable and the song mode more Initiative, they have made layers of complexity and it’s just awful. If this is what the MPC is going to be from now on, for me the MPC is over, I’ll sell it. I’m getting Sarato, koala, Logic and using a decent midi controller, and I’m leaning all key board shortcuts for when I’m just on my laptop.
The transition is simple, just use a more powerful computer with the same linear arranger that PC has been using since the end of trackers many years ago, I switched to MPC for change, the OLD DAW workflow was uninspiring and felt like work sat at a computer, now they bring this same old linear arranger to MPC, might as well go back to PC with more RAM and processing power and bigger screen to see everything more clearly than on a 7" screen.
dude... because there i describe it in the video, use the timecode chapters. but if you dont like a snare pattern, for example, you need to go to EVERY sequence and redo this snare pattern my friend. how much time will it take?
@@MastaKraftprodyou don’t need to redo every sequence. Let’s say you have the snare pattern how you want it in sequence 1. You just copy the events to the remaining sequences. Just take seconds.
MPC 2.x: 1. Load a drum program 2. Assign that drum program to 128 tracks Result - very little memory and cpu is used. MPC3.x 1. Attempt to load single program to multiple tracks using the [LOAD TO NEW TRACK] function. Result - You will max out the CPU and RAM attempting to load the sample program multiple times.
i am in the same situation... to cut a long story fuck akai, fuck engineer ego department, go back to 2.15 and let them alone, cause they have mental block u will never emove, way worse than mpc programs. trust me
Knock it off, it’s still in beta and better than the old workflow.. you can simply downgrade instead of misleading folk for some views. Two pages same videos both Russian and English is wild work
Cant really say its better..its just up to the users preference..its going to be better for some..its going to be worse for some...personally I really want to see what the actual public release will be after all the beta versions are done
yes and no. I want to keep up with the time. I don't want to end up 1o years later as an old fart saying: oh, 2.15 was great, now your new updates are shit😀
You’re an instructor thinking like a consumer. If you master 2.15 and teach your students the benefits, someone in your community may fork the OS which would make a neo-vailixi. Be a trailblazer, bro.
@@MastaKraftprodit’s not like someone will tell “oh he’s using 2.15 or 3.0 based on the music you put out lol come on dude you don’t have to update every time akai throw something out there lol
Well, I actually do have to upgrade, because I have the largest in students online school for mpc production and the largest UA-cam channel on mpc production (not this yet) so I need to keep up with the updates
Huhhhh? I mean faster processors and more ram would be cool, but you can do so much right now. The music you can make on these machines is insane. The spec suits its place in the market. Furthermore when you connect it to your computer the “limitations” become nonexistent as you can use as many plugins as your computer can handle. Akai is an amazing company with a great product line. Obviously there is room for improvement. All I’m saying is you can’t make heat with what you have. A processor or extra ram won’t change that.
@@eddiecardona1161Extra ram and processor means they can add more features. 🤦🏻♂️ - 8 inserts for instance The same warping algorithm as the desktop software … should I go on.
Basically you have a niche workflow. If that’s what works for you cool. But the mpc workflow has always been linear. Not stacked. Great part about mpc is there’s always creative ways to do things. Use sequences Place the sample chops you want to use into their own program track You gotta go back or recreate another niche workflow with update
![Lp. Сердце Вселенной #60 РОЖДЕНИЕ ЛОЛОЛОШКИ [Финал] • Майнкрафт](http://i.ytimg.com/vi/YoR0pAV9FVQ/mqdefault.jpg)
Your comments at 5:30 or so are inaccurate. If you copy a track to a new track, the MPC does not create a new copy of the audio data, it pulls the same audio loaded into memory. Duplicating an audio track does not use more memory. The only problem is, the inability or limit of 4 effects per track. They could easily lift this limit, as well as lifting the limit on the number of VST's in a track and this entire problem goes away. I support the change Akai has made, it is smartly done such that using the same audio track for multiple audio tracks does not use more memory or CPU, and you can test this pretty easily. Load a 5 minute wav file into a track, then check your memory usage, then create a new track and use the same five minute audio track, your memory usage will not change. By the way, disk streaming now exists, so you dont even need to load the audio file into memory, so the entire argument about having audio tracks consuming memory is a moot issue.
Okay, you are so smart, but haven’t been with mpc long enough I guess… what if you need to rearrange some slices? (We always do that) so do that in ALL duplicated tracks
What if we need to change attack/ decay/ offset and so on (we always do that)
We’ll, again, you need to change it in AALL duplicated tracks
Pitch, mute target, simultaneous play
Well, it’s seems you are not using sampling as profound as many do, sorry
But the process became much worse and much more complicated
@@MastaKraftprod This is not true at all. One big long track. You slice it up. Then export the slices to their own pad in the same track (or hell, a different track if you prefer). Create copies of the tracks with your slices so you have several duplicate tracks of the original slices, make sure you keep one track UNTOUCHED from the original, unless you know the changes you are going to make will be changes you want in all versions of the tracks containing your copied splices. Change each track as you need to. Memory usage will not increase. This was my original statement, you are not consuming more memory by reusing samples in new tracks.
The limitation of 8 fx chains (four on the original track and an additional four coming from the sub send bus) is, well, a limitation, but one that should not be much of an issue for most people, especially if you take the time to process the audio beforehand. For example, if you are going to use a stereo widener on all the slices from the track, before you slice the track up, apply the stereo widener to the track so it has the settings you want it to have, export the audio from the modified audio file, then slice it up. You shouldnt need the stereo widener at all on the newly created audio track or the slices.
The problem is, you want to complain. You want to work in scenarios where you have no limitations. You want to insult the intelligence of people that are telling you what you are stating is in fact, incorrect.
Stand alone MPC's are not your i7 PC with 64 gb of ram. The MPC is really powerful for what it is, because the software has been written to utilize as much of the hardware as possible, but sadly, there are going to be limitations, some artifically created to limit the number of customers that experience issues (I put 12 reverbs on this track and the CPU cant seem to handle it, gee, I wonder why).
I have given you a fairly easy way to work around the limitations you talked about, I addressed your incorrect statement about more memory usage for duplicating audio tracks, if you prepare by having one track with your original audio and put your slices in the same track, then simply duplicate that track and only modify the duplicated tracks, you wont be using more memory, and the limitations you describe are not going to be an issue.
@@joshuagardner894Damn! You crushed his ass 🤣🤣🤣🤣🤣🤣🤣🤣🤣
@@joshuagardner894You definitely shut his *ss down 🤣👊🏾
I totally agree with you regarding programs. Akai needs to bring back independent programs. I think the decision to remove that ruined the traditional MPC workflow that has been around for years that many producers/beatmakers are familiar with. Why ruin what already has been proven to work? With that said, the arranger view is cool, and so is the new mixer screen. The new mixer screen is dope! I also like what Akai did to the track mute screen regarding the solo function, which makes soloing tracks much more convenient (although there was a bug in 3.0 that wouldn't let me record track solo events, which I hope they fix). Why not just go back to the 2.15 source code and "add" the new arranger view, the new mixer screen, and new track mute/solo screen arrangement (with a bug fix to make track solo events recordable, of course) to the 2.15 workflow instead of redesigning the entire interface and changing the workflow, thus making older projects incompatible in the process?
Wow, so much appreciate your comment! These are my words…
You are 1% of those who DO understand the issue
@@MastaKraftprod You are very welcome. We both share the same sentiments in regards to this topic.
Cosign
I really mis the programs. I usually load up a bunch of drum programs. Then just start playing around with paterns and switch programs to see what sounds cool.
Also switching the track type. Hate the way it is now.
Normally I would play something via midi. (Motif or whatever) and was able to switch easily between midi, keygroup or plugin track. With the same midi data.
Now its just so much work
@@grouphomesite Exactly!! That's the reason I went back to 2.15 for the time being.
I kinda see where they’re going with the tracks and plugins since you can easily create a midi track and “send to” whichever program or track. But it still screws up old 2.15 projects and is an absolute pain having to set up all that up to work on old stuff. There is a lot I do like about 3.0 like the arranger and how you can access the track mixer/fx and whatnot. If they can sort out opening older files in 3.0 better then I’m all on board but it ain’t there yet.
I totally agree. I stayed on the mpc 2. The reason I bought the MPC in the first place was that I wanted to get further away from making music on my computer. I feel like this update just tries to bring the computer into the MPC. It needs more touches on the screen instead of buttons which I also don't like. If I wanted to make music that way I would've bought the Koala sampler for ipad for $5 instead of spending a $1000 on an MPC. And the projects on this are at least 30 times heavier than on the previous version. So I'm sticking with what works for me.
Finally, a video answering the big question about the lack of programs.
It is really sad.
I will stay in v2 until the end.
Why AKAI???
makes no sense at all
why simply not upgrade and that's it? there's people producing superb stuff with 15 yr old MPCs
because I want to keep up with the time. I don't want to end up 10 years later as an old fart saying: oh, 2.15 was great, now your new updates are shit😀
I tried beta 1 and beta 2. Both rendered previous projects created in Song mode broken. If I created a song in Cubase 12 or Ableton Live 11 and Cubase 13 and Ableton Live 12 rendered them broken, I would consider the update as defective. I think he should complain.
@@MastaKraftprod tbh Akai can't even keep their hardware up to date with the software updates. The current MPCs are low-tier PC with a DAW installed. Sure it's "standalone" but you're more than likely producing in your home.
@@MastaKraftprodhonestly you should just delete this video. Too many are switching over to hardware and newcomers are hopping on the Akai train. Too many videos showing how great this update really is even in beta. Then here you are complaining, as if you didn’t even try to learn the update in which takes 10 mins.
@@RealJohnnyHash Your point? Using buttons and pads on a seperate machine is far more satisfying then clicking in, IMO. Controllers have too much of the same problem as well. Learning off the standalone box was the only way for me. Its all preference, you dont gotta yuck someone elses yum tho.
I'm not an Akai Force expert but that is where MPC is going. And Force users seem quite happy with their workflow. So for now, we should await more Force features and trust them to get it right.
I had 0 issues updating. All my old songs in 2 were just fine in 3, not only that but the workflow is better for me.
Akai should have added the oldskool Atari Cubase workflow into the mpc. It’s straight forward, easy and less time consuming.
Yeah, they basically removed the "program is the instrument which you can use on multiple tracks" concept.
exactly! not ,any people noticed that
thanks for this! i stay in mpc 2 until they release mpc 3 software version. its nonsense to me make standalone beats with mpc 3 and then downgrade when you want to use software also.
On Akai force , You use clips as sequences under the same track. MPC 3 is derivate of Force OS, it will be added.
Stacked variations of tracks is how I work & MPC3 has pretty much ruined it :(
Working with sequences just doesn't work for me. With stacked tracks you can bring in variations of instruments without waiting for the sequence to complete and, using track mutes, you can create songs that sound more fluid and natural.
Only thing i love about mpc3 is the Mixer its fyre to be ableto adjust everything on the touch screen is superb
Just stay on 2.15 and hope they don't release instruments that require 3.xx. People are saying, people don't like change but, the reason I bought MPC was because I was bored using the OLD DAW workflow, now they give us it on MPC, it is the newer generation that has being moaning about wanting an arranger mode so now they gave us this OLD DAW workflow that hasn't changed since the tracker days, it is better suited to a big computer screen, this tiny 7" screen makes everything cramped in the arranger.
MPC 3.0.x is trying to be all things to all people and it fails. Ran both betas.
I reported 5 bugs over the course of a week and half and downgraded the first time. The second beta lasted about 20 mins. Most of the broken stuff is still broken. Reported out the bugs and downgraded.
I think that I won't upgrade when the time comes. They likely won't be supporting legacy workflows well. The party is over.
No, that's not what's happening when you duplicate a program. It doesn't create extra samples, it refers to that same program sample pool and it it's always been like that. Check your sample pool and you won't see any extra samples. One of purpose of duplicating programs is that you could have your drums sounds on separate tracks and it allows you mix on the program level instead using the pad mixer. If you look at it this way, you'd duplicate the program before you add effects to avoid copying the fx 3 or 4 times. I got this insightful information by an another Master of his Craft...Ski Beats. Akai actually got this right from the get go and it's very effective.
That still doesn’t solve a lot of problems of the “previous” workflow unfortunately 😕
@@MastaKraftprod If you want to keep up with progress, you have to say goodbye to the old workflow in the longterm....it doesn't work like "wash me, but don't make me wet"....it's still a beta by the way.
That’s why I update and will stay in new platform. But when a company make a huge update, I don’t really think they should kill off something extremely important, a cornerstone.
Like tomorrow you wake up and a new iOS removes keyboard completely
I wasted alot of hrs going back and forth too. How is this the only video?
When I was on an MPC 2000 XL. And the program and sequence structure worked well for that unit. Then I would string up the sequences and create one large song when I was done to overlay more tracks over the entire song.
On the NEW MPCs, that I owned this structure never seem to catch on with me. I know I’m not the only one. Which is why I believe a guy is changing it up.
So I can understand how people that are used to old this way would be upset. But there really is more than one way to skin a cat. Also, we have to be clear. That resources are not being copied over and over as you describe. But it is definitely a different type of workflow. You have to start using the arranger method believe. Maybe Akai will pull through because I know you’re not the only person that’s complaining about this feature since it was basically a legacy workflow.m. But I feel like Akai is trying to push the MPC forward so we may have to get used to the new workflow for all the great new features that are being added. I think it’s worth it personally. I love innovation. It’s actually made it easier for me so everybody is different.
You know how many times I was working on a track. And then I go on a new track and change the drums and then it messed up the drums on my previous track? That’s the downfall of that method. Yes I know I was not doing it right, but it was hard to wrap my head around it. so what is good for one person is not necessarily good for another.
subbed this was brilliant and hilarious
Completely agree. Not enough people appreciate the programs that's why you saw so many track mute videos which were way easier to work around than this. Hopefully they bring them back.
Completely agree this takes away all the flexibility that we had for creating. It's too restricting
Great video👍🏽 I will try 2.0 tomorrow. Ran into so many issues thinking it was just me. Hopefully 2.0 is similar to an mpc 2000xl & 2500 workflow.
It's STILL a Beta ... features will be added even in the beta. People love to whinge about everything even when it was completely in their control ...
I would LOVE to see USB external 1080 touchscreen support.
with mouse and keyboard support too
Why not simply use sequences for variation?
because there i describe it in the video, use the timecode chapters.
but if you dont like a snare pattern, for example, you need to go to EVERY sequence and redo this snare pattern my friend. how much time will it take?
@@MastaKraftprod that's why I'd work on one sequences until I have the "full beat" situation with all sounds that I like, and then make copies of patterns for intro, etc. Alternatively, if you like daw workflow, you don't even have to step out of the single pattern - this seems quite popular with the producers on the 3.0 it seems
Yes! Exactly
I also love working until a full beat in one sequence
Although now we cannot build variations in 1 sequence
Being able to create track stacks or nested tracks would be really cool. The way Logic does this is amazing.
Create a master drum program track, and be able to create cloned or nested tracks that reference the top level program, to be able to quickly do new performances with that program, but always be able to go back and make tweaks. Really the way the previous Program workflow was setup it was essentially just cloning that program across tracks, I feel like that is definitely something they are working on.
I think people should just keep providing feedback through the beta program that they still want access to the program level, or at least an option in settings to expose that. They are obviously listening and taking feedback so I wouldn't be surprised if it happens.
Do you really think that they consider returning it back?😕
Personally with how I make music, playing all of my own parts on a keyboard or with guitar, this isn't part of my workflow, but I can see how some workflows would be changed negatively by this.
My bigger issued with MPC 3 is that they got rid of odd time signatures. That was the main reason why I got rid of the Akai Force, even though I enjoyed pretty much everything else about it.
The upgrade is a choice, I like it very much. However people that are use to the old way have the choice to keep it.
Id always find boring and not intuitive to the point i never ever bother to grab or once grabbing one, use a mpk or mpc before, but now I really like to work with the 3 Beta, its much more intuitive and daw like, thats an instant win for Akai.
5:50 & 10:39 you would point to a program with a midi track, using 'send to' its same thing as having single program being used by multiple midi tracks. as you said it, midi track weighs nothing but you didnt try use them.
My workflow is 🗑 right now
Just recently got a live 2, so not familiar with the original workflow. It actually confused the hell out of me. But, why do the demos still work fine on the mpc3 beta and not your own projects from mpc 2.x?
MPCs without 3.0 will hold their value in the future because at some point downgrading from 3.0 to 2x wont be possible
Yea I like some aspects of it but I’m not sold on the 3.0 beta just yet especially when I load up my previous beats and they play I can’t save them tho
@ 8.20 your problem here is that your original track was a drum track. If you create a drum track and point it to the program all is good.
@14.56 in 'Track Mute Settings' you can adjust 'solo behaviour' select 'multi' to enable stacking when soloing.
Didn’t really get you…
Well, anything that you chop becomes a drum track, yes
But drum track IS a program now, they are inseparable. There is a way to rout it through midi track that I showed, but that’s crazy to me:)
@@MastaKraftprod Your chop track is a Drum track, you created a 'MIDI' track and routed that to the original chop track. If you had created a Drum track and routed that to the original track all note mapping will be correct.
@@MastaKraftprod 'But drum track IS a program now' You can add a new drum track that doesn't 'contain' a program, which is the process I just outlined in my previous reply, so that statement is incorrect. A drum track is just a MIDI track (not a 'fake' one lol) mapped in a format to address a drum program.
I wrote 'contain' as it doesn't actually contain anything, it routes MIDI to the program as it always has done. In the old OS when you created a drum track on the main page to address an existing program, you still had to point it to the desired program. In the new OS you still need to do that, but you do it in a different place (I/O in mixer). Same with plug ins, only you do that via 'MIDI' tracks now to address an existing plugin.
The change as I see it is that to create a sampler program requires you now to create a track to anchor it to, sampler programs can't exist without being assigned to a track, that's it. Once you have that track created, you can point multiple drum tracks to the original via I/O routing.
Can't help but think that your view of some literal MIDI tracks as being 'fake' could be a hinderance to your understanding of the architecture/routing.
Are there issues? Of course, it's a Beta that is making some pretty fundamental changes to the architecture to try and achieve their intention. There are choices here for Akai and consumers. For consumers, if you want/prefer a more DAW like workflow 3 could be for you. If you prefer legacy MPC workflow maybe stick to the old OS. If you don't want to BETA test don't download 3 until the full version is rolled out.
Thank you for this!
Are you not disc streaming your 5 minute long samples?
It is beta. I've been in Akai beta previously and betas were not production ready, and full of unfinished stuff. People should wait for the final version.
I think the new update is great. It definitely makes it more like a daw, but I like it. If I wanna switch to a true mpc workflow I use my 2500.
I like the update just waiting for the computer version so i wrk with it better
All my tracks are messed up😢
The problem with programs is simple. Anyone, and I do mean anyone, please tell me what a program was on pre-3.0 in a way that makes sense to a new user to MPCs. The explanation can involve required knowledge of MIDI on a PC, that is fine, but as a new user to the MPC world, describe a program, and tell me the difference between a program and a track. Im willing to bet, very few of you can. You might even understand in your head what the difference between a program and track is, but can you verbally explain it, using words that make sense to a new user? That was the problem. It took me 6 months to wrap my head around this, coming from writing music in a DAW, because no one, not even Akai had an explanation that made sense. Now, I will give you the explanation in the next paragraph.
A PROGRAM is the audio with which the MPC plays the music created in the TRACK, which is the actual notation data. In simple terms, the PROGRAM is the piano, the TRACK is the notes / velocities / key switches that play that piano.
It makes zero sense to have these as separate. The real issue comes from the limitations on the number of plugins allowed per track and the number of VST's allowed per song. Lift these limitations, your problem is solved across the board, leave it on the user to deal with the CPU limitations. Now that we have disk streaming, memory usage is practically non-existent, with exception to using things like VST's, and you can always do what we have done in the PC world and bounce VST's to an audio track if you were reaching memory or CPU limitations.
One other quick note, if you are needing more than 8 effect chains, maybe you need to bounce your samples to new audio tracks with some effects baked in so you dont need more than 8 fx plugins, because 8 fx plugins is alot for one track, a limitation I rarely come across.
@@joshuagardner894 a program is a container in the sampler that is created to set up samples to be addressed by the sequencer A track contains MIDI data that is sent to the program you have it routed to. It's that simple, nothing has changed in that respect.
@@KM_Mountain Yea sure, and it is a decent explanation that was never provided or explained in Akai documentation, and all of the reviews on recent generation MPC products never explained this adequately, in fact, many reviewers struggled to explain the difference. And your descriptions says nothing about VST's, drum programs, etc. I would argue, it is also an overly complex description, where in very simple terms, the program is the instrument, the track is the sheet music. A track is nothing more than the notation, without the program, it will not do anything, much like staring at sheet music. A program, much like an instrument, wont do anything without knowing what notes to play, hence, the track.
joshuagardner894, It is very simple, IMO. Program is the sound. Track is the notes. You can have the same sound with different notes (in other tracks or other sequences), and you can adjust the sound for ALL of them just setting up the program.
Now, as far as I understand, with V3.0, You simply can't
@@elhombredelisboa Not true at all. Just duplicate a track. Theres even a button right at the bottom of the screen of the main page for doing this. It is very common that I write two bass lines using two different bass sounds to create a punchier main section of my tracks. Easy to duplicate the track, which copies the MIDI notation and the sound that will play, then I just change the sound that plays, and make use of the track mute, or, simply delete the MIDI data for the track I dont want to play in that sequence.
Oh, but now Im going to hear that youll hit the 128 track limit. Please. My most complex songs dont even have more than 80 tracks, and that is for orchestral music I have written in a DAW on a PC, I cant remember a time where I utilized more than 30-40 tracks on a song in the MPC. It is just not a problem, it is not an issue in the real world.
This update is a smart update, it really is. Yes, it makes the MPC more DAW like. Yes, it changes the way you design songs in a very fundamental way. It however does not make things more restrictive. The limitations being described are not real world limitations you will ever hit unless you artificially try, and youd have to REALLY try to hit these limitations.
This 3.0 update brings the MPC very close to what a DAW like experience is, and more importantly, allows us to start writing in more complex ways that do not merely involve 8-10 instruments that we duplicate and just mute certain tracks between each sequence. People writing in the MPC world have gotten so lazy. Oh, that drop was "fire"... You mean the one where you muted all the instruments except the percussion for 1 measure and then unmuted everything and blasted the listener with a volume of sound, repeating what the listener already heard for the last three minutes?
Every sequence should be truly unique. Even tho a band repeats a chord structure twice for a verse does not mean each verse heard is identical. Even tho they repeat a chord structure for the chorus does not mean each chorus should sound identical.
Akai is doing what they should be doing, trying to evolve what people are writing into something more than just muting and unmuting 8-10 tracks. Anyone can write a 4-8 bar loop with 8-10 instruments and unmute / mute tracks as needed. The real art is when someone can write a 60-120 bar piece that is truly unique in each sequence, with subtle but noticeable changes that keep the entire track refreshing, fun, and enjoyable to listen to.
Akai is giving us the tools to be more creative and think outside the box, write more creatively, and elevate people that write cool beats into the big boys game of real music writing, because if all you are doing is muting and unmuting tracks, that is just lazy.
@@joshuagardner894 thanks for your answer, but I'm afraid you did not understand what I meant (or I was unable to express it correctly).
In short.
In V2: -> 4 sequences sharing a drum program . I'm not happy with the quick and I change it in the program. It is changed in ALL the sequence using that program.
Is the same case for V3? I guess it is not. You'll have to go across all you sequences and perform the changes in each of them.
is that correct?. If so....we have a big issue here
I would have agreed before I actually used it - I come from a 2500 background before that a 1000 so I’m well versed in thier workflows - and tbh I thought there would be more of a change with 3.0 - and Akai alienating thier old school customer base - but nope ! Works like a dream ! And work flow is pretty much the same depending on how you make beats -
Yeah I’m not too keen on the MPC 3.0- I use my MPC X Se everyday and I have no desire to keep up with Jones’s. Perhaps i would get a force for MPC 3.0 but I don’t want my projects messed up. I load a tonne of drum programs especially my own and usually have five or drum tracks with a project. Using track mutes to mess around with what works with what. 2.15 forever! I have a dawless and studio and may the Twain shall not meet unless I’m finishing projects. ❤
It's always been a DAW (of sorts) in a box, even going back to V1...
No. MPC 2.0 wasn't a DAW, not a PC-like DAW anyway. The MPC 2.0 followed the ALESIS MMT-8 workflow philosophy, but on steroids. And that's why I love version 2.0. I might buy another MPC for 3.0 though... But I will always need ONE MPC with 2.0 software installed.
are you sure man? so u wont be able to load old project from 2? without issue?
Ive had zero issue with loading beats from 2 to 3.
@@santaslilhelper4945 phew! thanx
I have not upgraded to MPC3 Beta nor I don't intend to do so anytime soon. What I see in this video is that somehow you are forced to create a a kind of "Program Track" and the using the MIDI tracks with the MIDI events routed to that "program track". So it's replicating the old 2.0 formula but in a more cumbersome way. I don't like it.
just a personnal analyse ...
3.0 is good for me. (just new to mpc)
Using Mpc3 feels like trying to turn a guitar into a piano. If I wanted to play piano, I would have bought one.
I think Akai is lessening the legacy of the MPC by attempting to make it more like a DAW. Its corky workflow (that we have adapted to) is what makes it an MPC.
We have to be some of the most spoiled mf ever with these machines we have so many capabilities we can do there isn't a Standalone on the market that is fn with mpc just enjoy the beta
Hard to enjoy something that breaks all my previous projects. The logic (or lack there of) that I should "enjoy" having hundreds of my projects broken and about the same amount or more hours of work to repair those projects under 3.0 is foolish at best.
I'm so "spoiled" that I only have hundreds of hours to make my old projects compatible with 3.0.
It's a defective product thus far. Cubase 13 didn't breaks Cubase 12 projects. How us Cubase users are spoiled. Ableton Live 12 didn't break my Ableton Live 11 files. Spoiled again!
This is a problem with understanding. You can still do exactly the same. Duplicate track without events.
Exactly, you duplicate tracks, making it as a separate “new” program
With doubling all the fx and so on
@@MastaKraftprod been using mpcs for a very long time. I am sure they will bring the workflow back to something near. At this point I see how they want you to use them and it is much faster once we old heads understand. One other way is to point midi tracks to the existing tracks. Or use a submix track for FX so that duplicating the track does not cause your fx problem. I place fx on individual pads so this does not matter.
Well you overstand ( more than understand) .Thank you .after 3 days of use I flow away that update this is just a workflow killer and a hungry CPU . The interface is busy ( to many things ) and the mixers man you just lose your brain to understand we’re you are. I don’t ever speak about that stupid linear view on small screen 😂😂😂. Is like looking Facebook On old Nokia phone.Come on
The funny things is more and more MPC user just realise how easy is the 2.15 thank to the 3.00 beta .Bless to all
I uninstalled the MPC 3 Beta after one hour, and it wouldn’t save the project. I’ve had my MPC for a year and learnt the work flow, I like it to a point but the song arrange is awful and very unintuitive. The upgrade is an attempt to fix this but instead of making the arrange page more usable and the song mode more Initiative, they have made layers of complexity and it’s just awful. If this is what the MPC is going to be from now on, for me the MPC is over, I’ll sell it. I’m getting Sarato, koala, Logic and using a decent midi controller, and I’m leaning all key board shortcuts for when I’m just on my laptop.
it is in beta currently
you want to the Akai development team to abandon the project? more realistic and useful maybe, use your knowledge to help users make the transition?
The transition is simple, just use a more powerful computer with the same linear arranger that PC has been using since the end of trackers many years ago, I switched to MPC for change, the OLD DAW workflow was uninspiring and felt like work sat at a computer, now they bring this same old linear arranger to MPC, might as well go back to PC with more RAM and processing power and bigger screen to see everything more clearly than on a 7" screen.
Dude is the same,Just work with sequence
dude... because there i describe it in the video, use the timecode chapters.
but if you dont like a snare pattern, for example, you need to go to EVERY sequence and redo this snare pattern my friend. how much time will it take?
@@MastaKraftprodyou don’t need to redo every sequence. Let’s say you have the snare pattern how you want it in sequence 1. You just copy the events to the remaining sequences. Just take seconds.
@@Exkoprcorrect, we can replace or merge the current sequence to any sequence we want. No needs to go into each sequence to make the change..
Have you ever played live in clubs? How convenient is it with sequences?🥲
Track mute was so cool for that
@@MastaKraftprod Do you want to switch snares while playing live....I don't think so
I still haven't upgraded to 3, I like it as is.
MPC 2.x:
1. Load a drum program
2. Assign that drum program to 128 tracks
Result - very little memory and cpu is used.
MPC3.x
1. Attempt to load single program to multiple tracks using the [LOAD TO NEW TRACK] function.
Result - You will max out the CPU and RAM attempting to load the sample program multiple times.
i am in the same situation... to cut a long story fuck akai, fuck engineer ego department, go back to 2.15 and let them alone, cause they have mental block u will never emove, way worse than mpc programs. trust me
I am more disappointed with region and events drag and drop inconvenience and sequences interaction in arranger window
were is the free drum kit that's what i'm here for!! haaaa
i found it !!! thank you Haaaaa
No it speeds up work flow for me
Yeah i dont like using ableton style on my mpc
Its in Beta!!!
yes, however its not a bug, its a feature. dont you see, that they are not considering it as a bug, for them its a new worflow
yo instead of copying programs copy sequence my guy and name that verse 1
And loop launcher!
Knock it off, it’s still in beta and better than the old workflow.. you can simply downgrade instead of misleading folk for some views. Two pages same videos both Russian and English is wild work
1: how am I misleading?
2: if this logic remains in the official release, will you apologize?
Cant really say its better..its just up to the users preference..its going to be better for some..its going to be worse for some...personally I really want to see what the actual public release will be after all the beta versions are done
😂😂😂
Downgrade back to 2. Problem solved.
yes and no. I want to keep up with the time. I don't want to end up 1o years later as an old fart saying: oh, 2.15 was great, now your new updates are shit😀
You’re an instructor thinking like a consumer. If you master 2.15 and teach your students the benefits, someone in your community may fork the OS which would make a neo-vailixi. Be a trailblazer, bro.
@@MastaKraftprodit’s not like someone will tell “oh he’s using 2.15 or 3.0 based on the music you put out lol come on dude you don’t have to update every time akai throw something out there lol
Well, I actually do have to upgrade, because I have the largest in students online school for mpc production and the largest UA-cam channel on mpc production (not this yet) so I need to keep up with the updates
@@MastaKraftprod understandable, respect
It's a beta not an update 😂
Isn’t new beta an update?
your workflows seems complicated
MPC 3 killed MPC workflow period!
We need 8GB of ram and faster processors - I’d pay 2k for it and be happy
Akai are idiots - it’s 2024 and they are clueless
Huhhhh? I mean faster processors and more ram would be cool, but you can do so much right now. The music you can make on these machines is insane. The spec suits its place in the market. Furthermore when you connect it to your computer the “limitations” become nonexistent as you can use as many plugins as your computer can handle. Akai is an amazing company with a great product line. Obviously there is room for improvement. All I’m saying is you can’t make heat with what you have. A processor or extra ram won’t change that.
This!!! #facts@@eddiecardona1161
@@eddiecardona1161Extra ram and processor means they can add more features. 🤦🏻♂️ - 8 inserts for instance
The same warping algorithm as the desktop software … should I go on.
Btw I want also better reverds
You're a "know it all" and i wish i had more thumbs to give you 👎🏾 👎🏾👎🏾👎🏾👎🏾
and you are...?
😂😂🎯
Basically you have a niche workflow. If that’s what works for you cool. But the mpc workflow has always been linear. Not stacked. Great part about mpc is there’s always creative ways to do things.
Use sequences
Place the sample chops you want to use into their own program track
You gotta go back or recreate another niche workflow with update