Log · 15 entries
What shipped, what ran, what we measured.
Every release and every milestone, in the order it happened, with the number that proves it. We claim only what is built and tested.
Shift-scroll, drag, nudge.
Lane editing that feels like a DAW
The automation editor now zooms, drags and nudges the way producers expect.
SHIFT + scroll zooms around the pointer; SHIFT locks a drag, ALT frees it from the grid; arrow keys nudge by beat or bar.
Proof a value-only drag kept its exact time (66 563 ms) despite a sideways wobble; zoom kept the spot under the pointer to four decimal places.
Draw the light into the track.
Automation lanes
Sketch a fade for any DMX channel or Resolume parameter right under the waveform, and it plays with the DJ: loops, jumps and pitch included.
- Fades and builds for Art-Net and OSC, drawn on the beat grid.
- Follows the track’s position, not a clock: a loop loops the light too.
- Only the deck on air moves the lights; a fade can follow the DJ’s channel fader.
- 44 updates a second, 16-bit for smooth moving lights, TEST without a DJ.
Proof tested to the packet: Art-Net at a steady 44 Hz (mean period within 1 ms), lane values exact to the curve at every position.
It moves. The show doesn't.
Motion, without the cost
Pages glide, menus settle and numbers count up, while timecode and waveforms never lose a frame.
- Calm, Apple-like motion: one curve, three speeds, no bounce.
- Timecode, playheads and waveforms are never animated: they always show the truth.
- Motion steps aside by itself if a screen ever drops frames.
- AUTO / ON / OFF per screen.
Proof 24 page changes, measured: identical frame times with motion on and off (6.1 ms typical, 0 frames over 50 ms).
Dallas, not America/Chicago.
Say the city, get the time zone
Type “Dal”, pick Dallas, Texas, and every time from that night reads in Central Time.
- 34,000 cities built in, so it works on venue networks with no internet.
- “Time zone in Dallas, Texas, United States (GMT−5) · Central Time”, daylight saving included.
- Every device has a history: which venues, which nights, which IPs.
- Old strangers on the network move to an archive by themselves; nothing is ever deleted.
Proof "Dal" lists Dallas, Texas (Central) above Dallas, Oregon (Pacific): a picked city means the right zone.
Plug in. See only tonight.
Tonight's rig, at a glance
Every night starts with a clean device list, and SINGULARITY remembers each venue’s rig for you.
- The Network list shows only tonight’s gear; every venue’s devices are one tap away.
- Each night in History keeps its rig: which CDJs and mixer, which IPs.
- A new rig? SINGULARITY offers to save it as a venue.
- Set reports you can read: every track on its own row with the mixes shown, and a tempo curve.
Proof a 58-track demo set against a 120-track set list reads top to bottom on one screen width; the clock check matches Windows' own time service to the millisecond (47 ms vs 48 ms).
What did the artist actually play?
Venues, time zones and set reports
One tap at the start and end of a set, and SINGULARITY writes the artist a report: what they played from their set list, what they skipped, and what they dropped in.
- 9 of 12 played, 3 skipped, 2 extras, 1 h 05 on air, at a glance.
- A timeline of the set where the overlaps are the mixes.
- Export a one-page PDF for the artist, or a CSV.
- Every night in the venue’s local time: Dallas, San Francisco and Atlanta on one tour, all reading right.
Proof the US tour (DUCTWORK Dallas, The Midway San Francisco, Believe Music Hall Atlanta) spans three time zones; each night now shows in its own (CDT, PDT, EDT).
Readable from across the booth.
Easier to read, safer to tidy up
Bigger deck titles, calmer screens, and an UNDO for when you tidy up a bit too much.
- Deck titles 15 → 20 px; no text anywhere under 10 px.
- The set list says ON DECK and PLAYING, and only the playing track lights up.
- UNDO after forgetting network devices.
- Restore devices, venues or set lists from any earlier session, without overwriting anything.
Proof a real save: 33 devices from three US tour venues brought back from a session report after they'd been deleted (2026-10-05).
Your crew's screen, any phone.
CALL screens fit every phone
The department CALL screens now fit an iPhone edge to edge, with nothing squeezed off the side.
the countdown, note and GO bar always fit the width; long track titles shorten neatly; the first update installed from inside the app.
Proof measured at iPhone size: elements off the screen went from 17 to 0, on every CALL view.
One click. Always current.
Updates inside the apps
No more USB sticks between soundchecks: SINGULARITY now updates itself.
- SINGULARITY and SINGULARITY:RECEIVER find new versions themselves, then download, verify and install them with one click.
- Never mid-show: updates are refused while Show lock is on, or while timecode is running.
- Each download is checked against a published SHA-256 before anything is installed.
- One setup for both: install SINGULARITY and, optionally, the receiver in one go.
- the updater found the new version, downloaded 360 MB, verified the checksum, closed SINGULARITY cleanly, installed silently and reopened it, all in about 24 seconds after the admin prompt;
- the Mac standby covered the show throughout, then HAND BACK;
- SINGULARITY + receiver went in with one setup, and the folder move kept the licence and set lists.
- the receiver’s own icon (cyan frame, pink bars, receive arrow);
- a NETWORK choice per address, for two subnets on one cable;
- LTC at -3 dB by default;
- files in
Documents\SINGULARITY.
Proof (tested 2026-10-04 on the Windows show laptop):
One silent receiver can't break the rest.
No dropouts when a receiver is off
Switch off a receiver mid-show, and every other one keeps its timecode.
each receiver gets its own send; the crew CALL screens fit phones and tablets.
Proof found on 2026-10-04 with a Mac sending to two receivers; fixed and retested.
Proof Resolume got the right frame.
The read-back that can't be fooled
SINGULARITY:RECEIVER listens to its own LTC on the cable and only says VERIFIED when it’s right.
it counts a frame only after three in a row; no false alarms on idle decks.
Proof tested on 2026-10-04: DECK A VERIFIED for the whole test at -3 dB (102–108 ms path, compensated); DECK B idle with zero false alarms.
A laptop dies. The show doesn't.
Main/standby takeover, measured
Pull the plug on the main: the standby takes over in 4.6 seconds and Resolume never jumps.
- The standby took over in 4.6 s.
- A restarted main comes back held, so the two never send at once.
- HAND BACK returns control cleanly.
Proof measured on 0.4.1, Windows main to Mac standby, 2026-10-04.
Timecode that survives the network.
SINGULARITY:RECEIVER
A tiny always-on-top app that turns your Resolume computer into a timecode receiver with failover.
- LTC made on the Resolume computer, into a virtual cable.
- Failover per deck, with no jump on Resolume’s timeline.
- The next cue and the one after, counting down and pulsing.
- Paired by PIN; every packet signed.
Proof a TCNet takeover tested with Resolume Arena: Resolume follows a new server within 1–6 s, invisibly.
Every fader. Every knob. Live.
Mixer data, live from a DJM-A9
SINGULARITY reads a DJM-A9’s faders, knobs and on-air state straight off the network.
the mixer’s layout as a hardware-style console; on-air drives which deck is the master; Show lock and crew PIN pairing.
Proof proven on a real DJM-A9 at a venue on 2026-10-02 (94 parameters at about 4 per second).
Live at the show: timecode over the network.
First show with SINGULARITY:RECEIVER
Our receiver ran LTC into Resolume for a full live set.
timecode packets instead of audio over the network; LTC made on the Resolume computer; read back as VERIFIED.
Proof a full live set on 2026-10-03, with Resolume decoding throughout.
Want these in your inbox?
No newsletter yet. Instagram and this page are where releases land.