pouët.net

Kill it! Kill it with fire!

today I started working on a new demo tool.
the concept here is to have an editor host running alongside the demo exe.
the demo is linked with a small utility library which is used to connect to the editor and e.g. retrieve parameter updates.
a "scene definition" (ASCII-) file (.rsd) is used to describe a hierarchical set of (named) objects and parameters.

the main purpose of the editor is to sequence / animate parameters.
this is not going to be an "engine" in the traditional sense.
the editor (once ready) will export properly formatted data files (hopefully not too large) and maybe a small header file with some minor utility functions so the editor library can be removed in a final release of the demo.

status (day1):
- ".rsd" scene definition files are parsed and transformed into a "DOM" tree which can be updated and queried
- an editor host continuously updates around a dozen parameters
- a client library connects to the editor host to retrieve the current parameter values
- a simple client test application renders some (anti-aliased) rectangles and ellipses based on the parameter values (yay!)

there's obviously a lot left to be done but regarding the editor I also have a lot of code that can be used (e.g. color / envelope / timeline editors).

here's a YouTube video that shows what's there so far: YT: demotool day1 06Aug2026

In case you are wondering what happened after day 1, here's a small progress update.

On day 2 I went to the zoo to consult a giant mouse-hamster. Unfortunately he wasn't very talkative and looked rather preoccupied with guarding his rock (it was a nice rock, though). Spent some time watching the rays and sharks at the aquarium and thinking about the software architecture. No code written but I'd still call it a success.

Days 3 and 4 were spent laying the foundation of the editor. While a lot of code could be reused (from my 'DAW'), around 70 "new pages" had to be written as well.

On day 5 (today), the first version of a "replay" (including clip transitions) was drafted, along with a very simple test project.

Here's a YT video: demotool day 5 11Aug2026

"snapshots" are basically key frames (at the moment). They can be assigned to clips, which in turn can be placed on the timeline.
The ASCII scene definition file (.rsd) now supports classes (everything is better with classes, right!).
The editor parses it and lets you create snapshots of object-parameter(-trees). The checkboxes are used to select which parameters to include in a snapshot.
For the transitions, the clip/snapshot parameters are interpolated between the current and next clip, taking into account the current loop area.
Last but not least, project files can be saved and loaded.

Still a lot left to do but at least it's a start.