Hello.

I am continuing work on a large patching network. I’m using JSON and user actors to route MIDI controller information and audio modulation to control effects parameters for four separate video "layers." The playback is handled in Resolume, while all the logic is managed in Isadora. Isadora controls Resolume using OSC.

Each video layer uses the same user actor, with an input for the layer number. The layer number is used to extract the appropriate parameter values from a JSON file, allowing me to tweak the entire system by editing the actors for a single layer.

Everything is progressing well, but I sometimes lose track of the parameters during performance while navigating through pages on my Streamdeck controllers. To address this, I'm builing a monitoring control panel that lets me see all the parameters at a glance. The control panel is for monitoring purposes only and doesn’t control parameters directly.

My current challenge is how to get the parameter values from each effect, layer by layer, into the control panel. Ideally, I’d like a way to assign the control numbers programmatically within the "video layers" user actor, so I can maintain the "single user actor" workflow and don’t have to create a large patch elsewhere to expose the effect parameter values and assign them to control numbers.

Here’s how the setup works:

Video Layer Effects Midi to OSC user actor X 4 (OSC is sent to Resolume for playback)

Video layer actor. Parameter values are extracted from a JSON in a global variable 
using parameter names and a .csv lookup table for JSON keys. Parameter values are 
modulated by audio and logic and then routed to the appropriate OSC address inside 
parameter user actors. Currently, I have exposed the parameter values on each effects 
parameter actor. This is where I would like to be able to assign the CTL#s 
programmatically using the layer# input and a lookup table or some math.

 Work in progress: control panel monitor for a single track

Is there a way of assigning CTL#s programmatically

I would grateful for any input.

Thanks, Justin

@sla247365

it might help if you were to give us a little more information. what system are you using? what version of Isadora? maybe attach your file so someone can have a look at it?

I am a new user and am trying to project 3 video files across 8 projectors. Everything is playing and routed correctly inside Isadora but every time I attempt to output to my projectors the application crashes. Anyone out there know what the issue could be? Help please and thanks in advance!

Hi all, thanks for the replies, unfortunately I can't update often as I only have access to the computer on show days, and have limited time to troubleshoot.

I did some more tests after updating drivers for the Declink to latest version, with no change on image quality on Isadora. I later checked on Blackmagic Media Express and quality was OK, as expected.

Source looks good on any software I use, problem only appears on Isadora while importing via Decklink, no matter the resolution, frame rate, interlaced or progressive scan, or device used as source. When capturing the same signal into Isadora via a HDMI to USB device (tested with an ATEM Mini Pro and a Roland V-02HD Mk2) image looks ok, unfortunately due to production requirements I'm forced to use the Decklink, so no luck there.

I'm at a loss here, only things I can think of is to update video drivers, which I will do next time I have access to the computer, and to enable/disable hardware acceleration; if that doesn't work I don't know what else to try.

Again, many thanks for the responses and suggestions.

@jonathan

This seems to have been resolved in Isadora version 4.0.2. Many thanks to Mark and the team for looking into this.

Jonathan.

blind mode?

(its in the Scenes menu at the top)

Hi,

I need help with passing HSBA color values through a Data Array actor. I am looking to use the Color picker control module to set RGB values for DMX send. The Color picker control module calibrates Hue/Saturation/Brightness. I have then control ID linked the Color picker to a Color Maker HSBA to feed - as color data type - into a Data Array. The Data Array then passes the color type to Color to RGBA actor, which routes to the RGB DMX channels.

However, when the Color picker is set to 0% saturation (white) it does not appear to be interpreted correctly when passed through the Data Array as a color data type. I want the efficiency of using the Color type through the Data Array as it reduces the number wires required to link up the overall system for DMX.

Best Wishes

Russell

@eva the Mac Studio should be able to handle this easily. This sounds like an issue with the machine or a driver. I would test this setup in another software (try obs) and another computer. There is more than enough power and bandwidth on this machine. 

As for the newer 360 camera it will say clearly on the specs page. 

@mark_m

thanks for your wonderful reply. I've been using Isadora since 2005 and have not used this option ever before!

It seems like something else is wrong though. The programme keeps on crashing. 

@karlakr8

Pause the engine, delete the scene, restart the engine

So, in Isadora, go to  menu / output / pause engine, or CTRL/CMD + Shift + P

A red border will appear around Isadora interface.

Now you can just click on the bad scene's name at the bottom of the interface to highlight it, and either right click and choose 'clear' or use the keyboard shortcut CTRL/CMD +B. That removes the bad scene.

Then CTRL/CMD + Shift + P again to resume the engine, and you can carry on.

Pausing the engines stops Isadora from processing anything, and it's just what you need in situations like this!

Hope this helps!

Mark (a different Mark)