• SONAR
  • OMG Now I know why everyone screams about sonar! (p.2)
2016/01/19 09:08:50
Bristol_Jonesey
I was mumbling last night, my wife told me not to eat cheese before bedtime
2016/01/19 09:18:23
MarioD
Other questions that I have are:
What is your OS?
What is your sound card/audio interface?
What is your antivirus and was it on during installation?
What are your computer specs, ram, HDsetc?
2016/01/19 10:47:26
Anderton
notscruffy2
Even though hyperbola has been mainstreamed in what passes for modern discourse it has not been shown to been effective in providing solutions.



Highly tweet-worthy  If you don't tweet it, I will!
2016/01/19 10:53:02
thedukewestern
Sorry for your frustrations - Some of the best things about being a sonar customer can be found here in this forum.  The other thing is their telephone support - http://www.cakewalk.com/Support/Contact  Ive had to call from time to time - the thing is they are super cool, and they are always there, and hold times are usually minimal to non existent.   I had a botched install last year with rapture pro synth that took 20 minutes to figure out via phone support.  Once your up and running its a fantastic platform and community!
 
I hope this helps
2016/01/19 11:07:16
robert_e_bone
Here's the thing.  IF Sonar itself was at fault for the issues you are having, then there would be an ENDLESS set of very loudly typed complaints about it - in other words, we would easily see a whole bunch of threads/posts indicating some major problems with the current release of Sonar.
 
The fact that this is NOT the case, indicates a high probability that the issues you are currently experiencing, as maddening as they most certainly are, are likely to be some set of solvable local issues with your system, like maintenance or interference from other programs, or some sort of download issues (perhaps antivirus corruption of downloaded files), or that sort of thing.
 
The GOOD thing is that because whatever is going on for you is likely some sort of local system issue, it is also QUITE probable that with your engagement in the debugging analysis, and the assistance of a bunch of really helpful and knowledgeable forum folks, we can get to the bottom of the issues and get your system fixed up.
 
To DO that, we really need more information ABOUT your system, and details about the issues you are having.  We really do need to know what OS you are running, whether or not you are up to date with Windows maintenance, etc., as had been asked in a post above - prior to this one.
 
In addition, it really is a good idea that you go through an uninstall of all of the demo software, since you won't be using it anyways, and because it will help eliminate things that for whatever reason might interfere with the proper installation and operation of both Sonar and the Cakewalk Command Center.
 
So, please provide:
 
Operating system, and indication on its maintenance condition
Cakewalk Command Center version
Sound card or audio interface being used, AND information on version of its drivers
Computer info: CPU, memory, hard drive models (it makes a difference)
Any detail you can provide about installation of Sonar, including demo versions, etc.
 
There are a bunch of folks here that will bend over backwards to help you get all of this sorted out, and I hope you are willing to work with us to get you squared away.  :)
 
Bob Bone
 
2016/01/19 12:32:44
notscruffy2
It is yours.
2016/01/19 15:35:06
JoeyAudioey
eph221
Oh I'm sure it's my fault, no doubt about that.  But all the other daws are idiot proof :D  Last night I was absolutely stunned by how great and useful audiosnap is.  Anyways..I'll figure it out.  I think I'll just download ccc and start over.  



It might not be a good idea to just start trying things. Use your resources - all the people in this thread appear willing to help. I'm willing to bet this is an easy fix, I've seen this happen a lot when there's an issue with the initialization of the audio driver (which isn't a SONAR problem necessarily, but it can prevent SONAR from opening). 
 
Try resetting your AUD.ini file, sometimes that'll do it:

 
With SONAR closed...
 
1) Open the Run Command by holding down the Windows key on your keyboard and pressing "r".
2) At the run prompt type the following: %appdata%\Cakewalk
3) Navigate to your SONAR folder
4) Locate and delete the file named AUD or AUD.ini
5) Close the folder and re-launch SONAR
 
That may or may not do it. The more details you can give, the better, and remember that support is only a phone call or email away.
2016/01/19 17:34:26
Keni
tenfoot
Have you tried manually running the latest update? It will be located in whatever directory you have set in CCC.
 
And OMG......not everyone is screaming about Sonar😠


Many of us are screaming GOOD things about Sonar!

;-)
2016/01/20 17:12:45
TPayton
Anderton
notscruffy2
Even though hyperbola has been mainstreamed in what passes for modern discourse it has not been shown to been effective in providing solutions.



Highly tweet-worthy  If you don't tweet it, I will!




I also appreciated this well crafted sentence and its message.
12
© 2026 APG vNext Commercial Version 5.1

Use My Existing Forum Account

Use My Social Media Account