the code supports multiple effects at the same time, but the user interface does not

[marc365]

all effects are allocated to CHAIN$(1), but if the array is populated it will process them all in order

it remains to be seen how useful this would be, maybe reverb, resonant filter and mix is a good combination, but you can layer these easily anyway and there are multiple banks to store the layers. The UI would need updating to have a way to "attach" an effect once you have set the parameters (a button in the window, and designing an icon), then if another effect is previewed it will join on CHAIN$(2) etc. but the interface would need to be able to roll back the attached effects, maybe even modify the parameters. it could have a control window showing the active effects with a X button to remove them, but how fun would that actually be, and how useful. a previous version had a full window with all the effects available that could be toggled on/off - but that was before the window popup and parameter modification with the sliders was added, it becomes cumbersome with multiple entry/options - and i never used that feature for anything. it added overhead I didnt want.

if i add 2 new commands -

CHAIN=1..max
and
SETFX

macros can rack up effects.

to clear the effects a new macro "Clear Effects.asc" can simply be

CHAIN=1
SETFX ""
CHAIN=2
SETFX ""
etc. to the max

[marc365]

i have discovered that i can't release these new CHAIN, SETFX and _TGLREALTIME commands. some effects have buffers, these buffers are dynamically allocated when they are opened from the menu which shows their window. when using the effects directly with SETFX and _TGLREALTIME without the window and without the allocated buffers there are crashes as the effect writes to an arbitrary memory location. I was writing a function to check if the buffer was zero before proceeding, a framework to get around this error, which needed a notification instead of just no effect processing. the notification then spammed the scroller and flashed the screen each time it attempted the effect, 50 times a second. i realized i can't be bothered creating a layer for this error, its not an error, its an implementation flaw as only "some" subroutines function correctly with the new commands. after implementing the feature and playing around testing i did not use it for anything "real" so there is no real "loss", it was a precursor to how i would like the sequencer to interface with the effects. I could disable the things that cause the crashes, but that fractures the system and just doesn't feel right to do. these commands are not being added to the next version, but will return later in some form. Version 1.17 is incomming...