Support alternative TCP encoding

[nicolaiunrein]

When adding TCP support to the project I am working on lately I ran into an issue where my test setup using the generic OSC companion module would send data which could not be parsed. I first thought they had failed to implement the framing according to spec and I opened this issue. It turns out there is an alternative TCP codec which is being used here. It is specified in this paper. It would be great if rosc would support this codec as well. I will see if I can contribute a PR to support it.

My idea would be to implement this as a separate decode_* function. As a second step it would be great to have a decode function which automatically detects the format by looking at the first byte.

Let me know if this is something you would want to support.

Thanks,

[tm1000]

Same here and I think it's worthwhile to note that programs like https://github.com/ETCLabs/OSCRouter and ETC Lighting consoles both allow the end user to select the framing as 1.0 or 1.1.

It seems that Qlab also uses 1.1 framing

Ref: #31

@nicolaiunrein would you still be willing to do the PR?

[nicolaiunrein]

I will be on holiday for the next two weeks and I need to check with my contractor if they are willing to let me spend time on this. I am not keen on doing it myself so feel free to give it a go if you or anyone else wants to do it.