TraceyStudios


An interesting previous post on the intel vs. amp:

http://forum.cakewalk.com/tm.aspx?m=2660354

Yes I just looked at the link to that.


This is from that thread:

wildman, you wouldn't happen to have an amd machine would you ? :-)

It seems that with each new version/patch some systems fall by the wayside. Over the long run I could see this happening from new functionality no longer being supported by older equipment, but there has to be something else going on. It's as if our systems are all teetering on the edge of a cliff and when a new patch comes along that requires 1% more throughput some of our systems fall off.

Either that or the software is so full of bugs that certain combinations of hardware activate different sets of them, leading or not to disaster.

It makes intalling a patch or upgrade a pretty scary enterprise. And you can't even sit back and wait to see what happens to others. They may be fine but your system ends up being one of the unlucky ones.

I wouldn't mind hearing from one of Sonar's developers as to what they think is the cause of instability suddenly raising its ugly head. Maybe it's Windows, for all I know.

This kind of computer problems can keep me awake at night for days and days. Hope I'm not destined to be hit by the ghost any time soon.

Paul P


wildman, you wouldn't happen to have an amd machine would you ? :-)

It seems that with each new version/patch some systems fall by the wayside. Over the long run I could see this happening from new functionality no longer being supported by older equipment, but there has to be something else going on. It's as if our systems are all teetering on the edge of a cliff and when a new patch comes along that requires 1% more throughput some of our systems fall off.

Either that or the software is so full of bugs that certain combinations of hardware activate different sets of them, leading or not to disaster.

It makes intalling a patch or upgrade a pretty scary enterprise. And you can't even sit back and wait to see what happens to others. They may be fine but your system ends up being one of the unlucky ones.

I wouldn't mind hearing from one of Sonar's developers as to what they think is the cause of instability suddenly raising its ugly head. Maybe it's Windows, for all I know.

This kind of computer problems can keep me awake at night for days and days. Hope I'm not destined to be hit by the ghost any time soon.

Yes I did have an AMD machine, but it was scrapped when X2 killed it.
I could have rebuilt it AGAIN but decided it would be pointless, having already done that.
I went the Intel i7 route. All ok with X2 there now although had to get the config right to get good results.
Just need the bugs fixing.


I am convinced tha X2 is the culprit as too many people apart from myself have experienced too many issues with X2.


Again I know that others have negated such experiences as "more negative comments" but hey, people have ditched Sonar as a result of the problems! I nearly did as well, but for my Intel machine working out ok.
Folks are not making this stuff up!
Their issues are real.

I never had any probs with cakewalk up until and inc. X1, and I have have had cakewalk since it was on floppy!
X2 is great when it works, but the bugs need to ironed out.
We need NO more new features, rather we need what we have to work correctly and be stable for everyone.
I hope X2b sorts it out properly, and pronto!


(For instance, why does the Dock not resize when you undock an item. This bug got introduced with X2a, it never did i in X2)


I would not consider upgrading again in the future untill X2 runs perfectly, as I have had my fingers burnt with this.
I have spent more time 'fixing' the pc than making music.

the wildman

Paul P


wildman, you wouldn't happen to have an amd machine would you ? :-)

It seems that with each new version/patch some systems fall by the wayside. Over the long run I could see this happening from new functionality no longer being supported by older equipment, but there has to be something else going on. It's as if our systems are all teetering on the edge of a cliff and when a new patch comes along that requires 1% more throughput some of our systems fall off.

Either that or the software is so full of bugs that certain combinations of hardware activate different sets of them, leading or not to disaster.

It makes intalling a patch or upgrade a pretty scary enterprise. And you can't even sit back and wait to see what happens to others. They may be fine but your system ends up being one of the unlucky ones.

I wouldn't mind hearing from one of Sonar's developers as to what they think is the cause of instability suddenly raising its ugly head. Maybe it's Windows, for all I know.

This kind of computer problems can keep me awake at night for days and days. Hope I'm not destined to be hit by the ghost any time soon.

