@gapworks said:

reflection2.izz

 waterdropx2.izz

It seems that the Color choices for the Shapes actor changed between Isadora 2 and Isadora 3. I suspect this was due to increased support for alpha channels, but I can't be 100% sure at this time. In any case, changing the shape to have a White Line and Black background (and increasing the Displace amount) got the effect working again.

Then I made a new scene, and converted the User Actor to use the GPU as @dbini suggested !

Knowing that rendering a shape every scene has some overhead,  I decided to make one more version where the circle is only rendered once per frame (rather than 8 circles per frame) an use Video Delay actors to make multiple ripples.

In the end it seems that the overhead of the Video Delay actor is greater than that of the render time for Shapes. 

attached is the file I worked on

@dusx

Got it! Thanks a lot Dusx

@laverdi

I think I would use a chopper actor to achieve this. I would use it because it makes it easy to crop to the correct size, and position the original image within this crop.

I am sure you could use IzzyMap in some way, but then you have a harder time mapping if needed.

In the image below, I have cropped off the bottom 120px for output... You can just as easily take it off the top or anywhere between (the original has a thin Black border all around the white).

@juriaan thank you very much :) 

Thanks @dusx @Maximortal

@joshuawg

If they're both running on the same computer you could use an AppleScript cue in QLab to bring Isadora frontmost then tell system events to keystroke P using Cmd+Shift

Best wishes,

Woland

@decametre

This file might also be useful to you. There's a method that'll let you detect a click on an object of any shape (the example I used is a png of a banana).

magic-shape-02.zip

Best wishes,

Woland

@thatmattrogers

Isadora currently doesn't offer any UDP capabilities other than OSC (open sound control is sent via UDP).

We do however have beta options which would/should allow you to interface with your camera.
I will private message you to see if you might be suitable for our Beta program.

@mjotas

You will need to use a background scene to allow a video to play across a scene transition. 

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

It works in the same way as the video tutorial outlines for sound :)

@dusx said:

use multiple GLSL actors, one for each buffer. @mark has made an example of this somewhere in the forum

Thanks  @dusx, 

this is good to know. I never thought on that path way, multiples & individual shader buffers..

So, its time to search  that @mark example. Thank you for the feedback!

@dusx -- thank you so much. ya'll are so generous. i literally have never thought of using the movie player in any way other than playing a movie. duh. that's very helpful. And your timer patch cracked open another scene for me, so I really appreciate that.

@Woland -- this is great. yeah, we control shows with qlab because it cues both izzy and eos and that's been the easiest for our workflow. but I'm excited to look at these actors. thanks for sharing them!

thanks for fielding my questions! (hoping to have no panicked posts this time...)

@avieira

Hi,

Thank you for the great suggestion!

I have uploaded to the Add ons page, it is now awaiting approval before it will appear there.

Best Wishes

Russell

@dusx

Thank you very much, that was really helpful! 

@reinhard Absolutely wonderful thank you! Never knew about the Scene Intensity actor - very useful

@juriaan said:

personally I set the input / output to timecode

 Yes, this is a very convenient way to have standard time to reference. Simply use the Timecode comparator to do the > (greater than) test.

@jameshooton

Here is a demonstration of working with Blender 2.79 to assign an image texture to a 3DS geometry file...

assigning a texture to 3ds in Blender

Best Wishes

Russell

@hlm001 said:

Is it determined by the resolution of the projector?

 Ideally make them match the resolution and aspect ratio of your physical projector, yes.

@gaspar

@Woland is absolutely right about the issue with the button. You can do the same by manually clicking the trigger input twice on the Jump++ actor (this is a sort of hidden feature).

A MulitBolcker actor is another easy way to solve this double-click issue (however setting the buttons up correctly is preferred).

And on Cinema 4D just make your 3D model and export it to 3ds format.

@dusx

thanks. that did it