MeldaProduction

Celphor · Post by **Celphor** » Fri Oct 30, 2015 8:06 pm

Hi,

I have around 20 tracks each having an instance of MMultianalyzer. When switching to sonogram MMultianalyzer starts to "stutter" and then hangs. CPU is normal, no difference if GPU on/off.
Can anybody confirm ?

9.12 on Reaper x64 using VST3

mesaone · Post by **mesaone** » Fri Oct 30, 2015 11:06 pm

I've heard about Reaper having issues with VST3 plug-ins. I'm not sure the extent of it, but have you tried the same thing with the VST2 version of MMultiAnalyzer?

Celphor · Post by **Celphor** » Sat Oct 31, 2015 12:06 am

No, I didn't try. But I have no problems with all other (Melda) VST3s...

mesaone · Post by **mesaone** » Sat Oct 31, 2015 2:38 am

Yep, so I tested it. Reaper 5, MMultiAnalyzer 9.11 (64 bit VST2)

20 tracks, each with nothing but an instance of MMultiAnalyzer inserted. Spectrum worked fine, sonogram did not. Display would lag horribly, no sonogram was displayed. Returned to normal operation when switching back to the spectrum. Things got a little better when I reduced it to 12 tracks, the display was still laggy but at least the sonogram would display properly.

I tried the above with all three GPU acceleration modes (Full, Basic, and None) and experienced the same thing each time.

I did not test collisions or loudness, I'll leave that for another day.

But then I got a memory error (I have 16 GB, plenty for this) and then got my first ever blue screen of death on this computer. So maybe there's a memory leak. I don't have time tonight to test this on Pro Tools to figure out if it's just with VST and Reaper, but I'll try tomorrow.

Extra info if Vojtech needs it:

Laptop on "full performance" power profile, plugged into the wall. No CPU or PCIe power management turned on.

i7 4700HQ (2.40 GHz)
NVIDIA GeForce GTX 850M 2GB GDDR3
16 GB RAM @1600 MHz
Boot drive is a Samsung 840 Evo SSD
Windows 8.1 64 bit
Display is 1920x1080

MeldaProduction · Post by **MeldaProduction** » Sat Oct 31, 2015 11:43 am

I'll check it out folks, but it's actually quite possible that you indeed ran out of memory. Especially if you have displayed multiple instances at the same time.

Celphor · Post by **Celphor** » Sat Oct 31, 2015 1:21 pm

Hi Vojtech,

yes, it consumes memory and cpu. The more often you click the tab, the more resources are used.

MMultianalyzer has at least 2 more problems, but I can't figure out them exactly now.
One is a crackling noise when using it in the montitor fx chain in Reaper in my 20+ tracks setup from before.
I don't know if it does matter if it is in the monitor chain, but when I disable that instance in Reaper the crackling is gone. CPU load is never more than 20% on my work horse.

The second problem is that under certain circumstances MMultianalyser forgets his instance name and color.
I tend towards it has to do with multiple projects opened parallel in Reaper with the same track names. Or, with copying/pasting instances from one project to another and using them parallel.
Does each instance have a unique id with conflicts when copying it? Just an idea...
If I can reproduce it I will let you know.

MeldaProduction · Post by **MeldaProduction** » Sun Nov 01, 2015 3:30 pm

Ok, I'll check about that. I don't think there are memory leaks, but I'll verify. The crackling could be a problem, if you have too many tracks, the CPU load obviously increases, a lot, no way around it.

Abou the forgetting name & color - please NEVER do open multiple projects at once. The plugin cannot know which instance belongs to different project, so it will all be connected together and the results could be, well, unexpected.

GilJ · Post by **GilJ** » Sun Nov 01, 2015 9:34 pm

Hi,

Just wanted to let you know that I also experienced a couple of crashes yesterday on a project using MMultiAnalyzer and MAutoDynamicEq v9.12 (among others)

The crashes happened randomly (was not able to reproduce the bug) mainly when manipulating the GUI:
- MMultiAnalyzer: once when opening the GUI (it was all black) then Live stopped responding
- MAutoDynamicEq: once when changing the frequency of the HPF with the red bar. Then another time when typing a new value for frequency with the virtual keyboard...

Using Ableton Live 9.2.2 (32-bit) - Windows 7 SP1- CPU i7 - 4 Gb RAM.

Cheers,
GilJ.

MeldaProduction · Post by **MeldaProduction** » Mon Nov 02, 2015 11:08 am

Hmmm, odd, aren't you using the plugins bridged? I couldn't overlook that you are still using 32-bit version.
It can also be not enough memory error, with 32-bit environment I wouldn't be surprised. Or GPU driver considering the "black screen" you reported.

GilJ · Post by **GilJ** » Mon Nov 02, 2015 4:47 pm

Thanks for your answer Vojtech!

There's no internal bridge in Live unfortunately and I still use some old 32-bit plugins (and don't want to use a third party bridge right now, as I have heard some incompatibility issues)

Also my computers only have 4 Gb RAM, so not really interested in upgrading to 64-bit (until I change my DAWs)

Maybe I'll try disabling GPU in order to see if there is an improvement? (the crashes happened mainly on my laptop, not my desktop PC)

Celphor · Post by **Celphor** » Mon Nov 02, 2015 5:38 pm

Hi Vojtech,

there is definitly a memory leak in MMultiAnalyzer. When clicking the sonogram tab around 200MB! (see below) are allocated (Reaper, 1 empty Track, one MMultianalyzer, nothing else). The memory is allocated each time you active the tab. This memory seems never to be freed, even if the plugin is removed from the fx chain.

The memory consumption increases with the size of the sonogram pane, so it might be the image buffer or the buffer you temporarilly store the collected data. If you resize the plugin you see the memory varying in the task manager.

Hope it helps.

Edit:

If you have 2 instances and click the tab in one instance 2 buffers are allocated. So it is linear with the number of instances. If you toggle "global disable" after each activation all buffers are again allocated (and not freed).
This explains why a 20 instance setup completely f***s up the system

And: Same behavior also in MAnalzer.

mesaone · Post by **mesaone** » Mon Nov 02, 2015 6:52 pm

Celphor, do you see the same memory usage when un-checking "Enable when hidden" inside the Analyzer settings of all instances of MMultiAnalyzer?

Celphor · Post by **Celphor** » Mon Nov 02, 2015 7:28 pm

@mesaone: Where is this option in MMultianalzer? In MAnalyzer I tried it, but it doesn't fix the problem.

mesaone · Post by **mesaone** » Mon Nov 02, 2015 7:51 pm

Oops, looks like that option isn't in MMulti, I thought it was.

MeldaProduction · Post by **MeldaProduction** » Tue Nov 03, 2015 3:33 pm

God damn it!!! You are right!!! The sonogram contains some memory leak

. Needs to be fixed!

MeldaProduction

KVR Audio

Bug report 9.12 MMultiAnalyzer hangs on sonogram