I'm new to the Blend Maker tool. I'm running a Mac Pro to two identical projectors. I'm not using a splitter; using the HDMI output to one projector and usbc adapter to the other projector.

I've got the setup going but when I preview Stage 3 (which combines stages 1 and 2), it doesn't send the blended image to go to the projectors. It just goes into force preview mode on my laptop screen. It I'm attaching screenshots of my Stage Setup Screen on my patch. Thank you for any help on this!

@ray

You could try clearing the Isadora preferences from the menu. 

I think you need to restart windows, get it so it remembers everything cleanly on reboot, then open Isadora and fix any stage assignments. 

If windows is struggling it will be an issue. 

Hi All 

I'm working on an installation with 8 projectors plus my workstation with 3 monitors and it's working less than optimal. It was working fine but I tripped on a cable and cut off the power. Now every time I start Izzy the stages are assigned to displays that are different to what was saved and I have to re-order them.I'm using win 11 so I tried system restore with no luck. Also tried only 1 monitor on my workstation but it didn't help. Is there a cache in Izzy that I can purge or something like that?

Any help would be great.

Ray

@woland hello, thanks for answer. I've install and lauunch Isadora 4 in demo mode without any problems.

I just tested the latency of a Blackmagic Design Ultrastudio Mini 4K and it was 100ms (6 frames). This was using HDMI 2160p60.

I like to use Companion to send commands, like shutter, to any projector. I then trigger Companion from Izzy. It makes swapping out different brands of projectors a lot easier. I also find if Companion can't control something its not meant to be controlled at all.

@dusx said:

With that said, you use the standard method of mutating your inputs/outputs to the expected types. 

 @Aolis 

These User Actors of mine can be quite useful for that: https://troikatronix.com/add-ons/mutator-user-actors/

@dusx

Copy this. 

Thank you for this information. I appreciate it. :)

@aolis

Pythoner basically passes values from Isadora into your Python script as raw Python objects. There is:
❌ No built-in type system for inputs/outputs
❌ No way to declare types like “this input is always an int” at the actor level
✅ Only positional passing of values

With that said, you use the standard method of mutating your inputs/outputs to the expected types. 

Additionally in your python code it is useful to test the type of inputs to ensure proper function. (I honestly don't do this often because I'm quite careful with my input connections. Using user actors to contain my pythoner scripts makes this even easier because you can set the type of the user inputs before attaching them).

You might look into using:

# Validate types
if not isinstance(my_input, expected_type):
    # convert or handle error

# Convert if needed
my_input = int(my_input)  # or float, list, etc.

This allows you to test incoming values in your python_init() function

Hi there,

I'm working with the Pythoner actor and I'm trying to figure out if there is a way of indicating that an input should have a particular range to start with inside the python code?

I'm able to get it to make different kinds of inputs but they always populate as "0". . . . 

Any guidance would be great.

Thank you!

-=Alex=-

(edit: added extra words for more clarity)