bsmith96 / qlab-display Goto Github PK

onRefresh:

send(theIP, 53000, '/workspace/' + theWorkspace + '/cue_id/' + theCueList + '/children');

interpretIncoming:

  if (address.endsWith('children')) {
    var replyData = JSON.parse(args[0].value); // decode the JSON reply from Qlab
    var toReturn = replyData.data; // get the cue display name from within the JSON

    console.log(toReturn[0]);

    var cueList = []
    for (let i in toReturn) {
      cueList.push(toReturn[i].name)
    }

    receive(nameAddress, cueList.join('\r\n'));
  }

Possibly, display a list of cue names but keep a list of IDs in the menu. Then, if possible, find a way to highlight the current cue?

When running the script on the backup computer, it could not locate the config.json file in the same folder as itself to write the information into. Need to doublecheck if it's a script error, or a computer settings error.

• Bootstrap html document to display this information. Standalone web page, eliminating the need for working in terminal

Once it also sets the users preference of TCP vs UDP, this will enable it to automatically setup the correct IP addresses in the correct fields. (#17)

Add skip forward and skip back (which work on both Main and Backup computers simultaneously), only visible if requested – probably hide and show the same way as the BACKUP button.

Is it best to connect via TCP rather than UDP (set TCP PORT to 53001 and TCP TARGETS to qlabIP:53000), or to still connect via UDP and provide a heartbeat (/workspace/id/thump) every minute?

Discovered on playing-separate-cuelist branch, but likely exists in the main branch. When the displayed cue list reaches the end and displays no cue, the playing cue display does not update until you hit refresh.

More user-friendly

Currently, if qlab is quit before the script, it will continue displaying the last known reply.

Would be great if there was some kind of 'heartbeat' to alert the remote viewer when qlab was successfully connected.

• Get-IDs.applescript > 1-generate-module-config.applescript
• Create-Server-Setup.applescript > 2-generate-OSC-config.applescript
• get-cue-list-playhead.js > qlab-display_module.js
• open-stage-control-template.json > qlab-display_layout.json

On Top Hat.

Suspected the problem has to do with every computers' users being named the same e.g. "sss".

However, the Qlab mac also struggled to disconnect from the system Mac, and I had to reboot to disconnect. It could be that the connection was just not working properly. Investigating further.

The second script to setup the .config file for Open Stage Control must be run on the computer being used as the server, in order to have the correct path. This means it can only be run on a Mac, since the script is applescript.

Maybe rewrite in JS? Or find a way to allow running remotely from the Qlab mac while still finding the correct path?

Applescript 1: says it's still beta
Applescript 2: changelog doesn't tie to version number

On raspberry pi at home. 2 line shell script to open full screen browser window and launch OSC in headless mode.

On Linux at least, can use relative paths - generate the config from applescript on the Qlab Mac's.

Is it worth bundling a version of open stage control?

Ensure the handler can handle an undefined value

Try to leave only Main and Backup

Add a backup Qlab IP; get script to poll backup as well, but only display backup if the primary hasn't reponded (plus indicate this).

Might mean using the qlabReplies.on("message") function to simply set some variables, and display/update them elsewhere in the script?

Heartbeat would change too: sending to Open Stage Control. Maybe "/qlab/connected MAIN" and "/qlab/connected BACKUP" if switched?