MPC 3 -- Let's GO!!

It's weird.. I actually don't use the Mutes, but I should. I just delete. I do understand and have enjoyed that workflow, but I would assume with enough peoples feedback, they would add that back in. A lot of people work that way so.

Yeah, MUTE States absolutely need to be saved with the sequence. BIG BIG BIG change though: all tracks are global to the project, which means that if you create 10 tracks in Sequence 1, then they will show up in sequence 2. So depending on how one used to work, it could be either a plus or a BIG minus.

No need to say that some of these changes will be very controversial. I'm mostly fine with all these changes, aside from the removal of "clip programs".

Yeah all the updates like disk streaming look great but judging from the Marlow video above they've changed the workflow so that an mpc project is basically like an ableton project with global mutes and track types that can't be changed. So its really now one tune/project like a daw? With no per track mutes what's the point of having 100+ sequences then? I hope I'm wrong about this and he has some really early version!

jpeg wrote:

ugh....this makes me question things even more. I dont need a new workflow. I use the MPC for a specific reason, the workflow!!

I dont want Ableton or FL in a stand alone box. I want an MPC. The whole structure of programs, seq, tracks, song mode is a key part of what makes an MPC what it is.

ceeprm wrote:Yeah all the updates like disk streaming look great but judging from the Marlow video above they've changed the workflow so that an mpc project is basically like an ableton project with global mutes and track types that can't be changed. So its really now one tune/project like a daw? With no per track mutes what's the point of having 100+ sequences then? I hope I'm wrong about this and he has some really early version!

I'm guessing by "Global Mutes" you mean no mutes per track in sequence/mainscreen?
I'm assuming there are Mutes for Each Track in the new TimeLine View but maybe I'm wrong?
Didn't the Akai dude do a video where he was "Muting" sections of a Track, but it seemed almost per clip. I forget. I don't wanna watch it again. That guy sorta irritates me.

BeatWilson wrote:

ceeprm wrote:Yeah all the updates like disk streaming look great but judging from the Marlow video above they've changed the workflow so that an mpc project is basically like an ableton project with global mutes and track types that can't be changed. So its really now one tune/project like a daw? With no per track mutes what's the point of having 100+ sequences then? I hope I'm wrong about this and he has some really early version!

I'm guessing by "Global Mutes" you mean no mutes per track in sequence/mainscreen?
I'm assuming there are Mutes for Each Track in the new TimeLine View but maybe I'm wrong?
Didn't the Akai dude do a video where he was "Muting" sections of a Track, but it seemed almost per clip. I forget. I don't wanna watch it again. That guy sorta irritates me.

Yeah- as I understand it the mutes now work like the mutes in ableton so no per/sequence mutes but you can mute tracks globally. While it's great to have an arranger added it looks really fiddly and I'd rather just use ableton!

Part of what makes mpcs great is the ability to make a sequence, quickly duplicate it with some tracks muted and then play around with arrangements in real time..

mpc_fan_2022 wrote:Yeah, MUTE States absolutely need to be saved with the sequence. BIG BIG BIG change though: all tracks are global to the project, which means that if you create 10 tracks in Sequence 1, then they will show up in sequence 2. So depending on how one used to work, it could be either a plus or a BIG minus.

No need to say that some of these changes will be very controversial. I'm mostly fine with all these changes, aside from the removal of "clip programs".

Looking through project folder I noticed no sequence files in evidence.
On a project imported from 2.15 with 23 sequences.

mpc_fan_2022 wrote:Yeah, MUTE States absolutely need to be saved with the sequence. BIG BIG BIG change though: all tracks are global to the project, which means that if you create 10 tracks in Sequence 1, then they will show up in sequence 2. So depending on how one used to work, it could be either a plus or a BIG minus.

Would you be able to explain the above for me please, and how it's different between 2.0 and 3.0?

My workflow has always been to create a primary sequence, usually 8 bars with all the required tracks and elements that I am looking to use in the whole song. I then duplicate that primary sequence as many times as needed for say Intro, Verse 1, Chorus, Verse 2, Chorus, Bridge, Outro etc. Basically what is needed for the full length song. Then on each sequence I just mute the tracks I don't want, make a few changes/transitions then stitch the sequences together in Song mode.

I would really appreciate it if you or someone could let me know how this workflow may or may not work in 3.0. Thanks

BeatWilson wrote:

