OK - here is where I am ...
I am still trying to figure out how to get the soft synth controls to map.  
 
For now the keyboard, mixer faders and transport buttons work fine and I like that a lot!!  Nice for mixing multiple acoustic guitar tracks.  I am not able to get synth-related faders or rotary control to work with the soft synths.  I am sure I've missed something to setup.  Taking a break and reading the manual again. Other than that I am pretty happy!
 
 

Bigdaddyd54
OK - here is where I am ...
I am still trying to figure out how to get the soft synth controls to map.  
 
For now the keyboard, mixer faders and transport buttons work fine and I like that a lot!!  Nice for mixing multiple acoustic guitar tracks.  I am not able to get synth-related faders or rotary control to work with the soft synths.  I am sure I've missed something to setup.  Taking a break and reading the manual again. Other than that I am pretty happy!
 
 

OK, I hear ya!  I really don't bother to map my controllers to particular soft synths globally.  I just use the mouse most of the time to setup the soft synth the way I want, then use "MIDI learn" for specific functions in the synth.
 
If there are some synth performance parameters that I want to control from the keyboard, I just right-click on that control in the soft synth, then select "MIDI Learn" from the context menu, and twiddle the control on my keyboard that I wish to map to that function.  Done.  Save the project and those settings stay with the project. 
 
Unfortunately, the next project you create and insert the same synth, you need to map again.
 
That is where certain keyboards that have dedicated soft synth maps, such as the Native Instruments controllers, make working with Native Instruments soft synths a breeze.  It's called plug-in integration.  Different thing from DAW integration, which is what you have now.  They would like for you to buy their software AND hardware!
 
This: https://www.native-instruments.com/en/products/komplete/keyboards/komplete-kontrol-s-series/
 
So you could end up needing two or more dedicated controllers. One for your DAW, and at least one more for your soft synths.
 
Me, I just live with the "midi learn" and life is good.
 
But be sure to check your documentation for the Nektar. It may have built-in control maps for select soft synths.

 
To me it's not that big of a deal.  Just a loose end.  A couple of other things I forgot to mention before is that the "play" transport button is stuck in click mode and I can't seem to turn it off.  "Shift-Click" didn't work.  Sonar crashed and it's been that way since.  I can always use the spacebar if I don't get it figured out. I really don't want to re-install.  
 
The other thing I noticed when there are multiple synth tracks and you tap the LX49's instrument button it always defaults to the first synth you inserted.  You can easily launch the synth via the track but I found that kind of odd.  I tested it out. First project I started with EZ Drummer and that was the default.  New project I started with Addictive Keys and that was the default.  Do you think that has something to do with the Synth rack?  Again, to me it is not a big thing but a loose end I wouldn't mind addressing.
 
BTW - I checked out every Cake Walk synth provided.  WOW!  LOVE! z3ta+1 -- Xpand!2 -- Rapture Session -- Dimension --  Wow!  It looks like they'll keep me busy!!  It will be some time before I upgrade to Rapture Pro.  I've got to get start reviewing all the info you sent.
 
Overall, I am pleased with the Nektar -- I would recommend it others.  It was able run everything right from the start.  Love the mixer side of it and I'll keep exploring the synth mapping.
 
Later!
 
 
 

Bigdaddyd54
 
To me it's not that big of a deal.  Just a loose end.  A couple of other things I forgot to mention before is that the "play" transport button is stuck in click mode and I can't seem to turn it off.  "Shift-Click" didn't work.  Sonar crashed and it's been that way since.  I can always use the spacebar if I don't get it figured out. I really don't want to re-install.  
 
The other thing I noticed when there are multiple synth tracks and you tap the LX49's instrument button it always defaults to the first synth you inserted.  You can easily launch the synth via the track but I found that kind of odd.  I tested it out. First project I started with EZ Drummer and that was the default.  New project I started with Addictive Keys and that was the default.  Do you think that has something to do with the Synth rack?  Again, to me it is not a big thing but a loose end I wouldn't mind addressing.
 
BTW - I checked out every Cake Walk synth provided.  WOW!  LOVE! z3ta+1 -- Xpand!2 -- Rapture Session -- Dimension --  Wow!  It looks like they'll keep me busy!!  It will be some time before I upgrade to Rapture Pro.  I've got to get start reviewing all the info you sent.
 
Overall, I am pleased with the Nektar -- I would recommend it others.  It was able run everything right from the start.  Love the mixer side of it and I'll keep exploring the synth mapping.
 
Later!

Hey, ran across this on the product page:  http://www.nektartech.com/impact-lx49-61-plus.html
 
INSTRUMENT

• Open/close VST instrument window
  
• Nektar Map System store and recall map settings for VSTi plugins
  
• The Default  page maps  pots to parameters as per blue control labeling
  
• User page for secondary mapping or user mapping
  
• Faders 1-4 commonly mapped to amp ADSR envelope
  
• Faders 5-8 commonly mapped to filter ADSR envelope
  
• Fader 9 control VSTi Instruments main volume
  
