So...as forumites know, I am not above embarrassing myself publicly if I think I can help others not make the same kind of stupid mistake
 
I installed X3c and recorded a hex guitar part. There were little dropouts and annoying crackles on both record and playback and I had never experienced this before. I figured there was some X3c problem so I rolled back to X3b.
 
To make a long story short and prevent more embarrassment, I realized that the record and playback buffer I/O sizes had somehow reverted to 256. When I increased them back to their usual values, X3c worked fine.
 
Based on advice in this forum I left 64-bit engine unchecked, and haven't encountered any problems.

LOL! Been there! Thanks for posting...

Anderton
So...as forumites know, I am not above embarrassing myself publicly if I think I can help others not make the same kind of stupid mistake
 
I installed X3c and recorded a hex guitar part. There were little dropouts and annoying crackles on both record and playback and I had never experienced this before. I figured there was some X3c problem so I rolled back to X3b.
 
To make a long story short and prevent more embarrassment, I realized that the record and playback buffer I/O sizes had somehow reverted to 256. When I increased them back to their usual values, X3c worked fine.
 
Based on advice in this forum I left 64-bit engine unchecked, and haven't encountered any problems.

Ok I'll bite. What are the usual values that you have set. I think I have left those set to the the default of 256 thru Sonar 7, 8 ,8.5, X1 and X2. I am having cpu spikes and pops and crackles in X2, maybe I should look into raising my values.

Your humility is only equaled by your generosity.
 
Kind regards,
 
tecknot

Anderton
So...as forumites know, I am not above embarrassing myself publicly if I think I can help others not make the same kind of stupid mistake
 
I installed X3c and recorded a hex guitar part. There were little dropouts and annoying crackles on both record and playback and I had never experienced this before. I figured there was some X3c problem so I rolled back to X3b.
 
To make a long story short and prevent more embarrassment, I realized that the record and playback buffer I/O sizes had somehow reverted to 256. When I increased them back to their usual values, X3c worked fine.
 
Based on advice in this forum I left 64-bit engine unchecked, and haven't encountered any problems.

Hey Craig, I wonder if that playback/record I/O really was the problem and not just the 64-bit engine check box? I've always gotten pops and crackles having the 64-bit engine box checked. The reason I say that, I've never experienced any crackles or pops from the record/playback I/O settings. I can run 128 and 256 for just about anything. But I use 512 for my large projects. If you set it to 1024, you would just get a 1/2 to 1 second lag before sound kicked in after pressing space bar. Lower than 128 might bring on pops and clicks, but I've never been lower than 128. Most of the time I'm at 512 and my hard drives barely show any activity even with large projects. You said you increased from 256, so I take it you're a 512 man also. I've never in the history of using Cake or Sonar had a drop out from my hard drive using 512 in both playback and recording I/O. 128 and 256 are snappier of course and work perfectly for me....but leaving it at 512 just handled everything without the need to ever make a change. I'd be willing to bet it was that 64 check box. ;)
 
-Danny

Thatsastrat

Anderton
So...as forumites know, I am not above embarrassing myself publicly if I think I can help others not make the same kind of stupid mistake
 
I installed X3c and recorded a hex guitar part. There were little dropouts and annoying crackles on both record and playback and I had never experienced this before. I figured there was some X3c problem so I rolled back to X3b.
 
To make a long story short and prevent more embarrassment, I realized that the record and playback buffer I/O sizes had somehow reverted to 256. When I increased them back to their usual values, X3c worked fine.
 
Based on advice in this forum I left 64-bit engine unchecked, and haven't encountered any problems.

Ok I'll bite. What are the usual values that you have set. I think I have left those set to the the default of 256 thru Sonar 7, 8 ,8.5, X1 and X2. I am having cpu spikes and pops and crackles in X2, maybe I should look into raising my values.

 
I've always found the I/O buffers to be system specific rather than a "one size suits all" thing.
 
Every time I change my set up I go through the procedure of balancing the recording & playback I/O buffers against the sample buffer I prefer to run on my interface. Basically those I/O buffers are used for reading and writing to disk. Too large can be as bad as too small as they then take too long to fill and that's dependent on how efficient your hard drive is.
 
Trial and error is the method I use but it is only a one time thing unless something changes on your system.
 
That's all in my experience btw rather than based on any scientific fact.
 
HTH

Craig mentioned a "hex" guitar part in his original post. To me, a hex pickup is a divided pickup often used with guitar-midi interfaces, so I read his mention of playback and recording buffers to mean the MIDI buffer settings, not the audio interface buffers. I may be wrong, hopefully Craig will clarify.

Well I have not checked the 64 bit engine issue...But I have changed buffers up and down and still get drop outs and recorded anomalies in x2a, and then in X3b...With that engine checked as specified to do....So I will uncheck this feature....and try try again.
 
Funny thing is in X3b...when changing Buffer sizes with in the preference pane , the sonar x3b software shuts down...
 
So for me it isn't about buffer sizes, it is about something else...again I have not turned off the 64 bit engine, and will try that next.
 
But the features mentioned in this post...are suppose to work within the confines of the code....if they do not work as coded...then it is a bug....I say.
 
More input is necessary before making rash statements about cause and effect....Dani D  has it right I believe.

Just had to do this in X2 to prevent Audio Engine stops in a track heavy project.

Houndawg
Craig mentioned a "hex" guitar part in his original post. To me, a hex pickup is a divided pickup often used with guitar-midi interfaces, so I read his mention of playback and recording buffers to mean the MIDI buffer settings, not the audio interface buffers. I may be wrong, hopefully Craig will clarify.

I'm sure  Craig will clarify but he does specifically mention the I/O playback & record buffers as opposed to the MIDI buffer. The I/O buffers relate to read and write operations to the hard drive. Too small and there isn't enough data  available when needed. Too big and they take too long to fill, either can cause problems.