K-OSPythonPygameFFmpegSoftware ArchitectureOpen Source
Order in Chaos: Architectural Decisions Behind the K-OS Audiovisual Engine
•Shawn Ashley Wilson
Why Build K-OS?
Commercial digital audio workstations (DAWs) and non-linear video editors are engineered with rigid paradigms: linear timelines, timeline-bound clips, and siloed tracks. When attempting to create live, improvisational audiovisual art that marries rapid-fire video sampling with live multi-instrument performance, existing tools constantly get in the way.
K-OS (the Keyframe Operating System) was created to eliminate those barriers.
Design Principles
- Entropy as a Feature: From a pristine piece of media to absolute noise or randomness, points of state mutation and added entropy are where artistic revelation occurs.
- Pythonic Control: Built with Python 3,
pygame,pygame_gui, andffmpegbindings, K-OS enables near-instant hacking of new DSP algorithms and video shader-like effects. - Real-Time Capture and Paint: Beyond playback, K-OS functions as a real-time digital chalkboard and screenshot annotator, allowing frame capture, live visual remixing, and generative digital canvas creation.
- Hardware Agility: Designed to run lean on Gentoo Linux with customizable command-line DIP switches to govern CPU threading, shadow modes, and full-screen renders.