JigDAW

A plugin format native to the web

Overview Example plugins

Specification

JigDAW architecture JigDAW Host and Plugin Contract Latency and feedback Message protocol The portable module ABI Serving the namespace Plugin bundles Plugin collections Jig profiles Project format Web Audio Modules The agent surface

Guides

Loading plugins in your own host Publishing a JUCE plugin's DSP as a Jig Building and publishing a plugin What Jiggy does Testbed

Background

The clip launcher: what it is before it is drawn Collaboration: several people in one session Deployment HTML skins A path from the first sound to the whole studio A livecoding language The layout of the main view Nested plugins What Jiggy can take from Oxide Studio Building a plugin editor with the bridge A project as a folder of files that a web server could serve Jiggy as an installable app Reaper plugin management, and what Jiggy keeps Revisions SVG skins How a plugin gets its interface What sets Jiggy apart
Source on GitHub ↗

Jig

A plugin is a URL. Dereference it and it runs in a browser, with nothing to install. Jig is the plugin format native to the web.

  • Demo: pick a tune, press Play, change the sound.
  • Example plugins: the worked plugins, with their panels.
  • Guide for plugin developers: make a plugin loadable anywhere.
  • Guide for DAW developers: load other people's plugins.
  • Specification: what a host and a plugin must do.

More: the overview, the maintainer's version and the revisions log.

Generated from docs/index.md by bin/build-docs-site.js. The markdown in the repository is authoritative; this page is a rendering of it.