Loud Buzz when Starting Transport in X3c

Hi, guys.  First off, I don't think this has anything to do with the other "buzz" or "hum" threads that I've read lately.  In short, the situation is that occasionally when we start the transport in Sonar X3c there is a loud, harsh buzz sound.  Sometimes it corrects itself after about a second or so.  Other times it just causes the audio engine to stop.  It happens more often when I start and stop the transport several times in a row.
 
I can perform the same operations in X1 without any issues whatsoever.  Same project, same DAW.
 
The project has about 100 tracks.  Most of them (a bit over 50%) are archived.  There are many effects and automation envelopes.  The system is an i7, 16 GB, a Lynx AES16e connected to a Lynx Aurora.  We have current firmware and drivers.  When the project is playing back, only about 15% of the CPU is being used, so it doesn't seem like a horsepower issue.
 
The problem of the audio engine stopping seemed to be reduced when we increased the "droupout timeout" value in the configuration.  But, it only helped a bit.
 
Any thoughts?  Thanks in advance!
 
Ed

Thanks for the reply.  I should have mentioned that I already tried that based on the comments in the other threads.  From what I can tell, this buzz (only when starting the transport and lasting about a second) is different from the other buzzes and hums I have read about.  Maybe I'm wrong and X3d will be the fix.
 
Again, thanks for the reply!
 
Ed

It sound like what some people here call "motorboating", or some such.
 
Try a search with that, or I'll have a look in the morrow.

Hello Ed,
 
Yes! i experience the same thing. Sometimes the buzz/tone sounds like Morse code as the scrub bar moves along during playback. There is sometimes a similar noise when clicking in the the timeline to move the scrub bar to a different position on the timeline.
 
I am using a MOTU MicrobookII USB interface.
 
All the best,
 
Lee.

Hi, Lee.  I'm curious, did you experience the buzzing in X2 or is it only in X3?  In my case, X1 continues to be fine and the buzz when starting the transport is pretty reproducible in X3c.  Just for grins, I've updated drivers and firmware (and disables the 64 bit engine) just to rule those out...
 
Ed

Reset the audio engine before starting playback and see if the problem still happens. There is a button to do this on the control bar.

In that case, do you think it was a cached sound from before you hit stop? Maybe from a synth or specific vst?

If you happen to get a chance, please listen to this sound and let me know if you have any idea what may be causing it.  I am posting this to emphasize the fact that this is not a typical 60 cycle hum.  It's really a harsh buzz that seems to only occur when starting the transport.  In addition, sometimes Sonar will just stop responding for a minute or two.  After this huge pause, sometimes you hear the buzz.  Sometimes it recovers from the buzz.  Other times the audio engine just drops out.
 
[link=https://skydrive.live.com/redir?resid=FF49D1C9A24E716F%219760]https://skydrive.live.com...F49D1C9A24E716F%219760[/link]
 
Thanks.
 
Ed

Which soft synths are in your project?

I do not own any Waves plug-ins, but have seen some posts in passing on Waves and X3, so it may be worth searching the forums on that specifically (try googling "site: forum.cakewalk.com Waves plug-ins X3").
 
The other thing that sticks out is 32-bit plug-ins in 64-bit X3. Some seem to work, and others do not play so well. Threads are out on that topic as well.
 
For where you are, it may be "easiest" to save your project as a new one, and remove Waves/32-bit plug-ins and see if you can get that new project to playback correctly (or create a new project and moving tracks into it).
 
I may have missed in the thread... have you checked the ASIO and I/O buffers on another project?

dwardzala
If you turn off all the plug ins (I think E does this) do you have the issue?
 
Otherwise, it sounds like a buffering issue since you say it takes 10 secs or so for playback to start.

+1 and we need to know if the issue happens with new X3D projects or not.