bapu

Guitarpima


X2a definitly works better than the forum software!!!

Best post by Guitarprima EVER!!!!


LMAO!!!!!

Thanks Bapoo!!!

Well, the project continues. The display is totally bugging out...I solo a track and it takes a few seconds to actually happen...opening lanes causes a track dance that has to be seen to believed...I delete automation lanes and the track responds like they are still there...everything is frozen and the CPU hit is enormous. I hope to finish it up by tomorrow. God willing.

jamesyoyo


Well, the project continues. The display is totally bugging out...I solo a track and it takes a few seconds to actually happen...opening lanes causes a track dance that has to be seen to believed...I delete automation lanes and the track responds like they are still there...everything is frozen and the CPU hit is enormous. I hope to finish it up by tomorrow. God willing.

How are you deleting automation lanes? Because I've always been confused about this. If I choose "remove automation lane" or hit the minus sign on a lane, it acts like it's still there and it seems like all I've done is remove it from the view. So to get rid of an automation envelope entirely, you have to right click on the envelope and select "delete envelope." Hope this helps. 

James, 

sorry to hear about your woes. The problems always seem to popup at the most inopportune times. I've had the pleasure of hearing a few of your productions you've posted to the song forum and really enjoy your style.

Have you called Tech Support? I'm just throwing this out there (I haven't read every post in the thread) but I know you were hit pretty bad by Sandy. Is it possible with all the reconstruction going on that your power is a little flakey? Do you have your system on a battery backup? I've seen alot of crazy computer s**t happen because of fluctuating voltages.

Best of Luck with the project.

Steve

jamesyoyo


Well, the project continues. The display is totally bugging out...I solo a track and it takes a few seconds to actually happen...opening lanes causes a track dance that has to be seen to believed...I delete automation lanes and the track responds like they are still there...everything is frozen and the CPU hit is enormous. I hope to finish it up by tomorrow. God willing.

its nice to hear jim that you can continue even under the curcumstances.
i hope you can finish your project,and i  look forward to hearing it.
 
every once in a while we need a thread to vent our frustrations.no matter what the issue is.
 
i say this with the upmost respect for you james.
why even bother explaining the solo button,or automation lanes,cpu spikes ?
you never posted your system specs so the ones who care could help you.
 
i think you were afraid someone would start trolling on your system specs,when in fact iyou probably have a state of the art DAW.
you would fair better by letting people help.(maybe you did post your specs,i searched 5 pages and didnt see it)
im the same person that offered my help a few months ago when i was down in breezy point for the week at my in laws.
why would it be any different here.
 

jamesyoyo


Well, the project continues. The display is totally bugging out...I solo a track and it takes a few seconds to actually happen...opening lanes causes a track dance that has to be seen to believed...I delete automation lanes and the track responds like they are still there...everything is frozen and the CPU hit is enormous. I hope to finish it up by tomorrow. God willing.

I am also having substantial display issues with X2a. Do you happen to be using a video card with a AMD HD 6850 chipset? Thanks

rcklln

jamesyoyo


Well, the project continues. The display is totally bugging out...I solo a track and it takes a few seconds to actually happen...opening lanes causes a track dance that has to be seen to believed...I delete automation lanes and the track responds like they are still there...everything is frozen and the CPU hit is enormous. I hope to finish it up by tomorrow. God willing.

I am also having substantial display issues with X2a. Do you happen to be using a video card with a AMD HD 6850 chipset? Thanks

No, but it is an ATI Radeon HD4350 

Danny Danzi


I saw some stuff early with X2, but so far for me, everything is in good shape other than a few crashes due to Kontakt...which has always been a thorn in my side. (Kontakt, just so you know, I hate you! LOL)

What amazes me about the stuff I read on here is....either someone has a bunch of weird stuff happening, or they are perfect or near perfect. I can tell you this....and I mean it sincerely, I don't know how Cakewalk handles their beta testing, but in the testing I do for companies I test for....we beat the living heck out of the stuff and try to break it any way we can. We had a release of something that was pretty popular where we on the beta team for that product and cycle felt wonderful. We couldn't make the thing act up no matter what we tried.

Some really skilled people on that team too. We released it and the next day, there were like 25 things that were found to be wrong. We went from feeling like we were awesome to feeling like we failed. Case in point....software is always going to behave differently for people depending on how it gets used. Even if you have 100 beta testers that know what they are doing....there will be 200 users that will use the product differently.

I'm not sticking up for Cake, or any of the companies that I test for...there are obviously problems or people wouldn't be complaining. The first step in fixing these problems is recognizing that they exist. The next thing...which is a nightmare....is finding the recipe to reproduce them so they can be recognized as legit bugs. Anyone that's ever been on a beta team can relate to that. It's not only frustrating, but can do your head in and make you think you're crazy. You see something happening to you as a blatantly obvious thing that happens to you religiously. Several others try to repro the problem and it doesn't happen. What do you do? Whay can THEY do if they don't see it? Trust me when I tell you, this part totally sucks!

For example, I like to always try to repro the stuff people complain about on these forums. If you ever see me post "yep, confirmed" it happens to me too of course. If I don't post anything, chances are I tried it and was unsuccessful....but I always try to reproduce just about every bug someone posts on here just because I'm curious and it usually only takes about 3-5 minutes to try.

