X3 Producer - No sound from VST but TTS-1 DXi Synth Works

I have been having issues with VSTs producing sound. My setup was working then stopped. I reinstalled Sonar X3 Producer up to X3d. I have a midi track. I insert TTS-1 and assign midi output to it. Works fine. I insert SI-Drumkit, click on the drums and get sound. I assign midi track output to the SI-Drumkit and get no sound. Open the SI-drumkit properties and no longer get sound when I click on the drums. My system was working great until a couple weeks ago. No changes now it doesn't work. (And Lost Session Drummer 3 in the reinstall)
 
Very frustrated.

Well it started with losing Session Drummer 3 which is what I usually use. First it was happening with that. Dimension Pro does not work either. Addictive Drums does work. It just seems to be that the MIDI won't output to SI and DP. I have not tried other synths yet. As I don't really use other ones.

It works when triggering from controller when I first insert synth. Then when I play MIDI data, no sound and then controller no longer works.

How do I enter the controller value?

Ok, I just recreated a file from the normal template. I inserted the DP 1.5 instrument with just a Simple Instrument track. Then inserted a MIDI track manually. This all seems to work. So my original problem seems to have something to do with the midi sequences that I'm using. I started with a midi sequence and removed all events except notes. And still get no sound from it. Any ideas?

jdenio
I started with a midi sequence and removed all events except notes. And still get no sound from it. Any ideas?

Wrong Midi Channel ?

Nope to the midi channel, and Nope to the 32bit version

One more thing about controller 7 - a common scenario is a MIDI file that uses controller 7 to fade the level down to 0 at the end of a song. The synth is left in that state until a new controller 7 value comes along to change it. That's why you want to have an initialization at the start of the file. I'm not saying that's definitely what's happening in your case, but it's easy enough to check out and find out if that's the issue.

It's not a matter of midi files supplied by cakewalk and third party files. It's files that I created, that worked, now do not.

"Was record EVER turned on between the time you created the sequences and you started having these problems? If so, and you turned down the volume while it was recording, you can be missing that controller 7 maximum level initialization."
 
No, these are files that were complete, that I had mixed down and created finish product. They worked... now they don't. 

I've had it happen,  The controllers, yes, problem  that I have found is that Sonars Event list does not always show everything. I'm not sure why, one thing I was going to check was if this is MID type 0 or type 1 issue. 
So what I do is open the midi file in another midi editing program, There are lots of free ware basic midi sequencers or even Reaper. I now use CubaseLE. 
I will always then see the event that did not show in Sonar and so I delete it. 
 
Other things I'll do. 
 
Split the midi track to the place just before the first note in the track and delete the empty part ahead of this. This works a lot of times for hidden PG info.
Sometimes you can open the GUI for the offending synth, start the transport, and observe the volume control or what ever, and you'll see that there truly is something hiding on you. . I've had efx sends in TTS-1 coming back on after I shut them down. Once again, nothing shows in the event list. 
This is also working with my own older MIDI files from my Atari days. 
I always inserted my PG and CC7 etc within the first count in measure. They just plain don't show in Sonar. But they are there because I know my GR50 patches, 92 was my bass and guess what the TTS-1 plays. 

MarkieMark
Another classic problem is with the pitch bend sensitivity.... I had this problem with 3rd party midi files using DP and S1 bass.... I deleted all the pitch bend sensitivity events, saved the project, re-opened X2 and the problem went away. I do this automatically with new 3rd party midi files now

Pitch bend sensivity is set at the instrument itself. In my esperience most MIDI file assume this will be set at + and - two semitones, but that's not always the case.