Why won't Sonar3's fx recognize my MIDI cc??

[ew]

That IS weird...
I'd guess there's some screwy registry problem there.
First thing I'd try is a complete reset of the adapter and then rescan,changing the appropriate fx as discussed above.Then,reboot.Try THAT and see if it works...
ew

[KLG]

As ew stated, you'll have to add a midi track, then assign that midi track to control the VSTi (change the "out" field of the midi track to point to the VSTi). Also, make sure you have this midi track selected before you attempt to bind the controls.

First of all, i'd like to thank everyone for their help, but my problem still isn't solved. So unless i'm retarded, there is somethign wrong with my Sonar Below are detailed steps of what i'm doing so maybe someone can spot the error(s).

1. Run cakewalk adapter
2. scan for vsts
3. go to chainer, or any effect, highlight, and click on "properties"
4. make sure that both "enable DX plug in" and "configure as DXI synth" are checked.
5. click next -> finish
6. open sonar.
7. go to any audio track and right click on the FX box.
8. "insert dxi synth", since now my effects aren't under the "audio effects" tab.
9. Attempt to bind a fader to my controller.....nothing happens.
10. try inserting chainer as an "dxi synth" into FX box.....load plugin, learn midi.......NOTHING....

WTF???? The problem cant be my controller as any knob in sonar can successfully see it. just not fuckin fx!

[Mr. Slater's Parrot]

KLG:
As ew stated, you'll have to add a midi track, then assign that midi track to control the VSTi (change the "out" field of the midi track to point to the VSTi). Also, make sure you have this midi track selected before you attempt to bind the controls.

Yes, Quex, all your listed steps are correct. But, as KLG said, you have to add an extra midi track to your project and assign its "midi out" to the effect that you want to control. Then, as KLG also mentioned, click on that new, extra midi track. Now you should be set. The midi data from your keyboard/controller will go to your newly added and selected midi track and then Sonar will pass it on to your effect because the midi output of that track points to your effect -- even though the effect was instantiated in a separate audio track.

If you are willing to use Chainer as a wrapper, the above becomes much simpler. What I do is to wrap the Chainer VST instrument. Then I make an instance of it and load my desired VST instrument in Chainer. Then I add VST effects in this same Chainer instance. If you do it that way, then you can immediately control your effects with midi learn or automation envelopes and there is no need to add that extra midi track.

Using Chainer this way also allows for very simple and streamlined layering of multiple instruments in Sonar. Plus, then you don't have to wrap any other instruments or effects -- just wrap Chainer and you are done. The only exception I make to this strategy is when I need a multi-channel output instrument since Chainer doesn't handle that case.

[foulaire]

automate the audio channel the fx are assigned to, not the midi channel.

[Lixx]

I GOT IT!!!!! Thank you! Thank you! Thank you! Thank you! Thank you! Thank you! Thank you! Thank you! Thank you! Thank you! Thank you! Thank you! Thank you! Thank you! Thank you! Thank you! Thank you! Thank you! Thank you! Thank you! Thank you! Thank you! Thank you! Thank you! Thank you! Thank you! Thank you! Thank you! Thank you! Thank you! Thank you! Thank you! Thank you! Thank you! Thank you! Thank you! Thank you! Thank you! Thank you! Thank you! Thank you! Thank you! Thank you! Thank you! Thank you! Thank you! Thank you! Thank you! Thank you! Thank you! Thank you! Thank you! Thank you! Thank you! Thank you! Thank you! Thank you! Thank you! Thank you! Thank you! Thank you!

[foulaire]

Glad to help. That one drove me crazy for a long time.