Code-Driven Sound Synthesis Tool earshot v0.3 Expands Motion Design Audio Workflows
Leon Lin released earshot v0.3, adding 201 code-generated sounds, sound kit generation, improved frame-exact timing, and integration with the cinetic motion des
Image source: @LexnLin on X
Leon Lin (@LexnLin) has released earshot v0.3, a code-driven procedural audio tool featuring 201 programmatic sounds, full sound kit creation, improved frame-exact timing, and integration with the cinetic motion design skill. The update advances procedural sound synthesis aligned to visual timelines.
201 Programmatic Sounds and Sound Kit Creation
The core update in earshot v0.3 is an audio library of 201 distinct sounds synthesized entirely through code. Standard media workflows typically rely on static WAV or MP3 audio samples that require manual slicing and external management. In contrast, earshot generates sounds programmatically from procedural definitions, offering flexible parameter adjustments. Additionally, the new earshot kit feature generates entire sound kits, allowing creators to build cohesive acoustic sets for unified design themes.
Frame-Accurate Audio Timing and cinetic Integration
Accurate synchronization between visual transitions and audio cues remains essential in motion design. In v0.3, the earshot sfx capability has been improved to time sounds to exact visual frames, minimizing manual alignment. Furthermore, earshot is now integrated with cinetic, a skill for creating motion design. Leon Lin noted that the announcement video was produced using Opus 5.5 and cinetic with earshot handling audio, showing procedural sound embedded in visual generation pipelines.
Practical Implications, Verified Details, and Limitations
Procedural sound generation offers tangible benefits for design automation and version-controlled media pipelines. Managing audio parameters in code reduces binary asset overhead and simplifies collaborative iteration. However, adoption should be weighed against verified details. While Leon Lin shared the repository link (https://github.com/Leonxlnx/earshot/), the post provides no package manager commands, runtime prerequisites, or licensing terms. Production teams must review the repository directly.