C'mon Cake fix 64 bit buzz!!

We've been told it will probably be included in the next update - X3d
 
As a side note, are you saying you can actually hear the difference?

> and I think it was resolved immediately with just an hot fix for that problem.
 
Patience. The wizard of Oz is not a software developer. Software doesn't magic itself right. Sometimes fixes can be hard and testing the fixes can be even harder.... and time consuming.
And hotfixes in the end slow down bug fixing, as time is spent pushing out the patches to customers and testing against additional scenarios to do with the hotfix.
 
I'm in no rush for X3D (I'd prefer to wait for MORE fixes and for it to be baked properly). 
I am also in no rush to enable 64 bit precision engine, working totally fine without it. It is clearly not a showstopper otherwise the patch would have been released last month.
And one patch every three months for me is fine (unless there really is a showstopper), I don't want to spend time installing software, I want to make music. I want the bakers to be smart in their decisions not reactionary.

Bristol_Jonesey
We've been told it will probably be included in the next update - X3d
 
As a side note, are you saying you can actually hear the difference?

Hi guys ,yes i 'm a fan of 64 bit engine and i have made many posts for this.....long time ago many clients began to choose Sonar Prj over "the industry standard" for its depth and detailed sound.
Bristol ,i can hear the difference (ADAM,K&H )when i work with file recorded at 32bit/96khz for movie tracks and acid jazz(Incognito style),with Brass Section and Bass especially,where the low frequencies and body af sound is important.
It's only my experience.
Best

Jimbo 88
Can you work with the 64 bit engine off,  then turn it on just before rendering?? 

Absolutely not,the buzz is present after the rendering with 64 bit on.

GIM Productions
I am excited about Sonar X3c but I do not understand this delay in solving the problem of background noise by enabling the EC, with the 64-bit engine  enabled.
This is an important (workhorse) technical and sound feature of Sonar and I think it was resolved immediately with just an hot fix for that problem.

 
I agree completely.  This should have been fixed already, or at least CW should provide an update and expected date for a fix.
 
If Cakewalk addressed other known bugs more quickly, including apparently simple fixes like some zoom problems that were acknowledged at least 8 months (and several revisions) ago, I would be more willing to say "this must be a tough one so I will cut them some slack."  The reality is X3c, while much better than X2a, still has far too many bugs that for some reason seem to linger from version to version.  And these are not esoteric bugs, these are basic features like snap, zoom, and now 64 bit engines that are fundamental to how many engineers work.  
 
I give Sonar a lot of credit for X3 as it has many fantastic features, but as a long time user I am getting tired of the number of bugs and the slow pace of addressing them in the X series.  
 

CakeAlexS
Proof that 64 bit matters ;)
http://youtu.be/ybGOT4d2Hs8    

Ha ha ha! I remember buying Harmony Corruption on cassette in the early 90's.

mudgel
Have to say I can't understand the impatience of some folks.

X3 has only been out a few months with 3 updates already and work on the fourth one going on. Cakewalk admitted that x3c broke something in connection with the 64 bit double precision engine and they're going to fix it along with some other acknowledged problems.

I would think patience would be appropriate after years of calls of taking time to make sure things worked blah blah blah.

Surely you can still make good music without this one feature.

+1

Well... having buzz introduced by heavily touted features is kind of bad. The bakers themselves very much acknowledged this and were quick to state it was a top priority for the D update. Disabling the 64 bit thingie as they suggested or rolling back to X3b (provided you weren't experiencing any of the bugs fixed in C) seem to be reasonable solutions. I did actually notice a few things between the brief time I was messing around with the b patch and how the c patch is responding. With the b patch things were loading LIGHTNING fast and everything just seemed far snappier. After installing the c patch though there was significantly more lag and that hyper snappiness cooled a bit... but in both cases no more than I experience with X2a and probably less actually.
 
So as I move forward with writing a new project (my first) in X3c I'm keeping an eye out for any problems. If things start going wacky I may uninstall and just patch up to b and see if that's better.
 
That said I do not get the hum everyone is talking about and I even tried turning on the CE to see if something would happen. It just isn't there. Granted I have very few tracks on this project so perhaps it's cumulative... or I could just be deaf and not hear it. I don't think so though.
 
One thing that MAY be a result of this though is on my newly programmed TH2 preset I'm having a bit of a hard time gating out some buzz before the gate closes but I think that is more due to the ultra distorted high gain settings of the set up as opposed to anything coming from Sonar. As soon as the gate closes it's gone.

This is the worst question on the blog:
 
WHEN ?

Beepster
 
Not trying to diminish the problems of those actually having problems with this but is a rollback to B and/or not using the CE (or whatever causes this... still didn't get an answer on that) and/or simply unticking the 64 bit option as you work until the patch is released not an option?
 

Well, if your project had a bunch of mono interleaved tracks with the CE on each and you count on the functionality of the 64-bit engine, you'd probably be a bit annoyed.  Apparently, the EQ doesn't work properly in this situation either.
 

mudgel
Have to say I can't understand the impatience of some folks.

X3 has only been out a few months with 3 updates already and work on the fourth one going on. Cakewalk admitted that x3c broke something in connection with the 64 bit double precision engine and they're going to fix it along with some other acknowledged problems.

I would think patience would be appropriate after years of calls of taking time to make sure things worked blah blah blah.

Surely you can still make good music without this one feature.

Hi Mudgel,i agree with you in general.....i think that Sonar X3c is the best DAW on the market then i'm surprised seeing that Cakewalk technology workhorse feature was broken and I thought that dedicate themselves more quickly to the solution of the problem.
Just this.
Best

cowboydan
This is the worst question on the blog:
 
WHEN ?

 
Maybe this would be a valid question if this was now February 2014.
Otherwise Cake will tell us when they want to tell us, leave them alone.

@Andrew... Well that was Alex's projection, not mine but whatever you guys have in the pipe. I'm not being held up by anything so it's just nice to know something is coming... even if I don't need it yet AFAIK. The R key is working fine, editing seems to be more fluid/normal, graphics are better (had a couple quirks but nothing major), less whiteouts, the Take Lane MSR buttons seem to be working properly and I've only had one real crash but that was because I was hitting Ctrl + Z frantically when I should have used the History option. So on my minimal usage so far this release has been playing far nicer on my system... and I still have not wiped it/set it back up again with optimal settings/config.
 
There is however that matter of the other thing... you know... the thing?
 

CakeAlexS

cowboydan
This is the worst question on the blog:
 
WHEN ?

 
Maybe this would be a valid question if this was now February 2014.
Otherwise Cake will tell us when they want to tell us, leave them alone.

Your birthday Alex? February 2014 ?  That would be something.

neirbod

Andrew Rossa [Cakewalk]
 
It will be sooner than Feb 2014. Much sooner. That's all I can say for now but we are working hard on it.

 
Good to hear, thanks for the update.  Are you able to share what other fixes will be included?  

Will do an article like we did for the X3b and X3c with the fixes. They are still busy fixing so we'll publish it when we release so it's the final version.