No this is intended behaviour: unlike every other module in HISE the MPE modulators will not retain their state but rely on the MPE Panel to set their parameters.
I've added some MPE chapters to the documentation but @Dominik-Mayer locked me out of the server with his weird SSH fetish so I can't update it LOL.
Well your snippet deactivates the LFO with the button callback of the interface 
But if I have 4 different filmstrips with 128x128 and 128 frames it would take up more RAM than one single 500x500 filmstrip
4 filmstrips with 128x128 take about 25% of a single 500x500 filmstrip. The area of a rectangle is not linear to the size of its edges
Well, you don't have to go all the way to the other side and ditch every single image just because a 500x500 filmstrip is overkill
You can also combine bigger "static" images with smaller images that contain the animation, or images with vector effects (rotation, applying some shadow) etc.
Whatever you do, this is the entry point to the vector UI world in HISE:
https://docs.hise.audio/scripting/scripting-in-hise/scriptpanel.html
But you probably want to wait for David's upcoming video on the subject
@ustk said in SlotFX add rearrange Method along with swap:
Because the ID is reset at init, and "getCurrentEffect()" will return the same thing.
If you restore the scripts using a Base64 encoded state, it will retain the ID (even if the ID is actually stored in the state).
So if you have only Script FX, just don't use setEffect but ScriptFX.restoreState with predefined states.
Shouldn't affect it too much, the original file size of the images is more important - it may be possible that it has to create an resampled image during the UI rendering, but this will not stay in memory after the job is done AFAIK.
I think the increased maintenance effort because of another configuration does not justify this.
You can create literally any signal inside HISE (just render and load an audio file into the looper). If you want to run it through a series of analysers, use the plugin version of HISE and slap some FX after it.
Bypassing a global LFO causes instant crash.
OK, fixed that one, I hope everything's smooth now when bypassing global mods...
Check the % (modulo) operator, it is commonly used to wrap values around a upper limit.
wrappedI = (i + 1) % 5;