Good day to all,
      I have been a member for a long time. Don't post that much, because I haven't had all the problems that seem to pop up. That starts my question. Are the problems really computer/software/hardware driven, or are they pilot errors. I look at the specs that people have, and some of the systems look incredible to what I have. Not complaining, I am satisfied with what I have. Most glitches I have are usually self caused. JBS, I call it. John being stupid. I know it must be frustrating to have a working system, then update, upgrade, add whatever and all of a sudden things go haywire. I find myself locked into others problems with the desire to help, but I don't have the problems. Maybe I just don't use the in-depth stuff as much as others. Don't get me wrong, I use most parts of the software. Not a lot of the synth parts as I have more synths than I can count. In the long run I find that I spend too much time worrying about others problems. This time could be spent in manuals, videos, etc., etc.
It's great to see all the good help that is here, even when 'written tempers' rage. I also realize there are so many variables. Just not seeing why so many problems on great systems. Just observing.
Good luck to all
MJ

musicjohnnie
Just not seeing why so many problems on great systems. Just observing.
 

Although many of the "problems" are pilot error, the computer system itself is somewhat of a combination lock...if one of the tumblers is off, things won't work. Here are some of the common issues I see here.
 

• The Windows version is ancient and requires re-installation
• Outdated drivers
• Windows hasn't been updated in months or years
• Older C++ libraries overwriting newer ones
• Virus or other malware infestation
• Graphics card issues
• Software that "hogs" the computer and causes latency spikes
• Non-recommended practices (e.g., using a USB interface with a hub)
• Spurious sound, video, and game controller drivers that need to be removed
• 3rd party plug-ins not written to spec
• Mixed 32-bit and 64-bit plug-ins
• Inadequate power supply
• Failing hardware (hard drive, RAM sticks)

 
And of course, computer poltergeists 

Since every system is built differently and not everyone uses the same hardware/software, there's bound to be an issue as nothing is perfect and no guarantees.
Still, with a little patience, there's always a workaround to get the job done and if it's a universal error, the bakers are very good at finding a fix. Most people are (generally) impatient and want everything here & now.     
 
Also, most people that are posting in here is because of some issue they're having and looking for help (so it seems like there are a lot of problems).........but, I think the vast majority are actually making music.

Mesh
Also, most people that are posting in here is because of some issue they're having and looking for help (so it seems like there are a lot of problems).........but, I think the vast majority are actually making music.

It's like that with all DAW forums. If you look at any DAW forums, you'd think that no music software works at all. Very few people post a thread that says "I'm in the middle of a project, and just thought you should know that nothing has caused problems."

That's true enough.    Or, as I'd say, "I'm in the middle of a project and have become inured for the moment to all the irritations like a lame controller pane, and paste issues, and the need to click twice in the loop begin and end box, and so I don't post anything." 

Anderton

Mesh
Also, most people that are posting in here is because of some issue they're having and looking for help (so it seems like there are a lot of problems).........but, I think the vast majority are actually making music.

It's like that with all DAW forums. If you look at any DAW forums, you'd think that no music software works at all. Very few people post a thread that says "I'm in the middle of a project, and just thought you should know that nothing has caused problems."

Nobody wants to jinx their project 

Sonar also has bugs and things that cause it to crash.  In my personal experience, Sonar is much less stable and crashes much more frequently than the other DAWs I use (Studio One and Reaper, both of which pretty much never crash).  In instances like this, there isn't a great argument for it being an issue with my system or computer.  This is a shame because I like Sonar a lot.

Graig's list seems to be spot on. I also think that its important to try to get a really solid computer first than work on getting the right software.  A little money spent on components will save a lot in the long run.  

for some reason "thread titles" (like the one used in this thread) seem to attract a lot of folks who have been waiting days, weeks, even months to dump out every single little problem they have ever had.
 
I believe for the most part, we are living in an age future zed computers.
everyone seems to take for granitite, the things we can do today with computers were un thought of just a few years ago.
 
thus believe that every thing should be perfect and a perfect world.
ive had my issues with sonar, ive been vocal about it too. pee'd off a few people in the process
but for the most part, ive been very happy using Sonar Vs. pro tools, Cubase, Exc.
most of my issues have been trivial, hardware, software, driver conflicts.
 
I still have a few grips today as well, but nothing that would have me leaving Sonar to go to another DAW
and nothing that would have me here in these forums trying to make a negative impact.
ive tried to problem solve issues here and have had great success, except the few that were related to improvements. but even those improvements that I think Sonar needs to fix, work on.
I cant really complain too much because every one works in a different way, what I may want, someone else does not. what I may like and think is a feature everyone uses every day, they may not.
so I have to recognize that in picking/choosing my battles.
 
I am 100% sure about one thing though, this is by far the best forum I have ever been a part of.
people will bend over backward to help you solve your issues and these are not just ordinary users, they are smart, helpful people who donate their time not only to help others, but to in turn better the software.
 
 
 

rlared
Sonar also has bugs and things that cause it to crash.  In my personal experience, Sonar is much less stable and crashes much more frequently than the other DAWs I use (Studio One and Reaper, both of which pretty much never crash).  In instances like this, there isn't a great argument for it being an issue with my system or computer. 

 
Hard to say. Studio One deliberately excludes running 32-bit plug-ins in a 64-bit version specifically to avoid one of the #1 source of crashes. Not sure about Reaper, I believe you can install bridging during installation, but if you look in the Reaper forums you'll see that bridging is hardly flawless there either. It's not Reaper's or SONAR's fault, just that bridging is, in the words of Wolfgang Kundrus (one of the main Studio One developers), an "inherently flawed technology."
 
I hardly ever have crashes with SONAR. Actually I can't remember the last time I had one that was related to SONAR itself. But whether it's my hardware, avoiding suspect plugs, not doing something that annoys SONAR, or whether the fates just smile on me, I don't know. I do know that a series of crashing problems magically went away when a) I switched to a different audio interface, b) I eliminated the "HD Audio Driver," and c) SONAR went to Platinum. I have no idea whether one of those, or all of these, are what led to the reliable behavior I enjoy now.