If you've ever added an observer (a third person) to a Tuple call, you've probably run into some surprising limitations.
I'm very happy to report that we just eliminated all those weird eccentricities.
Before: we had this weird observer mode with surprising limitations. Now: everyone on a call is an equal participant.
Sounds kind of simple, but was actually months of work. Classic software development.
A few other things in this release:
We hope you enjoy the new version!
Previously, we only supported sharing your entire display with your pair. This worked fine when using similarly-sized displays, but lead to near-unreadable text when sharing something like a 49" widescreen to a 13" Macbook.
As of today, you can pick a fully-customizable portion of your desktop to share. Just right-click (or Control-click) a contact and you'll be able to pick the portion of your screen to share. See the docs for more details, or check out this demo.
We just pushed a point release that fixes several bugs:
We also improved our update flow significantly. Tuple should now automatically download and apply updates in the background. Hopefully, you'll almost never see the "you need to update" message when you're trying to pair.
P.S. If you're curious about what's coming next, we just published a public roadmap.
We shipped our last quick update of 2020:
Enjoy the rest of your year!
We just pushed a bunch of improvements for those of you that use Tuple for three-way calls:
For more details, see our blog post.
Reconnecting a previously-connected microphone while Tuple is running no longer triggers bad audio behavior.
Nerdy details: the audio encoder we use has an API which identifies devices by their index in the list of available devices. This could get out of sync when disconnecting/reconnecting devices. The fix was to recalculate the index every time a device changes.
Classic, right? Persistent state is such a reliable source of bugs.
Sorry for the trouble, and the flurry of required updates recently.
When we pushed v0.81 yesterday, we inadvertently introduced a bug where folks were unable to un-mute themselves after muting. Sorry about that! This is fixed now.
After plenty of beta testing, we finally flipped the switch and deployed our new UI to everyone.
This new version attempts to address several issues from our old (MVP-ish) UI:
We feel like we've taken a solid step toward resolving these issues. (We hope you agree. 😁)
Thanks to our friend Derrick Reimer for his design and implementation work on this!
Also, if you'd like to hear more about the redesign, Derrick wrote a deep dive into how we planned, executed, and shipped the new design.
Good news if you like pairing with your webcam enabled: Tuple now uses way less bandwidth.
We did reduce the webcam quality/resolution a bit, but we think the bandwidth savings more than make up for it. (Please let us know if you feel differently after trying it.)
We believe we've fixed the issue that led to some folks having their drawings/highlights offset by some number of pixels. Thanks to all of you who reported this and provided replication steps!
As always, please email us with any feedback, big or small.