@dbini said:

The little scene name buttons at the bottom of the page are all grey, and turn blue when active, pale blue when active in the background and red when using blind mode. But would it be useful to be able to change the default state colour independently? kind of like the new coloured actor titles, you could create groups of scenes just by changing the button colour. I guess the palette might need to be restricted so it doesn't interfere with the functional colour changes, but a right click - simple palette selector (a bit like the slots in Ableton) might be useful. Even a choice of 4 different greys would be nice. What do you think? 

 I'll add this to the existing feature request.

@citizenjoe

numbers 2 and 4 seem to be contradictory. 

@fred said:

Although these have a test pattern generator, I would make some complex test pattterns for them to line things up accurately, One (annoying to make) would be an imager at the native resoltuion of the projector with alternating lines of R, G and B pixels, you can cut the image into 8 sections and alternate vertical stripes and horizontal. This will make it easy to see if the pixels are spot on as the colours will change if they are not.

 Especially Panasonic projectors (they where my main job machines), have an internal grid pattern which can be set to one of the rgb colors. If you set one projector to a specific color (eg. red) and a second to another (e.g. green), they mix to a third color (e.g. yellow) if they perfectly match. This makes it very easy to identify miss matches and even the direction to shift/warp.

Some projectors offer the option to set the whole system to one of the RGB basic streams. This way every every test pattern becomes monochromatic.

@joshuawg said:

I didn't need to try after a nice restart. Everything's working.

 Nice, happy to hear everythings working :)

@callie said:

project with 3 projectors in a 3x1 layout.

 Are you using projection blending?
As @Woland mentioned, we will need to look at your full configuration to fully understand what is happening.

@dusx No, but I will do that, thank you.

@bonemap @jandraka 

Performing a little bit of thread necromancy since I ran across this and wanted anyone who ran across it in the future to know that, as of Isadora 4, the Button Control has Control Properties for the color of the button in its on and off states:

The method of using a picture is still totally viable, and can be nicer if you want to include a fancier-looking button designed in Photoshop. Also, it's worth noting that you can use images that have alpha and the alpha will be transparent on the button in the Control Panel and you can make some pretty neat buttons that way.

UPDATE: I tested the system yesterday with the organisers of the conference. This time I had 2 external monitors (one to pin the zoom participant, one as a projector for my studio) and it didn't work. : (
Screen Capture was constantly getting confused about which screen to capture. Even when running in a background scene, sending video over a Broadcaster, when I changed the Listener scenes, the output from the Screen Capture would change to a different screen.
So now I am running Zoom on 2 machines. One has a HDMI output to a capture device on the other one. I pin the Zoom participant to the capture device and then the video shows up as a Video In source in Isadora. I then use Syphon Virtual Webcam to get the output from Isadora into Zoom.
It seems to work OK now I'm not using Screen Capture. Time for more remote testing.

EXTRA UPDATE: as long as the host doesn't Spotlight anyone, then the pinned video feed works fine!

@bonemap Here are some more that might be useful:

cueing-cue-stack-user-actor.izz

qlab-osc-cueing-examples-2024-05-02-3.2.6.izz

manual-override-for-automatic-cues-2024-02-06-3.2.6.izz

@dusx said:

What specific RTSP feed do you want to capture?

 motion jpeg and h264 with the possibility to switch the sound on/off

It would be great if you could made an actor. I am too bad with python to write it myself. I will try but my success chances are very low.

thanks

Jean-François 

@thatmattrogers

Once you double left-click a Projector actor to open IzzyMap, you can right-click on a mapping slice or any of its points and you'll get the option to publish various parameters that will show up on the Projector Actor to allow you to manipulate them programatically.

Gif: https://jmp.sh/D2RE0VVC

@lwebster

sharing the steps I provided in the support thread. These steps corrected the issue both on my machine and lwebster's

I have just gone through the process of getting my Astra Pro to work on my Windows 11 machine, and ran into some problem.

Here is what I found and how I fixed the issue.
The driver for the device failed after first being plugged in. I saw the red IR laser activate, but later it was off.

Looking in Device Manager, I found that the device is listed under 'other devices' (note it is also listed under Cameras.. but that's not what we need) and had an alert icon that indicated no valid driver was available. Trying to update automatically failed.

To fix this.

ensure Isadora is closed.right click the device in device manager (under Other Devices) and uninstall it.get the Orbbec Camera Driver for Windows from: OpenNI SDK - ORBBEC - 3D Vision for a 3D World  (Note: you do not need the OpenNI SDK)unplug your Orbbec if plugged in.unzip the driver and install it.reboot your systemOpen Isadora and add the OpenNi Tracker actor, and allow it to connect to the device. 
mine was using 'sensor index = 1'

@fred said:

@citizenjoe yep, but these are not great for optical transparency for cameras.

 True, but for what I use it for (tracking) it doesn't matter. They are a cheap and cheerful alternative!

Cheers,

Hugh

@tr742

And this is an example of that background scene that I talked about

Unless I'm misunderstanding this completely it just sounds like you need to familiarise yourself with the different types of scenes that operate in Isadora.

Basically you can have 2 scenes operating simultaneously. 

So for example you might have a scene which plays your video content on screen B, whilst simultaneously activating a background scene which shows video on screens A + C.

The benefit of this is that background scene will keep playing until it is deactivated. So it can play in the background of multiple scenes. 

So in this scenario you could trigger a jump actor to go to the next scene where a different video plays on screen B. But the video on A +C would continue as if nothing has happened. 

It's the same technique you would use to have an audio track which runs through multiple scenes.

This video explains it all

@judiths

Here's an example file that shows how a Virtual Stage and the Get Stage Image actor might be able to help solve your issue. (Though if you post your actual file with the media I'll be able to understand and help more specifically with what you're trying to do.)

File ---> zooming-content-2025-02-26-4.0.9.izz

Without Virtual Stage:

With Virtual Stage:

@princecarlosthe5

The Rokoko Studio Live Watcher actor and the OpenNI Tracker actor have different joint lists so we moved them to those two actors. (I swear I put a task to add to the Skeleton Decoder's 'point sel' help text to check those actors for their joint lists, but I guess that slipped through the cracks. I'll go re-add it.)

The joint list for the OpenNI Tracker can be seen by just mousing over it, as one used to with the Skeleton Decoder, but the joint list for the Rokoko Studio Live Watcher actor was a bit too long to comfortably display inside the program so for that one you'll need to right-click the actor and choose "Show Actor Help In Browser" at the top of the contextual menu to see the additional actor help with the joint list included.

I've been trying everything I can think of, changing every option/configuration, software/hardware, etc., without any luck. I hope someone can find some solution to this issue. For now, I only have two solutions: use another video capture card brand with Isadora, or use Blackmagic with another software.

@casselli

Very strange. Can you send a screenshot or recording of the issue (so we can reproduce and then attempt to fix it) and also let us know what setting you had to change to fix it (so we can help others who might have this problem in the meantime)?

@joshuawg said:

@woland thanks for the response! I think you may be right about hardware limitation. I did get it to work though! I am doing the live delay that I posted about previously, which is why I ended up shifting to a three computer setup. Now the macbook pro does nothing but process the live video delay and send out a single 4k NDI stage (I had previously be sending out several different stages to the Mac Studio) with all 9 stages to the other two computers. Working pretty well actually! 

 Awesome to hear! Yeah, distributing the work based on which computer(s) are the beefiest is one of the best ways to optimize performance when running video between multiple computers.