Done, thanks.

bitflipper
Good stuff taccess! There'd be a lot more solid information on this forum if more users, instead of just wondering out loud, took the time to actually figure stuff out empirically.
 
Just a thought...let's be careful about extrapolating specific results into universal advice. CW put these options in for a reason, which is most likely because how well the zero fill trick works may depend entirely on your own software environment.
 
Also, caution should always be exercised when you're trying to establish cause and effect for an intermittent problem that can't be reliably repeated. I don't know how many times I've been misled by seemingly efficacious actions that later turned out to just be coincidental.

Wow...I have been coming here to get help for some time, using some real expensive stuff....and lots of issues...some tried to help me with the basics.
None of that worked out....
 
Now is it up to users, and many have tried..and many have paid for troubleshooting the systems here on my end of things...and life time updates paid for them to solve it.
 
So...user need to be what?
 
 
Think again that process of thinking into...being stupid to pay for it...to needs be a trouble...Might set this post proper?....Never mind the user based forum, and the complaints being put....of things oddly not a users fault to needs be doing any of...More the case put forward back onto...

Now, if setting up, is not mentioned how to, or what may solve for X....and many seem to be chimed into knowing something is not right somewhere with....Where with all this saying to new users, to update and set up liken this...does not solve, ...If so setup as so said to do here on these forums by users...of well known merits in setup of.
 
And....Now again we are supposed to make the fixes also be made?
 
Nah!

bvideo
I was suspecting zero fill as part of the problem in this project. Among other findings, I saw the track meter jumping during playback in a zero-filled area, and spikes printed in a zero-fill area of a track when using real-time bounce. And turning ON the 64-bit engine made the spikes go away.
 
When I get a chance, I'll try out some of the options listed by taccess

Tried out; seems unrelated to my project's problem.

bvideo

bvideo
I was suspecting zero fill as part of the problem in this project. Among other findings, I saw the track meter jumping during playback in a zero-filled area, and spikes printed in a zero-fill area of a track when using real-time bounce. And turning ON the 64-bit engine made the spikes go away.

When I get a chance, I'll try out some of the options listed by taccess

Tried out; seems unrelated to my project's problem.

Yeah you might be right I have tried zerofillmethod = 0,1,2 only 3 left to try because 4 doesn't work at all and my problem still occurs also!

I have downloaded Microsoft essentials screen capture ,I am going to video screen record my project spike/pop issue during playback ( because it's random and impossible to re Create with steps ) and maybe start a post with video evidence that Cakewalk staff and forum users can visually and audiably connect to ! There is no other way other than putting up with this , so if you can do the same please do .
Regardless zerofillmethod=4 still needs to be fixed it has a bug currently !

Another one !

Loud pops
http://forum.cakewalk.com...-Comping-m3630924.aspx

Well, I'll be damned! I disabled the 64 bit engine in Preferences -> Driver settings, and my problems have gone!
Granted, my problems only showed when opening a project, with buffers set too low - but the "problem" files have some VST3 plugs, and I had the 64 bit engine enabled.
 
Turning off all FX also solved the problem, so I knew that my problem is related to the others...
 
The ZeroFillDB and ZeroFillMethod settings didn't have any affect here.
 
My problem isn't really the same as most others (and I always blamed the MOTU driver for it) but I think it is related to the SONAR/certain plugins/64 bit engine problem.
 

jbraner
Well, I'll be damned! I disabled the 64 bit engine in Preferences -> Driver settings, and my problems have gone!
Granted, my problems only showed when opening a project, with buffers set too low - but the "problem" files have some VST3 plugs, and I had the 64 bit engine enabled.
 
Turning off all FX also solved the problem, so I knew that my problem is related to the others...
 
The ZeroFillDB and ZeroFillMethod settings didn't have any affect here.
 
My problem isn't really the same as most others (and I always blamed the MOTU driver for it) but I think it is related to the SONAR/certain plugins/64 bit engine problem.
 

Can you describe your particular problem that disabling the 64 bit engine fixed for you so others know , or even better catch it on a short video for us to see please

Turning off the 64-bit engine reduces CPU and memory usage. That could be a cure for many scenarios, but probably not this one. I never use the 64-bit option.

taccess

jbraner
Well, I'll be damned! I disabled the 64 bit engine in Preferences -> Driver settings, and my problems have gone!
Granted, my problems only showed when opening a project, with buffers set too low - but the "problem" files have some VST3 plugs, and I had the 64 bit engine enabled.
 
Turning off all FX also solved the problem, so I knew that my problem is related to the others...
 
The ZeroFillDB and ZeroFillMethod settings didn't have any affect here.
 
My problem isn't really the same as most others (and I always blamed the MOTU driver for it) but I think it is related to the SONAR/certain plugins/64 bit engine problem.
 

Can you describe your particular problem that disabling the 64 bit engine fixed for you so others know , or even better catch it on a short video for us to see please

I think I described my problem earlier on - but basically, when I load certain songs in SONAR, and the buffers are set too low - I get the previously mentioned problem where:
- sometimes there is a pop
- the SONAR meters max out (on one or more tracks)
- no sound comes out of the audio interface
I have always blamed my MOTU drivers for this - and would change them to a higher buffers setting - then the same song would play fine. With the latest MOTU drivers, I could just change the settings there and then, and the audio would be fine - previously, I may have had to close SONAR, change the buffers, then re-open (and then it would play fine)
It was after reading this thread, and the similar ones, that I realised that my problem may be related to what others are seeing.
I do have some VST3 plugs in these songs, and have always used the 64 bit engine. I also learned (from these threads) that turning off all FX makes the audio paly fine too.
 
I don't really have anything on my music partition to make a video with.