I'm trying to set up ACT with my Akai MPK88 midi controller/keyboard.
 
I have the midi input enable in Preferences | midi devices.  (I'm using the first bank of 16 midi channels only.  No midi output device.)
 
I have "ACT MIDI Controller - 1" selected with an In Port of "Akai MPK88" which is the correct midi output port.  I have ACT and WAI enabled.  (So far - by the book...)
 
I have the MPK88 set up to send data on channel 1A.  I have an instance of Rapture in an Instrument channel with the midi in set to MPK88 channel 1.  I can trigger notes on the soft synth.  So far so good...
 
I open the ACT MIDI Controller - 1 preference panel from the Control Bar.  I select the Akai MPK49 [Preset 30] cuz there is none for the MPK88 and I know they are similar.  Then I try the midi learn on R1 just to see if Sonar ACT can hear from the Akai.  No luck.  After digging for a while I find that the default Sonar preset on the MPK88 has the knobs and sliders coded to use midi channel 1B (verses the Common Channel or 1A as I expected.)  So I need to create a new Sonar preset for my Akai MPK88 (I think...).
 
But before I do that -
What is the typical (or best) strategy for using ACT with a keyboard/controller.  I need to be able to change the midi channel freely to be able to work with multi-timbral synths like SampleTank.  I do that by changing the Global Common Channel.  If I make all my knobs, sliders, switches, pads, etc. map to the CC, then all controls change their midi channel every time I change the CC.  I think this makes sense for midi learning when working with a soft synth set to receive notes on any given midi channel.
 
Does ACT use a Omni mode to listen for midi controllers?  Will ACT work if I have the midi channel for knobs, sliders, etc. match the channel I want to send notes, velocity, pitch bend, modulation on?  Or is it better to lock all the knobs, sliders, switches, etc. that I want ACT to work with to a dedicated midi channel?
 
Also, does ACT cover the transport buttons? (rewind, forward, stop, play, record)  Or am I going to need a midi mapping separate from ACT for those buttons?
 
I hope this is making sense...
 
Thanks
 

Please take some time to read at least the following:
http://www.azslow.com/index.php/topic,160.0.html
http://www.azslow.com/index.php/topic,120.0.html
If you have more time:
http://www.azslow.com/index.php/topic,107.0.html
 
 

kmcintyre
I have the midi input enable in Preferences | midi devices.  (I'm using the first bank of 16 midi channels only.  No midi output device.)

From computer perspective, there are no "banks" of MIDI channels, there are 2 independent MIDI input devices ("ports" in AKAI documentation) (3 if counted with MPK hardware MIDI input). I recommend to enable both devices in Sonar MIDI settings and configure AKAI to:
a) send keys and whatever else used for direct instruments control to "A" ("1A", etc...), using MIDI Common Channel.
b) send ACT related controls to "B" ("1B"). With fixed channel assignment (so, NOT MIDI Common Channel).
 
ACT is used to control Sonar, it can control instruments throw Sonar, but technically it is completely independent from conventional MIDI controlling for plug-ins. You can not use the same MIDI message for ACT and normal MIDI, when that happened (http://www.azslow.com/index.php/topic,118.0.html) you get side effects.
 

I open the ACT MIDI Controller - 1 preference panel from the Control Bar.  I select the Akai MPK49 [Preset 30] cuz there is none for the MPK88 and I know they are similar.  Then I try the midi learn on R1 just to see if Sonar ACT can hear from the Akai.  No luck.

That means your MIDI routing setup is incorrect, for example R1 is sending on "1B" (you should see that on AKAI) while you configured ACT MIDI Controller to use port "1" (A). MIDI Channel does not matter there (you should be able to learn signals sent on "1A", "2A", etc. if you set input device correctly).
 

  After digging for a while I find that the default Sonar preset on the MPK88 has the knobs and sliders coded to use midi channel 1B (verses the Common Channel or 1A as I expected.)  So I need to create a new Sonar preset for my Akai MPK88 (I think...).

As I have already mentions "1B" and "1A" are different MIDI input devices in Sonar. In any case you better create own preset (that takes less then 5 minutes once you understand how that works).
 

But before I do that -
What is the typical (or best) strategy for using ACT with a keyboard/controller.  I need to be able to change the midi channel freely to be able to work with multi-timbral synths like SampleTank.  I do that by changing the Global Common Channel.  If I make all my knobs, sliders, switches, pads, etc. map to the CC, then all controls change their midi channel every time I change the CC.  I think this makes sense for midi learning when working with a soft synth set to receive notes on any given midi channel.

You may want to setup one of AKAI presets without ACT so all knobs/faders/buttons are delivered "as is" to instruments. That way you can "MIDI Learn" inside plug-ins (if plug-in support that). Still it make sense to keep MIDI channel fixed, so you can for example control ST independent from the instrument you currently playing.
 

Does ACT use a Omni mode to listen for midi controllers?  Will ACT work if I have the midi channel for knobs, sliders, etc. match the channel I want to send notes, velocity, pitch bend, modulation on?  Or is it better to lock all the knobs, sliders, switches, etc. that I want ACT to work with to a dedicated midi channel?

ACT does not support "omni" mode.
 

Also, does ACT cover the transport buttons? (rewind, forward, stop, play, record)  Or am I going to need a midi mapping separate from ACT for those buttons?

You better configure these buttons to send CC (instead of MMC). Since ACT MIDI plug-in support 8 buttons only, you need either configure Generic Control Surface (instead of ACT MIDI, or in parallel with already mentioned caution) or dive into AZ Controller world (which has no limitations).
 
For Knobs I recommend Inc/Dec mode on AKAI side (since they are physically endless). You need adjust configuration with "Ctrl+Click" in ACT MIDI to inform you use endless mode after MIDI learn (Sonar does not detect that automatically). For direct MIDI control check particular plug-ins documentation either they support endless knobs.
 

I hope this is making sense...

Sure

Thanks azslow3!
 
I've read this stuff a couple times and still am not really clear about when to use Generic Control Surface  vs ACT vs just using MIDI Learn on a few controls that I need at the moment.  I think I'll start with MIDI learn and see how far that gets me. lol
 
Keith
 

Relative to plug-in control:
a) MIDI learn is the way to go if (and only if):
a.1) plug-in support MIDI learn. When plug-in support fixed MIDI, you will be forced to configure AKAI for each such plug-in.
a.2) you do not control sonar by the same controls (till switching AKAI preset)
a.3) till plug-in supports endless encoders directly (rarely), you agree to use your knobs in "normal" mode
a.4) you want record controls changes into MIDI clips
b) GCS and AMC is the way to go:
b.1) for transport
b.2) for Sonar parameters (volume, pan, etc.) in case you do not want MIDI learn them for every single trick in every project separately (to change mapping, let say for next 8 tracks, you are forced to relearn everything in MIDI mode)
b.3) for plug-in parameters which have no MIDI input associated or have it fixed to something you do not like
 
GCS vs AMC:
GCS support arbitrary number of strip controls, has separate transport controls, but is has limited "ACT Mapping" (plug-in parameters) and it can not control buses.
AMC has fixed number of controls but all of them have several banks, so effective number of controlled parameters is 4x.
AZC has no limitations and supports functionality not available in GCS and AMC, but it is harder to configure initially.
 
Note that you can use some combination, for example  GCS for transport and track volume and MIDI for plug-ins. In case you want GCS and AMC at the same time on the same port ("B"), it is good idea to add AZC to the end of the list (in Sonar preferences), with empty configuration but with "block all messages" option set. That will avoid unexpected MIDI leaking to tracks.