Let's get some closure on this a year later.  I went back to test adding layers and since Windows has updated, graphics drivers have updated and of course Isadora has updated I wasn't getting the same numbers.  But relatively, using the RTX was still quite a bit higher than using the Intel GPU when looking at Isadora's load stat.  Although DusX was right, adding more layers and effects added less load on the RTX above its base.  On the other hand, the mystery was about Isadora's ability to run a show and keep up FPS in a given config so I'm still concentrating on that load meter.

So still unexpected swingy numbers.  That is, until I found one setting I'd somehow missed this whole time.  In the NVIDIA Control Panel there's a setting for power management, which I set it to prefer maximum performance and rebooted.

Suddenly the test show wouldn't break the 8% barrier on RTX, within a percentage point or two of what Intel is showing now.  The setting had different options on some other computers I looked at, but its equivalent was present and did give me lower and stable load.  So problem solved, missing one setting can make things weird.

Also, the show I was given to test is sort of a mess.  Different file formats, codecs, sizes and frame rates getting mixed sure didn't help things.

@video-architect here's a quick Izzy file with the appropriate actors. You just need to change the I.P. address of the ArtNet Send actor.

Hope this helps! 

Simon

dmx-lighting-artnet-send.izz

Hi Izzy community! 

I make use of the Screen Capture actor quite a bit, but recently I've noticed the actor crashes Isadora as soon as it is added to a Scene, or alternatively when a Scene containing the actor is entered. Is anybody else experiencing this issue? Any ideas?

Thank you Simon

@tatrapikao said:

isadora 3

 Isadora has not been updated.
All updates since the release of Isadora 4 are in subsequent Isadora 4 releases.

I would love it for there to be a custom shapes actor that could behave a little like the Composite Mapper in Izzy Map. It would be great to have an actor that could make a custom shape by double clicking on it (like how we get to Izzy Map) to allow you to use the methods of the Composite map to create unique shapes for masks and the like. It would be amazing to have the ability to soften the edges of the shape inside this custom mapper as well.

I often do this via a virtual stage mapping a Background Colour with the Composite Mapper in a projector going to a virtual stage then Getting the Stage Image and sending this custom shape often to the Alpha Mask Actor or using it as a piece of content. It would be lovely to have an actor that does this alone, without having to use a virtual stage.

I hope that is clear. Thanks so much.

Cheers,

Cam.

@gpeddino

It depends on what your text file looks like and whether you can easily reformat it. If your text looks like this:

You can use the Data array actor. By changing the Recall value, you can call up the corresponding line from your text file. 

For the same text file you can also use the "Read Text from File" actor. Set auto read to on and read mode to line. You recall the line with the start input (take care 0 is the first line)

If your text has characters before and/or after the timecode ( - 00:00:01:08,)
 you can use the Text chopper actor. 

It is IMPORTANT that the text file is in the same folder as the Izzy file.

Best regards, 

Jean-François 

@citizenjoe nope. Playback still stops after a few hundred frames backwards..

@mmharvey

In the program you can also go to Help > Isadora Manual...

The section Actor Reference is what you're looking for

@juriaan

Thanks. Just found this topic. I assume it's all still relevant. Thanks this is just what I need as I'm setting up the exact same hardware.

@Eva

another possibility on Mac is syphon Recorder. I use it always, it is easier to configure as OBS and it works very well:

https://syphon.info/recorder.html

Best regards, 

Jean-François

@drpjm

Did you close and re-open Isadora? It won't remap the python environment until that is done. 
I assume you have watched these tutorials: Using the Pythoner Actor – Do More in Isadora with Python - YouTube

NOTE: Python is not initialized in Isadora until a Pythoner actor is added to the project. You can update the 'environment activation file' and restart Isadora, and the Python Virtual Environment setting under the Help menu will appear GRAYED OUT & (Awaiting Activation) until the Pythoner actor is added to the project. 

@ubik Thanks for sharing...loved the Fluid UV Distort !

Best,

Maxi-RIL

