Enabling MIDI Out may crash Sonar X3 [solved]

I have been experiencing frequent crashes doing certain things (see below) and Sonar X3 will freeze. It will never recover and I try to stop it in Task manager. After a few minutes it finally dies - usually it is easier to just restart or log out/log in.
 
I'd love to send a crash report so this can get fixed, but I never see a crash dump. Are there any things I can do to help out?
 
The crashes all seem to be related to MIDI channel routing. I frequently use an external application (a fractal sequencer) that sends MIDI events (notes, controllers, etc.). I use LoopBe30 to create internal MIDI ports and I select them as input channels on Sonar Tracks.
 
Often I will have 3, 4 or 5 voices on as many MIDI channels, so I will select LoopBE MIDI in and channel 1, 2, 3 or whatever on the Sonar track and send the MIDI data to a VST instrument (typically Reaktor or Kontakt, but I don't think it matters).
 
While setting up the tracks, usually I have no problems with one or two such tracks, but when I reach 3 or higher, I may often get a crash (hang/freeze/white screen/SONAR not responding).
 
I've resorted to saving often and progressing in steps. Eventually I can get things set up, and often again, Sonar will freeze during recording, but eventually I can finish. But this is far from ideal and a real step backwards for Sonar.
 
I have nothing more to add. This didn't happen in Sonar X1 or X2 and doesn't happen using Live 8 in a similar fashion (that is, using LoopBe30 and these VSTs with the same MIDI generator). I haven't used X1 or X2 in some time, so perhaps I aught to try them in Windows 8.1 as a verification that it is unique to X3).
 
So, in short, I'd like to be able to submit some sort of error report - how to do so?
 
This post is the closest I can come to an error report.
 
Attached is a picture of a setup I used yesterday while evaluating a new Konatakt instrument called REV. I had about 8 or 9 crashes setting this up. There are 5 Kontakt tracks - no effects, no ProChannel (except for a limiter on the MASTER):
 

 
Here's the final mix:
 
"Tragedy in Tacloban"

http://soundcloud.com/arachnaut/tragedy-in-tacloban
 
 
 
 
 
 

I forgot to update my sig, I am using X3c.
All my drivers are up-to-date and the system is running very well. I don't run virus scanners.
This seems to me to be related to this, reported earlier and still not fixed:
 
http://forum.cakewalk.com/X3-freezing-because-of-MIDI-routing-m2900977.aspx

It took me no longer than 5 or 10 minutes to recreate the entire track setup and start recording using X2a. There were no crashes or glitches whatsoever.
 
Using X3c it took all afternoon yesterday because of the crashes.
 

Fair enough, only I've read about a few people who seem to be having problems starting with templates not created in X3
 
Carry on... Nothing to see here....

I deleted all my custom templates and started with the factory versions.
 
Here are the changes I had made on the older template, in case this impacts others:
 
I added custom BMP files for the track icons - one for Output and one for Master.
 
I made the Master and Output buss visible, but not the Metronome and Preview buss.
 
I'm sure I made a lot of changes to the Track Control Manager as well to display things the way I like.
 
I put some comments in the Project Info page (copyrights, etc.).
 
I think I'll go with this default template for a while and see if things improve.
 
I do have a lot of track templates made (again mostly just synth BMP icons and colors). I think I'll lay off them for a while, too. At least until the older MIDI routing issue gets fixed (X3d, perhaps?).
 

> All my drivers are up-to-date and the system is running very well.

The procedure above could fix a specific issue with a specific version of Sonar freezing regardless of whether your system may/may not be working overall.
 
Please carry on diagnosing your issue,but If you are still in the same situation and need to go to Cakewalk I suggest you fully follow the procedure in my original post (which is not just about drivers or your system) even if you believe your drivers are up to date, first to rule out any existing unknown scenarios. Please never assume anything. Otherwise good luck.

Cheers...

I've deleted all the old track and project templates I made and started from scratch with blank templates.
 
I've encountered problems when I make a track template, for say Kontakt. I usually put a Kontakt BMP icon file on it just before I save the template.
Sometimes it seems that Sonar crashes on load. Maybe my BMP format is wrong, but it is the same size (in pixels and bytes) as the standard track and synth icons.
So I've eliminated all the glitter and stuck with just thee built-in templates and icons. These icons, however, didn't seem to cause problems in Sonar X2.
 
I have no problems at all when I use a MIDI keyboard (omni) or standard MIDI files, but when I use an external MIDI program (such as Reaktor or the fractal generator Tune Smithy) I have problems with using multiple midi channels on the virtual MIDI port.
 
The virtual MIDI connector I use is called LoopBe30 which has always been stable for me on XP, Win 7 and Win 8, using Live or previous Sonar versions, so I don't think that is it. I had to re-install it for Windows 8.1 because it is an unsigned driver, but that has been acknowledged on the developer's web site as an issue. It is a native WDM kernel driver. I had to do the same thing for Windows 8.
 
Well, I'll see how this develops...
 
Maybe I should route my MIDI keyboard to LoopBe30 using MIDI-OX and try that virtual port for everything for a while...
 

Can't you as the creator edit the initial post and change the subject?

Just open the first post and alter the subject line.
 
Bob Bone