MVR xchange Unified Global Import dialog library and Workflow consistency.

[kinglevel]

I’m not a software architect — just a lighting guy, with some software capability.
But we need to address the elephant in the room with MVR.

MVR shouldn’t just be a file format. It should be a shared ecosystem.
As expected with MVR xchange, it is probably comming. (?)

As of right now, every manufacturer implements MVR differently.
Import/export behavior, patch merging, fixture mapping — it all varies — a mess.
That makes moving between systems harder than it needs to be.

What we really need is a standard public MVR libraries that offers UI capabilites in different forms — an open, shared implementation that manufacturers can integrate directly.

Be it C++, Python libraries, compilied shell binaries or other handy tools.
Like NDI has done with their tools.

Import/export logic.
Patch conflict handling.
Validation rules.
UI Dialog workflows.

Ideally, it would include a scalable reference UI (desktop, web, touch, cmdline) so the experience feels familiar across all softwares.

MVR was a big step forward.
The next step is workflow consistency.

And i hope that MVR Exchange thinks of this in a more unified global way, and not just network capability, so MVR will be that format we all want.

[kinglevel]

oops sry this should had been in some of the other repos