iMPC Pro!

The new Audiobus Sdk will enable IAA for apps automatically. So all the apps that have Audiobus will have IAA also. That's super awesome.

alexbuga wrote:The new Audiobus Sdk will enable IAA for apps automatically. So all the apps that have Audiobus will have IAA also. That's super awesome.

Yeah it's already in AB now.

It's about time,it's like real musicians are making the software for musicians and communicating and getting it tight and right,...he even said that they are going to do something special for existing iMPC users

moooove over bacon!

I've been using Beatmaker 2 and it's been pretty sweet, but the ability to use the iMPC in Tabletop is making me seriously consider the switch. Inter-app functionality FTW!

Buttttttttt, I dunno if I can wait for iMPC Pro to come out to make the purchase...

Does anyone know if Pro will be a free upgrade for people who've already purchased the regular iMPC? Or will it be a separate app altogether, meaning iMPC Pro will have to be purchased in addition?

themagicalkamja wrote:Does anyone know if Pro will be a free upgrade for people who've already purchased the regular iMPC? Or will it be a separate app altogether, meaning iMPC Pro will have to be purchased in addition?

Looks like I've answered my own question: https://plus.google.com/100282965258005 ... qNGvEN7WYx

Apparently, it will be a whole new app, not an upgrade to the current iMPC app. No word on pricing yet, but apparently current iMPC owners will get some kind of deal? I dunno, we'll see. I'll just hold off as it sounds like the release is just around the corner ::fingers crossed::

I predict >$20, since after the release of iMPC Pro most people will probably stop purchasing iMPC, and also to make up for the increased loss in sales of hardware MPCs that iMPC Pro will likely cause. Sucks that they have to cannibalize their own market just to keep customers!

Yeah most firms wouldn't go the upgrade/discount route and really Apple's guidelines keep it from happening in most cases. But at least they seem to be brewing an app worthy of a new purchase and yeah $20 should be the ceiling.

The Tabletop thing is nice, for me because you can run multiple instances. It's nice to have that element we are all accustomed to with VST/AU plugins.

iMPC Pro looks a few features short of BM2 but certainly a huge improvement over the first one. And I'm sure many will prefer an MPC style sequencer over BM2s layout which while power ful can be fiddly to navigate.

My concern is Retronyms is weird about MIDI. It took users with pitchforks to get MIDI in Tabletop at all. To my knowledge they are mum on any sort of MIDI Out functionality on the Pro revision. If it's MIA that's pretty bad on a device/OS that is fully equipped for it. MIDI Out is too integral to what anything called MPC should be to not have present.

If anyone has heard otherwise and it will have MIDI do tell. It's been asked for on their FB page and me and another guy tried to bump the likes. But Retronyms would not comment at all.

Yeah I understand their opposition towards Audiobus but if there is any lack of midi in and out then

Ocular wrote:Yeah I understand their opposition towards Audiobus but if there is any lack of midi in and out then

I'm pretty sure it has midi in. They showed it being used with the Element. Probably the same layout as the original which also can be mapped to other controllers.

midi out is the question. So far Retronyms has not said yay or nay, which probably means it won't be included in this version. Maybe it could be routed via virtual midi to another app. such as midi bridge and then sent to hardware modules.....

coolderb wrote:

Ocular wrote:Yeah I understand their opposition towards Audiobus but if there is any lack of midi in and out then

I'm pretty sure it has midi in. They showed it being used with the Element. Probably the same layout as the original which also can be mapped to other controllers.

midi out is the question. So far Retronyms has not said yay or nay, which probably means it won't be included in this version. Maybe it could be routed via virtual midi to another app. such as midi bridge and then sent to hardware modules.....

Perhaps, and if so you're certainly the guy that will figure it out right fast coolderb.

But then aren't we looking at a situation where you're simply passing the MIDI input data from the pads to other apps or to whatever physical MIDI solution you might use with an iPad for external synths or to your DAW's VST/AUs?

