Qlab remote update

[Jonathan Pearce]

Since updating my qlab remote app it refuses to connect to either Qlab4 or 3.2. It will see that I have qlab open on my machine, and list the machine's name, but not list any open workspace(s) for me to select. I've tried with and without license.

Any ideas?

[luckydave]

Do you have more than one version of QLab open at the same time? That can confuse the OSC ports, so it's helpful to keep only QLab 3 or QLab 4 open for use with QLab Remote (or any OSC control).

--

luckydave

On November 17, 2016 at 4:22:12 PM, Jonathan Pearce (jonrp...@gmail.com) wrote:

Since updating my qlab remote app it refuses to connect to either Qlab4 or 3.2. It will see that I have qlab open on my machine, and list the machine's name, but not list any open workspace(s) for me to select. I've tried with and without license.

Any ideas?

--
--
Change your preferences or unsubscribe here:
http://groups.google.com/group/qlab
 
Follow Figure 53 on Twitter: http://twitter.com/Figure53
---
You received this message because you are subscribed to the Google Groups "QLab" group.
To unsubscribe from this group and stop receiving emails from it, send an email to qlab+uns...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/qlab/5fb36afa-515c-4817-ba63-7d670b517ddd%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Jonathan Pearce]

Nope, just the one at a time. And nothing else open that would be trying to read OSC.

[Thomas Press]

I have also had this (computer shows up- but no workspace), but weirdly remote would work fine with another computer on the network that had a qlab workspace open. 

[Brent Lord]

Hello -

Thanks for reporting this, and we are working to try to reproduce this here.

Expanding on luckydave's reply above, if you did at some point have copies of QLab 3 and 4 both open simultaneously, make sure you quit both copies of QLab and then relaunch just one of them. That ensures that port 53000 gets released by whichever copy of QLab had previously claimed it.

Second, check that OSC control didn't somehow end up switched off in your workspace settings. In Window > Workspace Settings (or cmd-comma), double-check that "Use OSC Controls" is still selected.

Aside from that, a few additional thoughts/questions:

1) Are you able to make a direct connection to your QLab computer via an IP address? (Tap on "Other..." on the connection screen to direct connect.)

2) Might there be anything that stands out about any of your workspaces' names... non-standard characters or something like that?

3) Are the problem networks IPv4 or IPv6?  QLab Remote is designed to handle both types, but knowing this might help us focus our debugging efforts a bit more.

- Brent

[micpool]

Great work on all the improvements in QLab remote

Unfortunately I'm seeing this problem as well

Sometimes there are no computers listed in remote

Sometimes computer but no workspace

Sometimes seeing duplicate computers listed  but no workspace

No difference if I try to connect to IP manually.

Sometimes remote disconnects but does not indicate this and then no when I try to reconnect no workspaces are listed.

One other thing, I think moving carts needs a longer finger down before engaging (or a double tap and drag) . At the moment it's very easy to keep your finger on a cart remote and have it go into MOVE cart position mode. It seems to do this within .5 secs.

This is even more problematic because QLab remote uses the keyup as the go (which means if you press nicely instead of Jabbing at it you get more latency) I understand that the reason it is designed this way is so that you can rest your finger on it and release it bang on the cue, but I don't know how many users realise this and just think it's very laggy on their normal press style, and secondly this is clearly problematic when applied to the Cart remote start, as if you rest you finger on it in preparation for a release to go, it will change mode and not trigger when you lift your finger.

Mic

[Brent Lord]

Hello again -

We are working on trying to zero in on the conditions that are causing these QLab Remote connection problems. So far, we have a hint that perhaps self-assigned IP addresses may not behave as well as DHCP-assigned. Otherwise, please let us know if anything about your particular network setup might be useful to us as we try to track this down. And what, if anything, works to fix your connection (i.e. does restarting QLab work? Toggling Wi-Fi or rebooting your Mac, maybe?).

Also, Mic - that's a great point about long-press on cues in a cart. The default duration to recognize a long-press was 0.5 seconds, so I'll make a note to increase that a bit.

Brent

[Jonathan Pearce]

Hi Brent,

My test setup was a mac mini (running Sierra - just testing on my usual desktop rather than a show machine) on ethernet with static IP, with a proper local DNS server specified. iPad was on a dhcp address. Didn't manage to get it working at all on either 3 or 4 (properly closing each) in my brief experiment. Won't get any time to investigate within the next fortnight.

Jon

[Brent Lord]

Good morning -

We should have a QLab Remote 4.0.1 beta ready to share today. Along with a handful of other issues, this build will hopefully address some of the connection issues you've been seeing. It also includes some debug logging that might help pinpoint the failures if problems do persist.

Please send your email address to me at br...@figure53.com if you'd like to try out the 4.0.1 beta, and I'll put you on the list. 

If you haven't beta tested using TestFlight before, it's really simple to use. You'll receive an invitation from Apple and the instructions will walk you through what to do next. Installing the beta replaces your existing copy of QLab Remote on your device, and you can delete the beta and reinstall the "official" release version from the App Store at any time.

Brent