@mark

hey thanks Mark. I think you are right. Need to move over to Black Hole. I get stuck with things because change is hard work. The story of my life (and my country)...

Also - I may have had conflicting Jump Actors inside the project. I'm trying to learn how to activate scenes from behind a single control scene, and I got lost in there. Black Hole will probably sort a few other issues too. I'll let you know here if the scene glitches continue.

@soulsense

Welcome to Isadora and the forum. I'm Mark Coniglio, the creator of Isadora.

I think maybe you didn't change the 'inputs' and 'outputs' on the actor itself.

The comments allow you to define custom names for the inputs, but they do not actually add or remove inputs.

Instead, you need to do that with the 'inputs' and 'outputs' inputs.

Let us know if that was in fact the problem.

Best Wishes,
Mark

@dusx @vidasonik

This thread went pretty far afield from the actual problem, with many of the exchanges focused on OpenNI Tracker when the actual issue had nothing to do with that plugin. So, for the benefit of any reading this in the future, I have removed all but the first and last posts so that the initial problem statement and the solution remains.

I've also changed the generic subject line "ARM 3.2 Crashes" to "Crashes Because of Value Delay Line Actor Using Strings" so that people will immediately know what the source of the problem was.

Best Wishes,
Mark

Thanks, I do understand how it works, what I didn't understand is why it changes on it's own.

I guess I'll rewrite the file to keep it from changing.

@JonesSeitz 

I recommend opening Stage Setup, and setting each o your Stages to use a Display that is not attached... so for instance, assign Displays 16, 15 etc...
Then ensure the resolutions are what they were before. (they default to 1920x1080)
Open stages, and position the preview windows that open.

Why? This removes any bottleneck that might exist in the output hardware. I don't know the inner configuration of your Mac, but if it works similarly to my PC it is possible one of the USB-C outputs runs thru an onboard GPU, while the others run thru a dedicated GPU. If that is the case, Isadora will have to transfer video textures between the GPU units, which is a slow process and will bring down the framerate.

If your project runs at the correct FPS when the displays are routed to non-existing displays, you can then connect each one at a time (the Display Port will be fine I am sure) to determine which port is causing you trouble.

as @Woland noted, the Video Delay will eat up Video ram, so you should also check that you have not used all your video ram.. if you have it will start using swap ram for video which is also very slow.

Thanks Woland and Mark,

I'll check out all your sugestions

best

Hi @woland,

1. I have a consistent recurring software 'hang' when attempting to change the 'Stage' assignment with several 3D Players and multiple Virtual Stages

 I have resolved this as being caused by scrolling input numbers associated with the use of a Apple magic mouse and residual input when changing the stage input number assignment. So perhaps less of an Isadora issue and more to do with the choice of input (mouse) device.

Best Wishes

Russell

@whitefly

Please open a ticket using the link in my signature and send us your file so that we can take a look at it to see if we can help.

Best wishes,

Woland

Dear Users,

If you're having any difficulty getting the OpenNI Tracker to run, please refer to our recently published article "OpenNI Tracker Troubleshooter". It covers running this Intel only plugin on an ARM/M1 machine, as well as the other most often encountered issues with this plugin.

Best Wishes,
Mark

@trevorn1 said:

. I see now that's a tough thing to figure out.

Actually, you can find out pretty easily do it from the Terminal.

Restart your machine and open a Terminal window. (Don't open Isadora!)

Enter the following command.

lsof -i4UDP:1234

and hit return. The result will show you what process is using the port. When Isadora is running on my machine, it says

COMMAND  PID      USER   FD   TYPE             DEVICE SIZE/OFF NODE NAME Isadora 1073 mconiglio   42u  IPv4 0xd3288f011e6d613d      0t0  UDP *:search-agent

If the process using the command is mysterious, you can try using Activity Monitor to look for the matching PID (Process Identifier) number.

Best Wishes,
Mark

@kmaeda

Hi there!

Welcome to the Isadora community forum. Glad to have you here :)

Regarding your question;

Are you sure that you didn't initialize the inputs in such a way that they default to 4?

To check this;

Click on the name of the input (so not the input field, but slightly to the right so that you press on the name)The Min / max / Ctrl Link / Initialize inputs open. Please check or the initialize input is not checked / the value is set to the value that you expect.

- Juriaan

@wolandI will try to get hold of them.

However, I asked them to change the laptop and the problem was solved instantly. As soon as I get the specs I will let you know.

@tomthebom said:

<p>@jfg<br /></p><p>How do you make "info for: value3" visible?</p>

 Just hover the mouse above the in-/output.

@whitefly said:

AUSplitter and AUMultiSplitter don't allow it, although they have one input and two outputs. Why ?

It's because these are Core Audio plugins that are part of the macOS architecture (we didn't create them), so they follow their own logic (which we cannot change). The warning that comes up when you try to do this also explains this:

It is possible to do what you want just by creating an AUSoundInput actor for each AUAudioDeviceOutput actor:

You could also create a Multi-Output Device and send your audio to multiple devices using that method.

Best wishes,

Woland

@dusx

Hi,

Thanks you for looking into that on an M1. I have also had success maintaining a connection on the intel 2013 Mac Pro. It appears that if a skeleton tracking subject is not established and maintained the Kinect V2 camera times itself out - when it does this it takes down the OpenNi Tracker and ultimately the Isadora application. This is my assumption as without the skeleton tracking operating the camera appears to stop functioning from start-up.

Best Wishes,

Russell

Hi @dusx, you mentioned, "there is a known issue withRealsense on M1 machines running Monterey". I am one of the people who suffer from this issue. Do you know will there be any updates on that? I really wanted to use my D455, but I don't know where I can get more updated information about it. Please let me know if you do. 

Thank you

@Eva

you can try to open Isadora directly with an empty file, then to pause engine:

and third to open your corrupted file. Sometimes it helps.

best

Jean-François 

@jrhooker

Hi there Jrhooker, 

That looks like you dont have the right permissions to write to that folder / location. 

Try to run the script as admin. That should give you the right elevated permissions.

Let us know or that solves your query!

- Juriaan

@juriaan

True ! I've just opened a Ticket.

As for the codec, I don't think the problem is on that side. I didn't mention but I've also tested with a shape and a background color actor and the same results occurs.

@Elena

Hi there Elena, 

In your message you say that you get an certain message, we do not see any image attached. Could you show us what type of message you see ?

And like Woland already suggested, please update your machine to the latest stable and see how that goes.

Thanks!