Akai MPK49 X3 Setup

http://forum.cakewalk.com...ai-MPK49-m3038483.aspx

I have an Akai MPK49 and tried for a number of years to make it work correctly with Sonars - from X1 to X3 IIRC.
The Vyvex software is lumpy to say the least, but in the end I solved the issue - I  purchased a Novation Impulse 61 which worked perfectly out of the box - also has automap software included.
I actually really liked the Akai keyboard but it was a nightmare software wise. 
Sorry
Nigel
 

Akai stuff works with sonar and then will suddenly just stop.  very frustrating. Akai has totally useless support.

As you could see in my thread: if you want integration with SONAR for some CS, just integrate it yourself.
 
I agree that AutoMap software works out of the box with SONAR. But not even close to the lever you can wish and it transpose itself into AutoBug periodically...
 
 

I can't get my MPD26 to work at all with my arturia software in standalone mode.  works via sonar.

This may be helpful to you. It's written for the MPK88, so the included ACT preset won't be useful. However, I'm guessing the directions to setup the controller should transfer easily to the MPK49. You will need to setup an ACT preset in order for this method to ultimately work. I haven't updated the post, but it works fine in X3.

Hope you are successful at setting up your MPK49.

http://www.unrelatednotes...i-mpk88-with-sonar-x2/

kw

LunaTech
I am using and Akai MPD 26 (hopefully that's about the same from a transport standpoint).  And The transport is working fine without any "special" cmd.

But are you a Steam user using the 64 bit version? If not then that explains why you didn't need that step. In my case I needed to activate the dll's for the Controller/Surface I wanted to use in the CMD, that's an issue on Sonar's part. Then you have to manually set up the transport. So what takes minutes to do in other DAWs took me two days in Sonar.
 
@HenD:
 
I'm using my MPK49 as a Generic Surface. Once you've followed the instructions sent to you by Akai open up the controller properties in Sonar. On the bottom right hand side you'll see "Global Parameters". Click on a parameter, press "Learn", then press the button on your Akai controller. Do that until you've mapped all of the transport controls.

azslow3
http://steamcommunity.com/app/241070/discussions/0/540736587127895581/?insideModal=1 ?

 
Yes that issue.
 

azslow3
There is no magic in this world, there is no "automatic" adaptation. Someone always has to manually set up everything, the difference is who is doing that:
1) Cakewalk, in case there is some affiliation with hardware producer (previously Roland, so Roland keyboards had "automatic" support)
2) The hardware producer, in case they want attract SONAR customers (Nektar Impact, Novation Automap, etc.)
3) The user, in case he/she has made a decision to use some arbitrary device.
 
The mapping itself takes ~5 sec per control, so several minutes in total for any device. What takes time is to understand why it is required and how to do it. It is still much less then a day, the relevant part in SONAR documentation is just several pages to read.

I don't get what point you're trying to make here. Are you trying to insinuate that I don't know the process behind mapping a controller to a DAW, along with saying that it didn't actually take me as long as I say it did searching for days to fix the issues I had with Sonar.
 
First, I assure you I know exactly what it is to map a controller to a DAW, and I'm not talking about basic transport controls. I'm talking hours mapping DAW functions (open windows, cut, copy, paste, jog, toggle options, etc.) to proper MIDI Channels with note assignments. Second, understanding how a DAW handles controllers and how to set them up is always necessary, I know that, but if you think not having basic support for widely used controllers is the norm I'll be the first to tell you that's not the case. My experiences with other DAW's gives reason behind my expectation for "automatic" in regard to basic transport control.
 
Just to clear things up if you didn't notice, I wasn't complaining, someone posted before me talking about Akai's software being a nightmare and I chimed in with my experience with Sonar being the nightmare.

FidelityMusic
Second, understanding how a DAW handles controllers and how to set them up is always necessary, I know that,

I have just mentioned that this takes most of the setup time and that is not SONAR fault. The technology is not simple since it does complicated things and provides some flexibility.

but if you think not having basic support for widely used controllers is the norm I'll be the first to tell you that's not the case.

http://www.akaipro.com/product/mpk49#downloads
Akai take care about "automatic" in these "other DAWs", not DAW programmers.
 

My experiences with other DAW's gives reason behind my expectation for "automatic" in regard to basic transport control.

There is no "basic" nor "advance" in anything corresponding to Control Surfaces. While for MIDI Hardware MMC looks like the common way for transport control, it is not the best option for CS (since you do not control the transport directly, but the DAW which control the transport).
 
My comments are not accusations, but a reply on your (quite strong) suggestions what SONAR does not have and should have.
 

FidelityMusic

azslow3
Akai take care about "automatic" in these "other DAWs", not DAW programmers.
 

I think you're misinformed about that. I know for sure they didn't program the FL Studio template, and the Logic Template uses a generic GM Drums on the MPK, which tells you that they didn't program anything specifically for Logic. That leaves Ableton Live out of all of the DAW's there are, and it's the only one that I'd assume Akai actually programmed because they bundle Live Lite with their controllers. Pro Tools, Studio One, FL Studio, no templates programmed by Akai and basic transport functions out of the box.

That is not (always) about programming. Akai provides instruction how to use THE device with concrete DAWs. They could do the same for SONAR, and that could save you two days to find out how it works from other (generic) sources and adopt it to concrete device. They could implement "SONAR oriented" MCU compatible mode in the device firmware, to have "deep integration" with SONAR. And yes, they could write special plug-in. But that is not a must. Still, Akai has to choose that, not CW.
 

When I say "basic" I'm talking about what would be considered the essential function of a controller in this day and age, the transport. Like I pointed out already transport control is common out of the box in plenty of DAW's in regards to widely used controllers, no thanks to Akai but the DAW manufacturers themselves. When it comes down to manually mapping it's usually the faders, knobs, and any extra buttons that have to be mapped manually.
 
After using different DAW's with something in common consistently there becomes an unofficial standard and expectation, so it isn't much of a suggestion as it me pointing something out for those who aren't aware.

 
The "basic transport" you mean is MMC and other MIDI sync commands. That is in fact official (!) standard to control transport in the "MIDI world". Do not mix "MIDI world" by itself and DAW Control Surfaces which use MIDI hardware/software abstraction for communication.
 
Just imagine you have many Hardware MIDI synths. When you use them standalone with your keyboard, you may wish the keyboard is the master. It should define the tempo, when to start play, record, etc. For that it should send MMC/MTC/etc. Now you have computer with DAW. Are you still want your keyboard defines when to start play and at which tempo? Most probably not, you want the project tempo is used and the "Play" button on the screen also start "Play" on your devices. The DAW should be the master in that case (and SONAR can do that, see "Project/MIDI" settings and note that has nothing to do with Control Surfaces). What you want from the "Play" button on your Control Surface is that it send some signal the DAW (not the rest) understand and translate into internal "Play" command. On MCU this command is "Note 94 On" (yes, technically nothing to do with the transport).
 
Back to the topic. Some DAWs you mention natively support MMC incoming from Control Surface. And you say that should be "unofficial standard" (again, for Control Surfaces, for MIDI it is Official Standard). Other will say Mackie is the "unofficial standard" for Control Surfaces, and then "Note 94 On" should be interpreted as "Play". Can you see my point now?