Helpful ReplySonar Refuses to KILL UPDATE STill WOnt Die

Page: < 12 Showing page 2 of 2
Author
Post
Essentials Only Full Version
Adq
Max Output Level: -82 dBFS
  • Total Posts : 426
  • Joined: 2015/01/21 20:05:25
  • Status: offline
Re: Sonar Refuses to KILL 2015/09/17 19:48:17 (permalink)
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.
#31
doncolga
Max Output Level: -60 dBFS
  • Total Posts : 1519
  • Joined: 2006/01/03 17:15:48
  • Location: Statesboro, GA USA
  • Status: offline
Re: Sonar Refuses to KILL 2015/09/19 11:52:05 (permalink)
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.

HP Z220 Workstation I7 3770, 8 GB RAM, Windows 10, Sonar Platinum, RME Multiface II via PCIe, JBL 4326 w/sub, AvanTone MixCubes
#32
Beepster
Max Output Level: 0 dBFS
  • Total Posts : 18001
  • Joined: 2012/05/11 19:11:24
  • Status: offline
Re: Sonar Refuses to KILL 2015/09/19 14:26:28 (permalink)
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.
#33
Doktor Avalanche
Max Output Level: -32.5 dBFS
  • Total Posts : 4294
  • Joined: 2015/03/26 18:02:02
  • Status: offline
Re: Sonar Refuses to KILL 2015/09/19 15:05:04 (permalink)
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)
post edited by Doktor Avalanche - 2015/10/01 14:26:26

Sonar Platinum(64 bit),Win 8.1(64 bit),Saffire Pro 40(Firewire),Mix Control = 3.6,Firewire=VIA,Dell Studio XPS 8100(Intel Core i7 CPU 2.93 Ghz/16 Gb),2 x 1TB SSD (Samsung EVO 850),GeForce GTX 460,Yamaha DGX-505 keyboard,Roland A-300PRO,Roland SPD-30 V2,FD-8,Triggera Krigg,Shure SM7B,Yamaha HS5. Rap Pro,Maschine Studio+Komplete 9 Ultimate+Kontrol Z1,Addictive Keys,Waves Silver,Izotope Nectar elements,Overloud Bundle,Geist,Acronis True Image 2015.
#34
Doktor Avalanche
Max Output Level: -32.5 dBFS
  • Total Posts : 4294
  • Joined: 2015/03/26 18:02:02
  • Status: offline
Re: Sonar Refuses to KILL 2015/09/19 15:07:44 (permalink)
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.

Sonar Platinum(64 bit),Win 8.1(64 bit),Saffire Pro 40(Firewire),Mix Control = 3.6,Firewire=VIA,Dell Studio XPS 8100(Intel Core i7 CPU 2.93 Ghz/16 Gb),2 x 1TB SSD (Samsung EVO 850),GeForce GTX 460,Yamaha DGX-505 keyboard,Roland A-300PRO,Roland SPD-30 V2,FD-8,Triggera Krigg,Shure SM7B,Yamaha HS5. Rap Pro,Maschine Studio+Komplete 9 Ultimate+Kontrol Z1,Addictive Keys,Waves Silver,Izotope Nectar elements,Overloud Bundle,Geist,Acronis True Image 2015.
#35
Ham N Egz
Max Output Level: 0 dBFS
  • Total Posts : 15161
  • Joined: 2005/01/21 14:27:49
  • Location: Arpadhon
  • Status: offline
Re: Sonar Refuses to KILL 2015/10/01 09:55:17 (permalink)
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.

Green Acres is the place to be
 I dont twitter, facebook, snapchat, instagram,linkedin,tumble,pinterest,flick, blah blah,lets have an old fashioned conversation!
 
#36
Adq
Max Output Level: -82 dBFS
  • Total Posts : 426
  • Joined: 2015/01/21 20:05:25
  • Status: offline
Re: Sonar Refuses to KILL 2015/10/01 10:01:26 (permalink)
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?
#37
Doktor Avalanche
Max Output Level: -32.5 dBFS
  • Total Posts : 4294
  • Joined: 2015/03/26 18:02:02
  • Status: offline
