Describe your issue here:
Hey Leo, not so much an issue as a question:
I have multiple iPads positioned around stage for the artist to use as a hidden teleprompter, because they’re obscured I don’t have a good line of sight to them and as such I’d love to have a way to display in my AbleSet canvas if the connection is happy. Is there a way to send a heartbeat to the specific IP addresses of the devices on stage and have an indicator in Canvas to give me peace of mind mid show? Is it possible with the OSC heartbeat built in to AbleSet or maybe by utilizing the HTTP API?
Thanks!
Jason
Please fill out these values to make it easier to troubleshoot:
- OS and Version: 12.5.1
- Version of AbleSet: 3.1.0 Beta 7
- Version of Ableton Live: 12.2.7
Hey @JasonBentch,
Starting with version 3.1 beta 8, AbleSet exposes a /devices/ namespace via OSC that gives you info about each connected browser. Every device gets its own set of values based on its OSC Device Name (set in the new Devices tab → Browsers).
For example, if you name your iPads ipad-1, ipad-2, etc., you can read values like:
/devices/ipad-1/page/path — the current page the device is displaying
/devices/ipad-1/page/title — the page title
/devices/ipad-1/names — the device’s name list
/devices/ipad-1/isLocked — whether the device is locked
So to build a connection indicator on your Canvas, you could add a Label element for each iPad with a dynamic background color like this:
${osc("/devices/ipad-1/page/path") ? "green-500" : "red-500"}
This checks if the device is reporting a page path. If it is, the label turns green. If not, it turns red. Set the Label text to something like “iPad 1” or “Stage Left” so you know which one you’re looking at.
You could even display what page each iPad is currently showing by using a dynamic Label text:
${osc("/devices/ipad-1/page/title") ?? "Disconnected"}
Version 3.1 beta 8 adds a dedicated Devices page where you can see all connected browsers, send cue lights and messages to their screens, change the page they display, and reload them remotely.
Make sure each iPad has a unique OSC Device Name set in its settings so you can target them individually.
Would that work for your use case?
Hey Augustin,
I saw your original reply in my email and tried what you suggested and it worked exactly how I need it to with beta 8, is there a reason I shouldn’t use the method you suggested there?
Hey @JasonBentch,
Apologies for the confusion, there was a mix-up with the drafts on my end. You’re good to go with that approach!
Glad it’s working for you!