I thought this was only a problem in conjunction with the Console Emulator. Am I mistaken on this?
 
I mean, I like the CE but not THAT much. I've heard many times there are better plugs for that anyway. I figured you being a pro studio you'd already have some of those if CEs are your thing.

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.

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.

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

This will be fixed with SONAR X3d.

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.

And as I typed that up Andrew chimes in. If things are getting fixed then let them fix it. That's all I've ever wanted and really all anyone can ask for IMO.
 

This is the worst question on the blog:
 
WHEN ?

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

From what I understand there was one time when they missed a promised patch release date and all hell broke loose. Now they don't make such announcements until things are ready. Really though... how many people are actually being put out by this particular issue? Seems minor compared to other stuff in the past and there are known ways to work around it in the mean time.
 
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?
 
I've been very vocal about problems in the past and if there was a totally unavoidable hum due to the program I'd be pretty ticked but this can be avoided and a solution is on the way.
 
Just my thoughts. Hopefully no flames ensue.

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.