MPC 3 -- Let's GO!!

renegadebliss wrote:I already started filing bugs against the things that I need. No need to wait for the Public Beta to tell them that they need to store the track mute's in each sequence.

Good shout, I've just logged a ticket as well for track mutes to be saved with a sequence.

Seems a simple change, it's low hanging fruit for them really.

jamos wrote:I have to admit that I can't understand all the consternation regarding this upgrade. Admittedly I don't work in the traditional old school MPC style, but it seems like all of the omissions have some sort of simple workaround.

For example, programs: they're still there! They're just tied directly to the track. For those who insist on using multiple tracks to play a single program, just duplicate the program. It shouldn't take up more than a few kilobytes of memory for the program data, the sample data will all be shared. I wonder how Explode to Tracks works now, I bet it does exactly that.

The lack of track mutes per sequence does sound like a pretty radical change, but it occurs to me, that if track mutes can still be automated, then that's a fix right there. Just insert a mute in track automation for the sequence that you want to mute a track on, and Bob's your uncle. Unless they removed mute automation, which would be a horrible change indeed.

And aligning tracks across sequences makes sooooo much sense. I pretty much gave up on using individual sequences to build a song because this was so difficult to manage.

So I'm excited. I will of course move slowly amd watch for fatal flaws - they may be there - but I think it will all work out.

You don’t understand the concerns because, like you say, you don’t use the mpc like we do.

Some of us have been using the mpc for decades because of the workflow that is now changing. It should be pretty understandable that there is some angst.

Its a bit like driving a car in UK vs Italy.
When you are used to drive in one country you will have hard time driving in the other country,
despite that the rules and the cars are basically the same. Except for the small thing that everything is on the "wrong" side.
And with driving, you have a flow. You can not drive properly outside the flow.
Its all muscle memory and subconscious moves.

And this is distroyed when you enter the other country.

Very nice that track mutes will be optionally available per sequence or global. Ive got nothing to moan about now.

B-Wise wrote:Tefty mentioned that the old mute way is coming back later: https://www.youtube.com/watch?v=PBENuWx ... CHEW0zpHZR He says it at end of the video.

He said event muting is coming back rather the current 3.0 Audio Muting, but we're still not 100% from that statement that it's per sequence.. probably will ask in a comment to Tefty and see if he can find out?

kaydigi wrote:For the few that were wondering like me... In healthy music's latest stream, he shows the Clip Matrix Icon in the menu screen. He moves it to put the arranger there.

When he goes to the arranger , his screen shows the Clip and List button on top like the Akai screen shot does.





You have to skip to the 15 minute mark to see it. Be warned it's a producer/YouTube personality video , I know it triggers some people on here.

https://www.youtube.com/watch?v=hrX97dwnMVc&t. couldn't get the embed to work

He is running an earlier beta build that still has the clip matrix and clips (3.4.0.17).

The version that is currently available to beta testers is 3.4.0.62 and has these features removed.

renegadebliss wrote:

B-Wise wrote:Tefty mentioned that the old mute way is coming back later: https://www.youtube.com/watch?v=PBENuWx ... CHEW0zpHZR He says it at end of the video.

He said event muting is coming back rather the current 3.0 Audio Muting, but we're still not 100% from that statement that it's per sequence.. probably will ask in a comment to Tefty and see if he can find out?

Yeah Tefty’s original complaint was track midi event muting doesn’t work, because it kills the audio tails from his synth.

It sounds like that is corrected not sure about the global issue , guess we can ask him !!

moonlake wrote:have you worked much with the MPC?

Yeah, pretty much every day for the last 5 years. Maybe not the same way you do.

moonlake wrote:The number of programs had been and most likely will be limited.

128 programs. I've seen no indication this has changed.

Can we strum chords yet?

MGoolas wrote:

He is running an earlier beta build that still has the clip matrix and clips (3.4.0.17).

The version that is currently available to beta testers is 3.4.0.62 and has these features removed.

Damn!

funkycoldmedina wrote:Can we strum chords yet?

can we copy a song yet?

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.

jamos wrote:

moonlake wrote:have you worked much with the MPC?

Yeah, pretty much every day for the last 5 years. Maybe not the same way you do.

moonlake wrote:The number of programs had been and most likely will be limited.

128 programs. I've seen no indication this has changed.

simultaneous programs. Instruments. Plugins.
That number is not 128. 128 is the number of "slots". Insert 9 plugin instrument programs and see what happens. I should have worded this more clearly. What was trying to say that a workaround for multiple tracks pointing to the same plugin by doubling the plugin comes at a cost that is it reduces the number if plugins you can use.
Lets say you want to split your piano to 4 midi tracks, all playing the same plugin.
You can not insert the piano 4 times instead. Cause memory and cpu dont suffice.

No, you use multiple MIDI tracks and send MIDI from all of them to the one single piano track. You don't duplicate the piano track.

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.