I realy start to think ,since I moved to 64 bit SONAR ,,,,,,,,it must be the conflicts of 32bit plugins .......I use some 32 bit plugins still ,but few ................I shall try to get them all in 64bit ....I see

But then the bitbridge or jbridge people are to blame !
I recommend MOST highly , Cakewalk developing its own bridge tool ; which is rocksolid !

Just my thoughts to it

kindest regards

I recommend all developers of vst plugins devote time & energy in making sure all of their range is updated to 64 bit versions.


But it's not going to happen

X2a is running reasonably well here although it does seem much more quirky that what I had in X1d. I'm looking for a new patch soon I hope.

Regarding the saving I agree it should be SOP but I agree even more with whoever posted that I shouldn't have to save every time I do something significant. This is 2013 not 1987.

Regards

SteveStrummerUK

Can you guys help me understand something here.

I've read through this thread (and many other similar ones) and a lot of you are making a big thing of how long SONAR runs for you without a crash, or more accurately, before a crash. This, I'm guessing, is a way of illustarting how stable SONAR is running for you?
 
Which leads me to a couple of thoughts...
 
Firstly, wouldn't a more accurate portrayal of reliability be garnered if, instead of stating simply how long SONAR has been running, you were to state what you were actually doing with SONAR during that time, and how often you were doing it.

And that is the crux of the matter right there. ^

Here's a prime example ... I had no problems running X2 W/QF while I was remixing/remastering old projects. Where I ran in to problems was when I started Tracking and then installed the A Patch.

Sonar does run very well ... if I don't use the Pro Channel, Track Lanes, Envelopes, Quick Grouping, and Screensets.

And that if is where these threads fall apart and people get their nose bent out of shape. I'm not excluding myself from that by the way.

Obviously I say 'unknown' procedure, as once you've identified it, you can address the problem to prevent further crashes. I would imagine the biggest pain is when a certain technique or procedure only occasionally causes a problem - especially if it's in the same project.

How do you address the Concrete Limiter from not working? LINK (If you don't have the CL, you won't see this problem)

How do you address all the modules from randomly stop working? LINK (If you don't use the PC you won't see these problems)

How do you address Take Lanes from not working? LINK LINK LINK LINK (If you don't use V-Vocal, you won't see these problems)

How do you address Track View related crashes? LINK (If you don't try to change Inputs in this manor you won't see this problem)

I've experienced all of those, as well as the other users who started these links.

If you don't use those things, you won't run in to those problems, but that doesn't mean that Sonar as a whole is stable.

I only bring this up to try and point out, once again, that I'm not just sitting here arguing about Sonar's stability for the sake of arguing. It's not a stable program depending on how you use it, and in my opinion it's not right to come on the forum and make such outlandish claims as you have never lost work in 7 years without a giant 'but' disclaimer of some sort.

The problems I run in to are legitimate, documented problems by other users. I think some of the problems mentioned above have been fixed by the way. But the point is, if you use all the features of the Producer Edition, and some features that cross over in lesser versions, you will run in to problems. It's not possible not to.

Here's another example that makes it so frustrating ...

This is one of the 250 bugs the A Patch fixed ... "Cloning a track within a folder puts it in another folder (CWBRN-1191). The patch did not fix this problem. It's still doing it

Thanks,

Bub

Cloning a track within a folder puts it in another folder

 
fwiw: I cloned two tracks in two different folders last night (one with two cloned tracks and one with three cloned tracks). All cloned tracks went into the parent (correct) folder. I recall it because I was kind of surprised.
 
That said, see my previous post about quirky behavior. I had numerous things going on and finally restarted X2 which seemed to solve the quirkiness. But the tracks were cloned to the correct folder. Just for reference they were audio tracks.
 
Regards,

Bub

Mick Moreau

Like Stratman, I too have been using Sonar for a long time (Since cakewalk 2004).

Me too. I've been using Cakewalk software since Pro Audio 9.0. Can't remember how long ago that was, I'm thinking 98'ish?

Now, I will preface my statement with the fact that I DO save often just to keep from losing important stuff as I would do in ANY software program I use.

Me too. I have Sonar set to save every 60 seconds.

All of my cakewalk experience until X1, was in the Home Stduio versions.

All of mine were with Producer Editions.

I dropped the whole dime on the full X1 when it first came out.  I didnt work well with my new system and had a lot of small problems that got repaired over time with updates. I actually went backwards and bought Sonar 8 full, and Cakewalk was nice enough to provide me with the 8.5 upgrade links so that I could have all the tools.  Once upgraded, 8.5.3 worked flawlessly on my system.

