Hello,
 
Was it mentioned that this occurs outside of Sonar.  Say same setup with a different software package (trial maybe) to see if it is consistent with the type a streaming that a DAW Does. 

FreeFly : I see firewire drivers , at this point I would consider getting the firewire card ..Im going to pass this by the canadain dealer/support ..see what they come up with !

FreeFly : the more I read the more is see the usb used for transfer/storage...I would get the Firewire running BTW you have to manualy invoke it in win8  see you use TI firewirecard...Im supprised its still a issue and you didnt try this option
 

Any chance you are plugged into a USB 3 port on the computer?  Some audio interfaces exhibit strange behavior if they are engineered or drivers written for use via a USB 2 port.
 
And - reaching - do your sample rates match between Sonar and the audio interface?
 
Bob Bone
 

 

robert_e_bone
do your sample rates match between Sonar and the audio interface?

 
Yes. Definitely correct settings. You wouldn't get a minute of playback with wrong sampe rate settings ...
 
 

robert_e_bone
Any chance you are plugged into a USB 3 port on the computer?  Some audio interfaces exhibit strange behavior if they are engineered or drivers written for use via a USB 2 port.

 
Yes, but there is only one physical USB port available and that piece of junk ... any chance I can downgrade that to USB???
 
I wouldn't have started using this tiny but relatively powerful machine if it hadn't worked so well for months ... so this turns into some sort of engineering crusade for me.
 
How can something work flawlessly over extended periods with heavy use ... and then just stop and no real explanation/solution can be found??
 
No hardware changes. No firmware upgrades. All music production related software tools unchanged. Sonar projects unchanged, ... which leaves IMHO only win 8.1 and its constant need to be updated as the source ...
 
I'm curious whether I'll get any sensible reply from Behringer on that matter??? For now I think I can only wait and see if they address or at least explain this ...
 
So the only idea I have left to fix the situation involves a gallon of petrol and matches ... but I reckon I should install a few more win 8.1 updates otherwise da d**n thing may not even burn ...

It is very likely that a windows upgrade broke you. One broke me last week. 3rd party tray apps (in my case tranzport, contour shuttle and the korg usb driver loader) that loads at startup which were installed in system32 were no longer loading for me. I had to move those system tray applications under program files and fix thier registry entries to point to the new locations to get them working again.

So a Windows update get definitely screw things up. :(

I can't believe it but I found it !!!!!!! Yeah !!!!
 
Pure coincidence, though ...
 
I was once more testing whether a UPS would help (which of course it did not), but noticed that the X32 digi mixer display starts to behave funny a few seconds before the X32 reboot happens ... so I tried fiddling with X32 mixer rotaries in that period and found it very slow responding as if it would be processing a lot of stuff ... and wondered how that can be???
 
hmmm ... the only time I had seen that before was when I had a MIDI loop going and so I started looking inside Sonar and found that somehow the default option to "Always echo current MIDI track" has turned on (which is totally strange because I hate that option and have it off ALWAYS) ... anyway, what makes it even stranger: the "current" track, which was set to auto echo MIDI, actually was a hidden + muted + archived MIDI track (hence I had never seen that, grrrrrrrrrrrrrrhhh!!!) which contains a single prg chg instruction (well, but that's muted and archived,right???)
 
So with that "Always echo current MIDI track" it must have received some MIDI messages from the X32 and echoed it back out (no clue what that could be ... I only have a single 1 in there per scene to change external FX once at song start) ... until it must have been enough to fill up some memory/buffer in the X32 and BOOOM !!! reboot ...
 
So this is 100% reproducible and I'm sure if Behringer RnD looks into target.cpp, line 94 this will have something to do with memory allocated to MIDI messages ...
 
Neither Sonar nor X32 seems to have any sort of MIDI loop detection, which is strange, especially if the consequence on the X32 side is a crash!!!

Is there a keyboard short cut (or even MIDI msg) which I may have hit by mistake that could turn  "Always echo current MIDI track" on and off ... ???
 
I really have no clue how that got activated and turned off and reactivated (because I had this problem in January, then it disappeared and last week it was back) ...

Wow, I am glad you found this! I had a similar issue with GR5 a long time ago where program changes were occurring at the end of a sandbox project that had been pulled forward through several versions of SONAR. The answer to that one was similar in that GR5 would run MIDI data down the other channel and apparently had captured write automation while I was flipping programs on playback one day. Took a lot of digging to find that one.
 
I am certainly no MIDI guru, so no idea of messages to enable/disable this on the fly, but is "perhaps" capture in read/write automation (how mine was caught). I am curious to the answer to this as well.
 
Didn't you say this was occurring with WMP as well though? I am really confused how that would trigger (I thought exported audio only contained audio). I may have misread that post when you were troubleshooting.

mettelus
Didn't you say this was occurring with WMP as well though? I am really confused how that would trigger (I thought exported audio only contained audio). I may have misread that post when you were troubleshooting.

No ... actually I had tried to explain that WMP did not cause a crash with stereo output while Sonar sending 2 channes did ... st*pid me could have spotted earlier that MIDI is one of the differences between MWP and Sonar ... but it's always easier in hindsight ...