Re: Sonar Refuses to KILL 2015/10/01 11:04:49 (permalink)
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.
post edited by Doktor Avalanche - 2015/10/01 11:18:57

Sonar Platinum(64 bit),Win 8.1(64 bit),Saffire Pro 40(Firewire),Mix Control = 3.6,Firewire=VIA,Dell Studio XPS 8100(Intel Core i7 CPU 2.93 Ghz/16 Gb),2 x 1TB SSD (Samsung EVO 850),GeForce GTX 460,Yamaha DGX-505 keyboard,Roland A-300PRO,Roland SPD-30 V2,FD-8,Triggera Krigg,Shure SM7B,Yamaha HS5. Rap Pro,Maschine Studio+Komplete 9 Ultimate+Kontrol Z1,Addictive Keys,Waves Silver,Izotope Nectar elements,Overloud Bundle,Geist,Acronis True Image 2015.
#38
mettelus
Max Output Level: -22 dBFS
  • Total Posts : 5321
  • Joined: 2005/08/05 03:19:25
  • Location: Maryland, USA
  • Status: offline
Re: Sonar Refuses to KILL 2015/10/01 12:39:11 (permalink)
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.

ASUS ROG Maximus X Hero (Wi-Fi AC), i7-8700k, 16GB RAM, GTX-1070Ti, Win 10 Pro, Saffire PRO 24 DSP, A-300 PRO, plus numerous gadgets and gizmos that make or manipulate sound in some way.
#39
Adq
Max Output Level: -82 dBFS
  • Total Posts : 426
  • Joined: 2015/01/21 20:05:25
  • Status: offline
Re: Sonar Refuses to KILL 2015/10/01 12:54:36 (permalink)
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.
#40
Beepster
Max Output Level: 0 dBFS
  • Total Posts : 18001
  • Joined: 2012/05/11 19:11:24
  • Status: offline
Re: Sonar Refuses to KILL 2015/10/01 13:33:45 (permalink)
In a "new" project with no 32bit/DX plugs this is still occurring to me as well. It doesn't hang for as long because the project is much smaller (I mentioned earlier it seems directly related to the size/complexity of a project) but it's still there.
 
No controllers attached. I do have a VRM Box though (setup VIA SPDIF on my Scarlett 18i6) but this, AFAICT, only started occurring with SPlat.
 
@H&E... do you have a VRM Box hooked up?
#41
Doktor Avalanche
Max Output Level: -32.5 dBFS
  • Total Posts : 4294
  • Joined: 2015/03/26 18:02:02
  • Status: offline
Re: Sonar Refuses to KILL 2015/10/01 14:08:24 (permalink)
The obvious way to rule out the VRM box is to remove it... I would think your issue is extremely unlikely to be related to the OP.
post edited by Doktor Avalanche - 2015/10/01 14:19:12

Sonar Platinum(64 bit),Win 8.1(64 bit),Saffire Pro 40(Firewire),Mix Control = 3.6,Firewire=VIA,Dell Studio XPS 8100(Intel Core i7 CPU 2.93 Ghz/16 Gb),2 x 1TB SSD (Samsung EVO 850),GeForce GTX 460,Yamaha DGX-505 keyboard,Roland A-300PRO,Roland SPD-30 V2,FD-8,Triggera Krigg,Shure SM7B,Yamaha HS5. Rap Pro,Maschine Studio+Komplete 9 Ultimate+Kontrol Z1,Addictive Keys,Waves Silver,Izotope Nectar elements,Overloud Bundle,Geist,Acronis True Image 2015.
#42
Beepster
Max Output Level: 0 dBFS
  • Total Posts : 18001
  • Joined: 2012/05/11 19:11:24
  • Status: offline
Re: Sonar Refuses to KILL 2015/10/01 14:33:23 (permalink)
Dok... it's EXACTLY the same issue. We established that early on in the thread and the similarities continue (as both of use have had a chance to see it occur beyond the original test paramters). I have not seen him post anything to the contrary. I am more familiar with this issue than others may be who are not experiencing it (obviously).
 
I am now trying to figure out what things H&E and I have in common in regards to our setups. Please do not dismiss troubleshooting/correlation attempts. This could expose a system specific bug/problem that can be reported and corrected.
 