• All VSTi mapping is user customizable using Nektar "Grab" function including faders, fader buttons and both page assignments
  
• User customization can be either temporary (active for as long a project is open) or saved
  

Yes I am looking into that.  I have a support call into them as well.  Haven't heard back yet.  I was looking at the ACT function in Sonar.  Is this the MIDI learn you are referring to?

Bigdaddyd54
Yes I am looking into that.  I have a support call into them as well.  Haven't heard back yet.  I was looking at the ACT function in Sonar.  Is this the MIDI learn you are referring to?

It's related, but different.  Midi learn is assigned and saved only on a per project basis. 
 
ACT uses a controller template within Sonar that can be used globally across any Sonar project.  It can utilize several modes, depending on whether you aim focus (active window) on the DAW itself, or an individual plugin. 
 
The DAW integration for some keyboards can work well.  I just recently discovered a ACT preset that allows me to use the transport controls and knobs on my old M-Audio Axiom 49, for Sonar start/stop/record/loop, and also use the faders and knobs for track control in Console View.  I haven't really used it to control plugins.  That is because the MIDI learn thing is so easy, it's a no-brainer for me. 
 
Using ACT with plugins really takes some customization. ACT is kind of like MIDI learn, but it's saved in the ACT function.  ACT switches focus as you switch to different windows, so certain controls can be used more than once, depending on the active window.  And it's always available when you connect your controller and start Sonar.
 
To see if you have an ACT profile for your controller, from Sonar's main menu click on Edit > Preferences > MIDI > Control Surfaces.  If you haven't yet added one, click on the "+" symbol to start the add dialogue.  Under Controller/Surface, select ACT MIDI Controller, if yours isn't listed.  Then select the input port for your controller below that.  Then from Sonar's main menu click on Utilities > ACT MIDI Controller.  This opens up the ACT window.  There is a preset window at the top that lists a lot of controller hardware.  Note: If you’re not using a Roland A-PRO controller, using ACT at this date means using either the ACT MIDI Controller Plug-in, or the Cakewalk Generic Surface Plug-in.   You could probably MIDI learn a few things into a generic ACT profile, but I think that in the case of Nektar, see what their integration can accomplish first.
 
Here's an article that Craig Anderton wrote a while back about Sonar ACT:  http://www.soundonsound.c...t-hardware-controllers
 
Sonar docs are here:  http://www.cakewalk.com/Documentation?product=SONAR&language=3&help=ExternalDevices.15.html

Thanks for the info!  I check that out and let you know how it works.  This is my busy time.  It may take a bit to get back you.  Thanks again!!

Follow up ... Sorry I took so long ...
 
Here is the response from Nektar support regarding Sonar Act and controls questions.  I have not had a chance to check them out yet, but the seem to be straight forward answers:
 
Instrument selection via Nektar:
Sometimes the Instrument selection in Sonar can get out of sync with Impact. To fix this click on the 1st instrument in the synth rack, then use the patch up/down buttons to select instruments. When you use this method the correct plugin GUI should appear when you press the Inst button. 
 
Synth mapping: 
We don't have maps for Rapture or z3ta+1. But you should be able to use the grab function to control parameters for those instruments. While in Instrument mode, hold Shift while moving a control in the instrument GUI, then release shift and move a control on the LX49+. The parameter should now be mapped.
 
Sonar Act:
You can use Impact with ACT in Sonar, but you shouldn't need to as our Instrument mode should handle most of that functionality. If a parameter you would like to control is not mapped by default, use the grab feature to assign it.

That sounds like good advice! 
 
In a perfect world all of the virtual instruments would magically map to our controllers, but we have a far from perfect situation.  Because of the flexibility and capabilities of having our synths virtualized, rather than being hardware based with dedicated controls, there are just too many variations in the possible controls available for one controller to map them all.  The exception here would be by bundling a soft synth with a keyboard controller from the same manufacturer.
 
So in my opinion, the best situation is for the VSTi developer to provide a few smart knobs, or morph controls, on the VST instrument GUI.  Some VSTi's allow user programming to assign these smart controls to deep parameters within the synth.  That lets us decide what we have control over when we play the instrument. 
 
In your case, using the grab function, which sounds equivalent to the MIDI learn function, lets you pick select performance controls for the instrument you are playing.  It's a customized effort, but it does keep things somewhat simplified.
 
For example, using Rapture Session, after selecting an instrument from the factory library, click on the Instrument tab next to the Browser tab.  You will see 8 knobs in the GUI.  You can setup any of them to be associated with a knob or fader on your controller.
 
Using Xpand!2 you can pick any knob or slider on the instrument.  The 6 knobs at the top are smart controls, that you can adjust from your controller as you play.  Just pick the controls you wish to use.  Enjoy!

I will!
 
I thought this would be good info to post for others.  I haven't tried the Grab function yet, but it sounds quite easy and it's really all I need.
 
Thanks again for taking me under your wing!!  You made it a much more pleasurable experience!!!