@pingdesigns 
If the sound file is recorded, you can set up Isadora to sequence the effects. As the sound file starts with a sudden noise (is this the 'clash' you are trying to sync to?) - you could use a Sound Watcher to listen for the start of the track and trigger a series of Envelope Generators so that the End Trigger outputs send your video flash cues. I've done this before when working with prerecorded soundtrack.
It's possible to do this using Trigger Delays, but I find that Envelopes are more obvious - you get to 'see' the pauses between triggers.
The way you chain them together can get a bit complicated, but there are many configurations: You could trigger all of the envelopes at the beginning of the track, each one a little longer than the previous one - this would help you to fine-tune the timing of each end trigger.
If it's being improvised, then you would need another method. How is the composer playing the sounds? is there a MIDI controller involved? you can network machines together and grab MIDI signals from their machine to trigger your video effects.
If it's recorded, can you play the sound file from Isadora? Then you will have timecode to link your effects to using Comparators.

@woland Maybe, if this feature is implemented one day (I also tend to do monster patches...) maybe one of its output is to generate a multi column list where in each line there is one entry (control number on column a, control name on column b, connected actor name on column c connected input on column d and active link status on column e). I think that the status is important because actors in the patching widows don't lose the control ID link number attached to their inputs if the control is deleted. Also it would be nice to have a visual feedback on that (control id number background in control window and actors in patching windows that are not connected could be red if not connected and green if actively assigned). Just a thought

@rosa

try the Matte actors. they enable you to shift a video image around without needing to zoom in.

@woland Thanks! I'll check it out. Really helpful.

@reload2024 said:

posterizer effect

On macOS there are the QC Posterize and CI Color Posterize actors, but they're not ours, we just pull them in from Apple's architecture and they're ancient and inefficient so I usually recommend not using any of the CI or QC actors. If you do go down that route you'll want to use the Video Converter actors (GPU to CI, GPU to QC, CI to GPU, and QC to GPU) to make sure you're using GPU video wherever possible.

Wow! Really appreciate this community's knowledge. Thank you very much

@jfg you're an absolute hero,

I knew that I'd done something like this before, I just couldn't get my brain to work.

Thanks.

@stephan-bergmann said:

Will try to log in to download (Safari is flipping around in this moment with username, ...)

 dx-8211-dmx-universe-8211-enttec-compatible-1.zip

I attached the file from the add-ons. Perhaps you can download this one?

@tingkumajique said:

also wondering why the text output from Isadora looks a little jaggy and not clean even when the resolution is set to 1080P

 To add to Marks thoughts, do remember that in the screen captures shown the Preview Windows are scaled down from the target size. Text will look cleanest when rendered to the full stage output.

Hi everyone! I'm trying out my new MacBook Pro M3 Pro Sonoma

Playing with the speed of the movie player in interactive mode I find that it doesn't play an mp3 audio file smoothly compared to my old MacBook Pro 2015 which has the possibility of using the Quick Time playback engine.
Is there any way to improve this? any settings? maybe a specific codec?
Thanks a lot
Maxi

@joshuawg

These systems shouldn't have changed between Isadora 3 and Isadora 4.

The first thing I would look at is drive health. 

Please open a support ticket and I can see if I can reproduce the issue with your help.

@gertjanb said:

Are there ways to know what might brake when upgrading?

 I think the release notes are probably the best documentation of any breaking changes. In the case of Isadora 2 to 3, we had the shift to 64bit which killed some 32bit fx (thinking about FFGL 32bit here), these where really beyond our control. We don't get rid of things as we add updated/replacement features, instead we take the approach of making things 'classic' and phasing them out so that projects have an easier update path. 

Some search features would be helpful. I would love to get a report for any given actor that provides the breadcrumb path to any instance of an actor. These are things we have talked about and I hope we can get into the software.

Did you ever figure this out @Aolis ? I am looking for something similar! 

@dusx Great thanks Ryan !

@dillthekraut

Thank you, that all makes sense.
Making progress :-)

@Fred @Juriaan Thanks for your suggestions. I'm finding a way through...

Will post results and workings when I've got the final thing going.

Much appreciated everyone.

Hi @woland

Any Update on this topic? If not, is there a good working workaround without big latency? 

I bought a BirdDog Play yesterday an like to do a small show on Saturday with it - i don't like to invest money into mitti ;-)

regards, Tom

@kazapp

Hi,

Eight years is a long time - so some incompatibility would be expected. I assume that some of the video codecs of your older files are no longer supported - this article might assist.

Fading between scenes can be problematic with some video codecs and with 3D Actors.

Best Wishes,

Russell

@jingyi3027

there are many ways to do this. a simple way to adapt your current patch would be to use Trigger Value actors instead of your Toggle/Envelope Generator.

Connect the True output of your Comparator to a Trigger Value of 100 - connected to the Intensity of the Projector. Add a Trigger Value of zero connected in the same way to the False output.

Remember to Intialize the Intensity at zero, so that when you enter the scene, the visual effect is not shown until the Comparator recognises a value of 1 or higher.

I think the problem you are experiencing with the Envelope being triggered at the wrong time is because you are using the Toggle actor in an unconventional way.

@bonemap thats great thanks Russell, will do that. Much appreciated! 🙏