Wishlist: Persistent Accumulator/Variable

It would be very helpful to have a module that holds a value that is stored with the ensemble and in snapshots--something like the accumulator module, but with the output value being saved.

You can get something like this using a invisible 1 by 1 event table with a bit of writing and reading logic, but the value is not stored with snapshots (until tables are stored in snapshots ). (Anybody: is there a performance hit in using this technique, or are event tables lightweight when invisible.)

You can get something like this using hidden knobs, but that involves all sorts of hackysack automation type stuff which isn't satisfactory, given the simple task at hand.

 

variables in snapshots

like you, I utilise 1x1 event tables for variable storage...there seems to be very little performance hit even with relatively large numbers of variables...I store 16*5 variables in my motor mix ensemble, and it seems ok, and I use them as sequencers and automation systems with (on only the heaviest areas) a hit of only +-2% - but it's that spiking kind of CPU usage....

on to snapshots...

if your input to your variable macro (which feeds the W input on the event table) also has a 'snapshot module' (new module hiding at the bottom of Auxillary or Event Processing) controlled by the output of the table and feeding the write input (you'll need an event merge), then your value will be stored with a snapshot, and recalled (and stored into your event table) every time.....the snapshot module will also need to feed the variable output (another event merge) UNLESS you 'bang' (sorry for the MAXism) the variable out AFTER recalling the snapshot.

just thinking - you could use a instrument as a memory storage, and when you need to select a new set of variables just change a new snapshot ......I wonder if you can 'save' snapshots automatically? I know you can recall them.....

hmmm....

 

For one value, use the "SnapValue" module to store a single variable in a snapshot.

You can even multiplex them together to store table values, like I do in my CL-909 ensemble in the user lib. It stores a whole 64x11 table with every snapshot save and recall.

If you just need a "placeholder" for an event, there's no need to use a 1x1 table, use a Add module with only one side connected and an "EventValue" on the output (connected to the Val input of the Event Value). Sending an event to the add module is the same as "writing" to a 1x1 table, sending an event to the "in" input of the EventValue is the same as "reading" your "memory location".

Of course it's not saved with the snapshot or ensemble - but the "snapvalue" will do that.

- CList