Skip to content

Proposal: mandatory DMXModeID for GDTF DMXMode and dmxModeID for MVR …#309

Open
kinglevel wants to merge 1 commit intomvrdevelopment:mainfrom
kinglevel:proposal/dmx-mode-uuid
Open

Proposal: mandatory DMXModeID for GDTF DMXMode and dmxModeID for MVR …#309
kinglevel wants to merge 1 commit intomvrdevelopment:mainfrom
kinglevel:proposal/dmx-mode-uuid

Conversation

@kinglevel
Copy link
Copy Markdown

Adds a new proposal under spec/proposal/dmx-mode-uuid/ describing a coordinated GDTF + MVR major-version change that introduces a mandatory portable UUID on and a matching required UUID attribute on the MVR-side reference.

Today mode identity reduces to (FixtureType-GUID, mode-name-string) — brittle to renames, reorders, exporter quirks, and GDTF-revision drift. The proposal closes the gap so patching/fixture-swap/MVR-update flows can rely on stable mode identity instead of name+index heuristics.

…GDTFMode

Adds a new proposal under spec/proposal/dmx-mode-uuid/ describing a
coordinated GDTF + MVR major-version change that introduces a mandatory
portable UUID on <DMXMode> and a matching required UUID attribute on
the MVR-side <GDTFMode> reference.

Today mode identity reduces to (FixtureType-GUID, mode-name-string) —
brittle to renames, reorders, exporter quirks, and GDTF-revision drift.
The proposal closes the gap so patching/fixture-swap/MVR-update flows
can rely on stable mode identity instead of name+index heuristics.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant