@barneybroomer said:

@dusx Eeeh people, that is what I already said in my question, this is how I use it. My question is if I make several mappings inside one projector I like to have the input and output mappings from each slice exactly the same, so I can animate parts of my projection.

 Really sorry for not understanding the issue. I will have a look at Ryans patch. 

@mark said:

Well, guess we're stuck with -1 to +1 for the moment.

 Unless you had an option moving forward to swap the range between using -1 to 1 and -100 to 100.

@juriaan said:

I agree complety with the OP, still I think that it is worth the discussion regarding the weird "++" naming, it becomes quite difficult to explain it to fellow students..

 I agree with all three of your points, but also:

Curvature ++ Macro.i3ua

Maybe I try to make things in a strange way, but it would be great to be able to get the input states of actors. For examaoke getting the visible state of a movie player, or the movie index. I know you can intercept the data going into the actor but it would be great to have access to this data coming out of the actors, as we cannot get data from inputs. I could guess that this does not have to be too much coding work. Right click on an actor and a new punish inputs as global value, give it a name and all inputs are sent out as a list of values in a global value namespace. It would be great to also be able to link controls directly to global value parameters.

Good catch.

Heres a few workarounds in the meantime.

3.0.1 Get Media Index 0 Workarounds.izz

You could stick any of these in a Macro or User Actor and use them in your patches if this is a problem you encounter frequently.

Best wishes,

Woland

We're also clarifying further on the Plugin Page which Artnet Plugin is for which iteration of Isadora

So, this is a tile effect that will take a small input image and tile it to create an output of X width and Y height.
This would better server some generative use cases, where I would like to 'draw' on a small virtual stage, and then tile this image to create a full output size image for output.

It might be nice to be able to see what is being sent In and Out for ArtNet.

@ianpep

Isadora 3 supports timecode, but it is not the default for Movie Players.
You need to right click and convert the Movie Player to use TimeCode.

ok, with the patch file it seems to work

prova.izz

@gertjanb said:

It would be great to have a play license where they can make some small changes. for example a license where you can only save the mapping. and/or change some media.

 I don't know that it would be sustainable for our team to develop, test, and maintain another specialized version of the software. I would suggest the rental and subscription licensing options as a solution to this.

@dbengali said:

publish the blend mode (transparent, additive, opaque) for elements of IzzyMap mappings.  At the moment, it seems the only solution to have multiple blend modes for one mapping is to make separate copies of this mapping and manually change the blend mode for each.  However, if one has encapsulated the mapping in a user actor so that it can apply to an entire show, one must manually copy and paste mappings back into the other blend mode versions, and manually change the blend mode again.It would be amazing if we could just use an input parameter on a scene by scene basis to use the same user-actor-contained mapping with different blend modes.

 I have logged this feature request in our sheet

I have logged this feature request

@dusx Just read this ;)

@mark

Yay, I am super happy I missed that!

Amazing.

@rodgy_fr and @bssd72 

Any news for NDI input release ? It would have very helpfull for me next week :-(

My attention has been focused on Kinect/Depth tracking actor. If you want this and are not part of the beta program, then open a ticket and ask to join the beta program. I will be posting a beta of the NDI input plugin to the beta tester only thread in the next day or two.

Best Wishes,
Mark

Thank you @dusx,

I know the workarounds. Those where described in the linked topics as well as comments by Mark about this.

I just thought this feature request forum category is meant to  keep track of the those and to see how many users would be interested in them?

Am I wrong about this?

Dill

@ughoenig said:

I see the problem with floating point numbers, but it would still be very nice with integers.

Implementing this in some cases and not others would be confusing for many users because the feature would seem inconsistent.

@mark

Thank you for taking this seriously and investigating every avenue. I can only imagine the frustration...

@woland

thanks a lot for the examples 

Matthias