@dcmp

I would be happy to put something together for you. Please just try to describe what You are trying to accomplish clearly so I can put this together in a useful way for you.
Is there a specific part of the video you want to control the lights? What is the light effect you are trying to get?

@wedkim

(Again, just posting this for the benefit of others who may run across this thread in the future)

I got in touch with the lovely folks at Rokoko, and they've now added a tutorial to their website on how to connect Rokoko Studio Live with Isadora: https://support.rokoko.com/hc/en-us/articles/42904491647889-Livestream-to-Isadora

@wedkim

(Again, just posting this for the benefit of others who may run across this thread in the future)

I got in touch with the lovely folks at Rokoko, and they've now added a tutorial to their website on how to connect Rokoko Studio Live with Isadora: https://support.rokoko.com/hc/en-us/articles/42904491647889-Livestream-to-Isadora

TextEdit has the possibility to set the background to dark, then set the text color to white, and you can also speak the text if you want.

I have added a "contrast adjust" actor because the TextEditor background appears not totally black in Isadora. 

if you can work with a second monitor for TextEditor it is very confortable

TexEdit:

Best regards, 

Jean-François 

@eva

If none of the information in my previous comment is of any use to you in terms of diagnosing what issue you're having, it would be very helpful if you could attach a screenshot of what you see in the video preview when you hover your cursor over each of the links in these actors like this:

This way we can see what is happening at what step and actually deduce what might be going wrong. With the current screenshots we can only tell what two different final results look like but we don't know what your content looks like originally nor at any of the steps before the final output.

Hi Wholand, 

Ah thanks, I will try that:)
Have a great dayEva

There is also another problem with the IP address in Isadora preferences. If you use a VPN, you get the VPN Tunnel address ( e.g. 10.2.0.2) but not the real IP address you can see in system preferences (192.168......or something like that). For Touch OSC and co you need the 192. 168..... address. It would be fine if it was possible to see both. (By the way, it is the same problem with the Apple Shortcuts app. It shows also only the VPN and the external address but not the real address in the local network. Not really a problem; then you can find the correct address in the system preferences, but it would be nicer to have it in Isadora.

Best regards, 

Jean-François 

Just to add.

I feel the post is just talking about the SDK, the development tools. Not the end user, or the finished product. Just my interpretation anyway. 

I will have a tool to share shortly that parses your IZZ files and returns a report of all the filepaths found. 

It is VERY experimental but provides very useful information already. 

It is broken into three parts: 

-1 Collect data from IZZ file (find all linked files) 

-2 Make Local copies of all link files. 

-3 Update a copy of your IZZ binary with new local filepaths 

 The JSON report from step 1 is for all Scenes in your project, and includes things like read/include() calls inside any javascript you have.  

The report provides a few settings you can adjust before running step two.

    {       "source_path": "C:\\pyFile2.py",       "target_name": "pyFile2.py",       "action": "localize",       "localized_relpath": "pyFile2.py",       "occurrences": 2,       "exists": false,       "scenes_found": [         "scene1",         "scene3"       ]     }, "notes": { "summary": "Structural scene detection + Deterministic Value Header extraction (Index 0).", "action_codes": { "localize": "Standard project dependency. Should be moved/collected for portability.", "ignore": "eg: Internal Isadora/Pythoner resource. Should remain in place.", "[custom-path]": "User-defined destination path (e.g. '/data'). Localizes the file into this subfolder relative to the project root." }, "exists_codes": { "true": "Absolute path found on this system.", "false": "Absolute path NOT found on this system.", "null": "Relative path. Existence depends on project root location." } }

The above JSON outlines what is collected for each filepath. In this case, the filepath was found in two scenes, and so both are listed for reference. The filepath entry is unique so it is listed once. 

The Notes provide details on what options are available. Mostly the action_code is what you might change. This can allow you to create a custom path. Custom Paths MUST be equal or shorter than the source_path if you want to use step three.  

Part 1 and 2 will be available for testing soon. 

Part 3 is more delicate, and will need more testing before I can release anything.

Thanks I’ll take a look.

@bonemap

We also had an existing feature request to this so I've now added my post here to that. 

@bonemap 

I've added this to the existing feature request for this.

@bonemap

The login to the Add-Ons Page has been fixed, so you could upload this there too if you'd like. :)

@bonemap said:

number input fields that resolve math

Added this to the corresponding, existing feature request :)

(This would save me so much time.)

@dbengali Hello! I couldn't replicate the issue with an Apple Pro Res 422 file nor a quick AVC codec saved via QuickTime Pro. I'm running on a MacBook Pro M2 / Tahoe 26.1 / Isadora 4.1.3

Best wishes Simon

Hi,
I usually do the chases using a sequence of [wave generator] shifting the phase depending on the amount of fixtures in the chase. The limit-scale allows me to set the max-min intensities of the chase.

I also use a Javascript actor to automatically assign the phases: This is actually not really needed since it's generally a one time job and you can do it by hand.

I hope this was clear. Don't hesitate to ask if I was not clear enough.

Thanks, I've now logged this.

@kosmopilot

As far as I know, you'd only potentially have trouble if you intend to use the Screen Capture actor with Isadora 4 on Tahoe. We've not had any other reports of issues with Isadora 4 and Tahoe as far as I know. 

That being said, technically macOS Tahoe is not currently a supported operating system for use with Isadora 4. (This doesn't mean that Isadora won't work at all on Tahoe, it just means that we are still in the process of discovering what we need to update in order to unbreak the things that Apple broke for us in Tahoe.)

@dusx

Thanks!

@dbini

from help file: