MPC 3 -- Let's GO!!

moonlake wrote:exactly.

we were talking about OS 3 where exactly this was said to be impossible.
And duplicating was suggested as workaround and I was just explaining that it isnt practical.

I didn't hear anyone say sending MIDI data from one track to another was impossible. I saw Loopop do it or said you can do it as a workaround.

At 18:37 Tefty describes routing midi to other Instruments. He's talking about muting mdi instead of audio, but it does suggest you can route the midi where you want.

I see, then I misunderstood. I thought you were restricted to one track per program.

You are not only restricted to one track per program, you are also restricted to one program per track. There are no trackless programs, and there are no programless tracks.

Instead of routing MIDI from a track to a program, you send MIDI from a track to another track.

moonlake wrote:
And I take that back that the screen design is on a new level.
I think its too contrasty and cluttered.



Channel strip. why. where s the improvement, maybe I just dont get it but why had these things have to change at all?

so basically it seems people wanted to keep the current layout and design; and maybe just change the grey to black, then add the arranger, disk streaming and mixer view.

Im not against that veiwpoint, I did not think there needed to be complete UI layout redesign, just perhaps the ability to customise the colours.

But seems Akai wanted to break from the old, maybe the colours are a bit bright, i would not have the multi colours as i prefer a more neutral look.

HouseWithoutMouse wrote:You are not only restricted to one track per program, you are also restricted to one program per track. There are no trackless programs, and there are no programless tracks.

Instead of routing MIDI from a track to a program, you send MIDI from a track to another track.

Which is a much less efficient method.
What happens when you hit program edit or try to record automations from the midi track you're editing.
So now you can have for eg 3 midi tracks pointing to a program but only one lane of automation.

When is it actually available? I thought it was out now the but it appears just to be a sign up.

jpeg wrote:

pedro_oliveira1993 wrote:
And Jpeg is what it is. "I was right in an internet forum. Suck it". Faith is faith. No point in arguing. Even if the mythical MPC3 is ......SUSPENSE........ the Force OS.

All the casuals singing praises will most likely be the first to abandon/complain about how convoluted it is because it's not exactly like "insert DAW" or how it's slower because it takes X clicks, pinching the touchscreen, etc. Lack of effort. The reason these things exist is their differences. Limits breed creativity.
If Im gonna use something that clearly ends up being a dawless DAW i'm probably gonna start thinking about QoL, comfort and power.

I also have a Push2, a Maschine+ (which I love to death because it is limited) and an SP404. Imagine getting mad because they don't work like an MPC.

u can use MPC in a limited way if that fits ur workflow; u dont have to use every new feature that is in 3.0

u call anyone who is not tied to the legacy MPC workflow a casual; maybe they simply have a different perspective, perhaps they dont over value the old workflow just cos its legacy.

Big chin dave always said the mpc 3.0 would be based on the force; because he said this so long ago people dismissed that intel.

People also dimissed bolo's intel about 3.0 coming this year, but I did not, as I enjoyed the speculation on Akai's next move.

Well seems like I can't. At least as of now. The point of the mutes was flexibility. Combined with all they're offering, it would be even better. So, in all truthness it would be less limited. But, like I said before, I can always not update. I bought it for what it was, not for the promise of what it could be. Even if there are a few misses here and there and a lot of things to improve, they've been doing a terrific job with supporting these devices.

And no I'm not calling everyone a casual. People use gear in different ways. But clearly there are plenty of users who like this workflow. So there's that. What I did see was a lot of people complaining about how an MPC was this and that because it wasn't like Ableton and how it should be like a DAW. Meaning, I bought something, didn't bother learning it or do research. I wanted a portable and underpowered version of what I already have. So that must mean the problem is the device, not me. And that's so ironic that I can barely hold my laugh. Because it clearly shows the need for being catered with everything. They want it and they want it now. How about learning? Things are different for a reason. And it's a balancing act. Doesn't to much? It's too limiting. Does a lot? Well maybe I'll use a DAW since it's probably faster. Don't like it? Try something else.

I own a lot of alternatives. And I don't sit around complaining that they're not something else. But it's better to get spoon fed of the hype and youtube videos where everything is better because it's new.

My main point with this update is, introduce whatever you want. A lot of stuff was missing. A lot of stuff IS missing. But make sure that you don't alienate the guys, who for the most part, have been rocking with your product. If they actually took it upon themselves to talk and be communicative instead of hiding behind their army of influencers, they'd get some answers. Instead this forum is a unofficial outsourced support center. Because they barely do that themselves. Producergrind and MPCGang are clearly better resources...

And look man. I don't know and don't care about big chin dave nor bolo. Kudos to you for being an Akai Sherlock and watching youtube videos. Don't know if you want an award or if you have a vendetta against the ungodly users who aren't so tuned in to internet rumours. It's insufferable reading grown people telling others to suck it and saying they're on a throne because they were right purely based on faith.

If I got here a month ago and said Trump would be shot in the ear it would still be intel that I pulled out of my ass.

Progress is progress. I'm the first one to change and embrace what's new. As long as it makes sense. Being on a fanboying crusade helps no one. You sound like Ave McCree

eLuSiVeMiTe wrote:What happens when you hit program edit or try to record automations from the midi track you're editing.

At least in the Force you don't hit program edit because there is no program edit. There is only "track edit". Sometimes track means track and sometimes it means track. We noticed you like tracks so we put tracks in your tracks so you can track while you track.

You can record MIDI track automations and they do what they do for MIDI tracks. Your MIDI track can be routed to who knows what outboard lighting control system or your garage door.

So now you can have for eg 3 midi tracks pointing to a program

No you cannot. Nothing points to programs. Programs cannot be pointed at.

but only one lane of automation.

Of course. What would you do with three simultaneous automation lanes for the same parameter?

HouseWithoutMouse wrote:

eLuSiVeMiTe wrote:What happens when you hit program edit or try to record automations from the midi track you're editing.

At least in the Force you don't hit program edit because there is no program edit. There is only "track edit". Sometimes track means track and sometimes it means track. We noticed you like tracks so we put tracks in your tracks so you can track while you track.

You can record MIDI track automations and they do what they do for MIDI tracks. Your MIDI track can be routed to who knows what outboard lighting control system or your garage door.

So now you can have for eg 3 midi tracks pointing to a program

No you cannot. Nothing points to programs. Programs cannot be pointed at.

but only one lane of automation.

Of course. What would you do with three simultaneous automation lanes for the same parameter?

Point. Midi sends. Thought that would have been obvious.

Il quote myself in the next post to save rewriting my methods.

Here.

Many duplicate tracks in a single short sequence comprising of all my songs parts. So duplicate tracks may need unique automation.

eLuSiVeMiTe wrote:
It defines a workflow for many.

I've never worked in a linear fashion on my MPCs.

One sequence. 4/8/16/32 bars depending on genre
6 tracks of drums. 1 program.
Kick snares hats etc.

3 bass tracks various variations for song changes.
Same for keys lead etc.

Il jam an arrangement playing track mutes
When the core parts of the track are in place and initially mixed il copy that sequence mute and create my intro
Copy seq again and so on building up the track in song mode.

Then individual sequences can be edited for builds fills etc working within small chunks rather than 200 bars to scroll through and try and set fiddly loop points.

When I'm happy. Convert to a new sequence and record automations.

As somebody said above. If I want to work in a linear fashion I may as well sit on my pc with many times the ram and a 49" ultrawide instead of piddling around with fat fingers on a tiny touchscreen.

My workflow evolved to keep my tracks structured across sequences and to avoid editing long midi tracks while being able to build full complex tracks quickly.

The current changes completely kill my workflow.

On your last point regarding staying on 2.15

My X was bought just before the XL dropped. I'd be losing any further support.
No more bug fixes. No more quality of life improvements.

Yeah. This update adds a lot but so many small changes that would have improved things are still absent.

A basic file management system. Copy move paste is a pretty basic thing to implement but is still missing.

Mute groups. So much wasted potential here. Mute polarity for instance. So muting one track automatically unmutes a second track. Or second third and Fourth track are muted when another track is unmuted. Jj managed this.

The only option for navigating the grid is your fingers. Despite a jog when and arrows. Having spent years on jjos grid it can be incredibly fast to highlight copy and paste sections compared to a touchscreen.

So yeah. No further updates sucks.

The workarounds to make it work for me are cumbersome and defeat the point of the machine for me.

jpeg wrote:

moonlake wrote:
And I take that back that the screen design is on a new level.
I think its too contrasty and cluttered.



Channel strip. why. where s the improvement, maybe I just dont get it but why had these things have to change at all?

so basically it seems people wanted to keep the current layout and design; and maybe just change the grey to black, then add the arranger, disk streaming and mixer view.

Im not against that veiwpoint, I did not think there needed to be complete UI layout redesign, just perhaps the ability to customise the colours.

But seems Akai wanted to break from the old, maybe the colours are a bit bright, i would not have the multi colours as i prefer a more neutral look.

I dont need to keep the current layout, design, and functionality.
They defintively can be improved, and definetively thats not an easy job, that will always have its own shortcomings.
But I think its a bit too colorful, too contrasty, and too much information crammed in a small space.
The channel strip does have some good new at-a-glance features and layout, but at the same time its getting more and more screen centric.
And the color thing might be a personal thing, I am quite sensitive to colorfulness, so when my dark blue piano sound has a bright yellow color, its slightly irritating me.
But just because I personally would have done differently foesnt mean its all bad or that anything more to my philosophy would be better.

I guess we all have to spend real experiences with the new OS to really judge.

Regard the colours, I'm a fan, I like colours. I linke my pink Behringer Edge, and Yellow TD-3-MO. If my One died and I replaced, I'd dig the new red version. Colours are always controversial, the pink Edge, upset loads that were excited for it, Behringer know, and Akai must have received feedback about the New Red MPCs. Some synths come with blinding LEDs that when you play in the dark make it hard to see, some include a dimmer function.

Hopefully Akai will add a global saturation level option for those that don't like the bright colours at some point.