ceeprm wrote:Yeah all the updates like disk streaming look great but judging from the Marlow video above they've changed the workflow so that an mpc project is basically like an ableton project with global mutes and track types that can't be changed. So its really now one tune/project like a daw? With no per track mutes what's the point of having 100+ sequences then? I hope I'm wrong about this and he has some really early version!

I'm guessing by "Global Mutes" you mean no mutes per track in sequence/mainscreen?
I'm assuming there are Mutes for Each Track in the new TimeLine View but maybe I'm wrong?
Didn't the Akai dude do a video where he was "Muting" sections of a Track, but it seemed almost per clip. I forget. I don't wanna watch it again. That guy sorta irritates me.

Yes. He was muting audio track blocks within the arranger but that option isn't available for midi at this time.

Feel the arranger would work better as a global track.
Insert sequences into the arranger as per song mode. Then individual midi blocks from each sequence on the timeline could be muted or edited.

Planemo wrote:

mpc_fan_2022 wrote:Yeah, MUTE States absolutely need to be saved with the sequence. BIG BIG BIG change though: all tracks are global to the project, which means that if you create 10 tracks in Sequence 1, then they will show up in sequence 2. So depending on how one used to work, it could be either a plus or a BIG minus.

Would you be able to explain the above for me please, and how it's different between 2.0 and 3.0?

My workflow has always been to create a primary sequence, usually 8 bars with all the required tracks and elements that I am looking to use in the whole song. I then duplicate that primary sequence as many times as needed for say Intro, Verse 1, Chorus, Verse 2, Chorus, Bridge, Outro etc. Basically what is needed for the full length song. Then on each sequence I just mute the tracks I don't want, make a few changes/transitions then stitch the sequences together in Song mode.

I would really appreciate it if you or someone could let me know how this workflow may or may not work in 3.0. Thanks

Pretty much how I work.

Now if you don't want unique drum programs /keygroups/plugins per track you would have to create a fake program with a blank track and send midi from midi tracks with midi data.

Much like the old track mute workaround.

Mute the midi track.

In fact. I need to test if midi track mutes are global too. Haven't delved too deeply. Spending most of my time trying to make multiple program projects play nicely.

A lot of faffing. Especially when you want to hit edit button and have to navigate to the fake program track.

Planemo wrote:

mpc_fan_2022 wrote:Yeah, MUTE States absolutely need to be saved with the sequence. BIG BIG BIG change though: all tracks are global to the project, which means that if you create 10 tracks in Sequence 1, then they will show up in sequence 2. So depending on how one used to work, it could be either a plus or a BIG minus.

Would you be able to explain the above for me please, and how it's different between 2.0 and 3.0?

My workflow has always been to create a primary sequence, usually 8 bars with all the required tracks and elements that I am looking to use in the whole song. I then duplicate that primary sequence as many times as needed for say Intro, Verse 1, Chorus, Verse 2, Chorus, Bridge, Outro etc. Basically what is needed for the full length song. Then on each sequence I just mute the tracks I don't want, make a few changes/transitions then stitch the sequences together in Song mode.

I would really appreciate it if you or someone could let me know how this workflow may or may not work in 3.0. Thanks

You'll still be able to create the different sequences for verse/chorus etc but your track type and order will now be the same for all sections and the mutes will act globally across all sequences. So if you mute the drums in verse 1 the drums will be muted for the chorus, verse 2 etc etc..

J.O.BEATS wrote:

jpeg wrote:

ugh....this makes me question things even more. I dont need a new workflow. I use the MPC for a specific reason, the workflow!!

I dont want Ableton or FL in a stand alone box. I want an MPC. The whole structure of programs, seq, tracks, song mode is a key part of what makes an MPC what it is.

Exactly this

So we're lookin at an MPC that's not exactly an MPC anymore. It does so much shit it almost feels like a DAW. And it's something I purchased to get away from a DAW. So I might as well use a DAW because it's faster that this pseudo daw with a touch screen.

Is this it?

pedro_oliveira1993 wrote:So we're lookin at an MPC that's not exactly an MPC anymore. It does so much shit it almost feels like a DAW. And it's something I purchased to get away from a DAW. So I might as well use a DAW because it's faster that this pseudo daw with a touch screen.

Is this it?

Nailed it on the head!

pedro_oliveira1993 wrote:So we're lookin at an MPC that's not exactly an MPC anymore. It does so much shit it almost feels like a DAW. And it's something I purchased to get away from a DAW. So I might as well use a DAW because it's faster that this pseudo daw with a touch screen.

Is this it?

its still an MPC; adding an arranger does not stop it being a MPC, some workflows have been speeded up or changed