Limited channels through websocket?

[prototype14]

Hi, I have recently set up and used Q Light Controller+ with a collection of DMX lights andd an ENTTEC Open DMX, which we had set up across 208 channels. Using the Virtual desk in QLC, we were able to run cue lists and everything worked well.
When we then connected to QLC via a websocket, it appeared that everything after channel 128 was being ignored when calling the cue lists with the "<program number>|PLAY" command to run these same widgets. Luckily, I was able to readdress the lights to fit within 128 channels, which is sufficient for our needs at the moment, though if we wanted to add more lights to this in the future, this could be problematic.

Is this a known issue where I have messed something up in my configuration?

[mcallegari]

Are you using the web interface or a custom solution of yours?
AFAIK there's no issue with channel numbers.
Number 128 sounds like a signed 8-bit variable issue

[prototype14]

Hi,

It's a custom solution, written in C# that sends a websocket request to play a cue list rather than an individual channel.

For example, it will send the message "1|PLAY" to play that cue list, like I saw in the API test page (https://www.qlcplus.org/Test_Web_API.html)

[prototype14]

This appears to be some sort of limitation with the Enttec Open DMX.

If I set up a brand new project, I have access to all of the channels.
If I load a project, only the first 128 are sent through.
If, after loading a project, I disconnect and reconnect (or use the Input/Output panel) the OpenDMX, I then have access to all of the channels.