IDEA 1: TouchOSC + Tablet/iPad As I stated on the other post, you can move some of your controls to a tablet/iPad and use TouchOSC. IDEA 2: One Isadora Patch, Two Control Panel Scenes You can click in between Scenes in the Scene List to split the Control Panel, giving each Scene its own Control Panel. Using one or more background Scenes for your content, (activated with Activate Scene or Activate Scene Amount actors), you can use as many Scenes as you want to make individual Control Panels that all affect your content Scenes. Putting labeled Button Controls connected to Jump Actors will allow you to easily navigate between your Control Panel Scenes. Each Control Panel Scene needs to have an Enter Scene Trigger connected to an Activate Scene actor to activate your background content Scene.  Here's an example patch with multiple (primary [dark blue]) Control Panel Scenes and just one (secondary [light blue]) content Scene Scene 1 (Effects) & 2 (Snapshots) are separate Control Panels that both affect Scene 3 (Content)Scene 1: Video Effects Control (Primary [dark blue]) uses Control IDs 1-29 (30 and 31 are used to navigate between Control Panel Scenes)Scene 2: Snapshot Control (Primary [dark blue]) uses Control IDs 995-999 (30 and 31 are used to navigate between Control Panel Scenes)Scene 3: Content Scene (secondary [light blue]) uses Control IDs 1-29 and 995-999 (30 and 31 are used to navigate between Control Panel Scenes) If you use multiple content Scenes, you'll need to make another background Scene for scene control with Activate Scene Amount actors and Envelope Generator actors so that you can fade the different content Scenes in and out from each Control Panel Scene. Here's an example patch with multiple (primary [dark blue]) Control Panel Scenes and multiple (secondary [light blue]) content Scenes. Scene 1 (Effects) & 2 (Snapshots) are separate Control Panels that all affect Scenes 3, 4, & 5 (Content). Scene 1: (Video Effects Control) uses Control IDs 1-29 and 33-46 Scene 2: (Snapshot Control) uses Control IDs 995-999 Scene 3: Scene Control (secondary [light blue]) uses Control IDs 33-46 to adjust the intensity of the content scenesScene 3 is a background Scene, controlled by Scenes 1 & 2, that adjusts the intensity of the Content Scenes.Scene 4: Content Scene 1 (secondary [light blue]) uses Control IDs 1-29 and 995-999Scene 5: Content Scene 2 (secondary [light blue]) uses Control IDs 995-999 Control IDs 30 and 31 are used to navigate between Control Panel Scenes IDEA 3: Two separate Isadora Patches on Two Screens Control IDs work across Isadora patches, so if you've got: Display 1: VJ Patch (with actors using Control IDs 1-999) and Control Panel (Control IDs 1-450, for controlling your bin pickers)Display 2: A second Isadora Patch with your second Control Panel (Control IDs 451-999, for controlling your video effects) The split of Control IDS I gave was completely arbitrary, but this should work if you don't want to put it all in the same patch and use multiple Control Panel Scenes.

@Woland thanks for you responses, they're appreciatedi haven't disabled snapshots since i use it often and i keep the status bar open so i can measure the load whilst live mixing. i know i can feed FPS to the control panel, is there a way to do the same with LOAD and CYC?i've been considering putting the video bin on a separate screen, maybe using bin picker and stretching the control panel over two screens... if this will work then would be easier than using Touch OSC and OSC over WiFi to extend the control panel.rgds, Mr J

@rosa I think this will get you the outputs you need, but there is no indication of what you want to do, how much post processing, effects, mapping, virtual stages etc.

@nandadaOK, I've recompiled the updater and created an installer so that it should run on any version of macOS from Yosemite (10.10) to Catalina (10.15) without issue. I hope this will prevent the library errors you got. I've also created a notarized installer to prevent problems running this on Catalina.By the way: your signature line doesn't indicate what version of macOS you are using. Please update your signature so I'll know which version of macOS you're using as this is critical information for a case like yours.See the original post at the top for the link to the new updater.Best Wishes,Mark

@jfg @Fred  I'm certain I've got an installer for the older X4 windows version saved on my PC, runs happily on Windows 10. Not got access to it today sorry, but I can check tomorrow. I think this is the link to the relevant bits, it's got the command line interface for mac there as well (Helpfully in 'Archive' rather than 'Legacy'). https://www.datapath.co.uk/datapath-archive-downloads/datapath-x4-archive I thought that Wall Designer was supposed to support X4 if the firmware was up to date but I may be wrong. I actually preferred the old interface to the new Wall Designer.[edit: sorry, I've read your post properly now and see you had this link already.]

@fred thank you!!

Please open a support ticket. Isadora should not have any trouble outputing to any display recognized by your operating system. A link to our support form can be found in my signature.

Thanks so much - I will do this next week and let you know how I get on! David

@carlosI have used a Wiimote in a project back in 2010, the actor uses an IR-Pen to reveal the live camera that you see on the right side and the Wiimote is about 8m away up in the rigg and used as IR camera.https://www.filmprojekt.ch/en/...Best Michel

@dillthekraut totally! I could program this with actors any number of ways. I'm more interested in scene list and status APIs that could exist at the application layer, rather than in the document layer, that let you check what Isadora is up to no matter what document is opened. That way I don't need to change a designer's file to implement the non-creative feature of remote status monitoring.

@woland: Thank you.

@ril Agreed! A native MacOS client would definitely be nice addition to ZoomOSC, and perhaps when we have completed StreamWeaver, I will return my attention to building such a port.