@bonemap

selecting from a set of pre-defined colours would be fine (for me anyway), since i'd probably only use up to 4 different colours and and wouldn't need to customise these to the same extent as colours used within the control panel (which allows selecting from a colour picker)

rgds, Mr J

@woland Be sure and log pure UDP it has come up a lot and would be very useful - this feature could have been a user actor with straight UDP capabilties.

I know this discussion is ongoing, but I wanted to say that I've added this to our list of feature requests.

@chimerik said:

I can contribute something small to your notes

 Thanks, I've added the info you provided to my comment up-thread. <3

@fubbi

It is a real pain for all nice UI..

[STAFF NOTE: This feature request has been logged]

@gertjanb

I use Hyperdock for that purpose.You can define a shortcut to move a window from a screen to another or use the icon in the dock to see the open windows and drag the one you want on the proper screen.  https://apps.apple.com/de/app/...

best

Jean-François

thanks for this thoughtful solution! sounds like a good job to do on a rainy afternoon in autumn... :-)

doc

I have logged this by creating a feature request ticket.

Best wishes,

Woland

You could always look online for another FFGL plugin that is 64bit or a GLSL Shader that does a similar thing.

Please see Mark's answers here: 

https://community.troikatronix.com/topic/6652/step-by-step-instructions-convert-isf-shaders-to-isadora-glsl/2https://community.troikatronix.com/topic/6642/answered-convert-all-isf-command-won-t-run-on-catalinahttps://community.troikatronix.com/topic/6433/conversion-of-resolume-arena-xml-plugins-to-isadora/13

I have logged this as a feature request in the ticket system.

Best wishes,

Woland

@Woland I will have to dig into this later this weekend, this seems pretty neat.  thank you for sharing this. 

It would be great if the ip address inputs on actors and OSC address inputs had some kind of validation so that entries with spaces or new lines will not close the data entry and accept an improperly formatted data structure. I see this every time new comers use actors with these inputs, they enter the address and then press the return key, this makes a new line and an invalid address. This action is logical as every other form we have entered data into on a computer accepts the return or enter key as end of input. Inside Isadora pressing enter when you are entering values with a keyboard will close the active data entry for a parameter on every other type other than text I think it should have consistent behaviour and close the data entry for any type.

It could be good also to have an indicator on a string parameter input that contains a new line.

A logical pattern could be taken from excel, where command+enter will add a new line when editing a string inside a data entry box. This would be a good model for Isadora as adding new lines in parameters is very likely edge case behaviour.

I also think that these inputs could have some simple regex validation and not close with invalid structures, particularly as things like spaces can be very hard to see and new lines at the end are pretty much invisible.

I was recently teaching a workshop with students and 90% of them could not send OSC because they had pressed enter after entering the address, it took a while to troubleshoot as the entry looks  perfect, this could save others the same trouble.

@weston Me too, I have the same 'drag right' workflow. I guess the management of jump actors is the complication; I'd suggest if a scene was 'disabled' that it is invisible to the jump actors?

So the following is purely for fun in response to @mark 's post imagining how this would be done. I did follow up on this over the weekend and got something "working"

I heavily modified the project I mentioned earlier by manually rolling it over to the Tensorflow Lite c_api (a real pain!), then porting it to Windows, and feeding it the deeplabv3_257_mv_gpu.tflite model. To make it useful to Isadora, I dusted off / updated an openCV to Spout pipeline in c++ that I used a few years ago for some of my live projection masking programs, so now my prototype can receive an Isadora stage, run it on the model, and output the resulting mask to Spout again for Isadora to use with the Alpha Mask actor. 

My results:

Now obviously, this is insane to actually attempt for production purposes in its current form. I'm getting about 5fps (granted no GPU accelerated and I'm running in debug mode). I could slightly improve things by bouncing back the original Isadora stage on its own spout server, but this is just a proof of concept. In this state, it should be relatively easy to port to Mac/Syphon and add GPU acceleration on compatible systems for higher FPS and / or multiple instances for many performers. 

Again, just a fun weekend project but I found it very educational. 

@fred said:

It would be great if we had a unified login for troika tronix in general not just the forum and the license part but unified - probably a big undertaking, but it would be license aware, have all details and if we need to log a support ticket it would have all the serial number and info already, obviously it would then also have full support history for each user.

 Yeah, currently there's separate information for:

Support Portal AccountForum AccountPlugin Page AccountOnline License Portal Account (All Isadora 3 licenses except USB Key and Sassafras Keyserver licenses)Isadora 1/2 Standard Edition for Mac and Windows + Isadora 1/2/3 Sassafras Keyserver + Isadora 1/2/3 USB Key Licensing Database

Would be nice to have them all using the same thing, but they're all based in entirely different systems so it's a huge task to try to unify them. I'll log this as a feature request though, because it's something that really would be nice to have.

@fred

I have logged this feature request (and oh boy that's a lot of universes!)

@fred said:

What I meant is like the scene cross fades that exist now where we can set in and out times, except having separate times for audio, allowing for proper more complex scene transitions.

Yes, I understood that. Having separate control of audio and video in fades would make doing this in a complex scene much simpler, I just wanted to give an example of what's currently possible.

@fred said:

@mark have you ever encountered or thought about this? It does not seem there is a logical way around this, but it is a case by case issue.

 @artoo  @Kathmandale  @woland 

As Fred has pointed out, considering how one might make use of the alpha channel in the Effect Mixer is a bit of a strange thing to consider.

The biggest issue is this: the Effect Mixer assumes that the two video streams do not use alpha. It actually premultiplies the input colors, assuming that they are straight alpha, which works as expected as long as the alpha is full -- but this is actually a bit of a bug if the streams actually do have non-full alpha pixels.

Now, for a mode like "add max" it probably makes sense -- whichever alpha is greater "wins" and that's the one passed to the output.

For something like "add ovr" it's bit more weird to consider. What happens if you add two alphas and they "wrap around" to a lower value (e..g, 192 + 128 = 320 which ends up being 64 after the wrap around.)

For something like "and" which performs a binary and operation on the two values, I don't know what would happen to the alpha. Might be pretty bizarre, which is sort of the usefulness of the Effect Mixer anyway.

In any case, I have prepared a patch for you to consider. It recreates the 'addmax' and 'addovr' modes but with two different ways to control the alpha.

In Scenes 1 and 2, the GLSL shader offers the 'alpha 1 amt' and 'alpha 2 amt' inputs. These allow you to mix the amount of alpha from the first image and from the second image. By changing these inputs, you modulate the amount of alpha transferred from the two source images to the output.

In Scenes 3 and 4, the GLSL shader simply selects the maximum alpha value from the two images.

Note that for these examples work properly, the video input to the GLSL Shader actor must be unpremultiplied. I've used the Alpha Tool actor to do this.

See if this inspires any ideas for you.

Best Wishes,
Mark

effect-mixer-alpha.zip

@Woland thanks for the prompt reply

I'm talking about media bin picker in the control panel. 

The media bin pallet works well in most cases. In some cases, I think, it would be beneficial to have the ability both import and play media from one place in the control panel.