Skip to main content

Murali v0.1.4: The First Public Release

· 3 min read
Ravi Shankar
Ravi Shankar

Murali v0.1.4 was the first public release of a Rust-powered animation engine for mathematical scenes, semantic graphics, and timeline-driven visuals.

This was the release where Murali stopped being an internal experiment and became something others could install, inspect, and build on. The goal was not feature parity with older animation tools. The goal was to establish a clean foundation: deterministic timelines, world-space authoring, a modern wgpu renderer, and an API surface shaped for larger authored scenes.

Why v0.1.4 mattered​

Murali started from a fairly opinionated premise:

  • animation should be deterministic and time-driven
  • world-space authoring should come first
  • GPU rendering should be modern and cross-platform
  • typed scene code should remain maintainable as scenes grow

v0.1.4 was the release that proved those ideas could hold together in one usable system.

What shipped in v0.1.4​

The first public release established the core platform:

  • Modern rendering backend via wgpu, targeting Vulkan, Metal, and DX12
  • Scene and timeline model built around explicit authored state and deterministic playback
  • World-space camera model with orbit and pan/zoom controls
  • Core tattvas across primitives, text, composites, and graphs
  • Animation vocabulary for movement, fades, scale, rotation, morphing, and writing/reveal patterns
  • Embedded text rendering with Typst and LaTeX support
  • Export pipeline for offscreen rendering to frames and MP4 output

That combination made Murali immediately useful for:

  • mathematical explainers
  • timeline-authored educational graphics
  • narration-first animation workflows
  • Rust-native animation codebases that benefit from stronger structure

What this release did not try to do​

v0.1.4 was intentionally foundational.

It did not try to ship every category of scene all at once. It also did not try to hide the engine’s authored nature behind overly smart abstractions. The emphasis was on getting the mental model right:

  • Scene
  • Tattva
  • Timeline
  • explicit authored transforms and visibility

That foundation has shaped every release since.

Looking back from later releases​

Many of the later improvements in Murali build directly on what v0.1.4 made possible:

  • a broader tattva surface
  • richer examples
  • better 3D and AI-oriented scenes
  • stronger docs and public positioning
  • more refined authored APIs

So while v0.1.4 was smaller than the releases that followed, it remains the most important architectural milestone in the project so far.

What came next​

From here, the next releases focused on making Murali feel more complete as a public platform:

  • more reference-quality examples
  • broader tattva coverage
  • stronger docs
  • more ergonomic authored surfaces

See the current roadmap for where the project is headed now.