Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Presenter screen lags, can take a long time for updates #14

Closed
tsmith512 opened this issue Oct 18, 2019 · 3 comments
Closed

Presenter screen lags, can take a long time for updates #14

tsmith512 opened this issue Oct 18, 2019 · 3 comments

Comments

@tsmith512
Copy link
Owner

tsmith512 commented Oct 18, 2019

This was reported by the stage manager as intermittent, but I saw it in rehearsal last night. Sometimes the presenter screen on the projector will "wake up" and show the cue within 5-10 seconds of being activated, but occasionally it never updated. My phone, the stage manager's laptop, and my own laptop on the debug screen all updated near instantly.

@tsmith512
Copy link
Owner Author

Preliminary research: The laptop attached to the projector was running Safari. Apparently Safari is more aggressive with throttling unfocused windows or when the user is idle. Since a lot of Socket.io's internals seem to be driven on setInterval and setTimeout events to fire polling for updates, that's my leading theory. Testing with my laptop running Chrome on the presenter and firing events from my phone on the SM display every 15-30 minutes, there was never any lag, on the same network.

tsmith512 added a commit that referenced this issue Oct 21, 2019
@tsmith512
Copy link
Owner Author

tsmith512 commented Oct 21, 2019

The "work" to address this issue so far is "don't use Safari on the computer attached to the projector." See socketio/socket.io#2924 which appears related --- but since the show is this week, I don't think I'm gonna get a workaround in.

@tsmith512
Copy link
Owner Author

No updates here, it was fine in rehearsal and postshow testing last night. Closing -- not "resolved" but "works for this scenario"

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant