Actually.... I think I do need to add LoopBe.... Although the process works, my external controllers are spanning the whole range from 0-127 (CC control), which is why I have to use MIDI Shape Shifter. So without LoopBe, the control is working, but it's just not routing through MSS. I'll install LoopBe and report back.

Hi scook, I installed LoopBe, see it in Sonar, and have followed your instructions as close as I can. I'm still not getting the full range of 0-127 from my external controllers for the FX parameters, so that means I'm still not going "through" MIDI Shape Shifter. I'll be honest, I don't understand how to use LoopBe inside of Sonar at all. And the help on their site is minimal. Any recommendations, or other sites that show how to use it in Sonar? I'll do some googling.

I did not use an external controller, the LFO was done within MSS using the LFO-1 preset. If you need to add an external controller and restrict the range, you may need to use MSS to map the incoming CC data to a different channel or CC so the remote control can be defined to pick up data from MSS instead of the controller.
 
The MIDI event filter MFX may be useful to restrict the range too.

I installed LoopBe recently to try it out. It basically shows up as a MIDI device in Windows (where it installs), but also needs to be enabled as a MIDI device in SONAR preferences. From there, it shows up on any Input/Output MIDI as a "controller," so you can route the output of a VSTi to it, and use it as an input to drive other VSTis. I did not get too in depth with it, but it seems that its advantage is that is appears as a controller (to MIDI functions requiring them), versus a VSTi output.

Hi mettelus, thanks for the feedback. Damn, I am feeling dumb lately! I am seriously not getting this virtual midi cable thing in Sonar. I'm tempted to draw out a block diagram or two of what I am specifically trying to do (with the external HW controllers that need the MIDI Shape Shifter VST plug-in to properly scale their ranges). I may do that when I have some time this weekend.
 
I have attempted to look on-line for how-to's on midi virtual cables, and am not finding anything of any substance. I have a feeling that there is something real basic here that I am just not getting.

For your application LoopBe is serving as a loopback for MIDI data. As mentioned above it needs to be defined in SONAR Preferences as a MIDI input and output device.
 
I would recommended setting up the test I described in msg #9. This will confirm everything is configured correctly inside SONAR.
 
Once the test is working, then try to substitute the LFO generated inside MSS with your external controller. This is when you will need to take advantage of mapping the incoming CC data to a different channel (or CC number) so remote control can be set to listen to the new mapping. Just like in the example in msg #9 the remapped data is routed via loopBe. It needs to be remapped because remote control listens to all devices but can be set to a specific channel and CC. The remapping allows remote control to only read to the data send through loopBe by MSS and ignore the original hardware data.

Hi Scook,
 
OK, I followed your instructions in post #9.  Here's a picture of the tracks in X3e Pro.  Track 2 meter is oscillating, and if I change the amplitude of the LFO in MSS, the meter level changes.  So tracks 1 and 2 look good.  But when I insert the audio track, the FX, and set remote control for one of the FX parameters (including setting it to cc = 7), and then press play on the transport, I don't get the oscillating parameter.  In this case, it's mix amount on valhalla room.  Do I have all of the track I/O's set correctly?

 

?????  Where's the picture that I inserted?
 
Scook, here's the URL for the picture on Dropbox...
 
https://www.dropbox.com/s/ud7ekp536x7d9pt/MSS%20control%20via%20LoopBe.jpg?dl=0
 

Hi Scook,
 
I think I'm almost there, gotten most of it to work. Thank You for your help!!
 
There's an weird anomaly occurring though, not sure what is causing this.
 
I have Diva as my test VSTi.  I am controlling two adjacent controls on Diva from my remote HW box.  The first one I assigned to control directly using the MIDI Learn command, and that control goes from 0% to 100% in Diva.  In other words, full scale.  The second one, however, I set up an automation lane with remote control, and that control goes from ~ 10% to ~ 90%.  Not full scale.  Same external controls, and identical adjacent controls in Diva.  I am missing something in setting up remote control in the automation lane?

You are operating with hardware and software I do not have access to or experience with moreover; I do not understand the need for the variety of methods to control a single plug-in. It seems overly complex but I am sure it is because I do not follow what your are trying to do.