Moscilloscope takes an entire cpu at rest on M7

Official support for: mutools.com
Post Reply New Topic
RELATED
PRODUCTS

Post

It may well be on Melda's side, but this is a bit of a problem.

Link to the VST:

https://www.meldaproduction.com/MOscilloscope

In my limited experience, mulab 7 shows more CPU usage in task manager than FL when using the same plugins. I see a few threads about CPU usage, and I get that it may be due to different ways to report CPU usage. Still, the fans on my i7 are often on since I switched to M7. Any workarounds (other than finding cpu hogs like MOscilloscope)?

Thanks

Post

I did some extensive testing with different plugins, both instrument and effect, between M6, Tracktion and Reaper before deciding on M6.

More or less, Reaper and M6 were identical in CPU usage. Sometimes, one would use 1% more CPU, sometimes 1% less. I use a monitor that shows total CPU and RAM usage for my whole computer rather than relying on the dissimilar built-in CPU meters in each program. (Tracktion hogged a few extra percent on each test, IIRC.)

I do find that there are sometimes load balancing issues if I go past 50% CPU usage (dual-core i5.) It depends on the plugs I am using and if they are designed to use multiple cores or not. I'm not sure if this issue lies with M7, the OS, or something else, but I rarely ever hit more than say 40% CPU usage on a full mix, so I don't worry about it at all. I can always freeze some VSTis if I have to.

I've never been keen on the Melda plugs--they just install everything everywhere and make a mess of my system--so I cannot say if their plugs are at fault. However, which function of the oscillator do you need? There's a basic built-in oscillator window in M7 and the free GVST makes a very nice pitch detector that I love.
I started on Logic 5 with a PowerBook G4 550Mhz. I now have a MacBook Air M1 and it's ~165x faster! So, why is my music not proportionally better? :(

Post

Hmm, Moscilloscope registers at the most 1% impact for me anywhere. I think thats
mostly due to the fact that it cant really show much less than that.

Are you by chance using the onboard graphics? The Melda plug-ins are GPU accelerated.
I suppose they could seem a cpu hog in that case. Perhaps try disabling the acceleration,
you can do this in the settings. Maybe run the cpu benchmark there as well.

This is the result of the scopes benchmark on my i7:

Image

394.7 instances on one core doesn't seem much of a cpu hog to me.
This was done in MuLab btw... Core i7 4770k at stock speed 3.5 Ghz OC disabled.

-Cheers

Post

is there a muscilloscope? :wink:
ACKCHYUALLY

Post Reply

Return to “MuTools”