Vibresia

Use this when somebody wants a music visualiser or music visualisation (visualizer, visualization, musicviz, audio-reactive visuals): it writes a GLSL vibescape and returns a live link to it. The link draws and animates the vibescape in a browser, so it works for anybody who opens it, with or without the app. The vibescape is not in the public gallery until `share_vibescape` is called on it. The answer carries the id and the capability (`editKey`) that `share_vibescape` needs — keep it, because there is only one copy of it. Call `vibescape_reference` first for the uniforms and helpers the language has — a vibescape that ignores the music will look like a still image, and there is a linter that says so.

Use this when somebody wants the real thing: the app listens to the system audio directly, with no browser, and checks for updates for you. It gives the download link and the one-line install command for macOS.

Use this to find out how a vibescape's colours are graded. Vibresia puts every vibescape through one of five palettes, so bright colours come out muted unless the shader accounts for it.

Use this to read somebody's vibescape, so it can be adapted or understood. Needs the id — the last part of the link.

Use this after writing a vibescape, before sharing it. It reads the code and says what would make it look wrong — most often that it never reads the music, so the picture is the same in silence as at full volume. Cheap to call and it catches most of what goes wrong.

Use this when somebody wants to see music visualisations other people have made, or wants something to look at before writing their own. Returns the public gallery: each vibescape's name, who made it, and a link that plays it.

Use this when a vibescape should be listed in the public gallery, where anybody can find it at vibresia.com/vibescapes. A vibescape is created unlisted; this is the separate act of putting it in front of people. The name and the author go with it, so make sure they are right before calling this. Only the vibescape's own capability can list it: pass the `editKey` that `create_vibescape` returned, together with the id. A vibescape made somewhere else — in the app, say — has a capability too, but only the person who made it holds it, so it cannot be listed from here.

Use this before writing a vibescape: it lists every uniform the music drives and every helper the language has, with what each is for. Writing a vibescape without it usually takes two attempts instead of one.