Page 1 of 1

MSEX 1.2 backwards compatibility with MSEX 1.1

Posted: Tue Jun 21, 2016 11:24 am
by jossgray
For a server that implements MSEX 1.2 and a lighting console that implements MSEX 1.1, what is the best way to negotiate the MSEX versions?

The MSEX 1.2 server will wait for a CInf packet to be sent, and the console will wait for a SInf packet to be sent, so there is a deadlock.

Re: MSEX 1.2 backwards compatibility with MSEX 1.1

Posted: Thu Jun 23, 2016 7:49 am
by lasso
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 timeout.

Re: MSEX 1.2 backwards compatibility with MSEX 1.1

Posted: Thu Jun 23, 2016 9:48 am
by jossgray
Ok so a media server that supports MSEX 1.2, MSEX 1.1, MSEX 1.0 should,

Wait for CInf for a short amount of time (<5ms) and send a SInf 1.1 / 1.0 after.

What should the media server do if it supports MSEX 1.1 but the client supports only MSEX 1.0?

Re: MSEX 1.2 backwards compatibility with MSEX 1.1

Posted: Thu Jun 30, 2016 6:21 am
by lasso
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..

Re: MSEX 1.2 backwards compatibility with MSEX 1.1

Posted: Mon Jul 04, 2016 10:06 am
by jossgray
Yes I'm implementing MSEX 1.2 but need to support a lighting console that only implements 1.1