Hi guys,
 
very strange things happening here.
I imported this midi-file: 
 
and assigned it to TTS-1
All is working well.
 
BUT as soon as I assign the "Drums*STANDARD"-track to the SI-Drum Kit, the DI-Drum Kit will stop working - it will become mute. Not even hitting the drums via mouse will revive it. Only deleting SI-Drum Kit alltogether and re-adding it, will make it work again. But only until you assign the Drums*STANDARD to it - it will become mute again.
 
Can you reproduce?

I have been digging a bit further and found out, that the midi works if I delete the embedded controle changes. So it is propably some corrupt entries, that is causing the problems?
I have isolated the midi and uploaded it here:

Maybe someone is curious enough to test it?

Ah - damn. No URLs allowed...

That's actually a fairly common occurrence when importing midi tracks.
 
I have amassed a pretty sizable collection of free midi tracks of a bunch of rock and prog tunes from the 70's, and sometimes some of the tracks will have embedded events that I have to go in an delete for them to work properly.
 
I look at it that it's still a lot quicker to go in and fix the occasional weird track than it would be to work the whole song up from scratch on my own - so I remain quite happy that folks take the time and have the desire to put forth the effort into creating and distributing these midi files.  :)
 
A happy camper - Bob Bone
 

Hi Bob,
good to know, that this is not my problem, but a general one :-)
Interesting enough, all the Cakewalk VST reacted the same way, by becoming mute; whereas 3rd party VST stayed cool...
Say, is there a way to delete the embedded events inside X3?

Just view the Event List for the midi track in question, and you can delete events from the beginning as needed.
 
Bob Bone
 
 

All right! There it is.
JFYI, in case anybody runs into future trouble with that.
Right at the beginning of the track was following line:
RPN / Pitch Bend Sensitivity / 256
It was marked orange, so next time a midi misbehaves, just look for orange lines ;-)
I deleted it, and DrumKit worked fine.
@SONAR (in case someone is reading this!)
You should make a bugfix for ALL of your VSTs to filter out orange lines, instead of allowing them to kill your instruments ;-)
If you need the midi, which caused all this trouble, just drop me a line here and I will send it to you via Email.

All of the sfz engine synths (Cakewalk Sound Center, DimPro, Rapture, the SI series and Session Drummer) have trouble with the control data typically found at the beginning of MIDI tracks designed for GM instruments. As Bob points out, opening the tracks in the Event viewer and stripping out the control data at the beginning of the track should solve the problem.

...which I will definitely do in the future.
BUT, has cost me almost the whole day.
It shouldn't be difficult for CW to establish a simple routine, which will do the filtering of unwanted stuff to prevent such things to happen. Even if the fault is within the midi, everybody will at first think, that it is X3s fault. Which - in a way - is true, isn't it?
If it was my software, I would do everything in my power to prevent such things ;-)
Anyway - thanks for the help everybody :-)

This issue crops up every few months or so, so it could have been searchable in the forum.
 
I don't think Sonar should be in the business of automatically deleting midi event data from imported tracks, so I disagree that the issue is caused by something Sonar failed to do.
 
Sonar DOES give you the ability to see and delete whatever you wish from your midi tracks, and once you are aware of this issue, it takes a matter of a minute or 2 to open up and remove the target events.
 
Glad you have this worked out - good luck with it all.  :)
 
Bob Bone