
i used this keyboards as a button can be reprogrammed as a midi device with the arduino ide

Since dedicated VS internal gpus can be a little tricky to figure out (each vendor deals with these a little differently) I will need a little more information.
note: I am running windows 11 on a Lenovo Legion
Which display are you running Isadora on?
Which display is your stage on?
How do these compare to your nVidia Control panels display of connection on the PhysX section?
This is mine:

Note: I have two connections that run through the RTX gpu, while the other listed is connected through my integrated gpu.
To further complicate things, my Laptop display (not listed here) connects directly to my integrated gpu.
Does your Lenovo have 'Lenovo Vantage'?
And if so in the Gaming section (my UI just changed, so maybe this won't match) can you change your GPU working mode?
Mine provides: Hybrid, Hybrid-iGPU, Hybrid-Auto, and dGPU
For general working I use Hybrid-Auto (uses both cards), but for shows I use dGPU (dedicated gpu only)
If I can understand your setup, I can try to reproduce the issue you are having, and hopefully find a solution.
@gaspar said:
Ouch.... just saw my reply is off. You intended to track everything as one blob... and you solved it.
My bad.
Looks great by the way.
Could it be that you're missing something very simple?
You should define the maximum amount of objects to track (second input of the Eyes++ actor). Then Eyes(++) will look for more objects.
You might face a different problem if the objects are close together, but you can play with the other parameters to catch those things up.
I hope this helped,
Cheers
I'm still on Isadora 3 and in the process of migrating to a new computer.
I was/am on the computer at my signature, running w10. The actual one is running w11, has about the same specs but has a NVIDIA GeForce RTX 4060 Laptop GPU instead of the 2070, and it runs on an i9 processor. And unlike the "old" computer, this one has also an intel UHD graphics card. (It is the Lenovo ThinkBook 16p G5 IRX)
As good as it sounds, I feel the old one worked slightly better.
TO THE ACTUAL ISSUE.
When Isadora is running and stage output is on, it works fine. Sometimes complicated transitions get a bit messy, can't reproduce it accuratelu now.
But if I open a different program, the stage output freezes... It unfreezes if I click on the stage output, but as soon as I get back to the "other program" can be notepad, browser or whatever, the stage shows the frozen frame of the first time I opened that other program.
Does anyone have a clue or better solution to this?
I've set the computer to use only the 4060 on Isadora, but it does not solve the issue.
Thanks...
I'm on a GIG next weekend, but I'll probably take the old one (which has several connector issues, but Isadora runs fine).

thanks to everyone for advice, I managed to tweak Eyes to make the most of Histogram mode and blurring and captured most of the inputs accurately.
Here's the results:
This was made at a STEAM event for children, so I couldn't shoot any footage of the system in action.