BLOG
Release notes, deep dives and how-tos.
Written while the thing is being built, by the person building it. Expect specifics rather than announcements.
DEEP DIVE
Can you run DMX in a browser? How that question became FlexViz -Part 1
How this all started.
Read the post →EARLIER POSTS
DEEP DIVE
Plan mode: see where your fixtures point to — the fixture-forward-marker
A plan that shows only position tells you half of what a rig does. Here is why every fixture in plan mode now draws its own aim, how the direction is derived from MVR rotation data, and what it caught in the first test scenes.
DEEP DIVE
From a lighting plan to a browser preview: what has to survive the trip?
An MVR import is not successful because a file opened. Fixture identity, patch, transforms, layers, geometry and intent all have to survive before a lighting plan remains useful in the browser.
DEEP DIVE
Why rendering gobos in a browser is harder than it looks
A gobo looks simple: pick a wheel slot, load its image and put it into the beam. Then surface projection, volumetric light, filtering and real GDTF data get involved. This is what it took to make browser-based gobo rendering look believable.
DEEP DIVE
What is GDTF — and why do fixture profiles need a standard?
Every lighting console has fixture profiles. That does not mean they describe the same fixture in the same way. GDTF exists to give consoles, visualisers and planning tools a shared device description instead of making every ecosystem cook its own soup.
DEEP DIVE
GDTF vs MVR — fixture definition vs scene exchange
GDTF describes the fixture. MVR carries the rig.
That sentence is deliberately simplified. It is also a much better starting point than treating both formats as mysterious files that happen to come out of your preferred Lighting- and Rig-Planning Tool.
5 posts in the archive.
Follow along by using it.
The beta is open. Open your own MVR, break something, and the next post will probably be about the fix.