@Skulpture Any thoughts?

Hello

I have made a lot of real time parameters to a glsl shader using sound level but i don't find the way to create a link between sound and video input shader.

Skulpture have made this link on you tube

but i don't understand which kind of channel input he had use

thanks a lot

@kolmon3853

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

@kolmon3853

You can get the most up-to-date information about any actor by right-clicking it and choosing the top option ("Show Actor Help in Browser") from the resulting menu. 

@jfg

Thank you, Jean-François.

This is extremely helpful. I have been using the manual mainly, thinking that it would be more detailed, but the statement you point to is not in the manual. I appreciate you pointing out how this works. I guess it is perhaps implied in the manual but not explicit the way this actor help statement is.

It looks like I should use Selector instead.

It's super wonderful that you took the time to help me. 

Best,

Craig

@kolmon3853

I think the explanation and solution can be found in the actor help:

Best regards, 

Jean-François 

Greetings folks.

I'm having an odd problem using the Table actor. I have used this many times in the past, and also in the project I'm working on right now, which is an interactive exhibition context. The exhibition control system has been working fine, but I have been doing a major upgrade using a lot of background broadcasters and listeners. It seems to me like all of that is working, except this Table actor thing causes an odd result that won't work for the installation.

I'm using Novation touchpads to trigger various sound and visual material, and am blocking out the 64-button touchpad into four equal blocks. I test the input MIDI trigger value, and depending on the area of the pad I select an adjusted number to pass along to the Movie Player.

The input evaluation is working properly, and the correct number appears in the value slots as expected. The problem is that the number that flows through to the "val out" is incorrect. It doesn't match the input number as it comes in. When I press a button on the pad the number changes, but a different number appears in the "val out" slot. If I press the same button again, or if I even press a different button, the correct number that I pressed originally then appears in the "val out" slot. 

I'm trying so many ways to work around this to get it working properly, and I don't know what to try anymore. 

There is a lot going on in the background before getting to the Table, but since the Table is receiving the correct information and is functioning properly on the input side, I don't know why anything else would be needed to figure out why it's working this way.

What is very odd also is that sometimes when I click directly into the scene it sometimes functions properly, but not always. I haven't figured out what is different when it works properly. But when I run the system so it automatically moves to a new scene it never works properly. 

I don't understand why it isn't passing the selected input number to the "val out" number.

I'm running Isadora 3.2.6 on a Mac OS Catalina 10.15.7. This is the most recent MacOS I can run and still have my Matrox and Audio Interface supported, so updating the OS is not a good option.

The attached screen shot illustrates what I see as I test the system.

Does anybody have any thoughts about this issue?

I hope there is a fix to this. Maybe I'm doing something wrong, but if so, I don't see what it would be. My other uses of the Table actor are working exactly as expected. Maybe there is something about the Broadcaster and Listener actors that are affecting the process, but if so, I still don't know why the correct number is received but not passed through to the output.

Thanks so much for any insights...

Best,

Craigscreen-shot-2025-09-30-at-10.09.08-am.png

@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.

Hi All,

Just looking into an interesting one on Izz4.1.3, installed on a M1 Max MacBook Pro - a show machine I've been running for years now.

Screen Capture in macOS Sequoia - works, tick.

Screen Capture after updating to macOS Tahoe - crashes the moment the node is placed down.

I've done a full reinstall of Izz4.1.3.

I've unchecked and rechecked all options in the OS for Screen Recording permissions.

The issue does not occur in Izz3.1.7b31 on Tahoe (which I also have installed for older show files), Screen Capture just works as expected.

Could someone have a look if you're also on 4.1.3 and macOS Tahoe and let me know if the node does or doesn't work for you? (That'll help inform my next steps!)

Cheers,

James

I’m adding some live camera feed scenes to a show, and decided to use a Sony A7s for it - since I already own one.

Got a Blackmagic UltraStudio Recorder 3G and it seems to work very well. 
Also, purchased a dummy battery not to rely on these tiny batteries that end up empty in ZERO time. 

In the context of a show, though, where I’d setup and check all connections, and then be back to it after a longer break (during which I have no access to my setup), right for show start, is there anything I should be aware of? Like : things that could go wrong? 

Camera settings that make it shut down after some time? Standby? Overheating??? 

What’s your experience?

Thanks!!