Literally everything I’m seeing people speak on about MPC 3.0 was exactly how I felt when the arranger came to the Force. After learning it, I developed a completely new way of making music standalone. Akai slapped MPC users over the head with this. Funny thing is, I saw countless comments begging Akai to put the arranger on the MPC when it dropped for the Force. I NEVER thought they would actually do it cuz I figured the arranger was a Force selling point. I was wrong lol I feel that the arranger on MPC is going to bring about multiple workflows. Want to combine sequences? Throw it in song mode. Want to take those combined sequences and arrange them further? Convert to single sequence and throw it in the arranger. Or not. Want to build everything in one sequence? Go ahead. There’s pretty decent amount of options with this.
Adding the containers for MIDI should be extremely straightforward to add. All the snapping, cloning (where changes in the clip is reflected in all clones of it), trimming etc., should be failry easy to implement. There's a lot of stuff that's invisible to the users, but on the dev side, this means stabbing the project file format for storing sequencedata (which, iirc is/was stored separately from the project data, which complicates things a lot) and storing everything in these new containers. I would love it if the clips were like audio clips that you could save and recall and reuse, basically just storing them as MIDI files.
Definitely appreciate your testing & the way they are rolling this one out tbh. I am excited about it but may want will hold out until it’s out of beta even tho I signed up
you are kinda addressing why they are making it a public beta, its such a stark change in the way you do thing they need the feedback to know if its the right way they are going. The amount of force user is relatively small and before they can force it on others the need a large amount of feedback
I fully agree. MIDI regions (as you mentioned in another video) would be a killer feature. It wouldn't be impossible to develop as you mention that initially the track is a full region, which could be split or when duplicating could be already split. I wish the MPC 3 public beta on standalone be long. It'd make sense and in accordance why they don't want to come out with the MPC 3 desktop till next year. To make research and time to figure out a true next-gen MPC 3 workflow for both standalone/software. I also have high hopes... :)
I always wanted to manipulate midi data like we manipulate samples. Right now we have to save the midi data as a sample then we can manipulate as a sample
I think that’s where the screen of the X comes in handy. For MPC’s to do what they can do know compared to the last is leaps and bounds ahead. It’s pushed more to the ones who want to remain standalone.
I agree we need it to be fluid , I don’t like going round the houses just to do one simple action , however we are in beta so I hope Akai watching this video as I’m sure there’s going to be a lot of people singing the same tune , but Akai did smash it with the new coat of paint and it’s looking 100 time more professional now
I completely agree. Still in beta but yea that's good info. Once they are done with beta and implementing the changes that all the testers see needing adjustments/improvements, I'm sure we will get want we want (for the most part). The MPC community is huge and spans generations. The future looks goooooooood! Thanks for the video my dude!
So that’s why I don’t use Song mode w/using Ni, I just use ideas mode so I can mute and cut and paste like I want want to. If I wanna mute I just use volume / velocity on the time line to control mutes on the chosen tracks so it’s makes edits non destructive. I can always go back and return the volume/ velocity to its original position. Try that in Akai, I don’t see why it shouldn’t work
3.0 is great, but im excited about new machines coming out. The stem vst needs a more powerful cpu so thats clearly gonna happen. Maybe 3rd party VSTs capability. An improved touch screen.
@@andremiller1566 exactly my thoughts. I won't update to 3.0 unless it's on fresh powerful new hardware, large, screen , large internal hd, with vst support. 2.x works just fine
If it’s anything like the Akai Force arranger, it is pretty simple adding MIDI…you just can’t turn MIDI to audio at a click of a button. You would have to sequence the MIDI, solo the track and then record the audio using the Looper function. Then put the recorded sample on a regular drum track and sequence it. Whats sucks is when you want to go back and make a change. Luckily, you have the option to save MIDI scores.
@gkm214 I've never used the Looper since having these new gen MPCs in the past 7 years. I've always just make my MIDI sequences and then sample them into the MPC or Force. I then trigger them on time manually if it doesn't hit on the 1.
@@thablackkat9905 Gotchu. Yeah I always liked the Looper because it starts recording automatically when you hit Play so there’s no offset on timing, & you can set the bar length according to the MIDI you want sampled. You can even play a clip in the background while it’s recording for reference. Super useful.
should be pretty straightforward for them. Mpc live 2 got bluetooth already and it's a linux embedded subsystem. Hell, the touchscreen is more or less nothing else than a mouse.
Man... I've used all of them, MPC's, Ableton Push and Maschine. Even with all it's short comings and rare updates, NI Maschine still has the best workflow out of all of them, IMO. The Groups, Patterns, Scenes and Clips thing is so easy to understand. It just makes sense. But of course, it could use some improvements like the Clips feature. Clips is kinda clunky, but it works. If Native Instruments would have given the Maschine software the updates it needed years ago... it would have been over for the competition(Akai MPC's). Maschine 3.0 software is being released later this year. I'm very curious to see the improvements to the software. I also think NI will release a new Maschine MK4 controller to go along with the 3.0 software.
@notsogood9449 Would have been over for Akai? Haha. Not when they've released 5+ new hardware units and 10+ FREE firmware/software updates and countless plugins/instruments over the last four years while NI is going under, being bought out by private equity firm. You're delusional.
You are correct. If they cant compete with the logic ,the cubase,the studio one, the nuendo. Then its no sense of this DAW type workflow. MPC 3 is trying to introduce a DAW workflow to a hardware unit that was never supposed to be software based. For us its a step backwards. Introducing a NEW workflow on a unit that worked for 30+ yrs is weird and strange. Whats the purpose of this DAW type workflow on a standalone machine? Till they can figure it out and give users those answers. It'll always be a work in progress. Because the previous work WORKED for 30+ yrs 💯
MPC has ALWAYS been software based, the original's software was written by a team led by Roger Linn, version 3.10 of which can be downloaded from his official website. Without the software it's just a useless block of metal and plastic. Yes, it appears that version 3 of the modern hybrid MPCs departs from the workflow of the legacy MPCs, but hybrid MPC users don't have to upgrade to 3.0. Just like some producers still use the legacy MPCs and some FL Studio users still use old versions of the software, hybrid users can stick with version 2.x, until they are ready to learn the 3.0 workflow, if ever.
Literally everything I’m seeing people speak on about MPC 3.0 was exactly how I felt when the arranger came to the Force. After learning it, I developed a completely new way of making music standalone. Akai slapped MPC users over the head with this. Funny thing is, I saw countless comments begging Akai to put the arranger on the MPC when it dropped for the Force. I NEVER thought they would actually do it cuz I figured the arranger was a Force selling point. I was wrong lol
I feel that the arranger on MPC is going to bring about multiple workflows. Want to combine sequences? Throw it in song mode. Want to take those combined sequences and arrange them further? Convert to single sequence and throw it in the arranger. Or not. Want to build everything in one sequence? Go ahead. There’s pretty decent amount of options with this.
Tru they should include strum and chord editing in the arranger
Adding the containers for MIDI should be extremely straightforward to add. All the snapping, cloning (where changes in the clip is reflected in all clones of it), trimming etc., should be failry easy to implement.
There's a lot of stuff that's invisible to the users, but on the dev side, this means stabbing the project file format for storing sequencedata (which, iirc is/was stored separately from the project data, which complicates things a lot) and storing everything in these new containers. I would love it if the clips were like audio clips that you could save and recall and reuse, basically just storing them as MIDI files.
3 is a good step and I welcome it. Hope they will release the software early next near.
September please
The old 2.x song mode was idea for me.
Definitely appreciate your testing & the way they are rolling this one out tbh. I am excited about it but may want will hold out until it’s out of beta even tho I signed up
you are kinda addressing why they are making it a public beta, its such a stark change in the way you do thing they need the feedback to know if its the right way they are going. The amount of force user is relatively small and before they can force it on others the need a large amount of feedback
I fully agree. MIDI regions (as you mentioned in another video) would be a killer feature. It wouldn't be impossible to develop as you mention that initially the track is a full region, which could be split or when duplicating could be already split.
I wish the MPC 3 public beta on standalone be long. It'd make sense and in accordance why they don't want to come out with the MPC 3 desktop till next year. To make research and time to figure out a true next-gen MPC 3 workflow for both standalone/software. I also have high hopes... :)
I always wanted to manipulate midi data like we manipulate samples. Right now we have to save the midi data as a sample then we can manipulate as a sample
I think that’s where the screen of the X comes in handy. For MPC’s to do what they can do know compared to the last is leaps and bounds ahead. It’s pushed more to the ones who want to remain standalone.
Really good insight. Hopefully those changes make the experience better if they happen.
I agree we need it to be fluid , I don’t like going round the houses just to do one simple action , however we are in beta so I hope Akai watching this video as I’m sure there’s going to be a lot of people singing the same tune , but Akai did smash it with the new coat of paint and it’s looking 100 time more professional now
I completely agree. Still in beta but yea that's good info. Once they are done with beta and implementing the changes that all the testers see needing adjustments/improvements, I'm sure we will get want we want (for the most part). The MPC community is huge and spans generations. The future looks goooooooood! Thanks for the video my dude!
That's what I said about the force they have the audio in blocks but the midi data is floating around
I need to watch a video about just the arrangement
So that’s why I don’t use Song mode w/using Ni, I just use ideas mode so I can mute and cut and paste like I want want to. If I wanna mute I just use volume / velocity on the time line to control mutes on the chosen tracks so it’s makes edits non destructive. I can always go back and return the volume/ velocity to its original position. Try that in Akai, I don’t see why it shouldn’t work
Mouse control in the 3 software will be much better than finger control in the 3 standalone.
3.0 is great, but im excited about new machines coming out. The stem vst needs a more powerful cpu so thats clearly gonna happen. Maybe 3rd party VSTs capability. An improved touch screen.
@@andremiller1566 exactly my thoughts. I won't update to 3.0 unless it's on fresh powerful new hardware, large, screen , large internal hd, with vst support. 2.x works just fine
Two things....
1. Money
2. Connections
That's the truth
Huh ? 😂😂
You guys just got the woo! Now it’s busted down to like Native Instruments song mode which to me sucks. Akai needs to change that bike asap
Does anyone know when we get MPC 3
They need to make it very simple to add midi tracks and route them to tracks also!!
If it’s anything like the Akai Force arranger, it is pretty simple adding MIDI…you just can’t turn MIDI to audio at a click of a button. You would have to sequence the MIDI, solo the track and then record the audio using the Looper function. Then put the recorded sample on a regular drum track and sequence it. Whats sucks is when you want to go back and make a change. Luckily, you have the option to save MIDI scores.
@gkm214 I've never used the Looper since having these new gen MPCs in the past 7 years. I've always just make my MIDI sequences and then sample them into the MPC or Force. I then trigger them on time manually if it doesn't hit on the 1.
@@thablackkat9905 Gotchu. Yeah I always liked the Looper because it starts recording automatically when you hit Play so there’s no offset on timing, & you can set the bar length according to the MIDI you want sampled. You can even play a clip in the background while it’s recording for reference. Super useful.
@@thablackkat9905 No hate here. That's I worked with 4000!!
I would love the ability to add a Bluetooth mouse
should be pretty straightforward for them. Mpc live 2 got bluetooth already and it's a linux embedded subsystem. Hell, the touchscreen is more or less nothing else than a mouse.
Man... I've used all of them, MPC's, Ableton Push and Maschine. Even with all it's short comings and rare updates, NI Maschine still has the best workflow out of all of them, IMO.
The Groups, Patterns, Scenes and Clips thing is so easy to understand. It just makes sense. But of course, it could use some improvements like the Clips feature. Clips is kinda clunky, but it works.
If Native Instruments would have given the Maschine software the updates it needed years ago... it would have been over for the competition(Akai MPC's).
Maschine 3.0 software is being released later this year. I'm very curious to see the improvements to the software. I also think NI will release a new Maschine MK4 controller to go along with the 3.0 software.
@notsogood9449 Would have been over for Akai? Haha. Not when they've released 5+ new hardware units and 10+ FREE firmware/software updates and countless plugins/instruments over the last four years while NI is going under, being bought out by private equity firm. You're delusional.
I agree, keep going back to maschine.
Yea stem’s definitely need a new hardware cpu or a way you can expand the current cpu RAM
I think i head it been said a mustard seed of faith can move a mountain well if akai is the mountain machine gotta ⛰️ everest in front of them jk 😂😂😂
You are correct. If they cant compete with the logic ,the cubase,the studio one, the nuendo. Then its no sense of this DAW type workflow. MPC 3 is trying to introduce a DAW workflow to a hardware unit that was never supposed to be software based. For us its a step backwards. Introducing a NEW workflow on a unit that worked for 30+ yrs is weird and strange. Whats the purpose of this DAW type workflow on a standalone machine? Till they can figure it out and give users those answers. It'll always be a work in progress. Because the previous work WORKED for 30+ yrs 💯
MPC has ALWAYS been software based, the original's software was written by a team led by Roger Linn, version 3.10 of which can be downloaded from his official website.
Without the software it's just a useless block of metal and plastic.
Yes, it appears that version 3 of the modern hybrid MPCs departs from the workflow of the legacy MPCs, but hybrid MPC users don't have to upgrade to 3.0.
Just like some producers still use the legacy MPCs and some FL Studio users still use old versions of the software, hybrid users can stick with version 2.x, until they are ready to learn the 3.0 workflow, if ever.
🫡👍🏾🫡 I watched both videos grate job well done enjoyed the First experience master class👏🏾👏🏾👏🏾