The OP really came through on this cure man-
Really this forum rox

Crg

Now hold down the space bar with something and veiw your memory manager

 
What does holding down the space bar do in this instance?

I was going to test this by starting and stoping with my control surface when I realized it would take about 863 more stops and starts to get my system to crash. So I started using the space bar, and then just finally held it down to start and stop rapidly to test it.

southpaw3473

A1MixMan


As far as I know, this is specific to SonitusFXDelay.dll and the version numbers listed in the linked thread. So if you are not using it, it shouldn't cause any problems, but who knows.

I'm using version  3.3.3.141 from PE 8.5 and it drains the memory. I take it the 8.5 install disc version won't work for the fix?  This is weird, indeed!

Nope the 8.5 disk won't work.

MNorman


I agree this is an issue, but am a little confused about the urgency.  I see about 3K of memory "leaked" in each start/stop cycle.  So, in a thousand such cycles, I've lost 3M.  In 30,000 cycles, about 100M.  I'd estimate the most I could possibly start/stop the transport in a productive session is about 12 times a minute, or about 7200 times in a 10 hour session - for a total of 22M memory lost.  The memory, of course, is regained when you close and open Sonar again.  I can't see an operational reason to hold the space bar down continuously.

Perhaps my mileage is different, or I'm missing something.  Am I?

The drain for me was about 10 mb per start/stop. So that would add up quickly over a session of midi editing and other such tasks. I agree no one is going to hold down the space bar, but really, it only took 2 1/2 minutes to go through 10 gigs on my system. Those chunks were going at a rate of about 30-40 mb per second. So something is very wrong, and who know what kinds of problems it may cause. I noticed  before it crashed strange sounds and jumpy behavior, until finally it crashed. And when I closed it down on another test, Sonar didn't release the ram. I had to do a restart, and then it crashed.

aleef

test this, simply load a project and insert the Sonitus Delay into an fx bin. (You may already have a project like this) Now hold down the space bar with something and veiw your memory manager (In Win7 goto Task Manager/Performance Tab and watch your memory drain away.)

 
 
 
 
Man!! Im not gonna do that sh*t...
 
 
on the serious side this is good to know, and does have me concerned.  thanx for posting.. 

You don't have to go that far with it. Just test it by starting and stoping a project with the Delay on a track. Watch how fast all of your memory disappears.

Sidroe


Quick question! I have 8.5 discs. I just downloaded the 8.0 sonitus delay file from the forum. What is the most painless way of installing this file. I am running 8.5.3 and X1, all 32 and 54 bit versions.

Find the offending file and rename it and move it to another location. Then copy the new file in the original location. Right click and check the file properties to make sure you have the right file.
 
Test it again to see if it's working.
 
And then enjoy your new found memory!

musicroom


All clear here with no problems like that.

Certainly worth the test though. Thanks for the heads up.

Sonar 8.53 PE, Vista64

Which file version?

Just for fun, I tried this to get some stats. 
Platform is Windows XP (sp3) with SONAR X1a (all 32 bit of course). I'm using the default Sonitus DLL installed with X1. 
The values on the right are the working set of SONARPDR.exe, as reported by Process Explorer.

SONAR X1 open, no project open:  45.1 MB
Open Mixing_Tutorial.cwp:           194.1 MB  
Close project:                                 82.3 MB
Open Mixing_Tutorial.cwp:           194.0 MB
Add Sonitus:fx Delay to track       197.0 MB  (Guitar Delay preset)
Save project
Wait for a few minutes. 
Seems stable.                              196.3 MB
Start/Stop playback:                    205.9 MB (+ 9.6 MB)
Start/Stop playback:                    208.6 MB (+ 2.7 MB)
Start/Stop playback:                    211.4 MB (+ 2.8 MB)
Start/Stop playback:                    214.1 MB (+ 2.7 MB)
Start/Stop playback:                    216.8 MB (+ 2.7 MB)
Start/Stop playback:                    219.6 MB (+ 2.8 MB)
Start/Stop playback:                    222.3 MB (+ 2.7 MB)
Start/Stop playback:                    224.8 MB (+ 2.5 MB)
Start/Stop playback:                    227.5 MB (+ 2.7 MB)
Start/Stop playback:                    230.2 MB (+ 2.7 MB) Total gain = 33.9 MB.

Close project:                              119.4 MB (-196.3 MB = 37.1 MB not released)
Open Project:                              229.2 MB
Remove Sonitus:fx Delay             228.8
Start/Stop playback:                    231.5 + 2.7
Start/Stop playback:                    231.5 + 0
Start/Stop playback:                    231.5 + 0
Start/Stop playback:                    231.5 + 0


Observations:
On this system, the Start/stop cycle appears to leak 2.7 MB when the Sonitus delay is in the track. The memory leak is not recovered when the project is closed. It's not quite that simple because when I remove the plugin, there is still an initial memory impact of 2.7 MB when i start the playback cycle again, but then it stablizes. 

This leads me to believe that the 2.7 MB increment is not defined by the Sonitus delay itself, but may be related to a standard block of memory provided to it by SONAR, which the Delay FX then does not release - if you know what I mean. The end result is the same, there's a leak.

I will re-test this at some point when I find my 8.0 install disks.

You should be able to just download the file I posted in the begining.

Can you try more than one instance of the Delay in your project. I bet that it's 2.7 for each instance, but I didn't check that.

Crg


