sACN CID bug?

Not really a problem, per se, but I've observed something in the sACN output that appears to be out-of-spec;

Working from a Hedgehog 4X, the CID encoded in the sACN packet is not an RFC 4122 compliant UUID (ANSI E1.31 Section 5.6), rather, it appears to be NCS UUID, albeit with no timestamp, and a bit set in the reserved fields.

For reference, the CID of this console is reporting as {00000000-0000-0010-0000-0090a1170055}.

Again, it's not causing any problems, but I would be interested in hearing back if this is a bug.
Sign In or Register to comment.