The other way to look at this is:
Even if it is proved that using 64 bit audio, internally,
causes a memory leak, who cares?
It's not as though a large percentage of us are ever gonna use SONAR that way.

gswitz:

Thank you for your reply and explanation.

gswitz



Freddie H - have you considered plug ins? Is it possible that one of the plugs you are using when testing is causing the issue? Even something like the x64 EQ might be the issue. 
  

 

 
Thanks for your input my friend!
Yes, I will try to sort this out here in STUDIO, when I got the time. I did turned of all software's to rule that out but you never know. Perhaps I miss something?
I will need to check that again. I can just tell you all what happen me, SONAR used 97 % of all memory and I have no clue why?
After Closing SONAR and re-loading the same project it went down to 27% instead. When I bounced the clip to 32bit instead, I could notice that SONAR stop read it into the memory. When I played the same clip with Wave64bit format again it continue to it eats memory. After I re-played the same clip in only 5min I could see my Memory  usage went from 27%-30% and continue counting.....
  
 
Best Regards
Freddie

jkleban


Freddie is a real friend to this forum.... he goes out to the bleeding edge and then gives up heads up to potential issues....

Hysterical or not, Freddie is DA MAN.

Jim

PS - Happy New Year ALL!!!!!

Thanks Jim for those kind words!
 
You very kind, have great Happy New Year!
 
 
Best Regards
Freddie

Fret Wizz
Even if it is proved that using 64 bit audio, internally, causes a memory leak, who cares?
It's not as though a large percentage of us are ever gonna use SONAR that way.

I care.
There are always users that use Sonar other way than most of the others. 

For example, here seems to be very few people that use External Inserts.
That feature is important to me and I'm very pleased that they fixed two bugs I reported after 8.5.1.
I'm sure that vast majoriity of Sonar users did not know of those bugs but for me they were annoying.

Cause of Freddie's memory leak may be something else than using 64 bit waves.
It may concern many x64 users.

Thank you! =)

Happy New Year everyone!


Regards
Freddie

Thank-you for your report!  Your reference number is below.
CWBRN-2347

mike_mccue


Hey Freddie,

How much of the feedback parameter did you have on those delays?

How long was (to borrow a term from reverb) the tail?

Is it the delay itself or some specific setting that uses up so much memory?



You may recall I've commented previously that you seem to draw illogical conclusions and then make a wildly dramatic presentation about your inconclusions.

I think this is why some people in this thread have made less than positive comments. Your "delivery" seems a bit over the top.

I've grown to enjoy your style... and I love the fact that you are enthusiastically digging up details about SONAR's capabilities.

Happy New Year.

best,
mike

 
 
I'm still so honest to recognize when or if I'm wrong!
 
I could easily just shut up and go on with my business without saying anything to anyone. I don't!
I'm into to try to help people here on this FORUM. I do it all for free too! 
 
Stange things happen when you work with any DAW:s or any programs. I hope that my honesty give me some credibility even if I'm sometimes wrong.... or have a wildly dramatic presentation about my "conclutions" and sometimes "inconclusions." 

  
 
Regards
Freddie

I think you are a good guy too.

As you say, you are honest... I hope you'll appreciate that I am as well.

It makes for good solid friendships.

all the best,
mike

Mod Bod


I'm curious and I reread the thread to find out what the solution was.  I guess it was to switch to 32 bit float files.  However, the original problem with 64 bit files, why was that expected behavior?

I think Freddie has now decided it is a memory leak in the Sonitus Delay... This makes me question his (original) test methodology. I think this thread can be safely ignored until a clear test can be provided by Freddie that involves an empty project and either a 64 bit file or the Sonitus Delay plugin and nothing else.

UnderTow

If there is a memory leak in the Sonitus Delay, I'd be surprised if it applies to the 64-bit version alone.

As Freddie surmises - he has his lucid moments - a memory leak would be more noticeable with 64-bit data, given that every allocation is twice the size as the 32-bit version. Having 4 instances of the plugin in a 64-bit project would seem to be a worst-case scenario.

Furthermore, the Sonitus Delay has had memory issues in the past. Still does, in fact, although the worst problems have been fixed. It's entirely possible that the recent fix for the unflushed buffer problem had an unintended consequence.

IOW, Freddie may well have found a real bug this time, in which case we are in his debt.

And over time, he may even learn how to perform empirical testing, to question kneejerk conclusions, and to verify cause-and-effect assumptions before making public announcements. Then look out!