citp-protocol.org

Hi,

Those are good points, you've got me convinced.

Hi,

Capture also assumes it's 0-based.. I suspect a typo snuck in there. Are you aware of any other systems than your Mbox which assume it's 1-based?

Hi,

How do you envision that being used? Since it would be cable agnostic, no system could use it to actually identify the DMX data in question?

Hi,

Prior to 1.2 the best bet would have been to respond to 1.1 requests with 1.1 responses and 1.0 requests with 1.0 responses.

If you are making a new implementation I would strongly suggest you go for 1.2..

Hi,

I would just resend the SInf message with the new layer list definition, but I would be surprised if any consoles support the subsequent workflows necessary to ask the user to deal with the addition/removal of layers and their patch on the fly like that.

Hi, The key to the answer lies in the documentation of the SInf message. If you support 1.0/1.1, then send SInf immediately, otherwise you need to wait for a CInf first. There is no timeout specificed, however the CInf message is to be sent immediately on connect so we're talking about a millisecond...

Hi,

Yes, it supports this.

Hi,

You're right, that's a typo. And I found a could of more along the same line. I've commited a fix now!

Hi, It's back online now (lewlight.com)! I think it does up to 1.2, but I know I should release a new version because it has flaws. I will point out that it's not an attempt at a CITP compatibility test app, the term "test suite" simply refers to being useful for testing. The UUID field is...

Protocol specification The CITP protocol specification can be downloaded as a PDF from the download section of the Bitbucket project where the specification is kept: https://bitbucket.org/lars_wernlund/citp/downloads Contributing The specification consists of an HTML document and a CSS style sheet ...