Flash-Scenes

[xn--nding-jua]

Fix flash-scenes in MIDI-In, Data-In and Keyboard-Control:

a) create new global storage for channel-values
GUID of the calling event
channelnumber (array)
channelvalue (array)
b) on calling the scene a new storage-element has to be created and stored with current values. then run the new scene
c) on releasing the scene (key-up) call the storage-element, restore old values and delete the storage-element

Thats it.

[digitalshow]

You know that I always think about a priority based system. My suggestion would look as follows:

inside the dimmer kernel, implement a priority based list. Normal channel setting calls will write at priority 0. Things like flash scenes write at a higher (customizable :) ) priority, their GUID is stored alongside. When a higher-priority scene is ending (flash release or maybe effect stop), that item is deleted. Then, flash scenes can take a higher priority and be preferred. When other channel values are set while a higher-priority scene is running, they are still stored at their respective item and are restored when all higher-priority items are removed. I don't think that will create large overhead in the dimmer kernel as those items should be rare and the priority field is cheap to process.

The advantage I see in this is that running effects or similar stuff won't destroy a flash. Even more important, restores from a flash won't destroy any scene started during the flash. There are some applications, like theater lighting, where this won't be an issue, but in any scenario where you have many effects (e.g. chasers) you will be thankful for a possibility for a flash without stopping all effects beforehand. I also don't think that it is a lot more work because you can keep existing methods and write new, overloaded ones. You have to edit the flash scene handling anyway.