Dear @primaldiving and all,

I just upgraded to 10.10.5 and Isadora 2.0.5 (nor the current internal build) does not crash on startup. The crash the user reported happened when Isadora was scanning for the video input devices, and was attempting to communicate with the DV Driver. Best Wishes, Mark

It seems to work now - please give it a second try.

After DusX reply here http://troikatronix.com/troikatronixforum/discussion/2188/trigger-text-actor#latest I can name the text actor the bad boy.

bdcf8f-foresee.zip

Yes, this seems to be a small difference in behaviour in 2 similar actors.

The 'Text' actor, and the 'Trigger Text' actor. In this case the 'Trigger Text' actor will solve the initial trigger issue.

perfekt!

@DusX

Will do :-).

Try copying this file into the Isadora folder. Perhaps your system has a path error.

I was never quite able to get my Kinect 1.0 to properly communicate with Isadora in Windows 7, tried out NI Mate on 10 last night and had no troubles. Thanks to all the contributors with instructions/tutorials on how to set it all up. Waaay too much fun. Here's a little clip from my first experiments.

https://drive.google.com/file/d/0B62fwSLyNBHQSVJoSkZCWkRHQlE/view?usp=sharing

I have just done what you described, and it DOES work alright

but in my patch I am using "integer" as type for the listener, instead of float that is the default value. When I did what you described, but set the type as "integer", after turning off and on the project, the values were again MIN and MAX Is it the right behaviour?

All I can say about this is that at our University a few people have the same issue with Firefox on Windows 7, they have to manually remove it from the taskmanager otherwise they can't open Firefox anymore.

Best Michel

absolutely! Unfortunate I cannot find any replacement for my "displace" freeframe plugin. Also it would be amazing to change only the width of the video with the FFGL-panspinzommer.

Yeah Epocam is not that reliable unfortunately. it's caused many a problem in Isadora over the years.

Filed

I found that if I run the program once or twice that I sometimes have to go into task manager and force quit the Isadora process.  Then it opens up just fine.

Seen one included with Resolume I think.

This is an interesting issue.

Since the actors correct behaviour is to be set to a type once connected to the initial type. However, I can see how if something in the chain is removed, and all trailing actors in the chain can handle both types, that the input could become mutable again.

In the end the problem was in the Matrox settings.

These can be a little tricky,  and depending on where you are located may require you to specifically select 60zh or 50hz to match your hardware.

Cheers

THANK YOU ALL FOR HELP!!!!
HAVE A NICE WEEKEND!!!

Thanks!

Break a leg as they say. Remember to change your wallpaper to black ;)

Ok, everything is working now.

The user actor that contains the Note On Watcher and the Jump++, anytime it would be updated, would cause the jumping. That bug was known to the designer throughout tech (I am assisting him). I added PJ Link actors to the User Actor, and linking Control IDs to them so they could be controlled via buttons on the Control Panel (Shutter on, Shutter Off, etc.). Izzy was not too happy with this, thus causing the bizarre continuous advancement that would occur when updating the User Actor. Deleting these added actors has stopped the unwarranted advancing.