T-Racks Leslie plugin not working with my controller's ModWheel

I do not have the plug-in but probably don't need it to explain what is happening and how to make it work.
 
The instrument or MIDI track driving the synth (in this DP) gets all the MIDI data coming in on its instrument or MIDI track.
 
In order for the effect plug-in (in this case T-Racks Leslie) to get MIDI data it needs its own MIDI track.
 
Here is one way to set up the synth and the plug-in to use the same MIDI stream.
1) Add the MIDI Event Filter MFX to the MIDI FX rack of the DP instrument or MIDI track. Set it up to filter out the mod wheel like this

2) Enable MIDI Input on the T-Racks Leslie plug-in by clicking on the VST3 drop down above the plug-in UI.

3) Add a MIDI track with the controller as input and the T-Racks Leslie plug-in as the output. This will send the full MIDI stream to the plug-in. I don't know if the plug-in will ignore everything but the mod wheel but it is possible to filter its stream using another instance of the MIDI Event Filter MFX.
 
Enabling input echo on the DP instrument/MIDI and T-Racks Leslie plug-in MIDI should have both working as expected.

Look closer at the image. The box next to Controllers is selected and the lower value in the CC# column is 2. This causes CC#1 (the mod wheel) to be filtered out of the data sent to DP.
 
BTW, consider creating an account on the new forum http://discuss.cakewalk.com the forum we are on now will be converted to read-only in a week or so.

If using an instrument track, the MIDI FX rack "B" is in the track inspector on the MIDI tab "T" in the image below.

The specs show the plug-in is supplied as a VST2 and VST3. Make sure the VST2 dll is installed in the SONAR scan path. ATM, I do not use IKM products so, really can't provide IKM specific solutions.

I only mentioned the MIDI method because of the OP. ACT is the way SONAR provides to send instructions from a controller to any plug-in. Before that there was remote control which is still available. It is a little easier to setup but has some limitations.
 
Good luck

I think there's a setting in preferences for disabling VST2 version if you have VST3 of the same plugin installed. You may want to uncheck it.

Are you sure the plug-in can use MIDI data directly? I could not find the documentation on the IKM site. If it does not and most FX plug-ins do not then there are two ways to use a controller manipulate the plug-in in SONAR, ACT and remote control.

scook
Restore the original properties and use the drop down in msg #2 image #2 to Enable MIDI Input.
Since only the VST3 plug-in is shown in the plug-in manager VST3 migration is not an issue. May also want to check in preferences in the plug-in to see if their is setup involved to use MIDI to control the fast/slow rotation.
 
I have got to believe the IKM specs for the plug-in are correct and the plug-in ships both VST2 and VST3 formats. Make sure the VST2 is not in the excluded list.

I tried going back to original properties as you suggested, and in the drop down selected Enable Midi Input, but that didn't seem to change anything. The original properties boxes that are checked are as follows: Enable As Plugin, Config as Tempo-Based Effect, Enable Delay Compensation, Enable Mono Processing, Max Used Inputs = 2.
 
I unchecked “Hide Related VST2 Plugins” in the VST settings. Then I noticed there were two instances of the Leslie now in the list, figured one had to be VST2. So, in a separate project file, I loaded the VST2 Leslie, added the Event Filter to DP like before, selected Enable Midi Input in the Leslie plugin, and got the exact same result as I did using the VST3 plugin.
 
In the Plugin itself, there is a gear icon and it does bring up a popup window for Midi Settings, but the only settings in there are: Speed Control Change = 1, and Brake Control Change = 64. Next to both of them is a “Latch” button. I think I tried using that too, but didn't change anything. Don't know if this is helpful in any way, but that's all I can find for midi settings within the plugin.
 
I'm wondering.....if I have disabled the controllers for DP using the Event Filter, and my ModWheel is now filtered out from DP, then why is my Pitch Bend wheel still working? Does that confirm that the Leslie just doesn't accept a controller for the Rotary Switch, but it's accepting all other controllers?
 
The thing that bothers me is that guy in the YT video was using Sonar as well, and he seemed to have it working properly. I would like to know how he got it working, he said using ACT, but as I said before, it didn't work for me, but I may have not been doing it correctly, and I can't see the same option in Sonar's main menu dropdown list that he used. I'll go back tomorrow and revisit that video, maybe I can pull something off it that I didn't see before.
 
Well that's all I have for the moment. I'll get some sleep and check back tomorrow. Hopefully by then IKM may have an answer to my support ticket as well.

