Hi everyone,

Just wanted to let you know we haven't forgotten about you.
X1b is still in the works and on its way to you as soon as possible.

Check the sticky for more info (updated today)!

Zyler Vega [Cakewalk
]

Hi everyone,

Just wanted to let you know we haven't forgotten about you.
X1b is still in the works and on its way to you as soon as possible.

Check the sticky for more info (updated today)!

That begs the question...when is soon?

amiller


That begs the question...when is soon?

Or better yet to quote Morrissey, "How Soon is Now"?

gtgarner

Keni


As long as it's not Half-Baked!

Half - Baked?  You know its gonna be half baked to some folks.  They are just lickin their chops to tear into X1b and suggest that Cakewalk shut down as a company. 
 
You know the people I'm talking about..... - The ones who have 5 different virus programs running at the same time - who overclocked their CPU 3 times over - who are trying to use X1b with only 500mb of ram on a 5400RPM HD with an outdated version of thier audio interface drivers , etc  .........and who wouldn't admit any of it even if they were.

Oh come now. The "incomplete" list of X1b fixes already has 14 bugs with the word "crash" in it. I think we are way past the point of blaming X1's problems on users' computers. It is becoming more and more clear that the common denominator here is a bug-ridden product from CW, and saying (directly or implied) that it is the end user's fault is insulting to those of us that live in the real world, and actually run into the bugs on that huge list to the extent that we can't use X1 in any practical way.
 
Maybe you should contact CW and tell them that the 150+ bugs on that list are all imaginary...

SilkTone

gtgarner

Keni


As long as it's not Half-Baked!

Half - Baked?  You know its gonna be half baked to some folks.  They are just lickin their chops to tear into X1b and suggest that Cakewalk shut down as a company. 
 
You know the people I'm talking about..... - The ones who have 5 different virus programs running at the same time - who overclocked their CPU 3 times over - who are trying to use X1b with only 500mb of ram on a 5400RPM HD with an outdated version of thier audio interface drivers , etc  .........and who wouldn't admit any of it even if they were.

Oh come now. The "incomplete" list of X1b fixes already have 14 bugs with the word "crash" in it. I think we are way past the point of blaming X1's problems on users' computers. It is becoming more and more clear that the common denominator here is a bug-ridden product from CW, and saying (directly or implied) that it is the end user's fault is insulting to those of us that live in the real world, and actually run into the bugs on that huge list to the extent that we can't use X1 in any practical way.
 
Maybe you should contact CW and tell them that the 150+ bugs on that list are all imaginary...

Its just amazing to me that many of the things on the X1B crash  list actually work for me on my laptop.  However they don't work on my desktop.  I've not found any of the X1b fixes listed as crash - actually crash on my DELL m6400 16GB Raid 0 SSD laptop. 
 
So.  I look at the most of the things listed as "crashes" being for some group of people of which I'm not included.  I've not had X1a crash yet on my laptop.  Maybe they are fixing it so that it works on my desktop. Its older, slower and the audio drivers are out of date.  I'm using the same external audio interface for both. (actually I'm not using my desktop at all).  I just wanted to see if x1a would work on it.......and it does not consistantly work.
My laptop is the bomb though.  Not one crash.

FastBikerBoy


That's strange 'cos I see some bugs on my laptop (x32) that don't show on my desktop (x64), very strange. Perhaps my desktop is a liar and my laptop is truthful?

Thats exactlly what I'm saying.  Some things crash for some people and don't for others.  Does that mean that X1a does not work? No - it does not work for some people. 
 
I just believe a bug is something that does not work for ANYONE.  But thats just me.  I've tried to produce the crashes that people are posting on my (x64) laptop by doing exactlly what is crashing their systems, but x1a does not crash for me.  My (x32) desktop - I can duplicate it.  I understand that people that have desktops like mine might be very frustrated, but I would have to disagree that its a problem with X1 as a whole. 
 
Look - I'm running X1a on two different computers - One desktop and one laptop. THE SAME PROGRAM is acting different on 2 computers.  Is it the program thats different?  ABSOLUTELY NOT.
 
X1b is not going to provide much improvement for my laptop because X1a is working just fine.  I would'nt mind if some features are added or enhanced though.

News Flash : Someone Left The Cake Out IN The Rain !!!

in the interm i know your all working on a better song than above

It seems then that X1 is geared for Windows 7 x64 and can concur this combination works fantastically well. For a short amount of time, I used it on my old PC under XP x86 (32-bit) which had only a Pentium-D and it seemed stable, but I didn't give it the thrashing it gets now on my i7 because I knew the machine wouldn't cope with it. It was an off-the-shelf gaming machine with a powerful Nvidia video card you see, and for some reason it decided that a PCI/USB2 card I installed should share an IRQ with it. Bad news or what!

Anyway, I'm still looking forward to X1B. Roll on the end of March!