@emullis

So you're all good now? Maybe it has to do with the order in which things are done. Try to experiment with whether it crashes or doesn't crash if:

You open Isadora, then Rokoko, then start streamingYou open Rokoko, then Isadora, then start streamingYou open Rokoko, start streaming, then open Isadora

To make clean tests, I'd do a restart between trying each of these.

JavaScript can't help. But Pythoner could offer a solution I am sure.

I can also enter a feature request to extend the actor. Truthfully though that won't be a high priority item, although it might be pretty easy.

@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!

@dusx Thanks, that really helped. It was in fact the opposite effect (to create a kind of negative fisheye process), but I tweaked the code you sent to do this.

@ray

Dual graphics cards is unsupported (meaning we are unable to provide tech support) since we have no way to create the same/similar setup.

With that said you can use more than one card. 
What is important is that you don't share/mix video from one output path to another.

So if you:

 add a movie player, and connect its output to stage 1 (using gpu1)add a movie player, and connect its output to stage 2 (using gpu2)

Don't try to mix the two videos together in any way.. keep them separate. Mixing will require moving the texture from one gpu to the other, and will be a spped/bottleneck.

No Isadora allows you to move video in anyway you like, so its very flexible. If you can keep the video flow simple, and maintain individual paths, you can make it work very well.

TEST, TEST, TEST!

Start simple, and build up.. test constantly

@ubik

Can you send the patch either here (if you're comfortable) or in a support ticket (see the link in my signature) so we can take a look at it? In medical terms, it can be hard to diagnose a patient over the phone rather than through a physical exam.