@woland Thanks for the Suggestion. Still - having this feature inside Stage Settings would enable the User to Safe the Setting with the Show. That would simplify Setup and reduce room for error, espacially in enviroments where we run multiple Shows from the same Computer. Cheers

@eva said:

Will it help to add a scaler or should I change the videos outside of Isadora?

 Re-exporting your media at a lower resolution then using that lower-res content in Isadora is less load-intensive for Isadora than scaling the content in real time inside Isadora.

I just posted an update to my DX – Cube2LUT – ColorGrading user actors (demo file).
It now includes a user actor that allows you to CREATE a 64^ CUBE LUT via 8 color inputs.
These basically allow you to remap colors within the grade to a new range

Please give it a try (requires a Pythoner virtual environment is setup, and numpy and cv2 are installed)
I see this has had a few hundred downloads, but I haven't received any feedback. I'm happy to continue to make updates to these tools if they are proving useful to you.

@wotrombone said:

Are there other ways to fade into the next scene with  a jump actor that use those times? is there a way to automatically grab those times?

You could also just use one of the different Jump actors (for example Jump By Name) and set your fade times in the Jump actor. I usually don't use the Scene fade times and use jump actors instead. This might be a lot of work depending on whether you've already got a bunch of cues programmed. 

Generally, I use a Background actor renamed to "#CUES" and put stuff like the Jump Macro you've built in there. Then I put that Background in the same place in every Scene (generally top right) so that I know where it is in any given Scene and, since the Background actor has been renamed to "#CUES", I can use the hashtag list to jump to it easily if I need to find and edit it.

I tend to make a template Scene with the stuff I need most often and just copy-paste that Scene when I need to create a new Scene, then modify the copy. It'll already have whatever Jump actor I'm using with a default timing of 3 seconds in it, so that I don't need to manually set that every time and only need to change that number if I want a different fade time for a specific Scene.

@woland said:

You’re already in the beta program so you should have access to the new beta and new audio actors. Have you tried working with any of those?

 I have not tried them, but will check it out. I was interested in VCV for things like envelopes with attack, sustain, release, sequencers,various modulators etc. Working with VCV when doing audio reactive work offers up all kinds of weirdo ways of analyzing and using audio-as-control. It also puts the "brain" in one spot and allows me to use the OSC outputs in Isadora, Touch, Processing etc. 

The goal of this set of actors it to help developers collect and package complex project files with a range of linked files.
So, this User actor doesn't collect your media. Nothing listed in the media bins will be collected, doing that can be done via: TROIKATRONIX : ISADORA - DX – PY – Collect_Media
This actor, searches the binary of your Isadora file to find linked files that are harder to see/find. For example the data file for the data array actor will be listed.
Current file types it will find: ".izz", ".txt", ".py", ".srt", ".oni", ".json", ".csv", ".xml", ".js" [I just fixed a bufg with .js files, so that isn't in the user actor yet.]
If you link other file types let me know. Right now this looks inside javascript for read() and include() calls, and will 'find' those files if they are not dynamically created [eg, this fails : read(basePath + "file.txt") ]. It does NOT attempt to find linked files within Pythoner code. The options Python offers here is far to broad.
Currently the JSON and Report, only provide the Scene name that each file is used/located in. I would like to extend this later with a breadcrumb path to help navigate into user actors if the file path is internal, as well as, adding the Q# alongside the Scene Name. 

@jfg said:

Why do you have to copy the addresses you have obtained back into the inbox?

 This was simply to make it clear what is being done. I am happy to change this later. Really there are 2 primary actors inside. By making you copy the path, you have more control over running each on 1, another file (doesn't need to be the active Isadora file), 2 re-running either function independently.. but I am not married to the approach.

@bootzilla

No problem :)

Hi Everyone, 

If you live in Quebec City consider joining us (Myself and Hugh Conacher) for our shows at Mois Multi - Festival international d’arts multidisciplinaires et électroniques!

February 12 and 13th:  https://moismulti.org/programm...

Here is the trailer:

We will be in Montreal afterwards from Feb 14th to 21st if there are any Isadora related events of performance with tech folks who would like to connect - reach out!

Best, 

Frea