Thanks for clarifying the 1 MiB limit. Reducing our SDK working-buffer request to 240,000 floats resolved the original loading problem, and we’ve since developed several functioning custom effects.
One follow-up: is that 1 MiB allocation independent for each Endless effect, or does it share memory resources with other effects running on the MESS?
I’m asking because I’ve experienced repeated freezes when saving presets containing a custom Endless effect alongside factory effects. The custom effect alone saves successfully, but adding another effect has sometimes caused the MESS to freeze during saving.
I’m using firmware 1.3 Beta 1. Could this be related to memory management, or would you prefer a separate bug report with reproduction steps?
Mess 1.3 Beta #2 is now available, replacing Beta #1.
This update fixes saving presets containing Endless effects and restores the correct Endless patch when loading a preset. It also displays “Not loaded” when a patch cannot be loaded.
Please download the latest beta and continue the discussion in the new thread:
Thanks to everyone who tested Beta #1 and shared feedback!