@mark_m

Hi

This is my bad. I confused the qlab one on the add-ons page with a one for isadora/eos.

But, if you peruse the links posted by Woland above, there is a treasure trove of information, guides and files to achieve the aim of using OSC to control lighting cues on the eos consoles. 

I read through those links and ,as usual, leant more than I thought I knew! I would start with those guides and Marks Guru session on OSC. I am sure ETC has OSC guides on their sites as well as having a healthy forum akin to here. One of the links gives a very detailed step by step set up guide here. 

You do not need the console but could practice this set up with 1/2 computers. Once they are speaking via network, then you could play with the command syntax and be ahead of yourself before you enter the venue. The venue lighting staff should be up to speed with this approach as it has become a very normative practice in the industry.

You are only sending a simple GO command to eos at the end of the day. You can specify the number but the syntax is very straightforward etc. Once you have the first one down, then it should be a simple rinse and repeat.

Eamon

I'll play around with these suit-related things and get back to you. 

As noted above, after the original crashes while wearing the suit, I've been doing all the tests by streaming pre-recorded mocap clips/data out of Studio. Legacy works great. No crashes. Streaming pre-recorded mocap data out of the most recent version of Rokoko Studio results in Izzy crashing (either immediately or after 30 seconds or so), no matter the sequence of opening the two softwares and turning on streaming. This has happened every time, except for one. 

Out of curiosity, I tried different clips and even just one of the avatars standing in place, but Izzy crashes.  

@skuven

I've added this to our existing feature request for this

@taeeix

You might try changing the video Projector actor ‘blend’ input from ‘additive’ to ‘transparent’. You could also try changing the same Projector ‘layer’ input to a higher value than the base Projector layer.

Best wishes

Russell

For anyone coming to this for answers like I did, there is now a "Float to Integer" actor that will do this. And if you're using a timer, which actually outputs in millis, divide by 1000 to get seconds first.

@jean-didier

Try:

Without Isadora open, unplug your KinectLaunch Isadorayour Isadora fileChange the 'mode' input on the OpenNI Tracker actor to 'both'Save the fileQuit IsadoraPlug in the KinectLaunch Isadora and open the file

If it works, you'll be able to use both color and depth, so you won't need to change the mode input again.

@tlaloc said:

Just to confirm, there is no way to pull the time from the scene time shown here at 0 sec?

 Correct, this value is not programmatically accessible by actors.

@tlaloc

Yes

@cacoos

It's a known cosmetic issue on newer versions of macOS with Isadora 4.1.3 and older.

This is fixed already for the release that's coming very soon.

In the meantime, you'll see that those areas are only blank when you do not have MIDI, OSC, Serial, or TCP/IP data going to or from Isadora. As soon as data is going in or out, the relevant section of the UI will update.

In its simplest form, you can do this to see what I mean:

Here's a slightly more complex example that demonstrates the same thing, but cycles through each of those four data types: DOWNLOAD

(NOTE: The MIDI won't work unless you use the settings shown in the screenshot for Communications > MIDI Setup > Port 1 > (Input and Output set to "Isadora Virtual Out")

@dusx Thanks guys.

I've used IOS Screen Mirroring to a Mac. There's an app called True Visage that hides all the phone's camera settings, just sends what the camera sees, which is handy.

Bumping this as a reminder to any Berlin-based Isadora users that this is tonight :)

ignore me - i found the solution - its the top half/bottom half active state thing. i'll make new images.

@jonesseitz

It's a mac thing, to do with privacy: it's the same green dot you see when making taking a selfie with your iPhone.
Here's one way to disable it. There may be others:

https://9to5mac.com/2026/02/14...

HTH

Mark (not that Mark)

@skuven thanks. I will check it out. 🙌

@eva said:

Ok I try again:Does this work? 

No, the links didn't work. Is it a commercial app that you can give us the name of so we can look it up? If not, and you're trying to share a custom-made app with us, you'll probably need to upload it to Google Drive/Dropbox/something similar, then share the link to that with us here.

@gpeddino

Can you share the .mp4 with me? DM me with a file share link if you can, and I will convert to HAP and test. The file should stream, but yes, it will be very large.

@dusx said:

@Woland Your thoughts?

 Agreed

@gel_mystery

A trick I use is:

Create a Control Panel with a button that takes you to the next SceneMove the cursor over that button.Put tape over the optical sensor of a wireless mouse (now the cursor cannot move off of that button).Put the mouse in your pocket, on the floor, or take it apart and make a glove that completes the left-click circuit when you put your forefinger and thumb together.Now you can slap your pocket, step on the mouse, or close your fingers (with the glove idea) to trigger things.

Further advice:

Use a USB instead of a Bluetooth mouseUse a USB-over-cat5/6 extender to put the usb receiver for the mouse above the center of the stage (for larger stages) or just closer to the stage (if your computer is already backstage and the stage is small enough for it not to matter).TEST TEST TEST! Always bench test your setup as much as possible, then test more once you're in the actual venue.

@woland YUM! thanks for sharing the future!