Post #2299376
2024-05-06 11:49 UTC
Expansion on tables:CuelistsCues (in lists)Channels (& cells)GroupsFixture typesFixture functionsIntensity, colour, beam, focus palettesPresets (another kind of palette)Palettes by fixture typeColour paths (description of how to fade between two colours)SubmastersFadersMacrosEffectsTimecode automation listsMagic sheets (custom visual layouts)Live/manual stateGobos (projected images)Colour wheelsbeam effect typescustom colour calibration curves
I’m sure I’m forgetting more.
Rows interact within tables in complex ways:
cyclic and directional relationships (eg cue cycles and links)hierarchy of simultaneous manual & stored state typesPriority levels including overrideshighest- vs latest-takes-precedence logicpermitted or unpermitted overlapping indiceslive and blind editing workflows (one edits via a manual state and atomic save operations, the latter via direct value modification)dependent transitions & timingchained timing dependenciesintentionally random values at runtimereference (palette) values and by-type referencesEtc.
It takes years to learn to operate these consoles to a very high level, but only a few.
I’ve spent a far shorter time (overall and by calendar) on one of these consoles than in the Unix shell, for a far greater overall proficiency, and critically, recall and ability to access all features without looking at a manual, after time away.
And before you say yeah, hobbyist — my day job involves Linux sysadmin duties. I only work on Lighting design a few times a year.
Replies (1)
-
@s0@cathode.church 2024-05-06 11:53
I’m not saying this to pick on any one UI paradigm, or software, or stack, or company. But to say that if you work on UI/UX, you need to be aware that the majority of what you use on a PC, server or mobile vehicle is light-years behind what professional domain-specific interfaces can do, and it’s maybe worth examining why, and how it’s gotten this way.