MIDI MAPPING HELP/Multiple Channel Graphite 49

Using it "standard" way is probably the best way to use it without big effort. Does it work for you? I mean:
http://www.harmonycentral.com/articles/how-to-use-mackie-compatible-controllers-with-daws
 
To setup "ACT Dynamic Mapping" in addition, there are several tricks. In general you should match what the controller is sending to what Sonar plug-in ("ACT MIDI" or "Generic Surface") are expecting.
The simplest way here - put graphite into "Performance" mode. Faders/knobs are in "7bit CC" mode then, which is default for "MIDI Learn" withing VSTi, "Remote control", "ACT MIDI" and "Generic Surface". No of these methods have any feedback, so the values will "jump". But you can adjust the options "Capture mode" in "ACT MIDI" preferences (to Match).
If you create your own preset, start with simple 7bit CC as well. If you want endless encoders to work as such, configure "Generic Surface" to understand that. "ACT Midi" understand a subset of possible endless transfers as well, but it also should be adjusted manually for that (Ctrl+Click on control to see the dialog). Read Sonar Reference Manual (chapters 20 and 40) for explanation.
 
I am not sure why all your knobs control the same parameter... One of possible cases: they are in (N)RPN mode (RPN is transferred using normal CC, so without future adjustment, single RPN is interpreted as 3/4 separate, always the same, CC messages).
 
I will also mention my own "secret weapon", the link in my signature. It support bi-directional communication, any type of messages, "instant change" mode for not motorized faders and any other allowed by Sonar (or available with some tricks, f.e. arbitrary key sequences) operations. But if you do not plan to spend next month(s) to create perfect (for you) configuration, do not look there
 
Well, in case you are going to use "ACT Dynamic mapping" for VST, even with standard plug-ins, you will probably need my "AZ ACT Fix" utility...

Azslow - Thank you for advice. I will start with reading the reference material. I am really frustrated about this all knobs same parameter staff. Where is an option to turn of RPN ?

Bob F check the link from azslow on harmony. Graphite 49 works without problem in sonar x3 as standard controller.

durovem
Bob F check the link from azslow on harmony. Graphite 49 works without problem in sonar x3 as standard controller.

I had it working fine as a regular surface.  ACT for plugs/VSTi is what drives me mad  ;)
 
I liked using it so much that I started wanting a Motor61 to get motorized faders, but I gave up waiting and grabbed a FaderPort.  In the future I will probably end up with an X-Touch or similar, but the list ahead of that is long :)
 
Thanks.

azslow3

BobF
I had it working fine as a regular surface.  ACT for plugs/VSTi is what drives me mad  ;)
 
I liked using it so much that I started wanting a Motor61 to get motorized faders, but I gave up waiting and grabbed a FaderPort.  In the future I will probably end up with an X-Touch or similar, but the list ahead of that is long :)

X-Touch works throw the same plug-in as Graphite, MackieControl. And that plug-in has no ACT DM (Dynamic Map) mode and so no way to control VSTi. But in addition to motorized faders, X-Touch has display, rather helpful when controlling FX parameters.
 
Looking into (rather short, but quite informative) Graphite documentation, it can be quite good ACT DM when used with AZ Controller. On-screen AZ Display can be used instead of hardware display, knobs are encoders and can be Fine/Coarse, faders in instant+convex mode and there is sufficient number of buttons for all other operations. Manageable to configure in two-three hours... for someone who has the device and know how to program AZ Controller 

Knowing how to program the azcontroller is the problem.  I've spent many hours with it.  What I have managed to accomplish with it with a FaderPort is really sweet.  Anything beyond that ... my brain and azcontroller wotk differently from each other.  Life is too short.
 
If X-Touch doesn't work, then I'll do without or move to a different DAW.  Eventually.
 
 

1) Remove all Control Surfaces.
2) make a project with one MIDI track, set input to Omni
3) record arm the track and start recording
4) move one knob a bit, move other knob a bit (no other control)
5) stop recording, open Event view and see what is there.
 
You can write the result here, in case you can not interpret it yourself.