@dbini You could also play with the parameters bleow smoothing about area surface and same area max distance. Bit it depends how what you are tracking moves

Hello,

how old is the file ? DO you remember the Isadora version ? What I would do it to try opening it with an older version....

hi everyone..

i have a problem with an older file ...after conversation to the new Isadora 4 I don't see video on my show...but only sound...

Anyone can help me?

thank you

@fred
Thanks Fred. I've been developing my patch to try to accommodate separate blobs, and realised there is an amount of maths involved. Rather than go down the Python route, I'm combining calculators and have found a way to determine the maximum size of the input, but am struggling with the average position. I think it just needs more maths. It's the kind of thing that my brain needs time to process. : )
I will be testing the system in the real world at the end of next week, so will find out then if my logic is logical....

@dbini this is kind of annoying to do, mostly as we do not really get an expanding list from the blob tracker. 

In principle though you can calculate a bounding box for all the bounding boxes of the blobs. 

You would have to do some fancy footwork, but likely python is the best bet - First you need to connect what you would expect to be the max number of objects to the blobs output.

Then we need to know if there is actually a blob on that blob output (the blob decoder as a tracking output that is a boolean for if there is a blob at position 0, 1 2 etc). We then use that to determine if the blob width height and horizontal and vertical positions should be taken into account when calculating the meta bounding box).

Then in python you can write a relatively simple script that will use the positions of any active blobs to get a meta bounding box - you can also get a centroid and area pretty easily.

@woland

What happens is when I quit Isadora, the file closes, all windows disappear, but Isadora remains open, lurking in the background. Attempts to quit from the Isadora dropdown do nothing and I need to Force Quit. I suspect it may have something to do with either the OpenNI Tracker or Screen Capture actors. Recently I've been working on a new patch that doesn't include either of these actors and Isadora is quitting perfectly.

@dusx

I've tried deleting the media on prompt when closing the file, or using the Delete Captured Media button in the Output dropdown.

@citizenjoe @DusX

So sorry for the late reply - other projects were prioritized, now I finally have the time to look back into this. My IT department has essentially abandoned me, so I'm on my own.

I'm still a bit confused, apologies that I'm not following. You're saying I *don't* need to convert the video to HAP? Isadora does that automatically?

Just to try your suggestion, I did convert it to the HAP codec manually in media encoder to try it out, but when testing in Isadora there's no difference between the original video and the new HAP video.

It seems that the spikes are better, I think because my computer finally transitioned to using the NVIDIA graphics card after I forced the setting. Once I start "show stages" the little NVIDIA manager pops up to tell me it switched over, which didn't happen previously. 

I'm no longer spiking at 180-200% load, but I am at a consistent 80% load. It spikes up to to the higher end of 80 when videos restart on the loop. It spikes over 100% when I use any watchers or generators. The same file on my personal computer doesn't go above 40%. It's not sputtering and lagging like it did before, but the spike is still concerning to me, especially because I'm doing relatively simple stuff. No depth cameras, external accessories, or generative content yet. This is all with the projector connected.

If it's not the HAP codec, and it's not the GPU, and it's not the security permissions, what else could it be? Agh!

Thank you so much!!

@dbini

My hope is to offer some form of crossplatform api in the future. 

How are you deleting the media that is leaving these Unassigned slots, via Applesscript?

@dbini

This can happen if you have the Isadora Preferences/Settings Dialog open. It will prevent you from quitting while it's open I believe.