Re: [Connecting eyes++ to Live drawing](/topic/9033/connecting-eyes-to-live-drawing)
I'm having an issue getting eyes++ and chroma tracking to work with live drawing. I am new to Isadora and only know the basics. If anyone had a quick tutorial/run through I'd very much appreciate it.
Thanks
dear troikatronix,
thanks for your youtube tutorials!
i encountered a problem on osx sequoia 15.2 / mbp 2021 M1 Pro (arm) / isadora 4.0.9 (rosetta):
i followed both pythoner tutorials Getting Started with pythoner and Beginner’s Guide to MediaPipe Tracking in Isadora
the installation and activation of the virtual environments with the apple-scripts worked fine (numpy/pillow/mediapipe "...install OK").
"Get a list of IMAGE URLS via webscraping" in the examplefile works.
BUT the interpreter shows a red (!!)-sign whenever numpy or pillow is involved. when i click on [OK] the interpreter in the example-files (eg. pythoner_examples_v0.4.izz / "Load an Image from the WEB and output to Isadora") says:
ImportError: Error importing numpy: you should not try to import numpy from
its source directory; please exit the numpy source tree, and relaunch
your python interpreter from there. (Module_A0LRGrXqdi.py, line 1)
pillow also produces a strange error. i did not set any arm64 or x86_64 variables. shouldn't isadora automatically chose x86_64 running in rosetta or maybe the "installer script" with pip recognized the M1 chip and installed the arm versions which do not work because i'm in rosetta? (see screenshots).
do you have an idea what's wrong?
thanks

@mschwenker said:
variables that are created outside the main function?
Yes, these are Globals to the active instance of Javascript. The Javascript actor does not have a built in method of sharing globals between actor instances.
You can bridge this by outputting values to a Set Global Values actor, and feeding the value into another Javascript actor via the Get Global Values actor. This works well when you want to share values primarily in one direction.
I updated my file and User Actors to make them even easier to use python-rename-scene-after-media-v3-2025-08-19-4.1.3.zip
@mschwenker said:
I have one more question about the memory management of the JavaScript actor. What about variables that are created outside the main function? I would assume that these are only available to the actor instance.
@liminal_andy Didn't you have a method for passing global values between JavaScript actors?
@DusX and @Woland thank you very much for your very detailed feedback and also for create this 8 Notes on and Off Watcher.
This helped me a lot to better understand how Izadora works, especially when it comes to data flow and actor execution.
I was able to use the actor as a basis and adapt it to my needs. I change it from 8 to 12 Notes and reduce it only the pitch and note on / off information which i combined to a On/Off integer because i only need to track the current pressed notes.
I have one more question about the memory management of the JavaScript actor. What about variables that are created outside the main function? I would assume that these are only available to the actor instance.
Thank you very much.
Malte
@skulpture said:
Thanks will check it out
Feel free to let me know if you have any issues with it. It should be easy enough to fix since the actions I'm performing are independent from each other and not very complex.
It's basically just taking the file name from the Get Media File Name actor, then doing the equivalent of these keystrokes:
- Cmd+c (copy)
- Cmd+r (rename scene)
- Cmd+v (paste)
- Enter (confirm Scene Name)
@woland Thanks will check it out - that's pretty advanced stuff. Cheers.
Here's a Pythoner file that does exactly that. It can take a media file name and rename a scene after the file name.
I tested it only on macOS, so you'd need to test it on Windows, but it should have code to handle working on Windows already. The script is not too complex, so it should be fine.