Well I would look at mine and tell what values I have set for the transport controls, but unfortunately I had to send my keyboard back today. Had a few keys that were hard to push down sometimes. It wasn't a big problem and I think I could have fixed if I got into thr unit, but Musicians Friend said that would void the warrantee and had me send it back for a new one. If I remember correctly, mine was set to MMC on the MPK. Which showed up as 149 or 146, with different values sent for each of the transport controls. Your supposed to be able to use just MMC to control Sonar, but I never could get that to work. So I just "Learned" the buttons in the generic control surface. I didn't have the problem that your having. Sounds like you understand what you need though and will probably get it working.

Now swamptooth says mappings are NOT remembered session-to-session, while FastBiker says there is a corruption. (If I'm understanding correctly.) 

I wasn't act-ually (:/) talking about act controls.  what i meant was that one of my favorite ways of working is to add automation lanes in the track view that i can map via remote control to my controller.  that way i can control the parameters of several different effects units at one time because i don't have to have any in focus the way that act forces you to...  this is nice and one of the main reasons automation lanes are so important in the production process.  you can add them to groups and all kinds of awesome stuff that you simply cannot do with act... the problem is sonar forgets all of those settings when the project is closed.  big darned shame imho.   

mjc9109

rloseven



By the way, have you got your transport on the mpk working ? As far as I can tell, you have to add a Cakewalk Generic Surface to get that working.   Nice to have though.

I got it half working.

As you (and others) have said, I made the Cakewalk Generic Surface. I set the transport controls on my MPK to send CTRL messages. I then learned these to the Generic Surface's Global Parameters. It didn't end up smoothly but I'm not as concerned with it as I was with ACT.

I was able to map the Stop, Start, and Record buttons, but Rewind and Fast-Forward are a no-go for me.
I had to modify the Trigger Value on Stop/Start/Record to 127. It was set to 0 and it wouldn't work with that value.
Trigger Value is greyed out on Fast-Forward/Rewind. Instead, MIDI Message Interpretation lights up, but the MPK only sends a full 127 value when I press them. (I used MIDI-OX to see this.) There is no 0 value sent when I release either button, so this MIDI Message Interpretation box is no good.

Am I doing something wrong again?

 
Have you tried using MIDI learn with the generic surface dialogue?
 

1. Click on the function you want to assign - Play, FF etc.
2. Press button on controller
3. Click "Learn" in the generic surface properties box - it's towards top right.

 
That should do the assign for you.
 
Once you've done that you can save it as a preset in a similar way to the ACT presets. In some ways I find the generic surface controller as useful, if not more so than the generic ACT controller - transport for example, and controllers with more than 8 faders.
 
HTH
 
 

Well, I've got the transport working now.

I set the MPK to use MMC instead and performed the Learn procedure to the Generic Surface.

Fast-Forward and Rewind work by jumping measures, which is fine by me. (don't really like the old skool "tape" feeling of FF and RW.)

-------------------------------------------

I'm now curious about syncing the MPK's clock to Sonar so that I can use the Tap Tempo on the fly. Anyone done this before? I'm going to attempt to research how, now.

No, I haven't done that, but I sure would like to hear from anyone that knows how. Ron