Musikman
I'm wondering.....if I have disabled the controllers for DP using the Event Filter, and my ModWheel is now filtered out from DP, then why is my Pitch Bend wheel still working? Does that confirm that the Leslie just doesn't accept a controller for the Rotary Switch, but it's accepting all other controllers?
...
In the Plugin itself, there is a gear icon and it does bring up a popup window for Midi Settings, but the only settings in there are: Speed Control Change = 1, and Brake Control Change = 64. Next to both of them is a “Latch” button. I think I tried using that too, but didn't change anything. Don't know if this is helpful in any way, but that's all I can find for midi settings within the plugin.

The pitch wheel is not a separate from the CC events. From the info provided it seems the mod wheel controls the speed and sustain pedal toggles spinning.
 
Leave the plug-in properties alone. They are fine at their defaults.
 
It is all about the MIDI routing. Make sure the input echo is enabled. Just like when playing a synth, no input echo no sound. Maybe try something simple like putting the plug-in on an audio track with an audio clip in it and see if you can get it working there. Forget about DP for the moment. Just concentrate on setting up the leslie plug-in.

To test if the problem lies in the plug-in, try a plug-in known to work.
 
For example, TH3 has MIDI learn. Here is an easy test:
Drop it into an audio FX bin,
"Enable MIDI Input" in the VST3 drop down above the TH3 UI,
Add a MIDI track w/ input set to your controller, output to TH3, enable input echo
Drag a component from the right in TH3 into the TH3 workspace, I used the "Cry Maybe" pedal
right-click on the component and select "learn Global MIDI"
move the mod wheel back and forth on the controller
click OK on the TH3 MIDI learn dialog
the TH3 component should now react to the mod wheel.
 
To clear the setup in TH3:
click MIDI at the top of the TH3 UI
scroll down to the component (the Cry Mayby" is called Wah on this screen)
click CLEAR
click the X in the upper right of the MIDI options to close

I picked a simple example so the basic routing can be confirmed with a plug-in known to work.
 
Different plug-ins have different ways to set up MIDI. From the description in msg #16 the leslie has a predefined CC
config. Do not expect the instruction supplied for TH3 to work for IKM products, however; the method of connecting a controller via a MIDI track to an effect plug-in is the same for all plug-ins that use MIDI data to control features.

Not all plug-ins manufacturers implement MIDI the same way. I can only help with routing in general. The TH3 experiment was to confirm you could get MIDI data to any FX plug-in. I cannot help you with IKM specific questions.

Musikman
...when I right clicked on the Leslie to get the Learn Global MIDI option, I didn't even get the popup box, nothing at all. When I tried just right clicking the rotary switch, it just moved the switch from slow to fast. Both left and right click just move the switch, no learn midi option. So what does that mean?

 
IKM typically don't offer MIDI Learn pop-up menu in t-racks modules. All MIDI settings are done on the setup page, make sure you left toggle slow/fast with CC#1 untouched.
 

I keep wondering how that guy in the YT video got his to work with ACT....I'll have to watch that again to see if I can pick up on what he's done there. It's only a small part of the video and the menu items he uses the text is kinda blurry, but I'll look at it again. I did watch a video or two on setting up ACT, looks to be a bit more complicated than the method we just tried.

I'm pretty sure it's doable, if the slow/fast parameter is showing up as an automation in your track then no reason you can't control it with ACT.

Hey guys,
I did a review and walkthrough of the Leslie plugin here: 
https://youtu.be/rvFr32F2JBw
 
There is a section of the video where I show how I worked around the Leslie speaker Speed issue around 16 or 17 minutes into the video.
Hope you find it helpful?

Musikman
What setup page are you referring to? Where?

 
here:

Musikman
In the Plugin itself, there is a gear icon and it does bring up a popup window for Midi Settings, but the only settings in there are: Speed Control Change = 1, and Brake Control Change = 64. Next to both of them is a “Latch” button. I think I tried using that too, but didn't change anything.

 
so just make sure the Speed Control Change = 1 if you are going to control it with your mod wheel
 

Musikman
...never done it before, and tbh I will have to spend some time reading and watching videos on how it works and how to set it up properly

Alright I've done this already some time ago and I might forgot some steps, but from the top of my head, I had to go to Sonar preferences and there add ACT to the Control Surface list (probably setup MIDI driver there). Then open ACT window from Sonar menu > Utilities and there click Enable on the bottom left. Now if you open leslie gui, you should be able to do MIDI learn: in ACT window click on the speed cell (R2) then move your modweel. If I didn't miss anything you should be able to toggle the speed now.