Hello! Me again. This just occurred to me this morning.
I've been using RDM-QR codes on my P-Touch for my fixtures to speed up addressing, but the only addressing/fixture numbering implementation I can see about is ELC's and it only works with their nodes.
There's a spec that ELC have been trying to get adopted, which actually I think could slot the web interface quite well: RDM QR codes. The format is quite simple, just UID: XXXX-XXXXXXXX. Just the manufacturer and device ID separated by a hyphen. Maybe using something like qr-scanner to read the code in the web interface, which could bring up the fixtures config and be able to identify and change settings.
Could also be used for quick addressing in a view where you scan the fixture's QR code, DMXRouter highlights/identifies, addresses it, set its device unit number (if supported) and then increments to the next address/unit number to do the next fixture along the line.
Hello! Me again. This just occurred to me this morning.
I've been using RDM-QR codes on my P-Touch for my fixtures to speed up addressing, but the only addressing/fixture numbering implementation I can see about is ELC's and it only works with their nodes.
There's a spec that ELC have been trying to get adopted, which actually I think could slot the web interface quite well: RDM QR codes. The format is quite simple, just
UID: XXXX-XXXXXXXX. Just the manufacturer and device ID separated by a hyphen. Maybe using something like qr-scanner to read the code in the web interface, which could bring up the fixtures config and be able to identify and change settings.Could also be used for quick addressing in a view where you scan the fixture's QR code, DMXRouter highlights/identifies, addresses it, set its device unit number (if supported) and then increments to the next address/unit number to do the next fixture along the line.