Knowaddiamean? Not trying to be a dick but I would like to figure out WTF this is... especially if some are experiencing it while others are not.
 
Cheers
post edited by Beepster - 2015/10/01 14:42:41
#43
Doktor Avalanche
Max Output Level: -32.5 dBFS
  • Total Posts : 4294
  • Joined: 2015/03/26 18:02:02
  • Status: offline
Re: Sonar Refuses to KILL 2015/10/01 14:43:19 (permalink)
If either of you cannot "kill Sonar" it's almost certainly drivers or plugins. More likely drivers if only a reboot will resolve it (HAL is locking something).
 
If plugins are ruled out then it's drivers/firmware. If both of you have similar systems hardware then bingo (so sure not saying your question about running VRM is invalid), other than that likelyhood is both of you have got a dodgy driver (or related firmware) somewhere, but probably a different one. First thing to do is update your audio interface and drivers in your instance (it looks like you aren't going to do this so you can't rule this out as an issue, so basically this is a standstill.. fair enough if that's what you want ).
 
Yet another suggestion... Have any of you tried the delete AUD.INI trick? (google for details)... Ta...
Anyway I think everything possible here has been suggested it's just a matter going through it one by one.
 
It's definitely not a Sonar bug, if Sonar was a possibility it would crash and then be able to start without needing a reboot or being killed in task manager.. Sonar does not have priority over the operating system here, however drivers do.
 
BTW software being locked out by drivers is fairly common...
post edited by Doktor Avalanche - 2015/10/01 18:06:57

Sonar Platinum(64 bit),Win 8.1(64 bit),Saffire Pro 40(Firewire),Mix Control = 3.6,Firewire=VIA,Dell Studio XPS 8100(Intel Core i7 CPU 2.93 Ghz/16 Gb),2 x 1TB SSD (Samsung EVO 850),GeForce GTX 460,Yamaha DGX-505 keyboard,Roland A-300PRO,Roland SPD-30 V2,FD-8,Triggera Krigg,Shure SM7B,Yamaha HS5. Rap Pro,Maschine Studio+Komplete 9 Ultimate+Kontrol Z1,Addictive Keys,Waves Silver,Izotope Nectar elements,Overloud Bundle,Geist,Acronis True Image 2015.
#44
robert_e_bone
Moderator
  • Total Posts : 8968
  • Joined: 2007/12/26 22:09:28
  • Location: Palatine, IL
  • Status: offline
Re: Sonar Refuses to KILL 2015/10/01 18:05:51 (permalink)
To answer an earlier question about what to do when you absolutely love some 32-bit plugins - you might consider installing a completely 32-bit Sonar, and 32-bit version of whatever 64-bit plugins you can.
 
This way, you could build some projects completely in 32-bit mode, where nothing should be bridged, and you would have only the limitations of potentially not having access to some plugins that didn't have a 32-bit version, and also the limitations of a 4 GB address space - overhead.
 
But at least it should all work, and you could run like that for quite a long time, and you would have the choice of which bit-version of Sonar you want to build a given new project with.
 
Bob Bone
 

Wisdom is a giant accumulation of "DOH!"
 
Sonar: Platinum (x64), X3 (x64) 
Audio Interfaces: AudioBox 1818VSL, Steinberg UR-22
Computers: 1) i7-2600 k, 32 GB RAM, Windows 8.1 Pro x64 & 2) AMD A-10 7850 32 GB RAM Windows 10 Pro x64
Soft Synths: NI Komplete 8 Ultimate, Arturia V Collection, many others
MIDI Controllers: M-Audio Axiom Pro 61, Keystation 88es
Settings: 24-Bit, Sample Rate 48k, ASIO Buffer Size 128, Total Round Trip Latency 9.7 ms  
#45
Ham N Egz
Max Output Level: 0 dBFS
  • Total Posts : 15161
  • Joined: 2005/01/21 14:27:49
  • Location: Arpadhon
  • Status: offline
Re: Sonar Refuses to KILL 2015/10/01 18:08:44 (permalink)
Well thanks to ALL especially Dr A I think I found my millstone...
 
My MOTU midi express 128 was keeping it held, I turned off devices one by one until Sonar Killed!!!
 
