SoPA SOUND PARTICLE ACCELERATOR

SoPA

00

A live instrument for light. It builds particles in a 3D space you can fly through — cosmological structure, graphs, text, images, a webcam feed — and renders them as galaxies, dark matter, stars or clouds, every parameter open to being driven by static or dynamic input sources, including audio and video data.

CAPTURED IN SoPA filaments & voids · galaxies + dark matter · bloom
01

What it is

01.1
Grown or given

Particles are created either from algorithms that mimic cosmological structures, or from material it is given: graphs, text, images, or webcam input.

COSMOLOGY GRAPHS TEXT IMAGES WEBCAM
01.2
Four ways to render matter

Particles are rendered as galaxies, dark matter, stars or clouds, which can be influenced live by many parameters.

GALAXIES DARK MATTER STARS CLOUDS
01.3
Driven parameters

Parameters can be driven by timers or events from various static or dynamic sources: patterns, images, microphone, video and even shared browser tabs.

SOURCE
PATTERNS IMAGES MICROPHONE VIDEO SHARED TAB
TRIGGER
TIMER EVENT
TARGET ANY PARAMETER
01.4
A composed render stack

Output is composed from a render stack — background, particle scene, post-processing — all driven by individually composable pipelines.

BACKGROUND field · gradient · feedback
PARTICLE SCENE galaxies · halos · clouds
POST-PROCESSING bloom · blur · displace
01.5
Yours to keep, yours to share

A scene — every source, pipeline and driven parameter in it — saves to your own browser. Nothing is uploaded and no account is involved. Hand a scene file to someone when you want to, or keep it to yourself. A performance can also be rendered out as video.

SAVED LOCALLY browser database · no account
SHARED IF YOU WANT scene file · deliberate act
VIDEO EXPORT frames → app server · the one path off the machine
02

Privacy

PROCESSING STAYS ON THE LOCAL MACHINE
01
To use some of SoPA's features like microphone and webcam access, shared tabs, etc. a user will be asked for permission.
02
Data that a user stores in their browser, e.g. a SoPA scene, stays in the browser's database and by design it cannot be read by any other web page.
03
Users are, however, free to share their data.
04
All processing happens on the local machine; local data never leaves the application (except video export, which hands frames to the server that serves the app).
05
Once the app has loaded, cut your network connection. SoPA keeps running.
WHAT LEAVES THE MACHINE
MICROPHONE local · on permission
WEBCAM local · on permission
SHARED TAB local · on permission
SCENES browser database only
VIDEO EXPORT frames → app server

Video export is the one path off the machine, and only while an export runs.

03

The Team

Emma RENDER PIPELINE Sits on the keyboard during long shader compiles. Insists the bloom pass is fine.
Lina QUALITY ASSURANCE Stares directly into the viewport until the frame rate confesses.
LAUNCH SoPA COMING SOON