Just basic MPC style MIDI tracks that can send to external destinations seems not something we should have to fight them for because they are hell bent on making people use Tabletop or whatever flawed reasoning goes through there minds.

But yeah MIDI In is certain, although I still need to confirm it won't do something crazy like block messages if it's not the Element sending. But I'd think you're right coolderb, it should be adaptable to other controllers even if a second or third app is required. But hopefully like in Tabletop when they finally caved to pressure and just let you map the app with Core MIDI and whatever class compliant controller or external MIDI In solution you use.

Apparently this has been submitted to Apple for review

https://twitter.com/Akai_Pro/status/482239125307666433

So the only things I didn't see or maybe I missed are

1- Exporting Songs into the MPC Renaissance/Studio to track out to a desktop daw. (It was confirmed in the last video that you can't multi-track export in the app.

2- Importing legacy PGM's from MPC Renaissance/Studio and hardware MPCs into the app.

Maybe they weren't talked about because it was already in the regular app. I just hope the features weren't pulled.

Metatron72 wrote:

coolderb wrote:

Ocular wrote:Yeah I understand their opposition towards Audiobus but if there is any lack of midi in and out then

I'm pretty sure it has midi in. They showed it being used with the Element. Probably the same layout as the original which also can be mapped to other controllers.

midi out is the question. So far Retronyms has not said yay or nay, which probably means it won't be included in this version. Maybe it could be routed via virtual midi to another app. such as midi bridge and then sent to hardware modules.....

Perhaps, and if so you're certainly the guy that will figure it out right fast coolderb.

But then aren't we looking at a situation where you're simply passing the MIDI input data from the pads to other apps or to whatever physical MIDI solution you might use with an iPad for external synths or to your DAW's VST/AUs?

Just basic MPC style MIDI tracks that can send to external destinations seems not something we should have to fight them for because they are hell bent on making people use Tabletop or whatever flawed reasoning goes through there minds.

But yeah MIDI In is certain, although I still need to confirm it won't do something crazy like block messages if it's not the Element sending. But I'd think you're right coolderb, it should be adaptable to other controllers even if a second or third app is required. But hopefully like in Tabletop when they finally caved to pressure and just let you map the app with Core MIDI and whatever class compliant controller or external MIDI In solution you use.

Yeah, hopefully we can figure something out. You're right they should have included MIDI out. But I don't mind finding workarounds, its fun. Another possibility that I'm going to checkout in the near future is a hardware solution, the iConnectMIDI 4+ http://iconnectivity.com/iConnectMIDI4plus. From what I have read and heard this box solves a lot of problems and greatly enhances the IOS MIDI and audio integration.

iConnect MIDI4+ is my future no doubt. Better than looking at a new dock. Although the Focusrite one is nice.

I suppose by virtue of being in Tabletop you can map it to MPD, MPC etc. But Standalone would appear to be Element only and and that's just foolish. And a lot of people as we have been discussing are just going to assume anything called MPC is ready to sequence other software and sequence other gear...then be like wtf?

Arbitrary artificial limitations just really make me bristle, when the majority of us are like hey charge more if you must just give us us the whole pie.

Metatron72 wrote:iConnect MIDI4+ is my future no doubt. Better than looking at a new dock. Although the Focusrite one is nice.

I suppose by virtue of being in Tabletop you can map it to MPD, MPC etc. But Standalone would appear to be Element only and and that's just foolish. And a lot of people as we have been discussing are just going to assume anything called MPC is ready to sequence other software and sequence other gear...then be like wtf?

Arbitrary artificial limitations just really make me bristle, when the majority of us are like hey charge more if you must just give us us the whole pie.

The original iMPC could be mapped to other Akai controllers and even controllers such as Quneo. Sinapsya developed an iMPC templete just for iMPC. The note values are here: http://noterepeat.com/products/akai-professional/mpc-series/impc-app/115-impc-app-101-triggering-the-impc-pads-with-a-class-compliant-midi-device