Akai MPK49 Midi Controller setup issues!!!!

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

I find That my MPK 49 is very flaky , ACT works but dont forget to have your MPK plugged in before starting Sonar, otherwise you'll be remapping again and again and again.  One feature I wish Sonar had , remember hardware settings a global save .
 How many times I clicked the sonar Icon when my hardware wasn't started . How many times I just gave up on working cause devices needed to be remapped and I lost the mojo.

swamptooth
Try the instructions for sonar here

I'll definitely try those instructions out and get back with you to let you know they work.

Hmmm... sorry about that.  I'm back at my daw now.  
Try this:
in sonar go to preferences/midi/control surfaces
click add new control surface
select cakewalk generic surface from the list
click ok
go to utilities and select cakewalk generic surface
click the presets tab and select akai mpk49
for each of the transport controls in the right bottom of the screen
click i.e. play, then press the corresponding button on the mpk, then press the learn button
do this for all your transport controls
 
trust me, a little patience goes a long way here...
i have 4 controllers set up and it took roughly 2 years to figure out an effective and natural way to map them to all the vsts that i use.  things as little as "do i always want this knob to control the filter frequency on every synth i use?" come into play -- not to mention situations like what if there is no filter to control?
 
you'll get it down!  the setup can take a while, but it's worth it in the end.

Hey alexy - it wasn't hard from a technical standpoint, but an workflow standpoint. When youre running 4 daws with their own peculiarities and >100 vst plugs it takes time to find the most natural setting for how to control it all. Not to mention how some synths have the same parameter mapped to different midi ccs depending on the preset.

ACT is ineffective for be because of the focus requirement.  What I'd like to see is something like this http://forum.cakewalk.com/FindPost/3176862

swamptooth
ACT is ineffective for be because of the focus requirement.  What I'd like to see is something like this http://forum.cakewalk.com/FindPost/3176862

You want to see it from CW? I can not help then since I am not working for them. My plug-in can do this. It is a bit difficult to setup (parameter names are not shown, so the position should be calculated) but since you are patient...
 

dubdisciple
Sad to see you feel that way.  the fact that these threads keep coming up is some evidence that users do want wha tyou are offering.  Everyone is just not cutout to be an alpha tester. Alpha testing in an area tha talready has you pulling your hair in frustration is even more intimidating for some.

I am just direct person. I am calling it Alpha because it is Alpha:
* Alpha - not all planned features are inside, stability is UNKNOWN
* Beta - all planned features are inside, stability is UNKNOWN
* Release - all planned features are inside are they are working as expected, stability is confirmed to be good.
 
When I have started to use X1, I have found out it is Beta at most since I was able to crash it within one hour several times and the result from some operations was far away from expected. I have learned what I should avoid to use, what "workarounds" exists, etc. (thanks to this forum).
 
I had several crashes with my plug-in, but these crashes was in SONAR. So that is like I trigger some bugs in SONAR. As many VST producers reply and sometimes CW claim, I could just say "my program is fine". But I do not, since I think it is not true. My "Released" projects work for years without single failure, this plug-in is not yet at that level. And without at least one "tester", that is not going to happened. That does not mean the plug-in is crashing every minute, it is not. It is just not on the level of my own imagination for "Stable Release" (SONAR X1/2, Windows Vista, Ubuntu 14 was also NOT at that level!).

azslow3

swamptooth
ACT is ineffective for be because of the focus requirement.  What I'd like to see is something like this http://forum.cakewalk.com/FindPost/3176862

You want to see it from CW? I can not help then since I am not working for them. My plug-in can do this. It is a bit difficult to setup (parameter names are not shown, so the position should be calculated) but since you are patient...
 

dubdisciple
Sad to see you feel that way.  the fact that these threads keep coming up is some evidence that users do want wha tyou are offering.  Everyone is just not cutout to be an alpha tester. Alpha testing in an area tha talready has you pulling your hair in frustration is even more intimidating for some.

I am just direct person. I am calling it Alpha because it is Alpha:
* Alpha - not all planned features are inside, stability is UNKNOWN
* Beta - all planned features are inside, stability is UNKNOWN
* Release - all planned features are inside are they are working as expected, stability is confirmed to be good.
 
When I have started to use X1, I have found out it is Beta at most since I was able to crash it within one hour several times and the result from some operations was far away from expected. I have learned what I should avoid to use, what "workarounds" exists, etc. (thanks to this forum).
 
I had several crashes with my plug-in, but these crashes was in SONAR. So that is like I trigger some bugs in SONAR. As many VST producers reply and sometimes CW claim, I could just say "my program is fine". But I do not, since I think it is not true. My "Released" projects work for years without single failure, this plug-in is not yet at that level. And without at least one "tester", that is not going to happened. That does not mean the plug-in is crashing every minute, it is not. It is just not on the level of my own imagination for "Stable Release" (SONAR X1/2, Windows Vista, Ubuntu 14 was also NOT at that level!).

Btw, this thread prompted me to finally attempt to use the alpha version of your software. I wish i understood it more intuitively. So far so good. No crashes and I was able to get sliders and rotary controls working.  I'm  going to spend some time trying to figure it out.

I will try to be patient. If I can get everything set up ideally it will be well worth it. I'm going to have a thorough read of manual today. If i can get quadcurve eq, transport and compressor all working seamlessly with cinsistency i will be a happy camper