@eamon
This is the method I have used to create chapters in a showreel. It takes a little time to set up the correct values for the Trigger Value actors, but is easy to use once it is set up. 
You can change your Movie Player to use timecode, if this is easier than percentages.

@videosmith

I posted about this in a couple relevant places on Discord.

Have a lovely workshop :)

@citizenjoe

@eMTv made a neat feather crop User Actor: https://community.troikatronix.com/topic/7848/feather-crop?_=1760522362139

There's also this thread with some solutions for angled cropping: https://community.troikatronix.com/topic/8776/answered-diagonal-crop?_=1760535965092

@woland @dbini these Pipo interfaces look great! Unfortunately I'm gonna have to wait until January until the next batch is available. Are these available anywhere else?

Best wishes,

Simon

@citizenjoe said:

this worked

 Great!
not exactly what I imagined, I though you might animate the 'bottom width' value. Interesting you need to toggle the visible (mental note taken).

@charlotte_e

You could adapt this template of mine and put an alpha mask inline: https://community.troikatronix.com/topic/5495/global-projection-mapping-simple-show-template

@reload2024 Hello! Pause Engine from Isadora’s menu bar is an alternative option to Blind Mode. Hope that helps!

We didn't make any changes to this as far as I am aware that would affect the ability to copy and paste between two patches that are open in the same version of Isadora. The closest thing I can find to a change is from the release notes of Isadora 4.0.0 that says:

"NEW: Run Multiple Instances of Isadora on Windows
You can now run multiple instances of Isadora on Windows! (This was already possible on macOS.)"

@gaspar said:

On Isadora 3 I could open two instances and copy parts of older patches into my new ones, or even copy whole scenes. At least in my case I'm unable to do so on Isadora 4. I'm running Isadora on two different systems: One on windows 10 and the other on windows 11. None of them allow copying between patches.

Try opening two files within the same instance.

Also, to copy between two instances of Isadora, they'd have to be the same version of Isadora. (So if one instance is Isadora 4.0.0 and one instance is 4.1.3 that won't work, but both being Isadora 4.0.0 or both being 4.1.3 would work.)

@aikia

I am not familiar with the Sony, but I use the Canon equivalent as a live camera in my work.

The little HDMI connections are a pain! I have a cheap Smallrig Cage on my camera. Attached to the cage are a cable clamp and a Smallrig converter which converts the microHDMI on my Canon into full size HDMI. The cable clamp makes sure the microHDMI cable doesn't get pulled out, and also protects the fragile socket. So I don't need to worry about the cable loosening or getting inadvertently pulled out, and I can attach a full size HDMI cable to the camera.


Like @bonemap I use a DJI Ronin Gimbal which allows me to fine tune the position of the camera remotely using the phone app. There has been lots of work done on other ways of remotely controlling the gimbal, using wired Ethernet connections or a Gamepad. I often mount my cameras above the stage, so it's great to be able to have this control and to be able to finesse camera positions from down on the ground, not up a ladder :-)

@dusx said:

<p>@undergroult said:</p> <blockquote>i don't understand which kind of channel input he had use</blockquote> <p> I am pretty sure, what he would have done is used a Sound Frequency Bands or Sound Frequency Watcher actor/s. In live capture settings (input/live capture settings) in Isadora you need to select a Sound Input device, ensure 'Sound Frequency Analysis' is checked, and Start Live Capture. That will provide the audio source to the Sound Frequency Bands or Sound Frequency Watcher actor/s in your scene. These actors allow you to convert audio frequency values into numeric outputs in Isadora. These numeric outputs can then be fed to your GLSL shader actor to control inputs, making the GLSL audio reactive.</p>

 Something like that probably.... I think I managed to publish an input in the code. This was 5 years ago... can't fully remember.

@kolmon3853

You may also want to take a look at the Data Array actor

@james-russell

I have logged this as an issue but as a best practice I highly suggest not updating to the newest version of macOS for at least a year after release. Personally I only ever update the OS on my machines when absolutely necessary, especially show computers. If a computer I have is doing everything I need it to do, I see no reason to introduce risk by changing the OS. To me it's comparable to going to a mechanic right before taking a big road trip and asking them to randomly swap out some parts of the engine. Yes, in theory the new parts are supposed to work the same or better, but the new parts could also be faulty or get installed improperly. If I instead stick with the old parts I know it will continue to work the way it has before. A more relevant example is that, during the run of a show I would never arbitrarily swap out what computer I'm using or change out all the signal cables, extenders, or projectors. Even if I were swapping to identical or theoretically better gear, it would be introducing risk and new potential points of failure to a system that I knew was already working before.

Apple rushes these new versions of macOS out the door every year and they don't care what they break or for whom, so early adopters basically just end up being lab rats as they're the first ones to run into any issues Apple may have introduced.

In general software and hardware developers need a few months to catch up and discover what changes Apple has made that cause problems for users of their products and in what ways. Even huge companies like Adobe and Ableton have this issue every year when Apple releases a new version of macOS.

@marclark

3.2.0.1  seems to solve the problem.

@bonemap
Hi Russell - that looks amazing! I will look around and see if there's anywhere to hire Mac Minis. It's another option. :)

@barrowcivic

Here's an article on how to use the Set and Get Global Values actors: https://support.troikatronix.com/support/solutions/articles/13000014936-using-the-global-value-actors

Additionally, if you take a look at the Isadora 4 Manual, you'll find:

The Get Global Values actor on pages 501-502The Set Global Values actor on pages 719-720

As you're new to Isadora, I'd also recommend checking out our Isadora Mini-Tutorials playlist on the TroikaTronix YouTube Channel. There you can learn some helpful basic tips, but also tricks and best practices that that might take you a while to figure out otherwise.

@riodio

There is a known issue where recent AMD graphics drivers are causing this error/message.
Users have had success installing older driver versions. This seems to be an issue on a select range of machines, we are looking for a solution we can implement for the next Isadora release.

@miketutaj said:

It just looked different than previous versions so I wasn't sure if was working correctly.

I mean, it looks different because there's a drawing bug so technically it's not working properly. It is just an indicator for data traffic though, so even if it wasn't flashing when active, all the data traffic would still be working, you'd just have to look elsewhere in the program to see that.

@eight

A possible workaround:

It only works if you select the scene in the Scene Select control, rather than in the Scene List at the bottom of the window. The transition time of the scene sending the OSC command must be set to at least 0.01 seconds.

This may not be exactly what you are looking for, but I hope it helps!

Best regards, 

Jean-François 

@gunther said:

n input of 1 second results in a sound loop of 4 seconds

 FUN