MPC 3 -- Let's GO!!

Apparently track mute is no longer unique per sequence, instead it works globally. I really hope they change that back of have an option to toggle either. I get persistent tracks across all sequences but the track mute workflow was genuinely one of the main efficiencies of using an MPC to draft an arrangement. Deleting notes as a work around is not the same.

Got a link to those images. I'd love to be proven wrong on this.

Its right on the screen image soon as you open the page. Top left of the screen
https://www.akaipro.com/mpc3.html

I really really hope it will be implemented at a later update because as of now it is not available (I have it running on my liveii already). Disk streaming and clips will take the live / remix situation of the mpc on a whole new level

robleighton22 wrote:Apparently track mute is no longer unique per sequence, instead it works globally. I really hope they change that back of have an option to toggle either. I get persistent tracks across all sequences but the track mute workflow was genuinely one of the main efficiencies of using an MPC to draft an arrangement. Deleting notes as a work around is not the same.

Uh ? Track mutes are the main pivot of my workflow... Losing per-sequence track mutes would be a major regression.

will disk streaming have any impact on the stems ? cos i recall akai in their stems guidance were saying not to have too many things in memory when running stems; and in this tubedigga vid; he says disk streaming removes any RAM limiations?

stem separation is an offline process so streaming won’t have any impact on it because once you hit the „separate” button, everything else grinds to a halt BUT…
since disk streaming creates pointer to an object on disk, you will have to save the stems first in order to utilise them with streaming. I wouldn’t be too exited about streaming multiple kits though, I’ve seen one of the internet numpties getting excited for streaming drumkits. While it might work for one, maybe two kits, you will quickly hit an I/O wall if you suddenly try to access a dozen of files at the same time imho.

robleighton22 wrote:Apparently track mute is no longer unique per sequence, instead it works globally. I really hope they change that back of have an option to toggle either. I get persistent tracks across all sequences but the track mute workflow was genuinely one of the main efficiencies of using an MPC to draft an arrangement. Deleting notes as a work around is not the same.

This is bad news- one of the things I like about mpcs is the ability to create arrangements on the fly and to have different mutes/sequence. Its also great for live performance.
I really don't want to be moving very tiny blocks around on a tiny screen to achieve this!
A shame as lots of the other features look great.

ceeprm wrote:

robleighton22 wrote:Apparently track mute is no longer unique per sequence, instead it works globally. I really hope they change that back of have an option to toggle either. I get persistent tracks across all sequences but the track mute workflow was genuinely one of the main efficiencies of using an MPC to draft an arrangement. Deleting notes as a work around is not the same.

This is bad news- one of the things I like about mpcs is the ability to create arrangements on the fly and to have different mutes/sequence. Its also great for live performance.
I really don't want to be moving very tiny blocks around on a tiny screen to achieve this!
A shame as lots of the other features look great.

the akai force allows track muting so I doubt it'll be missing in mpc os 3.x.
Not to mention "track mute" is a basic feature in ANY DAW

cocosushi wrote:
the akai force allows track muting so I doubt it'll be missing in mpc os 3.x.
Not to mention "track mute" is a basic feature in ANY DAW

It will definitely have track mutes but it looks like they are global for all sequences instead of per sequence. So say you have one sequence running with say drums/bass/synth/vox and you want to hit next sequence to a sequence that has just the vox playing and everything else muted that won't be possible..

ceeprm wrote:

cocosushi wrote:
the akai force allows track muting so I doubt it'll be missing in mpc os 3.x.
Not to mention "track mute" is a basic feature in ANY DAW

It will definitely have track mutes but it looks like they are global for all sequences instead of per sequence. So say you have one sequence running with say drums/bass/synth/vox and you want to hit next sequence to a sequence that has just the vox playing and everything else muted that won't be possible..

Understood- maybe it could be solved via an option in global settings to enable global track mutes vs seq. based track mutes in a future update

ceeprm wrote:

cocosushi wrote:
the akai force allows track muting so I doubt it'll be missing in mpc os 3.x.
Not to mention "track mute" is a basic feature in ANY DAW

It will definitely have track mutes but it looks like they are global for all sequences instead of per sequence. So say you have one sequence running with say drums/bass/synth/vox and you want to hit next sequence to a sequence that has just the vox playing and everything else muted that won't be possible..

If that’s the case then it’s just a matter of setting mutes of corresponding tracks in automation at the beginning of each sequence. Not much more work than going into mute screen to disable them there

It's a pretty bad workflow change tbh. The speed in which you can setup an arrangement using the per sequence track muting was a very major part to using and MPC.

Maybe Marlow Diggs got it wrong, although he does demo the limitation in his video but perhaps there is a setting to toggle track mute behaviour.

I really don't see much value in global track muting. Like it's useful for live playing but even then per sequence muting has more use.

Hopefully there will be an option to toggle from global to track mutes. What I love about mpcs (coming from a 1000) is the ability to just hit record hit pads and create music. If I want a Daw experience il just use ableton! That may just be me tho..

maybe if everyone in the beta says they want programs back, maybe they will add it back?

dustyslices wrote:If that’s the case then it’s just a matter of setting mutes of corresponding tracks in automation at the beginning of each sequence. Not much more work than going into mute screen to disable them there

In theory, yes - and that is what I do to automate muting the TB-3 with the MX-1's own mute because the TB-3 doesn't receive MIDI notes but plays it's own sequence (I actually set volume to 0 rather than mute, because that leaves the volume automation at hand for later use). But playing the track mutes on the MPC is a major part of how I get a feel of what the song's parts can be made of, and validating that with next seq chaining of sequences with different track mutes combinations is what I do before going into song mode... That would still be possible, but setting playhead to zero (so I don't have to nudge the inserted event later), Menu+Pad 1 to go to List Edit, then inserting the correct CC and entering a value is a bit more work and not joyfully spontaneous at all.

The problem comes from not having a container element between track and MIDI event. For audio there's the "section" thingy but for MIDI there's nothing. And that's why they show on the video how "easy" it is to select a range of MIDI notes and delete it. It's a pathetic brainfart workflow really. They forgot to show how to move such a MIDI event section or split it to two sections.