MPC 3.4.1?

I did it over wi-fi. I was on the most recent 3 beta. There were a couple freezes during the restart when I did the update. Had to long press the power button and try a few times before the update went smoothly.

solved my issue. dropped back to 2.15 over usb, then re-installed the current 3 via usb and it seems to be fixed.

jaymack wrote:I did it over wi-fi. I was on the most recent 3 beta. There were a couple freezes during the restart when I did the update. Had to long press the power button and try a few times before the update went smoothly.

Hmmmm... maybe try downgrading to 2.15 (via your account) on a USB Stick, and then upgrade (via your account download) via a USB stick. I know, a PITA and a workaround, but - might be worth it. You should NOT have to long-press the power button and force a reboot during an OS upgrade. That suggests something went wrong.

EDIT:

jaymack wrote:solved my issue. dropped back to 2.15 over usb, then re-installed the current 3 via usb and it seems to be fixed.

Nice - congrats!

They’ve also changed how Q-links function in Grid View using “screen control” mode :
Prior to 3.4.1 there were q-links assigned to zoom horizontally and vertically in Grid View.
They’ve been removed and replaced with a load of time correction functions and it seems the only way to zoom in and out now in grid view is to use the tool and pinch/pull the screen. Which is a complete pain.

I hope someone from Akai reads this….

herbie wrote:I hope someone from Akai reads this….

They certainly won't read it here, as no one from Akai monitors this fan forum. You should submit feedback to them directly instead. Try their social media channels (Twitter, Facebook, Instagram, etc). Or submit a bug report.

MPC-Tutor wrote:I'd go as far as to say this isn't even a 'release candidate' under normal circumstances. It's still a beta, and likely will be for months to come (IMO).

I fully agree

I have an overwhelming suspicion they will lock out users from already paid for plugins if you stay on 2.X

qcinematic wrote:Hello all,

In MPC 2.15.1 is was possible to assign independent outputs to the Submix busses and send/returns buses. This flexibility was removed in MPC 3 beta. Can anyone confirm that MPC 3.4.1 brings this flexibility back?

You can route submixes and returns to any physical output.

Is this what you have been asking for?

J.O.BEATS wrote:I have an overwhelming suspicion they will lock out users from already paid for plugins if you stay on 2.X

Why? That makes zero sense. If I've got an MPC on 2.x with fully functioning plugins on 2.x, there's no reason to lock me out from that. I suspect that Akai are aware that they will have a lot of users remain on 2.x for a while anyway, and I'm sure they're going to want to be able to sell new plugins to all customers, so...

Why? That makes zero sense. If I've got an MPC on 2.x with fully functioning plugins on 2.x, there's no reason to lock me out from that. I suspect that Akai are aware that they will have a lot of users remain on 2.x for a while anyway, and I'm sure they're going to want to be able to sell new plugins to all customers, so...

[/quote]

Because they want as many users as possible on 3.x.
If they want to force users onto 3.x (which they absolutely want) the easiest way is to do it through authorization

J.O.BEATS wrote:Because they want as many users as possible on 3.x.
If they want to force users onto 3.x (which they absolutely want) the easiest way is to do it through authorization

I just don't think they would go that route. That would be a sure-fire way to enrage the old-school MPC heads that have no interest in MPC 3, as well as the hold-outs that won't upgrade until MPC 3 is at a more mature stage in its evolution. The backlash would be pretty harsh. I do see a time when 2.x is deprecated to a point to where they'll no longer release backwards compatible plugins perhaps, but - forcing everyone to upgrade? Nah.

No "Lock Out"....Just making everything from here forward...MPC 3 Compatible only

I do see a time when 2.x is deprecated to a point to where they'll no longer release backwards compatible plugins perhaps,

They are already doing this. The NI content doesnt work with 2.X

Why would they want a huge portion of their user base not being able to buy their plugins and expansions which are clearly a main source of revenue for them?

40Beatz wrote:No "Lock Out"....Just making everything from here forward...MPC 3 Compatible only

And why would they purposely eliminate that huge source of sales?

Either they make all new products backward compatible or they force everybody into 3.0. And we now know they arent prioritizing backward compatibility so logic would follow that they want the user base on 3.0