@ vladasynI'm sorry if my first post was a little cross, that's not like me.
 
I think that I was trying to make the point that Sonar works okay for many people (including me), on many hardware configurations, and OS.  If it is not working for you, then it is probably fixable, because, if it was Sonar's fault, we would all be having problems.
 
If you could give some more details, such as audio interface, buffer settings, system specs  etc., someone on here might be able to help you.
 
There is no reason why you should be experiencing these issues with Sonar.  If you want help to fix it, then go into a little more detail.
 
If you don't want help, then more fool you.
 
As for Sonar only supporting newer OS, I'm with Scook.  If X2 needed Windows 8, I would have stayed on X1 (which was as stable as a rock), or investigated Windows 8 if I really needed some feature of X2.
 
I loved my Roland MC 500, and could have continued using it if I'd wanted.  I used many Amiga Programs (including a great DTP package) that I had to abandon.  I could have stayed on Amiga, but felt the benefits of moving on outweighed the negatives.  That is the nature of Hitech.
 

Jeezz-I sure am heart broken-

vladasyn - don't worry about taking over the thread. The OP is gone. These threads always move away from the drama quickly. Hopefully you can benefit from the OP flameout.

It really doesn't matter what gear or computer you have, Sonar should NEVER crash, this is bad programming. A program should be able to take whatever you throw at it, and keep going. If a plugin etc, is messing up, Sonar needs to work around it. This is basic programming 101, dealing with exceptions. Crashing isn't the answer. Yes this is more difficult in practice than in theory but it doesn't really matter. Before all the bells and whistles, the program should be rock solid.

I would think that what happens in practice is way more important than what should happen in theory. We we could have a good discussion about what should happen but that is not going to solve the problem at hand.

vladasyn


I am sorryfor taking over the thread- I am not the original poster. I just felt- I could relate and myself was looking in to Apple products.

I usually would install Son 5 while S4 still installed. I think, I was using SP5 when 7 came. I installed 7, kept 5 and uninstalled 4 via "Add/Remove Program". I installed X1 and kept 8, when 2X was released, I uninstalled 8, kept X1 and installed 2x.

Well, the original poster was just venting and leaving, so don't worry too much about hijacking the thread.

If you could provide specific details on the issues you are having, along with your system specs, perhaps the forum folks can help you resolve some of them.

Bob Bone

Kroneborge


It really doesn't matter what gear or computer you have, Sonar should NEVER crash, this is bad programming. A program should be able to take whatever you throw at it, and keep going. If a plugin etc, is messing up, Sonar needs to work around it. This is basic programming 101, dealing with exceptions. Crashing isn't the answer. Yes this is more difficult in practice than in theory but it doesn't really matter. Before all the bells and whistles, the program should be rock solid.

So, if you put sugar into your gas tank, your car should purr like a kitten?  Should souffles stay fluffy with the window open in a construction zone?


So, it is Sonar's fault if for some inexplicable reason I cannot get it to install in 64-bit mode on a computer with 32-bit Windows running?

Would it be Microsoft's fault that my Xbox 360 can't read a disc that my dog ate - then humped (not sure which order)?

Would it be the auto manufacturer's fault that a hard-left turn into oncoming traffic might result in injury?

Please stick to helping to solve the problems at hand in the post - take up your position on how life should work in its own thread, so people can ignore it without clouding up another poster's issues.

Bob Bone

Ill have to agree with Kroneborge. Cakewalk need seriously try to get a solid DAW, rather than adding loads of features.

Major upgrade / changes is more likely gonna cause problems and a buggy unstable program. 

It is better to make simple / stable DAW, then add one feature at a time and see if that work.
Then it is easier to to fix it when it don't work quite well.

I say 1 step at a time.


that said, i still gonna use sonar for a while yet !
but i have seriously considered changing DAW as well. 

Why i started with sonar, was cause it was simple to use, easy to understand
and easy to set up and run.

Now it start to be just a little difficult to get the full overview of it.
but that's just my opinion.

No one is forcing you to use Sonar.

I'm still using 8.5.3 every day without any problems, so it's really up to you :)

The Correct Way To Uninstall Sonar is as follows:

To completely un-install SONAR X2 Producer from your computer. You will want to manually remove the SONAR installation files by deleting the following directories. Do this by doing the following:

1) Open the Run Prompt by holding down the Windows Key on your computer and pressing "R"
2) In the Run prompt type in the following and press [OK]: C:\Program Files\Cakewalk\
3) Delete the "SONAR X2 Producer" folder contained within

4) Open the Run Prompt by holding down the Windows Key on your computer and pressing "R"
5) In the Run prompt type in the following and press [OK]: %appdata%\Cakewalk
6) Delete the "SONAR X2 Producer" folder contained within

7) Open the Run Prompt by holding down the Windows Key on your computer and pressing "R"
8) In the Run prompt type in the following and press [OK]: %allusersprofile%\Cakewalk
9) Delete the "SONAR X2 Producer" folder contained within

Next you will want to delete your SONAR related registry keys by doing the following:

10) Open the Run Prompt by holding down the Windows Key on your computer and pressing "R"
11) In the Run prompt type in the following and press [OK]: regedit
12) Click [OK] will launch the Registry Editor. If prompted with a message "Do you want to allow the following program to make changes...", click [Yes].

*****
IMPORTANT: When you access the Registry Editor, create a backup by going to File > Export. In the Export menu, make sure you have "All" selected and that the "Save As Type" is set to "Registration Files (*.reg).

It is very important to create a backup of your registry because if you accidentally delete a registry key there is no undo function. You can, however, double-click on the Registry backup you made above to re-import your registry keys if you make any mistakes. You MUST re-import your backup (if needed) before restarting your computer.
*****

13) Now delete the following Registry keys:

HKEY_CURRENT_USER\Software\Cakewalk Music Software\SONAR Producer\X2
HKEY_LOCAL_MACHINE\Software\Cakewalk Music Software\SONAR Producer\X2


IMPORTANT: You will want to delete the "X2" folder at the end of these strings of keys. Do this by right-clicking on the ""X2" folder and selecting "Delete". Only do this for the "X2" folders in the locations above. If you do not see these ""X2" folders, proceed to the next step.

*Please note that this will remove any effects presets and key bindings you may have made in Cakewalk. You can back these up separately if you like from SONAR's Plug-in Manager and Color and Key Bindings menus.

At this point, you will want to re-install the product. We recommend temporarily disabling your startup programs by doing the following:

14) Open the 'Run' command again and type in the following: msconfig
15) Click [OK] and then click on the Startup tab at the upper right of the window that opens.
16) Uncheck all items listed, click [OK], then restart your computer. You can always recheck those items again at a later time.
17) Reinstall SONAR X2