I am relatively new to the CLI, and I am slowly moving from beginner to intermediate, so I thought that I would try using CLI programs, to further improve my understanding. This program looks looks great, but the explanation of how to do the installation on Linux, is quite literally all over the place.

Whilst MacOS, Windows, FreeBSD, and Raspberry Pi have obvious sections close at hand, there i

Units should be documented, preferably in a way that makes the documentation available through tools and applications, keeps it in sync with unit implementations, and covers units that aren't built into the A2 core.

The easiest and most obvious way is probably to add suitable string pointers to A2_unitdesc and A2_crdesc, for describing the units and their registers, respectively.

Alternatively,

Currently all operations done on the synthesizer properties aren't stored in state history, therefor they cannot be undone/redone.

Link these actions to the state module.

Question is: do we maintain a separate history for the instrument editor or do we think it is logical that upon closing the window, clicking undo/redo restores the slightest of changes made to all the sliders in the now clo

So that you can pause one sequence without stopping all audio by setting Play to 0 on AudioEngine, perhaps AudioEngine should also have a Pause function.

Improve documentation by creating a demo game using the engine.