remco_k wrote: 26 May 2019, 12:27
Maybe its just what you say it is. A
byte that is a heartbeat. In this case 0xFF (=255). I can't find it in te docs either. Or maybe its something specific in your currently loaded FreeStyler location that triggers a send of this data every X time.
If its a heartbeat; My guess is it doesn't need to be a human readable character, since you're on the 'byte protocol' port (3332) of FreeStyler - if I understand the docs correctly. So you may get any byte between 0 and 256, where most of them evaluates to a 'strange' character you can't read because you're a human.
EEk.
Make difficult to read the TCP stream when it doesnt have a common "end" to the stream.
Wish it terminated the connection after each query or sent a return.
One thing im trying to do is create a seqence/cue looper (so it changes my cues automatically at given times.
Sorta like a timecode thing.
Sending commands is great, so that works fine ( I can now control all the lighting and cues via a web browser and javascript to make my own loops etc.
Would be good to auto populate the text but Ill just have to call then "cue1 to 32" in the code.
If anyone's interested, Its all done in PHP (as the server that talks to freestyler using TCP 3332/3)
Will be posting my project and the code once done.
Essentially made a small PHP api that sends the commands to freestyler.
You then use Javascript to create your scenes at certain time intervals. (Pick a cue/cuelist to run at each time slice)
