Allow to export found (RDM, LLRP...) devices to MVR

[vanous]

Thank you for all the work. I tested MVR-xchange of DMXRouter with BlenderDMX today and it works... well, in my last release i introduced a bug into MVR import - i missed to use my updated progressive MVR import in MVR-xchange, this is now fixed and i released updated version. I also added DMXRouter icon to DMXRouter stations in MVR-xchange in BlenderDMX, for nice UI :)

I wanted to mention - in DMXRouter, exporting found devices to CSV is cool, but a bit archaic :) , perhaps exporting to MVR is more modern option... you can get inspired by my PollToMVR tool :) . You already have all the other pieces together... :)

[fiverecords]

Thanks for testing, and good catch on the import bug. The DMXRouter icon in BlenderDMX is a nice touch.

Quick note on the CSV exports — they're diagnostic, not a fixture-list interchange. The operator uses them to verify the RDM discovery run found what the rig sheet says, per port.

The proper MVR path is already in flight on the patch side. RDM-discovered devices can be pushed into Fixture Check, where the operator assigns a GDTF profile per device. The next step is exporting that linked Fixture Check state to MVR — which gives the FixtureType + DMXMode + address triples a visualiser wants, with the GDTF library baked in. It'll be a position-less MVR, but for a "what's actually on the rig" handoff that's still a step up from CSV.

Will have a look at PollToMVR for ideas — thanks for the pointer.