I have the latest 64 bit driver so may google the problem.

Green Acres is the place to be
 I dont twitter, facebook, snapchat, instagram,linkedin,tumble,pinterest,flick, blah blah,lets have an old fashioned conversation!
 
#46
Doktor Avalanche
Max Output Level: -32.5 dBFS
  • Total Posts : 4294
  • Joined: 2015/03/26 18:02:02
  • Status: offline
Re: Sonar Refuses to KILL 2015/10/01 18:29:29 (permalink)
Ham N Egz
Well thanks to ALL especially Dr A I think I found my millstone...
 
My MOTU midi express 128 was keeping it held, I turned off devices one by one until Sonar Killed!!!
 
I have the latest 64 bit driver so may google the problem.




Assuming you are on the latest driver/firmware, may I suggest your first course of action may be to uninstall the driver/reboot/reinstall it/reboot/reset your interface settings on hardware and software (assuming there is such an option on your interface) and reconfigure it.
 
Also look at deleting AUD.INI if that does not work (google for details).
 
Cheers..
post edited by Doktor Avalanche - 2015/10/01 18:39:52

Sonar Platinum(64 bit),Win 8.1(64 bit),Saffire Pro 40(Firewire),Mix Control = 3.6,Firewire=VIA,Dell Studio XPS 8100(Intel Core i7 CPU 2.93 Ghz/16 Gb),2 x 1TB SSD (Samsung EVO 850),GeForce GTX 460,Yamaha DGX-505 keyboard,Roland A-300PRO,Roland SPD-30 V2,FD-8,Triggera Krigg,Shure SM7B,Yamaha HS5. Rap Pro,Maschine Studio+Komplete 9 Ultimate+Kontrol Z1,Addictive Keys,Waves Silver,Izotope Nectar elements,Overloud Bundle,Geist,Acronis True Image 2015.
#47
Ham N Egz
Max Output Level: 0 dBFS
  • Total Posts : 15161
  • Joined: 2005/01/21 14:27:49
  • Location: Arpadhon
  • Status: offline
Re: Sonar Refuses to KILL 2015/10/01 18:36:03 (permalink) ☄ Helpfulby Doktor Avalanche 2015/10/01 18:47:15
OK part 2
I don't know which of the two fixes helped but
1  I removed and reloaded the 64 bit driver
2  and I think this was it, the MOTU was plugged into a USB 3 port I move4d it to a USB 2 and now Sonar behaves itself.
 
thanks to all for the thought processes ..

Green Acres is the place to be
 I dont twitter, facebook, snapchat, instagram,linkedin,tumble,pinterest,flick, blah blah,lets have an old fashioned conversation!
 
#48
robert_e_bone
Moderator
  • Total Posts : 8968
  • Joined: 2007/12/26 22:09:28
  • Location: Palatine, IL
  • Status: offline
Re: Sonar Refuses to KILL 2015/10/01 22:49:42 (permalink)
MANY audio interfaces completely freak out if they are plugged into a USB 3 port, rather than a USB 2 port.
 
I have had it happen in the past, and my current audio interface had some patches to it that let you use either port, but I still generally plug it into a USB 2 port.
 
Some older computers may still have 1 or 2 USB 1.1 ports, and those might not work very well either, for many different brands/models of audio interfaces.  They mostly seem to like USB 2 ports, from what I have seen/experienced.
 
Bob Bone
 

Wisdom is a giant accumulation of "DOH!"
 
Sonar: Platinum (x64), X3 (x64) 
Audio Interfaces: AudioBox 1818VSL, Steinberg UR-22
Computers: 1) i7-2600 k, 32 GB RAM, Windows 8.1 Pro x64 & 2) AMD A-10 7850 32 GB RAM Windows 10 Pro x64
Soft Synths: NI Komplete 8 Ultimate, Arturia V Collection, many others
MIDI Controllers: M-Audio Axiom Pro 61, Keystation 88es
Settings: 24-Bit, Sample Rate 48k, ASIO Buffer Size 128, Total Round Trip Latency 9.7 ms  
#49
Page: < 12 Showing page 2 of 2
Jump to:
© 2025 APG vNext Commercial Version 5.1