Surreal Machines: Modnetic and Diffuse

[soma]

are there any clues when PB are going to update their copies - I've got diffuse from Surreal direct but modnetic from PB and they're on 1.1.0

We sent the updates to PB yesterday.

[GaryG]

Thanks for the updates, but the performance is unusable with anything outside 100% zoom here. Very sluggish. Please look into this.
(System: macOS Catalina, Macbook Pro 2020, integrated GPU)

I checked this on my old i5 Windows 10 laptop out of curiosity.

Using the default preset with modulation and reverb off, Reapers performance meter was showing Modnetic using around 1.3/1.4% (obviously it fluctuates all the time so I watched for a while and averaged out). If I set the zoom to 200% then I didn't notice any significant difference. If I set it to 130% then it did rise by about 0.1/0.2% or so. ie. nothing I'd ever notice normally, certainly didn't affect the responsiveness at all. I wondered if it was extra maths used to calculate those 'inbetween' settings, not straight doubling the dimensions etc?

Whatever, from my experience, observable but not really an issue on Windows.

[soma]

Changing the size shouldn't effect the CPU in any noticeable way.

[Vortifex]

Edited

[soma]

Modnetic doesn't remember the GUI size when I open a new instance. I select the size, then select make default. Close the plugin. Open a new instance and it opens at 100%. VST2 64 bit on Windows 10, FL Studio.

Can you confirm that you are doing these steps?

[Vortifex]

Edited

[ah@surrealmachines]

Hi Vortifex.

From what you are saying this sounds like it is to do with how FL Studio adds things to the database. The correct behaviour of the plugins is that they remember the last zoom they were opened at. New instances open at the default zoom (which you can set).

My guess is that FL studio creates its database by copying the current state of the plugin (like a preset) and the zoom is part of the DAW preset system. At present we have no way of detecting the difference between the state for a session and a DAW preset, and thus the zoom state (as you say) will depend on the current state of *that* plugin that is added as a favourite. You can confirm this behaviour by opening a plugin and setting the dials/sliders to non-default positions and then adding to your database in FL Studio. If I am correct then adding from the database will add with those settings, rather than defaults.

So, I would see this as an issue of how FL Studio creates its favourites, rather than a bug in the surreal machines plugins. I''m not aware of any way in which we could create the behaviour you would prefer.

[Vortifex]

Edited

[cantaloupe]

Changing the size shouldn't effect the CPU in any noticeable way.

Yes, just to be clear i am talking about graphical performance, not CPU. It goes from perfectly smooth at 100% to like 5 fps with 110%.

[ah@surrealmachines]

Changing the size shouldn't effect the CPU in any noticeable way.

Yes, just to be clear i am talking about graphical performance, not CPU. It goes from perfectly smooth at 100% to like 5 fps with 110%.

Thanks for reporting. We're looking into this - there were some late changes that improved performance at 100%, but seem to have significantly degraded performance at other sizes, at least on Mac, and unfortunately evaded testing. We have a route for noticeable improvement (but still not optimal) that will be rapid, and longer term we will be able to bring in much faster graphics performance, but the implications of that change mean that we might not be able to roll it out as quickly. Apologies for the frustration, although the 100% view should be useable in the meantime.

[ah@surrealmachines]

A quick update - we now have a route to much faster rendering when zoomed using the current backend that we can roll out very soon. We are investigating some reports of other issues also, and will hotfix a number of things as soon as we possibly can (bundling into a single hot fix update). The graphical performance issue will definitely be addressed as part of this.

Thanks again for alerting us to this.

[cantaloupe]

A quick update - we now have a route to much faster rendering when zoomed using the current backend that we can roll out very soon. We are investigating some reports of other issues also, and will hotfix a number of things as soon as we possibly can (bundling into a single hot fix update). The graphical performance issue will definitely be addressed as part of this.

Thanks again for alerting us to this.

Super! Glad you are looking into it.

[mi-os]

@surreal machines
thanks for your effort

Please make your plugins as CPU effcient as possible.

[AuralBee]

Mmm, still nothing at PI Boutique, sent them two emails already, requesting to make the update available.

[ah@surrealmachines]

As in another thread:

Updated installers are now both on our website and with Plugin Boutique that should fix the graphics speed issues and some other important issues that we hadn't encountered until release.

Thanks for bearing with us, and to those who reported issues and we hope you enjoy!