v1.7 - Where do we mix tracks at?

I saw this asked on the MPC software group on FB and I was asking myself the same question. If there are no more Audio channels and now they're Midi channels, where do we mix the tracks at? the MIDI channels show velocity not levels, I wouldn't use that for mixing, especially cause they don't show peak levels and I can't mix the program channels cause they have multiple sounds on them?

Also what is the reason for the midi channels and not audio channels besides less CPU usage....?

DJ A-Sharp wrote:I saw this asked on the MPC software group on FB and I was asking myself the same question. If there are no more Audio channels and now they're Midi channels, where do we mix the tracks at? the MIDI channels show velocity not levels, I wouldn't use that for mixing, especially cause they don't show peak levels and I can't mix the program channels cause they have multiple sounds on them?

Also what is the reason for the midi channels and not audio channels besides less CPU usage....?

You should now mix directly at the pad channels, or the program channels. When your in the pad mixer, you can cycle through the tracks to access the different pads on all your different tracks.

I think that there is two ways of working.Mixing inside the software or export for mixing in your DAW
For mixing inside the mpc software you use the program mixer as a single channel mixer, and then use the Program Channels in the track mixer or main window as Sub Buses for final mixing
As Hellfire stated in his in depth video, the Track Channels in the track mixer controls the overall scale of the velocity of each track and you can adjust it prior to export tracks as stems to mix in your daw.

Hi,

Mix the program or the pads, just like Hellfire said.

In another way, you may mix it after an exploded export.

Forget about "old" habits with the mpc software.

1.7 is just killin'it.

comtox wrote:
Forget about "old" habits with the mpc software.

1.7 is just killin'it.

Not even close to being true.

It's a very awkward migration to say the least.

In the initial Namm video there was an option to disable the new mixer. Was that not included in the final version?

THE ADVERSARY wrote:

comtox wrote:
Forget about "old" habits with the mpc software.

1.7 is just killin'it.

Not even close to being true.

It's a very awkward migration to say the least.

Exactly. Eager for more videos, and/or 7.1 update option

kaydigi wrote:In the initial Namm video there was an option to disable the new mixer. Was that not included in the final version?

Would be a nice option as some of us adapt to the new workflow default.

DJPureLogic wrote:

kaydigi wrote:In the initial Namm video there was an option to disable the new mixer. Was that not included in the final version?

Would be a nice option as some of us adapt to the new workflow default.

@1:21

THE ADVERSARY wrote:

comtox wrote:
Forget about "old" habits with the mpc software.

1.7 is just killin'it.

Not even close to being true.

It's a very awkward migration to say the least.

man its killing it for me too

but some of yall seem to be doing some more advanced stuff...so maybe it really does suck and i cant notice it

Overall I think the mixing is way better now, I can understand it being annoying to relearn some stuff though as well, a lot of functions on the mpc become muscle memory, so it can be pretty jarring when old behaviours are totally dropped/change. The main thing people need to get their head around is the separation of programs (global mix changes) and tracks (per sequence mix changes, as it was pre 1.7) in the mixer.

There is actually nothing new to learn. The mixer now works EXACTLY as all MPCs have worked in the past. You just now have a program channel for each program. But fundamentally, this is a legacy MPC workflow.

DJ Hellfire wrote:The mixer now works EXACTLY as all MPCs have worked in the past.

Except for pre-1.7 mpc software... A bunch of people have been posting confused by changes, and many of them may not have experience with previous MPCs, i'm pretty sure the track/program divide in the mixer is the route of the confusion, people don't understand when they're applying global/local mix changes.

Honestly I can understand the confusion, the programs were crying out for their own global mixer, but the UI for the program mixer is the same as what the ui used to be for the per-track mixer, so I can see a lot of people scrolling straight past the new track mixers showing blue velocity data and going to the program mixer expecting a per-sequence change, but getting a global one.

If you were planning on making any more videos hellfire, i think a simple 30 second look at the mixing behaviour using a single drum track on two sequences would be illustrative for users confused. lay a track, copy the seq, change the track volume on one sequence, then change the program volume as well, then change back to the original sequence to show that the track volume has reverted and the program volume stays the same.

The problem is that it broke how the MPC Software was working.
This is the typical reaction from when something is dramatically changed.

It's not so much about confusion it's more that many users may have happy with the different workflow.

I think that is causing people to dislike the change.