Good Morning everybody,
My name is Unknown Reality and i'm a new Sonar Artist DAW user, I purchased the program yesterday curious to see how good this program was. It didn't take long to download and install which i liked very much. I ran into a problem when i tried to install my MPK49 midi controller. Idk why i can't find any info online regarding how to properly set it up. The controller already has a Sonar preset installed but none of the transport buttons, knobs and faders seem to work at all which is a shame because I really looked forward to working with the program. I hope I don't have to buy another midi controller just to work with Sonar because my MPK49 works just fine with the other DAW's I use such as Logic Pro X, Pro Tools 11 and FL Studio. If anybody can help me solve this issue I would gladly appreciate it, thanks in advance have a nice day.

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

Thanks for the link, I follow the steps correctly until I get to step #5 when I try to click each green assignable area to MIDI learn the MPK49 controllers, nothing happens. Maybe its just me but for me nothing happens

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.

Try the instructions for sonar here https://www.google.com/ur...4TUWR9sRnOZfbAopfcNKMQ

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.

I tried to follow those instructions but they must be for an older version of Sonar because the version I have doesn't have some of those same buttons and menu choices etc., its getting a lil frustrating.

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.

swamptooth
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.

I wish someone like you could be convinced to be an alpha tester of my project
It is still alpha, but it opens more possibilities then ACT MIDI and Generic Surface together. I am advertizing my toy for long time already: arbitrary logic, feedback (able to provide indication for pads/buttons/endless encoders), device chaining, direct (not ACT, so can work in parallel) control of VST parameters, easy ACT mapping and FREE. But near no one has interest. For me the concussion is: CW and hardware producers was right, users do not really want seriously use control surfaces with SOMAR, so there is no reason to invest there.
 

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.