you can use the OSC projection mapping from the add-on page:

https://troikatronix.com/add-ons/projector-mapping-touch-osc/

Best regards, 

Jean-François 

@steinster

These are the 2 parameter types supported for input at this time. Isadora does not have a matching list type available. If you need multiple values you will need to create multiple inputs.
That article is the most complete documentation for the actor currently.

@mr_j Thank you!

@notdoc Thanks, It's easy to do. As there as many seasoned users available, and the forum is very active, that a Tip's & Trick's area is established as tutorials usually miss this 'way to work' option. Just a thought.

@dbini

It could be that you connected them to something which has a range that can't include a negative number (like the intensity input of a Projector actor which goes from 0-100) which caused the actor to mutate and adopt the range of the input to which it was connected.

@stagerabbit said:

There is some weirdness. When I add user input actors for intensity and active, they sometimes default to "0" or "1" no matter what I do. Also, the order that the user input boxes appear in the scene editor seems to be pretty arbitrary.

 You may want to watch our tutorial video on User Actors

@cacoos

I do not speak Javascript, but I suspect these links probably contain examples of some of the code you'll need:

Defining variables (storing team scores as variables): https://www.w3schools.com/js/js_variables.asp

Javascript arrays (storing team names and scores together): https://www.w3schools.com/js/js_arrays.asp

Sorting Arrays (to sort the teams by score): https://www.w3schools.com/js/js_array_sort.asp 

This Youtube video might also help

Hi Gertjan,

I don't know if you have the chance to choose whatever projector you want. I own a Fuji FP-Z5000 (discontinued now), and I've used the Z8000 as well, and there is a Z6000 (I think it is the newest).

The fixed lens is a 0.35-0.37:1, it has a very good lens shift, and a surprisingly even light for being that short-throw. I typically use it to fill a 8 x 5.5 m, screen. There are no focus issues. On the Z5000 it is important to be orthogonal to the screen in order to keep uniform focus. The newer ones have an iterative 2 step focus that accounts for that.

This would allow you to go for rear projection, and the flexibility provided by the strong lens shift can ease your placement.

The projector is not easy to find. So in case of interest I would contact directly with Fuji-Europe in Germany (that's what I did) and they referred me to their Spanish headquarters.

Good luck

@woland

Perfet Woland I need to try matte++ I gonna see the link below and the manual page 394...

Thx a lot. 

@gpeddino said:

matching the movie tint colors with the side lights in a dynamic way

 that sounds like a great idea.

@lsnoopy

This file of mine has some comments that explain how I used the limit-scale value actors inside it: https://troikatronix.com/add-ons/live-drawing-example/

This video tutorial on the TroikaTronix Youtube channel on value scaling might also be helpful: https://youtu.be/MG3pbjPHOGc

@mathieusanchez

Unless I'm misremembering (I don't use my Blackmagic device very often), that's not what the iPad is outputting, it's what the Blackmagic device is currently set to in Blackmagic's hardware configuration software, Desktop Video Setup. Isadora has no control over what the Blackmagic hardware is configured to do, you have to check Blackmagic's Desktop Video Setup software to see how you've configured your device, then make the Input Format in Isadora's Live Capture Settings match that.

@chameau132 said:

Hey There... And is it possible to capture stage to picture in differents bins ? Can different bins be differents media folder ?Idea is to make > Video In watcher  > a green treatment in > virtual stage 1> capture stage picture in picture bin "green"> Same Video In watcher > a red treatment in > virtual stage 2 stage > capture stage picture in bin "red"

 This is not currently possible but I already put in a feature request for this when I was looking at your original post. As far as Isadora being able to "group" red and green pictures for you, I was able to make an example for you. It involves:

Naming the pictures as you take them with the Capture Stage to Picture actorParsing the name of every new picture file to determine if it's 'red' or 'green'Saving the name and media index of the new picture file into one of two Data Array actors (one for red and one for green)Using a Counter actor to recall the entries in the Data Array actor (so you can sequentially recall the pictures that are part of each group and their media index numbers.)

The third Scene ("Sorting Red/Green Pictures") in this updated example file has the programming for this.

@chameau132 said:

i cant' figure out how to crossfade 2 picture when recalling via Get Media Count > Get media index > picture player ? Any idea ?

Check out the second Scene in the new example file above.

@vidasonik said:

scale min to 0 and scale max to 1

 Here you are telling this side of the system to expect values from 0 thru 1.0, it can't scale anything because it has no reference point. 

These min and max settings require that they exist on both sides of a link between actors. If on the first side you set min= 0 and max = 1, Isadora will expect values between 0and1 to be output, then on the other end of the link if min is set to = 10 and max = 30, the values from 0 to 1 will be scaled to 10-30.

This works in the same way as the Limit Value Scale actor.

I don't know what you full range of incoming values are, but if you use a Limit Value Scale actor, you should be able to scale to 0-1 or 0-127 depending on where you want to send that data.

Would love to see some of these solutions uploaded to the Add-Ons Page if anyone has the time :)

@woland Thank you so much! This helps a lot!

@juriaan ah! Thank you. This was my first post so it was in the moderator queue and so I never got to check it until now and notice the images hadn't worked.

That said I was able to fix it shortly after I wrote the above: I read the manual again and found that you can double-click on a User Input (or User Output) to set the data type of the actor. It's behavior unique to the User Input/User Output actors.

Can mark this as solved. Hopefully the answer above helps someone else.

Ah thanks all for the pointers and examples :)

Appreciate this community in my Isadora journey!

@juriaan

Thanks a ton!

Would have never figured that out.

@tease Yeah probably Rutt Etra set to solid I'd say. Can be pretty GPU heavy but worth it!