Sorry, I've not read the whole thread, but I've contacted Focusrite support recently, and they've said that to revert firmware "the interface would need to go to a service center". Also they don't recommend update MixControl and firmware, if all is working fine, and if it is not, they ask to contact them to try to solve it.

My rig was handing up when I'd close it out and sometimes when I'd delete a 32 bit VI running on a bridge.  Since I've gone back to my older PCIe RME interface, it's behaving nicely.  I've had this thing for a *long* time.  Can't seem to get away from PCIe.  I supposed I'll use the USB interface for my notebook.

Adq
Sorry, I've not read the whole thread, but I've contacted Focusrite support recently, and they've said that to revert firmware "the interface would need to go to a service center". Also they don't recommend update MixControl and firmware, if all is working fine, and if it is not, they ask to contact them to try to solve it.

Thanks for that input. As annoying as this issue is everything is working normally and this does seem to have only started occurring since Platinum. It COULD be an audio driver issue but I certainly am NOT going to futz with firmware stuff if it requires actual "servicing" of the device.
 
Oof... I am glad I did not just go ahead and update. FR should split their software and firmware updates out... or at least allow for firmware rollbacks. Almost sounds like the chip(s) needs to be yanked and replaced for a rollback or tossed in an EPROM writer.
 
I will be contacting them to confirm what's up when I get a chance and I am probably being paranoid. Just want to know what, if any, escape plans are available.
 
Totally not about to trash a working setup over this.

Adq
Sorry, I've not read the whole thread, but I've contacted Focusrite support recently, and they've said that to revert firmware "the interface would need to go to a service center". Also they don't recommend update MixControl and firmware, if all is working fine, and if it is not, they ask to contact them to try to solve it.

My interface was working fine with saffire. Then 3.6 drivers came around and it was working super. Looking at the Beep not everything is working fine is it?

Cheers..
 
(EDITED, pointed to wrong person)

Beepster
FR should split their software and firmware updates out... or at least allow for firmware rollbacks.

Good reason for that. The firmware interacts with the driver. They are not seperate entities.

I've only ever seen one bad update from Focusrite, even with beta, and even then it wasn't much of a problem.

WELL here is an update
removed all the 32 bit VSTs.
Start a NEW project, insert ONE 64 bit VST.
Close Sonar.
 
try to use another program , it cannot access my audio interface. WHY?
Because Platinum is still residing in task manager, and will not BE KILLED.
 
Log off or reboot is the only solution.

I'm sorry, maybe you've said it already, but do you use any midi inputs/outputs in Sonar, and if you use, what are this devices?

Ham N Egz
WELL here is an update
removed all the 32 bit VSTs.
Start a NEW project, insert ONE 64 bit VST.
Close Sonar.
 
try to use another program , it cannot access my audio interface. WHY?
Because Platinum is still residing in task manager, and will not BE KILLED.
 
Log off or reboot is the only solution.

Have you really removed all the plugins? Start it in Sonar safe mode and double check this:
https://www.cakewalk.com/Documentation?product=SONAR%20X3&language=3&help=Dialogs2.094.html
 
Definitely not Sonar otherwise we will all be experiencing the same issue. There is obviously another process locking it. Check over the thread again I suggest esp look at drivers and firmware. Also if you have antivirus enabled temp disable it.
 
You could try bundling the Sonar project and unbundling to see if this clears the issue (unlikely but worth a go).
Another thing to do is a full virus/malware scan of your computer in case a virus is the process locking it. I recommend malwarebytes and avg.
 
Also download a copy of process explorer and investigate what else is running alongside SONAR.EXE:
https://technet.microsoft.com/en-gb/sysinternals/bb896653.aspx
 
Ta
 
p.s. adq may also have a point here, a driver for one of your controllers could be holding it up also. Turn them off to rule it out. Also turn off your interface to see if it "releases" Sonar.

I also recommend Adq's comment. I had an older MIDI controller that had to be shut off after SONAR was closed or else SONAR kept "looking" for it.

When bringing SONAR online is best to power on interface/controller first and shut down in the reverse order.

I don't even need to switch midi controller off, just to press any note on midi keyboard, and Sonar stops.
But it seems that Ham N Egz may have some other problem.