I can see lots of mixed-resolution video in your media bin. 

Some are 4k, and some are not. Some are 30fps, and some seem 25fps, so Isadoara will be working mega hard to process those Videos. 

I would suggest making them all the same resolution (if possible) and converting them all to a more usable format such as HAP.

@eva

My bet is that it has to do with the Video Delay actors you have after your two 4k videos that have the 'frames' inputs set to '21' and '30' respectively.

In the righthand side of this screenshot is some relevant info from the help text of the Video Delay actor's 'frames' input:

Try deleting the Video Delay actors and see if the LOAD drops.

Also what computer are you running this on?

@eva

@woland ok, now I try again, with another one, its also really loaded it seems but I am actually surprised.
I have put the scene in Q1This is the file: Esther

All the best

Eva

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

@wotrombone said:

he has pivoted to wanting the cue numbers to, if not match, at least be in the same range as the LX q numbers.

Switch the Cue Numbering to "Manual"

Select one or more Scenes in the Scene List, right-click, then select the bottom option ("Renumber Cues...")

Choose your new Cue Numbers

Now you can have point cues (e.g. 1, 2.5, 3) and cues that can be non-sequential (e.g. 4, 8, 15, 23, 42)

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

Hi Everyone.

I am working on a project where the Designer wants to trigger Isadora from the light baord. he didn't want to go a MSC route, or an OSC like equivalent. 

So every cue he wants to go to the next cue he is executing a macro and then i have an OSC channel set to that macro and so it triggers when an lx cue executes macro 17.

I used a Current Scene Number actor and then I used a calculator to add 1 to that number into a text formatter to take the number and make it text and then used the Jump to Cue actor to go to the next Scene. This broke during Tech today, becasue even though in pre-pro we talked about not having point cues and just using the Scene index, he has pivoted to wanting the cue numbers to, if not match, at least be in the same range as the LX q numbers.

I did it with that actor becasue I wanted him to be able to use the scene fade times in the bottom left of the window to control fade times, and not have to put the times into the actor, as that is the workflow he is used to. The Jump to Cue is the only Jump actor that I can see that allows you to NOT override the scene fade times. 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?

I think the answer that I want is to recieve the OSC trigger, Send Raw MIDI to Isadora's own Virtual MIDI port, and edit go triggers to use that MIDI message to go to the next scene. Unfortunately, I have a Windows machine so I don't have the built in virtual MIDI ports.

Maybe Ill go in and try to get that set up for him tomorrow, but he has asked for me to just make a user actor to send to him to drop in to replace the one that i provided him that cant handle point q# s or non sequential numbers. For right now he is just going to have to type in the fade times he wants using the basic jump actor (in a user actor)

My Question really is though about using the scene fade times, I just never know how much context to give.

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.

@dusx

I don't know what the result should look like. I have 35 video files, 20 audio files and 3 images in the project. I use 3 video files and 3 audio files in the scene. The result looks like this:

Why do you have to copy the addresses you have obtained back into the inbox? It would be no problem to forward them in the Actor.

Do you need the .json and .txt files?

Best regards, 

Jean-François 

HERE is BETA 0.1

The above linked User Actor provides part one and two of a three part project. 

parts:

1. Scanner - Identifies all file dependencies in an .izz file
2. Localizer - Copies identified files to a local project folder
3. NOT AVAILABLE YET Remapper - Updates the .izz file to point to localized files

🚀 Quick Start 
(assuming we are going to work on the current file)

• add the User actor to your scene, & save
• Click 'update rootpath) to get the project root path from the output of the actor.
• Enter this project root path in the like named input
• Enter the isadora filename (must be exact. EG: test-find-txt-path_v4b.izz)
• Click the run filepath scanner' input
  if the filepath is wrong you will get details in the output status. 
  Otherwise you should see the 'json path' output is now populated and 'status' is success
• *** You now have a JSON file (at the 'json path') that outlines all linked files that are found and default settings for localizing.
  The end of the JSON files provides some details about possible settings, and advanced user can make changes in the JSON if needed.
  Generally the defaults are a good starting point, and it is safe to re-run these processes. 
• Enter the 'json path' from the output to the 'json path' input.
• Click the 'run filepath localizer' input.
• *** The status output will now provide details about: Copied, Skipped, Failed
  You also get a report (named, YourFileName_localization_report.txt)
  Files that have be moved, will be located alongside your Isadora project file, unless you customized the JSON file before running localizer.

I am hoping to get feedback on these features, before asking a few brave souls to help me test Part 3 of this project (seems to work well, but needs more hands on board for testing).