IIRC 8.0 was a crash fest. 8.5.3 is still my favorite DAW of all time.

I waited thru X-1 and when it went to X2 I upgraded immediately.  With a couple of insignificant glitches (still no lost work due to saving), X2 has performed to expectations.

Now before you jump all over me, Bub I will admit to NOT being a high end Recording studio user, but I do a lot of work with Midi combined with audio using an 6 year old audiophile 2496.  I record live sometimes, but mostly in house audio and midi equalling close to 80 tracks depending upon my needs.  Also, I use a lot of effects and until I get into multiple softsynths I dont have any real problems.  Even still they are mostly user controlled error on my part.  With a some research, and using the forum, I get what I need in plenty of time.

From everything I've read those 2496 cards are rock solid. I would never jump you. Your one of the many members here that can have a rational conversation about these kind of things. There's only a handful of us that get in to these virtual slug fests from time to time. ;)

Sorry to hear that youve been having a lot of problems with it, but if moving on to something better will help you get the job done then you probably should.  The way it reads in the last 3 pages there isnt any amount of convincing you that Sonar is a good platform, but from where I sit... its the best yet (for me)

Hope you find a form of a solution that suits you.

Keep in mind ... the A patch alone fixed 250 bugs ... Seems to me you would be hard pressed not to run in to one, that's why when people come in and claim they've never lost work work in 7 seven years and see no problems it seems so unbelievable. Heck, even using Auto-Save I've lost work because of crashes in Sonar caused by VST's.

All the other DAW's I've tried work. I've been using Reaper a lot, and I've been using a lot of the VST's that come with Sonar in it. I had one crash, it was a Cakewalk VST, and Reaper reset the VST and I kept on working. When it happened in Sonar, I would get a hard crash and have to reboot. It shouldn't be that way.

Anyway, I've been tracking all day and so far so good since I created that separate user account. That looks very promising.

It's good to see you Mick. It's been a while. Hope all is well.

Bub

Hi Bub, :)
 
Yeah, it has been a while, but I still pop in every couple of days to see whats new, read the threads and maybe learn something that helps me somewhere down the road.  If I do post, I try to be as objective, and factual as I can from the only viewpoint I have... which is mine...  Ive seen a lot of upset people over the years and if there is one thing I have learned from watching the "angry" threads is that it does little good to attack.  Everyone has their own viewpoint, set of circumstances and its very rare that we see "identical" sets of circumstances... especially when it comes to software and DAWs.
  Despite the vitriole thats been displayed recently, Ive learned some things in this very thread that will help me later on for that possibility when I AM a higher end studio user.
  I also like to see the kindness and civility pop up too (as in your response to my post),  made me feel pretty good about things and show that you care about what we all are going through.  In the end we all want something similar... the best operating platform, without so many bugs, and to make music.
 
Glad I came and participated in this one..
Thanks Bub :)
 
 

John T


I think X2 is currently a bit cranky. Here's my favourite current one: pressing the expand button to show ProChannel on a bus. About 50% of the time, that's a total white out, restart-the-computer crash for me.

Don't blame cake for this one. It is more likely to be related to the video card, driver or ram. 

I was seeing this every once in a while till i figured out I needed to increase voltages to my ram to get it stable. I could also have been my video card drivers but while researching display problems in Blender (3d design software) I figured out my problem. With that issue corrected no more video related issues with sonar so far. 


you can also check the sonar preferences/display setting to see if the use hardware acceleration is enabled. try togging that setting.

Edited for clarity.

and just for the sake of saying it, there are many work arounds these cakewalk pros know about
 and learning about .things you cant do like run vvocal on a track without bouncing( crash everytime) screen sets)crash
 and many more.
 funny how they alway say in a kind way .where stupid and run  battlefield 3  with origin and steam and 3 other apps when we record, i too have a clean install on arig with nothing but sonar on it
 i play games on my home computer not my daw. so please quit the sonar is perfect and all the other posts that rub it in how you have a 5 thousand dollor gold sound capture device that makes coffee for you as it records your tracks from bed. its a fact sonar runs like crap on the basic computer
 i run all those other daws flawless with my rig sonar is the only one that crashs every day drops out every 20 min. yes if you have the money to throw at it you can get it solid, but its not easy or cheap
 and x1 expanded was better than x2 bit still alot of the same stuff is broken on x1 and x2

I just spent the last 6 hours reading this post and Sonar was completely stable for the entire time.
:-J


Best,
guitardood

Quick question, do you have windows Aero enabled or disabled?


I don't have the problems you have mentioned as i've yet to upgrade. But I know this was a problem for some in the past.