
By Lampdog
Mon Jul 29, 2024 10:53 pm
kaydigi wrote:couldn't get the embed to work
He made his vid unavailable on websites other than youtube is why.

kaydigi wrote:couldn't get the embed to work
B-Wise wrote:I had a 1000/2500 since 2005 & I hated the traditional MPC way handling sequences/tracks/programs.
pedro_oliveira1993 wrote:They already are. Caught one of those today. According to him the problem with MPC's is that they don't function like Ableton as he was used too. So it's "outdated". Everyone will like it except us "legacy users". And I should watch a video by a youtuber because there's nothing wrong with track mutes.
renegadebliss wrote:No need to wait for the Public Beta to tell them that they need to store the track mute's in each sequence.
benway wrote:B-Wise wrote:I had a 1000/2500 since 2005 & I hated the traditional MPC way handling sequences/tracks/programs.
Well, the good news then is that you're probably gonna love Akai's new MPC firmware for people who don't like MPCs.
HouseWithoutMouse wrote:Akai have not made the MPC3 be like Ableton. The fact that traditional MPC concepts were removed, does not make it Ableton.
robleighton22 wrote:Agree that the clip matrix in the Force is an alternative to track mutes. Personally I found building anything more than an 8 scene arrangement confusing in the Force and Push 3. Particularly if you wanted to test ideas before arranging. Which is where the MPC track mute sequence workflow actually ends up being simpler. Despite it not being as immediate perhaps.
Plus the clip matrix is definitely most beneficial with an 8x8 grid. The differences in methods are the perfect combination! Clip launching for performance vs sequence based composition for song writing. And an element of you can do either option on both machines in more limited ways. That's basically what we had in V2.
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.

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