[Solved] Is it a BUG?

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?

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
 

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

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.

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
 

@lawp: Well, if it kills the VST, then I would consider it "unwanted" ;-)
All the other 3rd party VSTs were not affected at all, so I guess they must have some sort of fail-safe mechanism, which X3 doesn't have.
@Bob: Thnx, you too :-)
 

Ah. Thanx for clarifying. In that case I would wish for the future, that the engine would give a dialog to delete undesired data in an automated process. Would save some time, I guess. 

CAL would work for now. The CAL free way would be to create a preset for the MIDI Event Filter MFX and "Process Effect" or just add the plug-in to the MIDI track.

@scook
Doesn't work. Even if I filter everything but the notes, sfz will mute the instrument.
 
 

I already uploaded it, but I cannot post any Urls... wait a second, maybe I can trick the forumscript ;-)

Allright, let's try it.
Ah, I can post links now :-)
 
www.echt-gute-tattoos.de/test.mid
 
That's it.
Try the drums or the piano with Si-Drum Kit or Si-String Section and you will see what I mean.

Ah, yes. Works now. I overlooked, that my track was split and the filter only took effect on the second half. Created a Preset and I am a happy camper now!
Thanks once more.

The filter does not have to be applied on a per-clip basis, it can be applied to the entire track using the FX bin. If the FX bins are not visible in the track header, modify the track header using the drop down at the top of the track view just below the track view menus to the right of the time display. It is the drop down labelled "Mix" in the illustration below from http://www.cakewalk.com/D...amp;help=Views.02.html (ignore the red box)

@Bob2
Like that?