Yes I did have an AMD machine, but it was scrapped when X2 killed it.
I could have rebuilt it AGAIN but decided it would be pointless, having already done that.
I went the Intel i7 route. All ok with X2 there now although had to get the config right to get good results.
Just need the bugs fixing.


I am convinced tha X2 is the culprit as too many people apart from myself have experienced too many issues with X2.


Again I know that others have negated such experiences as "more negative comments" but hey, people have ditched Sonar as a result of the problems! I nearly did as well, but for my Intel machine working out ok.
Folks are not making this stuff up!
Their issues are real.

I never had any probs with cakewalk up until and inc. X1, and I have have had cakewalk since it was on floppy!
X2 is great when it works, but the bugs need to ironed out.
We need NO more new features, rather we need what we have to work correctly and be stable for everyone.
I hope X2b sorts it out properly, and pronto!


(For instance, why does the Dock not resize when you undock an item. This bug got introduced with X2a, it never did i in X2)


I would not consider upgrading again in the future untill X2 runs perfectly, as I have had my fingers burnt with this.
I have spent more time 'fixing' the pc than making music.

x2 killed your computer?

Yes chuckebaby,
It effectively killed it.
I could not reboot it, after one o it's many bsod crashes.
I ad to take it to my local computer repair centre.
They got it up and running again for me, but that was it for me.
I had struggled with it so so much since X2, that it was like banging my head on a brick wall.
It was driving me nuts!

My choices were
1/ try again, 
2/ scrap it and salvage the good bits, while replacing the rest.

I'd had enough already, so chose option 2.

wildman, yes i understand what you are saying! LOL!
 

some folks are having good luck with x2.  years ago I had version 5, purchased the upgrade to version 6, couldn't use it because cakewalk and tascam didn't coordinate (don't know how, what why). so I paid for something I couldn't use. continued to use 5 until i purchased x1, only because i needed a new machine.  Then I purchased the upgrade to x2. I would really like to get it to work properly on my machine. I understand now, that sonar may perform differently on amd as intel, however I am already $800 into a machine. I was really frustrated when I posted the other day, not so frustrated now. I may go backwards back to x1, but the last few sessions, x2 has been working pretty well. Maybe i updated something that fixed something. I will just keep recording and see what happens.

I had that too.
If you keep saving as you go along, just in case it crashes after a great take!
Should be safe.
But if not, then best go back to X1 d to sqve your sanity and your recordings.
X1 is good anyway. If I were to have further probs then I have decided that I would just revert to X1, but so far so good!

Firstly - I am sorry for any frustration you and others have with X2/X2a.

I have a question or two for you, regarding the X2 portion of your post.

1.  Was Windows brought up to current maintenance levels prior to your installation of X2?

2.  Did you also download and install the X2a maintenance patch?

3.  If you DID install the X2a patch, did you then follow the instructions for re-scanning plugins and all of that?

If my understanding is correct, from various snippets of posted text from the Cakewalk developers (who post here fairly frequently), the X2a patch contained something like 250 bug fixes from the original X2 release.

And, in at least one patch, one of the developers said that X2a was DEFINITELY a more stable version than the original X2.

One of the things it is important to note is that X2a requires at least a maintenance level of Service Pack 1 for Windows 7, for it to run properly.  This is due to certain C++ routines that are expected to be installed in Windows for running X2a, and those routines are part of that Service Pack 1 for Windows 7.

In any case, I hope things are working for you - I am curious on seeing your responses to the above questions,

Bob Bone

What I don't understand is, why does Windows have to be updated when Sonar wasn't coded on the latest version of Windows?

I never got that.

@Bub - I certainly do not know all of the ins and outs of the coding of Sonar.  I do know that certain code routines for the X2a patch are called - they simply MUST be present, and these particular routines only came into being with Service Pack 1 of Windows 7 (to the best of my knowledge).

Certainly the bulk of Sonar goes back quite a long while, but there comes a point in development where to advance some functionality of a product minimum system maintenance level requirements must come into play, and that is what has occurred with the X2a patch.  I am actually quite pleased that they have done this, as I think it will make it easier for them to develop moving forward, as well as to support.  That will hopefully make things both easier and better for us too.

Bob Bone