@dusx

You are fabulous! That works perfectly. Thanks so much!!

@jfg said:

A simple solution would perhaps be to reverse the order of the inputs: "in" as first and the *gate" as second.

If I recall correctly, actors have their inputs executed top to bottom, so I believe it needs to know whether the Gate is on or off before it accepts data.

@jfg said:

I agree with you but I think there is more important problems to solve before (e.g. the sound in the movie player).

Multi-channel audio routing in the Movie Player is a job that will take several weeks of programming and testing to complete. Possibly months. Removing the top input from the Gate actor to make a mutable thru actor would be like 20 minutes of programming and 20 minutes of testing, an hour of each max. They're not on the same level, so it makes no sense to compare them.

@woland I don’t think they should be removed I just want to be able to put a negative number in the min (or max). I get there there are a bunch of actor inputs that don’t accept/need negative numbers but there are also things that do, so many  

The wave generator not going negative is not really an issue (or crossing quadrants). It generates floating point values (these can be negative) so I just want to be able to make a negative min to shift the output. 

As I said  I don’t want them removed  and this would not change any functionality, but it would mean if you wanted to use a negative number as the min you could  it would be useful enough that it seems worth it and it doesn’t break anything or change use cases or isadoras approach  

it would be great to have some solid way of triggering events with frame timing. 

Let’s say I have a tap tempo that I want to use to flash a video on a screen (this was my actual setup when I encountered this). 

It feels like the events became really lose and the timing between flashes was quite uneven. I know that some calculations will not land on a frame but these seemed to be more off than just landing on the next frame. 

To be sure I was running with 300 cycles and mostly 24.9 fps and 50% load. 

I understand that a lot needs to happen but this patch was simple, it just used 3 large NDI screens. 

But what happens when I use the pulse generator to flash an image on an off at say 16hz with a frame rate of 25fps? Will the flash signals that are sent in between frames be executed later? Or will they be ignored?

this got me thinking that it would be great to have access to a frame edge notification pulse and sychronise events with this - so that they either get quantised or ignored (or maybe that’s what happens already. 

Fred

I was working with some large NDI screens and it felt like they were not running at the full framerate. My resource monitor in Isadora showed a healthy frame rate, but the refreshes and manipulation I was doing did not seem to be up to speed.

Is NDI resource use calculated in the resource monitor? Is the NDI data handed off in another thread? Is there a simple way to get the NDI frame fill rate?

Fred

I think the alignment grid could use some updating, firstly it would be great if it had some moving content, slow and steady so we can see if things are going ok and not frozen even if we don't feed content to it (this is especially great for NDI)

Second some more detail and colours and some clearer gridding as well as some more copies of the stage name - working with big multi projection stages especially with NDI if the screen is 10m long it is hard to see the middle and when I am at one end it would be great to confirm what is on display.

Especially now that NDI is integrated into many systems and it or other protocols will continue to get more use, it would be great to have some more options for stages that don't go to physical screens first and may need debugging or checking on a secondary system. 

@woland

At least 15 years izzy user, without knowing about THAT. This is hilarious! 😅

@reload2024

Don't know if this still is true, but I had the experience with some pro grade Panasonic projectors, that the geometric functions added some latency to the stream. But I guess, this was only true for more complex corrections with the optional warping board. Anyway, for latency sensitiv setups, this might be considdered / testet.

@vjw

My pleasure! Welcome back and happy patching <3

@dusx Oh geez I should have asked weeks ago! Thanks :)

@bonemap I believe only on MAC?

Cheers,

hugh

@anajcperfeito

This file should of mine should already have what you need in terms of randomizing media, plus has options for random or set hold times and bump transitions or crossfades (for picture, sound, and video files)

https://troikatronix.com/add-ons/random-media-random-duration/

@woland said:

/* a Displace Shader Actor proposed by Jacques Hoepffner after isadora Werkstatt 2017 updated by Mark Coniglio to move the pixels based on a displace amount and an angle instead of separate x/y inputs this version also calculates the actual greyscale brightness of the pixel using standard a conversion algorithm Note that this code will not produce the same results as the built-in Isadora Displace actor. */ // greyscale weights for RGB to gray conversion const vec3 sGrayScaleWeights = vec3(0.3086, 0.6094, 0.0820); // used to convert from degrees to radians const float sDegreesToRadians = 0.01745329252; // 2 texture inputs uniform sampler2D tex0; uniform sampler2D tex1; // ISADORA_FLOAT_PARAM(amount, amtt, 0.0, 100.0, 50.0, "Displace amount."); uniform float amount; // ISADORA_FLOAT_PARAM(angle, angl, 0.0, 360.0, 0.0, "Displace angle"); uniform float angle; void main(void) { // Convert angle to radians float radians = angle * sDegreesToRadians; // Calculate offset direction based on angle vec2 offset_direction = vec2(sin(radians), cos(radians)); // Sample the brightness from tex1 vec4 c1 = texture2D(tex1, gl_TexCoord[0].st); // Convert the sampled color to luminance float luminance = dot(c1.rgb, sGrayScaleWeights); // Calculate the displacement offset vec2 displacement = offset_direction * (luminance - 0.5) * (amount / 100.0); // Calculate the source coordinates in tex0 vec2 src_coord = gl_TexCoord[0].st + displacement; // Sample the color from tex0 at the displaced coordinates vec4 color = texture2D(tex0, src_coord); // Output the final color gl_FragColor = color; }

 Thanks for the code Impro

@donald said:

Is that something that you develop ? I couldn't find this "double chroma key" into the menu selections.

 Yes, it's a User Actor that I just made (specifically for you <3). This YouTube Tutorial on Isadora User Actors should be helpful.

@donald said:

Is that a way to select color with a pipette (like photoshop) on my stage window ? (previously the chroma key box was able to show me color/range selection, visually.)

I made you another User Actor 😁: stage-mouse-watcher-measure-color-2024-07-12-3.2.6.izz

@woland

Waiting for v.4. Thank you very much for your clarification, as always.

Best 

Javi

@elizachris

Hi there! 

Thank you so much for sharing your input :)

And welcome to the forum

@puppetisto

I have just confirmed that the corner-pinning and flipping in Stage Setup does transfer to Blackmagic Output, you just need to enable Blackmagic output for the Display itself instead of for the Stage, then do the flipping and corner-pinning on the Display, not the Stage.

@dillthekraut  AHA! That sounds very reasonable, the part about not shutting down the projectors while the computer is running. I should know better since I have 17 projectors running various interactive attractions at my LBE and I always tell staff the computer goes off first.  That might be a help there.  I'll check the link too and see if I can do static projector identifiers. I'm optimistic thanks!

@jjhp3 Same here ! Funny,. it had a SCSI port.... I remember well

@woland

Hi L - we generally don't invite duos or groups into the Hack, and it's not a space to work on an already existing project. it's more of a playground where everybody starts from zero and develops new ideas together.