Does the memory loss compound when the space bar is used in the proper manner? 

Do

 
Yes it does. If you just start and stop once you lose memory. You lose it EVERYTIME you start and stop. I just used the spacebar to speed it up.

A1MixMan

MNorman


I agree this is an issue, but am a little confused about the urgency.  I see about 3K of memory "leaked" in each start/stop cycle.  So, in a thousand such cycles, I've lost 3M.  In 30,000 cycles, about 100M.  I'd estimate the most I could possibly start/stop the transport in a productive session is about 12 times a minute, or about 7200 times in a 10 hour session - for a total of 22M memory lost.  The memory, of course, is regained when you close and open Sonar again.  I can't see an operational reason to hold the space bar down continuously.

Perhaps my mileage is different, or I'm missing something.  Am I?

The drain for me was about 10 mb per start/stop. So that would add up quickly over a session of midi editing and other such tasks. I agree no one is going to hold down the space bar, but really, it only took 2 1/2 minutes to go through 10 gigs on my system. Those chunks were going at a rate of about 30-40 mb per second. So something is very wrong, and who know what kinds of problems it may cause. I noticed  before it crashed strange sounds and jumpy behavior, until finally it crashed. And when I closed it down on another test, Sonar didn't release the ram. I had to do a restart, and then it crashed. And if you only have 6 gigs or even 4 gigs of ram, losing ANY amount for each start/stop is unacceptable. I'm kind of hoping that this may solve some of the random crashes in my system. For the most part it runs great. But every now and then,..., well, you know. Maybe this is THE FIX?
 
 

So is this issue based on the number of instances of the Delay installed on a project or specific computer designs?

Crg

  
 

So is this issue based on the number of instances of the Delay installed on a project or specific computer designs?

The memory leak is PER INSTANCE. So if you have 2 instances of delay on two different tracks your memory loss will double. 3 instances will triple your loss, and so on.

A1MixMan


You should be able to just download the file I posted in the begining.

Can you try more than one instance of the Delay in your project. I bet that it's 2.7 for each instance, but I didn't check that.

I just tried the version attached to your original post, but now I get an error. It is saying the the Sonitus:fx Delay plugin is missing or incorrectly installed. Is there another step required to register the dll (regsvr32 or similar?)


Wow. Ok, I replaced the original DLL but I still get the error when I try to insert the plugin into a track. So now I guess I don't have a working Sonitus Delay plugin. I suspect something is being cached somewhere. I may have to uninstall and reinstall to get things back in synch.

stickman393

A1MixMan


You should be able to just download the file I posted in the begining.

Can you try more than one instance of the Delay in your project. I bet that it's 2.7 for each instance, but I didn't check that.

I just tried the version attached to your original post, but now I get an error. It is saying the the Sonitus:fx Delay plugin is missing or incorrectly installed. Is there another step required to register the dll (regsvr32 or similar?)


Wow. Ok, I replaced the original DLL but I still get the error when I try to insert the plugin into a track. So now I guess I don't have a working Sonitus Delay plugin. I suspect something is being cached somewhere. I may have to uninstall and reinstall to get things back in synch.
 
 

I had this, just copying wouldn't work ... so just install it properly from the disk (I used 8.0 disk).  Make sure to UNcheck everything except the Sonitus Delay when installing.  Took about 20 secs to install.  HTH.
 
Edit: Then do a rescan ...

SONARtist

stickman393

A1MixMan


You should be able to just download the file I posted in the begining.

Can you try more than one instance of the Delay in your project. I bet that it's 2.7 for each instance, but I didn't check that.

I just tried the version attached to your original post, but now I get an error. It is saying the the Sonitus:fx Delay plugin is missing or incorrectly installed. Is there another step required to register the dll (regsvr32 or similar?)


Wow. Ok, I replaced the original DLL but I still get the error when I try to insert the plugin into a track. So now I guess I don't have a working Sonitus Delay plugin. I suspect something is being cached somewhere. I may have to uninstall and reinstall to get things back in synch.
 
 

I had this, just copying wouldn't work ... so just install it properly from the disk (I used 8.0 disk).  Make sure to UNcheck everything except the Sonitus Delay when installing.  Took about 20 secs to install.  HTH.
 
Edit: Then do a rescan ...

Yes I couldn't get the linked file to work either I am assuming because it came from a 64 bit install rather than an x86 one.  btw rescanning plug-ins in Sonar won't make any difference with dx files.

Here's a simple tip though to register (or unregister) dx plugs in the shared plugins folder.

In notepad create a new text file, type in;

regsvr32 %1

save this file out as reg.bat (make sure notepad doesn't add the .txt extension to that, rename if needed)

Make another text file this time type in;

regsvr32 /u %1

Save this as unreg.bat

Place these 2 files (reg.bat, unreg.bat) into your 'Shared Plugins' folder (NOT the vstplugins folder, this is for DX files only remember!).

Now you can just drop whatever .dll onto either batch file to register or unregister it from the system.  So say you only ever use the Sonitus Delay just drop the other files one at a time on the unreg.bat file to simplify the plug in list in Sonar.

Then if you want to re-instate the Sonitus Verb for example just drop it on reg.bat and it will re-appear on the plug-in list next time you start Sonar without needing to scan your plugs.

I've not tried this on 64 bit systems or Windows 7 yet but I can't see why it wouldn't work there too, but XP and Vista 32 bit it works like a charm.