If I were to take a guess at the problems people are reporting in Sonar, I would say the DAW itself has become a bit too sophisticated and in a sense, has lost its way. Sometimes "ground-breaking and innovative" can make something that was once great, go a bit astray. Though I have not had any of the issues reported here on my end, (Thank God) there ARE things that happen to me in X2 that didn't happen in X1 or 8.5.

A few examples: Certain plugins crash X2 that do not crash X1 or 8.5, issues with the new plugin manager at times...a few strange out of memory messages causing crashes that I have never seen before due to Kontakt, weird slip editing of clips, main power button on a PC track being disabled when it was saved as "enabled", tracks losing focus and not hi-liting or scrolling properly without clicking on them, screen sets not maintaining what was last saved/used....little things like that. No show stoppers for me other than the out of memory thing.

That said, I'm STILL not using X2 for any serious projects other than one I did last week since the bundle was sent to me using X2. Another thing I have learned which may be something for people to keep in mind. It could just be me, but I sincerely feel we should do this if at all possible for a while just until we know for sure...

Any project done in X1 should remain in X1. I've had too many issues with old projects being brought into X2. Anything done in 8.5, should remain in 8.5. When you do a project in X2, start it in X2 and name it "name of file X2" so you always know where it was created. I've noticed that any project created in X2, works well in X2 without any weird things other than my Kontakt issue and an old version of ARC crashing X2. But try that....no more old projects in X2. I really believe there is some truth to this even if it may be just on my end.

At any rate, I hope the issues can be sorted out whether they be due to the software or some sort of hardware anomaly if one exists. Speaking of hardware....here's one...not a show stopper, but something that has always bothered me that can't seem to be remedied.

Any Echo card ever made that I have, (Lalya 24/96, Gina, Audiofire Pre 8 and 12) cannot do a punch out in ANY version of Sonar from Sonar 6 to present without leaving a gap while "Allow Arm Changes during playback" is enabled. A gap will appear unless you use inputs 1 or 2. All other inputs produce a gap in punch out with ANY Echo interface. Though not a horrible thing, it only happens in Sonar. If this sort of hardware issue can occur, others can be culprits and it very well could change how they react with different versions of Sonar....you just never know.

At the end of the day, we just have to keep on reporting this stuff. If you feel you haven't received the right answer or no answer at all, it's pretty obvious what must be done. I found out about my Echo issue because one of the Cake staff was kind enough to figure it out for me. Will it ever be remedied in a future version of Sonar? I don't know...but at least the problem was found out, they are aware of it and at least I know it's not me or any of the 4 cards I was running.

The thing that makes this difficult is....there are quite a few of us that have been here a really long time. It's a bit hard to swallow that there were good versions of Sonar that worked, you take the plunge to the latest and greatest, and have nothing but road-blocks. The frustration is understandable on all counts. However, speaking for myself, the Bakers have never turned me away when I had a problem and I'm no one special.

I reported my issues like we're supposed to do and was assigned someone to help me. In just about all of my situations, I was fixed up and taken care of. If anyone else hasn't had that experience, I'm really sorry...but it's always worked for me. If at some point it no longer does, there are enough options out there to where I honestly wouldn't spend any time on this forum downing Sonar.....I'd buy a DAW that worked for me and would resume my business...but that's just me. Again, my sincere apologies for anyone having problems. I sure don't think you're crazy and can definitely relate to your frustration having been there a few times myself in the past.

-Danny

Danny, your post is logical and it does seem true that no matter how much a program is tested, there's going to be situations in which the programmers simply cannot plan for, hence one user or another will experience a bug.  And this is compounded by the many, many users who really do not know what they're doing and are not particularly adept at technology, troubleshooting and audio in general.  
 
But there's something else going on at Cakewalk that defies this reality:  They released a program that has a multitude of color options and most of the them do not work.  Cakewalk knows they do not work, they don't work on anyone's machine, and hence becomes a far different issue than a "bug".  This is is sloppy quality control, poor project management and/or questionable programming.  Most reputable software publishers would have either removed the color options that don't actually do anything, or they would have made sure they work.  This issue says a lot about Cakewalk's values and priorities, it says to me the company is going downhill and that perhaps they are simply not equipped to handle the complexity that a stable, professional level DAW requires.   I know that programming a DAW is not easy and there are bound to be a few bugs.  But the color option fiasco is a design flaw that Cakewalk let pass, not a bug, the color issue is not dependent upon the end user's setup or configuration.  It speaks volumes, at least to me, that this is not a company interested in producing serious software for serious musicians.  I just don't think a good company would make that decision. 
JG
www.jerrygerber.com
 
 
 

jsg : "But there's something else going on at Cakewalk that defies this reality: They released a program that has a multitude of color options and most of the them do not work. Cakewalk knows they do not work, they don't work on anyone's machine, and hence becomes a far different issue than a "bug"."

I've wondered about this attitude as well. For example, I bought X2 (actually X1 production suite but I got the free upgrade to x2) to create music, anything from space/ambiance to movie soundtrack type music like Avatar. So a big reason for buying what I did was the included synths.

The day I installed X2, and I'm coming off of Kinetic so I'm really excited, I immediately loaded Dimension Pro and started browsing the samples. With less than a couple minutes Sonar blows up and crashes. I was not impressed !

I've since learned about the DimPRo samples that crash X2. But the question I must ask is why on earth does Cakewalk leave those samples in the distribution package ? Someone is not looking at what happens when the product goes out the door.

Talking about threads that make Cakewalk look bad, and I know I shouldn't really throw gasoline on the fire, but does anyone remember THIS doozy?

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