*Solved Heads up, I was wrong! WARNING! SONITUS memory leak!

WARNING!! Possible memory leak With SONITUS Delay
I WAS WRONG!!!!!!!!!!!!
Thank-you for your report!  Your reference number is below.
CWBRN-2325
Thank-you for your report!  Your reference number is below.
CWBRN-2347


Terrible memory leak in SONAR 8.5.2 x64bit if you use SONITUS Delay.
Every time I play the 64bit SONAR it eats memory. It eats memory space every time SONAR play's it! I notice this when my computer start to get sluggish behavior? When I checked SONAR had used over 97% of total RAM in the whole SYSTEM. After Closing SONAR and re-loading the same project it went down to 27% instead. 
 
It doesn't help if you just turn them"OFF"; "off"-state it in "BUS"? You need to delete it from the BUS totally!
 

Why I first thought it was 64bit files was because it was larger then 32bit so it eat more MEMORY easy. I still need to check this out further... In some degree it stills read files but IT was enormous difference even with 64bit files.
 
 
I tried first turned off all Synth software. --No luck.
Then All “inserts”--No luck
But after deleted the all 4 instances of SONITUS delay the Memory leak stopped! Even if they were in OFF-State before they leak Memory? You need to delete them!
  
 


Best Regards
Freddie

Okay...I'll take the plunge...

What kind of 64-bit audio file have you discovered?

Why are you calling it a BUG if you haven't even confirmed if this happens to other users?  It isn't a "bug" unless it happens to others.  Have you confirmed this with at least one other person before making the announcement that you found a "bug"?

Thanks for the heads up Freddie. 
I'll stop using 64 bit audio files 
immediately until you get to the 
bottom of this. 

Papa Sonar can create 64 bit audio files.

64 bit wave files.  Now I've heard everything.  LOL

madfloyd


64 bit wave files.  Now I've heard everything.  LOL

Sony Wave-64 support
SONAR 6 and earlier wrote wave files based on the RIFF wave file format. The RIFF format has an inherent file size limitation of 2GB.
SONAR fully supports reading and writing to the Sony Wave-64 format, which has a limit of 8,388,608 terabytes!
SONAR only creates Wave-64 file when needed. The Wave-64 format allows an application to dynamically switch from classic RIFF WAVE to Wave-64 format even if the data was originally created as a RIFF wave file. SONAR detects when a file will exceed 2GB and will dynamically switch to the new Wave-64 format.
The table below shows the maximum duration for a stereo WAVE file before we hit the 2GB limit, as well as the max duration for a stereo Wave-64 file before we hit the 8,388,608 terabyte limit.
Table 44.  
Sample Rate
Bit Depth
RIFF-Wave
Sony Wave-64
44,100 Hz
16
3.38 hours
14,524,080,431 days
44,100 Hz
32
1.69 hours
7,262,040,215 days
44,100 Hz
64
50.7 minutes
3,631,020,108 days
192,000 Hz
16
46 minutes
3,335,999,724 days
192,000 Hz
32
23.3 minutes
1,667,999,862 days
192,000 Hz
64
11.65 minutes
833,999,931 days
When Wave-64 Files are created
Wave-64 files are created behind the scenes automatically under the following usage scenarios:
●
When the number of samples recorded exceeds the file size limit of a 32-bit RIFF WAV file (approximately 2GB file size).

●
When you export, bounce or freeze tracks or clips and the resultant wave size exceeds 2GB.

●
When you destructively process audio effects on a SONAR clip whose duration exceeds 2GB.

●
When you import audio and choose a wave file that exceeds 2GB in size (this could be a Wave-64 file).

●
When you save a CWB file and the size of any chunk in the CWB file exceeds 2GB, the entire CWB is saved in the new Wave-64 format.


 
Note: 64-bit CWB files are incompatible with previous versions of SONAR.
The above is from the help file in Sonar 8.5.2.

No, Freddie's talking about a MEMROY leak, which in his native tongue is "toilet", I think.  Or is it "bladder"?

Those MEMROY leaks can be very embarrassing.

Hmm, at 32 bits SONAR needs N megabytes of RAM. At 64 bits, SONAR needs N * 2 megabytes! Holy crap! Math strikes again!


Sorry, Freddie. SONAR may indeed have a memory leak, and it may only happen with 64-bit data. That's certainly not impossible. Memory leaks are very easy to have in a memory-intensive application such as SONAR.

However, it might be prudent to confirm that conclusion prior to announcing the discovery of a new bug in 20-point bold red text.

...still waiting to see why Freddie even did that or why he's so upset about it...

Yorolpal this is not the Coffee House.  The crude remarks don't go over well here.

pinguinotuerto


Oh, oh. Here comes the forum police (aka John).

Right! So watch it. LOL

There are many advantages of doing 64 Bit calculations internally within Sonar especially on the Mix buss and this has been talked about on other threads. But there is no real advantage in exporting the actual  file in any resolution much over 24 bit or 32 bit at the most if you feel you have to export something to another program for mastering or any other reason. So I guess this would eliminate the problems that Freddie might be putting forward here.

I fully appreciate the benefits of 64 bit operating systems and 64 bit versions of Sonar but as far as actual audio quality goes we are really splitting hairs if you really feel you must work with 64 bit audio files.

Jeff Evans


There are many advantages of doing 64 Bit calculations internally within Sonar especially on the Mix buss and this has been talked about on other threads. But there is no real advantage in exporting the actual  file in any resolution much over 24 bit or 32 bit at the most if you feel you have to export something to another program for mastering or any other reason. So I guess this would eliminate the problems that Freddie might be putting forward here.

I fully appreciate the benefits of 64 bit operating systems and 64 bit versions of Sonar but as far as actual audio quality goes we are really splitting hairs if you really feel you must work with 64 bit audio files.

I fully agree Jeff. It is overkill to me too. But if what Freddie found is true then it would be better for CW to fix it then not.