Dear All,

So, there is an issue with the Blob Target Proximity in that it does not allow take the aspect ratio of the source image into account when calculating the distance to the target. If the image fed to Eyes++ were square, then it would work. But given that it is 16:9 in Fred's test patch, the height is incorrectly calculated. There is nothing to be done about this at the moment, because we'll need to add more information to the "blob" structure so that it knows the resolution of the source image. 

In the meantime, see the attached modification of Fred's patch. It contains a User Actor called Target Proximity Pixels which accepts a blob, the height and width of the source image, the target position, and the target size, all of which are specied in pixels instead of percentages. (It could be percentages too... but maybe it's clearer with actual pixels?)

There is another User Actor called Quad Target Proximity Pixels that accepts a blob input and allows you to specify four targets. (If you don't want to use a target, set it's size to 0.)

The example now contains four white circles at 25% size, and one yellow circle at 50% size. The white text reports the output of the Quad Target Proximity actor, showing a value whenever you approch any of the four white targets. The yellow text reports the postion within the larger, yellow circle.

Hopefully that's enough to get you going on your own and address the problem until we can update the Blob Target Proximity.

Blob Proximity - User Actor Fix.izz

Best Wishes,
Mark

@tease said:

That was the key: movie player speed at 0 and HAP codec

 https://giphy.com/gifs/well-do...

it was working OK with me earlier today.

@blackmoonhowling
Did you try my suggestion?
It could work because you are stopping the execution of the JS before going to edit it.
It wouldn't remove your code.

@Juriaan and All,

I have verified that our Leap Motion Watcher actor does not work with the Leap Motion v4.0.0 Drivers, but that it does work with the Leap Motion Orion Beta v3.1.2 and the LeapMotion v2.3.1 SDKs under Windows 10. (MacOS is not affected by these changes.)

They seem to have radically changed things in the corresponding SDK, removing all interface options except for the Windows only C# (C-Sharp) and moving to a C language only interface. Our Leap Motion Watcher relied on the C++ interface so perhaps this is why it will not work with this latest Leap Motion Orion SDK. I will be posting on the Leap Motion forums to find out if there is some way to get our existing code working with the 4.0.0 system -- though I am not terribly hopeful. Leap Motion seems to be going in an entirely new direction (AR/VR) and the tracking API's all seem to be getting thrown under the bus. :-(

To get your Leap Motion working with isadora, the simplest route is to install the Leap Motion Orion Beta v3.1.2 SDK. You will need to create an account with Leap Motion to download this file.

Installing the 2.3.1 version found on this page is also possible, but requires performing the not-too-complicated "hot fix" as described in the leap motion forum.

I have tested both v3.1.2 and v3.1.2 installers with our Leap Motion Watcher actor under Windows 10, and it seems to work as expected.

Best Wishes,
Mark

So just to be clear, you’ve tried the following steps in this order?

1. Use System Preferences to find the resolution of the projectors.

2. Create a jpeg that’s just full white at the same resolution as the projectors.

3. Turn on the computer BEFORE the projectors.

4. Open Isadora into a Scene that’s just a Picture Player actor outputting the white image to an unmapped Projector actor.

5. Show stages BEFORE turning on the physical projectors.

6. Turn on the projectors so that the first thing they “see” upon waking up is the full white image with NO mapping at their native resolution (to prevent them from doing any auto-scaling).

I swear the problem you're having sounds like the exact issue I was having a few years ago and the steps above solved it for me because it turned out that the projectors were auto-scaling/auto-keystoneing and the only way to prevent it was to send an unmapped image at the full resolution before I turned on the projectors and letting the projectors "wake up" to that unmapped white image.

Can you please give us the make and model of the projectors? (Also make sure to go into the menu settings for each projector and ensure that you’ve disabled anything like “auto-keystone” or “auto-scale”.) 

@dusx thanks very much again. It was something I should've checked... sigh. Thanks so much too @WOLAND! 

@citizenjoe thanks for the info, very nice page! I was afraid that my machine had some issue, fortunately it isn't the case. I would like that the sound player had the same features that the movie player... and the windows version these of the mac! Cheers, AZ.

@karlakr8 said:

Any clues how to optimise Isadora 3 on a Mac?

 Hi,

This might be supper obvious, but I have had issues running Isadora with other apps open on the same machine - namely Microsoft Office programs and there is the old chestnut of the Adobe Creative Cloud conflict that may be an issue for High Sierra.

@dusx said:

 Actually I expect this will be much more resource hungry.

 I sit corrected ;)

@bc131 said:

Hello, i have a problem. When I import a 3ds file of Blender, i get an error mesage with the id: 1852402768. Its Isadora Version 3. In Isadora 2, its all ok. I reinstalled Isadora and reset the preferences, but the problem is still the same. But only on my mobile PC.At the the Tower PC at home, its all ok. They are both Windows machines. And i tried with the same 3ds modell, so the problem must be Isadora v3. Manu

 done

yes ... i cleaned up my preferences  ....  now it seems to be more stable ... thanks

Diether

@edjoynson

Which particular codecs aren't playing on the machine in question?

@mark 

The show closes tomorrow so I think they are fine to stay in 2019. I've upgraded all my other computers to 3.0.7 so moving forward that should be fine.

Thanks so much!

Cheers,

Cam.

@testcard67

The best thing to do is to open a support ticket so you can send the file to us so we can try it.

https://support.troikatronix.c...

There is a bug I have discovered in Isadora 3 that will lead to a crash if certain non-ASCII text is used in the older, 2.6.1 file. But this doesn't sound like the same things since that one always leads to a crash.

Best Wishes,
Mark

I am moving from isadora 2 to 3 and using the Artnet 64Bit plugin. The 'Matrix Color Send' actor has lost the 'flip mode' input. Was it removed because there Is another way to accomplish this for daisy chain logic of my LED strips?

It works well in isadora 2.6.

from the tutorial: 

"Take special note here of the use of the 'flip mode' input to horizonally flip the DMX addresses every other row. This facilitates daisy-chaning of the strips."

ok i will use javascript to fake a white channel value

@dusx Ok, I submitted a bug report, got a few in a row with very similar situations, but it was not 100% repeatable.

Dear all thank you for your input!

@DillTheKraut @bonemap thank you for taken the time in making a detailed feedback!

I didn't quite understand everything @DillTheKraut said but it's very interesting to investigate the movement timings.

@bonemap thanks a lot! there are so many features i have to learn in isadora. I'm very grateful for the optimisation that i'm going to have a look at.

The show went ok, there was really noticeable lag once the particles projected large scale.

Best,

David

Thanks, it's ok !

Best