@Maximortal There are always multiple ways of doing things yes, but if I have a Delay Gate User Actor, and you have a Delay Gate User Actor, and we both use them often, then having a built-in way to do it without placing an actor and remaking connections would theoretically save us, and other people who often use some iteration of a Delay Gate, massive amounts of programming time.

That's some impressive thread necromancy. Also I too would find this useful.

Hello all,

I know it would be helpful for me, and might be helpful to others to have a way to manually select the data type for individual parameters and/or whole actors that have mutable inputs and outputs.  

What I'm thinking of is having the "Data Type" options you get for the User Input and User Output actors inside a User Actor or a Macro (Fig 1) inside the "Settings" tab for individual parameters (Fig 2)

Fig 1:

Fig 2:

Just like with the "Data Type" options from User Input and User Output actors inside a User Actor or a Macro, it would be ideal to have the mutable parameter "lock" to the specified data type.

Thoughts?

Best Wishes,

Woland

@dbini

This will work there isn't some surprising flash or temporary increase in the light levels. I can understand why you'd want to do something like this for an installation work, but  for a performance, I would personally stick to manual calibration.

That said, excellent solution. 😉

Best Wishes,
Mark

Maybe a useful tip...

For 'indicators'... particularly for building/debugging I often use 'Speak Text'. 
Audio cues letting me know whats happening while I watch the output ect, is very helpful.

i would also love to see this feature. Have been using a basic loop setup (recording the stage output with an end trigger which jumps the video number to the new recording) but this results in loss of quality so this feature would be perfect.

Thanks again mark. I've send your comment to Nicolas Bats (Dlight creator). He really thanks you and will change the osc adress for device. Best regards Célio.

Thanks for sharing @GertjanB 

@Skulpture AFAIK there is no solution that lets us make a macro and then have edge blending and stage keystoning. This needs to be done by Mark.

@[Stephane_Morisse](http://troikatronix.com/troikatronixforum/profile/7760/Stephane_Morisse)  the stage setup is the best way at the moment. It misses some vital features but is better than the actors. A new version is "on the way" no word on ETA.

If you make your desktop white when you force stage preview white light will fill the stage.

I would also appreciate non linear go triggers possibilities, even if the workaround described by kdobbe is perfectly workable. I would add, even if that's OT, that I would really like the addition of non linear fade curves between scenes. But typing that, I realize that in non-linear scenarios, fades can potentially be a nightmare to manage.

I'm pretty sure the nudge amount is per pixel.

Feel free to add a feature request (if you've not already) for the modifier key.

Yes, I have had issue before when working with multiple apps (using spout)

@Michel yes

@Fred

Yes up to now Isadora supports HAP only with QT playback, but I'm sure this will change in future. Best Michel

It seems that it comes when I enable the mapper on a stage, so the empty project needs to have a projector and mapper for every stage. I guess that is an OK workaround but I noticed some other events triggering the mapper reset my last view settings in the mapper window. I need to investigate more but it is something about user actors.

When I click show image frame on the stage setup window it does not show on the output only the preview.

Bug report filed

This is something I get into often too. I think, at least the editing of points should be restricted to the splice/layer that is actually marked/active.

These are all very fair and valid suggestions @Fred.

Thanks for taking the time to explain your ideas.

I could imagine another menu option for, 'development status' perhaps.

Where this information was supplied like Fred mentioned. Since bugs are tracked in a database, and labeled, it is possible.. we may need to adjust our current labels etc, to allow for cleaner queries..