I have been playing Brandon's Room for Clarity through X1a. It uses a number of the Sonitus FX including the Delay. I don't use them Soitus plugins so I coldn't test with my own projects.

Over a 12 minute period of playing, stopping and starting, rewinding  and replaying from the start, memory usage jumps dramatically from 220,000kb at the start of the song to 890,000kb at the end of the 12 minute period. No sign of the memory decreasing - I can jsut watch the memory gradually increase without any action on my part even if I don't start and stop. Putting the fx into the bypass bin makes no difference - memory usage keeps increasing. Next test is to save a version without the plugins and see what happens.

I've deleted all the plugins and disabled all the eq on all the channels. NO PlUGINS at all. AND yet it is staill adding about 1k of memory to the sonar process every second even without the transport running.

Not sure what significance that has but that's what's happening here. definitely a quicker rate of memory "leaking" as more plugins loaded but interesting that its still happening with no plugins.

Win 7 64 bit X1a with the ASIO hotfix.

Same characteristics in SONAR 8.5.3 with the same project

Not that there is any doubt at this time, but here are the stats with the 8.0 version of the sonitusFXDelay.dll:

Run SONAR X1                    45.1 MB
Open project                    190.3 MB
Start/Stop                        193.5 MB
Start/Stop                        193.5 MB
Close project                     82.3 MB
Open project                   191.3 MB
Sonitus:fx Delay in track 191.9 MB
Start/Stop                       198.2 MB (+ 6.3 MB)
Start/Stop                       198.2 MB (+ 0)
Start/Stop                       198.2 MB (+ 0)
Start/Stop                       198.2 MB (+ 0)


This plugin is my go-to delay so I could easily have 5 or 6 instances per project. That said, I have not ever run out of memory in my SONAR sessions, but then lately my sessions don't run for hours and hours (unfortunately, not for want of trying).

I will be very happy to swap to the 8.0 DLL on my main DAW machine, both in 8.5 and X1 (actually, they share the same plugin directory so I don't think I have a choice?)

Thanks to the OP and A1 and everyone for researching this.

I'm bumping this because I'm still wondering what the CW team have to say about this, if they have even taken note of it, cuz this is not a minut detail...

Just a bump for those who may have missed this thread.

I see about 3K of memory "leaked" in each start/stop cycle. So, in a thousand such cycles, I've lost 3M. 
 

IIRC, it was 3MB per cycle, not 3kB. And if you have multiple instances, you can start to get into some serious memory usage in 100 cycles or so.
 
EDIT: Oops. Didn't realize when the thread got bumped that I was looking at the last post on page 1, not the most recent post in the thread.

Lanceindastudio


I just did the test and watched my ram shoot up steadily. I didnt need a crash. That was enough for me to try to install my 8.0 version of sonitus delay-

I tried to install the delay and then I checked. Still gaining memory usage.

I then renamed the sonitus delay dll as it was not reverted back to the old one and moved it to another folder like instructed above and installed 8.0 version again.


This time, the older 8.0 delay was in the shared plugins folder.
I guess it wont rewrite a newer version.

Anyways, the 8.0 version also solved this problem for me.

wow!

Cheers to you for discovering this and furthermore, finding a solution!

Great work!!! 

Gotta fix this Bakers!!!

Hi Lance...

Thanks for that info... I tried installing from 8.5 and got nothing changed... so I suspect it was the same issue as you found.

I'm a bit confused here tho as I have three version I find in my folder... One is 3.3.0.0 and anther is 12.0??? This last one I think is from the ultrafunk days...

Did you get 3.3.221?

I see that A1's post also mentioned the renaming/moving so I'm gonna try that right now... and then re-install from 8.0!

Keni

I was just reading through this..

Was there ever a hotfix for this or something? I'm sure it was just a small logic error and easily fixed by the developers.

Or did the problem just get let go and un acknowledged?

Cheers for posting the links A1 and cheers for everyone else who helped highlight this. Criminal that it didn't get fixed for x1.

 

You can also use the version that came on the 8.5 download (3.3.3.372).

So are we sure this one works? And both 32 and 64?




  And these as well"? 3.3.0.0, 3.3.221?  Both 32 and 64bit?

syntheticpop: Don't install the entire program, just the Sonitus Delay. Choose a "Custom Install" then de-select everything except the Sonitus delay. It only takes a moment.

The other option is to download the DLL's provided by A1 earlier on this page (make sure you grab the correct one. 32 or 64).

Yeah, I'm a little curious too. In many of the tuts and vids they seem to rely heavily on Sonitus. I'm kind of following those down to the letter until I get a little more comfortable with everything. I'd hate to cause a crash because of it.

Interesting you have 3.3.4.242 when I have the infamous 3.3.4.184, though I don't think it matters anymore. I have X1d Exp with no issues. Also, if I hold the spacebar it plays for about 1 measure and stops, so what's the point of that?
 
I think people should stop finding weird-n-wacky ways of crashing Sonar.
 
 
 
Just Stop it already!
 
 
 
I said STOP!!!!