Thanks so much Mark. I'd been trying to avoid this multi-file solution so that I could be more spontaneous, but I understand the logic. That patch is much more elegant than how I'd been doing it. Much appreciated

Great!! I'm having loads of fun turning video signals into dmx 🙂

Exactly my thoughts. Unless I'm dealing with a sensor that's wifi only, I'd much rather have a hardline for a production / installation stability. Even if only for the little bit of inner peace it brings.

Back in March I had an opportunity to see a production called Kindur put on by the Italian Company Compagnia TPO. One of the most beautiful and compelling effects that they utilized during the show was to use a live-camera to create a mask that revealed a hidden color field. The technique of using a live feed in this way allows a programmer to work with smaller resolution input video while still achieving a very fluid and beautiful effect.  This effect is relatively easy to generate by using just a few actors. To star this process we'll start with a Video-In Watcher actor. The video-in will be the live feed from our camera, and will ultimately be the mask that we're using to obscure and reveal our underlying layer of imagery. This video-in actor connects to a Difference actor which looks for the difference between two sequencial frames in the video stream. This is then in turn passed to a Motion Blur actor. The motion blur actor will allow you to specify the amount of accumulated blur effect as well as the decay (disappearance rate) of the effect. To soften the edges of this the image stream is next passed to a Gaussian Blur actor. Finally this stream is passed to an Add Alpha Channel actor by passing the live feed into the mask inlet on the actor. The underlying geometry is then passed in through the video inlet in the Add Alpha Channel actor. Finally, the outlet of the Add Alpha actor is passed out to a projector.  As a matter of best-practice I like to use a Performance Monitor actor when I'm creating a scene in order to keep an eye on the FPS count. This can also be useful when trying to diagnose what's causing a system to slow down during playback.  This effect works equally well over still images or video, and is certainly something that's fun to experiment with. Like all things in live systems, your milage may vary - motion blur and gaussian blur can quickly become resource expensive, and it's worth turning down your capture settings to help combat a system slow-down. You can see my full documentation set here:  http://matthewragan.com/2013/04/28/isadora-live-camera-input-as-a-mask/

I wouldn't spend the time to clone the information over (never a great idea), rather I would just include a link to the help desk from the support section of the site. It will be easier to maintain that way.
You would just need to remove the add ticket link?

thanks Mark!

Oops.. Blur

or use part of a sine wave from the wave generator actor

Right. I can't record a video because im in a busy office... so images only sorry. I created a really simple touchOSC patch with just an XY pad on....

1) Click auto detect. You can then see the stream coming in live. NOTE: at the end there are TWO lots of numbers in brackets - (0.6024, 0.5984) These are the X and Y values from TouchOSC X Y pad. 2) Click renumber ports. I only have one port (or one incoming stream from touch OSC) so its sets it to 1 - you can give this a number of your choice but it would get confusing. 3) Create TWO OSC Listener actors. 4) Tell one to look for Channel 1 and the other for Channel 2. OSC Listener actor 1 is looking at channel 1 which is the X data. OSC Listener actor 2 is looking at channel 2 which is the Y data. **NOTE:** You do not see channel 2 in the stream set up window....  But if you where to add anther Touch OSC item such as a slider, button, dial etc and renumber it you would see it jumps to port 3.  Hope that helps.

a07e65-screen-shot-2013-04-19-at-10.05.15.png fe6017-screen-shot-2013-04-19-at-10.05.38.png

Hi,

Are you familiar with using the control actors ? If not there are tutorials from Mark on you tube that are great for approaching that kind of functions. [https://www.youtube.com/watch?v=HLkmL7XheQo](https://www.youtube.com/watch?v=HLkmL7XheQo) Mehdi

Here is a link to program MultiScreenermade with Max/Msp: http://www.zachpoff.com/software/multiscreener/ .

_"MultiScreener is a set of free applications that synchronize the playback of Quicktime movies on multiple computers, using a local network to tie them all together. (It can also sync multiple movies on the same computer using multiple monitors.)"_ Tested: 1. MacBookPro (17-inch, Early 2011) as a server with one output + MacMini Server (Mid 2010) as a client with two outputs, OSX 10.6.8\. 3 x PhotoJpeg 1280x720 (quality - medium, 25 fps, 10 min long) 2\. Hackintosh 3.50Ghz Intel Core i7-3770K, 16 Gb Ram, Nvidia GTX 670, OSX 10.8.3\. first output: DVI to TrippleHeadToGo - AppleProRes 422 3840x720 + second output: DVI - AppleProRes 422 1280x720, (25 fps, 10 min long) On both configurations Multiscreener worked just fine, no visible delay. Video played as a loop about 8 hours.

It does work in FreeFrame but as it is not a FreeFrame plugin I would suggest to put it into Library-->compositions.

Best
Michel

Except I was connecting movie player to video fore and back which was incorrect. Thank you Michel and all - this has completely solved my problem.

🙂

it depends if someone is using the word sound and you search for audio, the search engine can't find it. But there is something everybody can do to enhance the search results, the person opening a post can fill in tags, there you post all related words to your post. audio, sound, recording, soundflower, sound output etc.

Best
Michel

To output from Isadora into Simple Synth:

1) Start up Simple Synth -- set the MIDI Source to "Simple Synth Virtual Input" 2) Start up Isadora 3) Go to Communications > MIDI Setup... 4) In the first popup menu under "Outputs,", nex choose "Simple Synth Virtual Input" 5) Then ensure that the 'port' input of any MIDI actor is set to 1\. (That's the default already.) 6) Send MIDI The MIDI data will go from Isadora's output into Simple Synth's input. That's it. 😉 Best Wishes, Mark

Dear Stefanie,

The delay is simply unavoidable, because you must do the following steps: 1) Draw everything that needs to be drawn on the stage 2) Tell OpenGL to render the results to the Stage 3) Wait for the rendering to be complete 4) Tell OpenGL to read the resulting image from the Stage Window 5) Do something else for a while (meaning other Isadora processes). 6) Immediately before doing step 1 again, get the image from Step 4 as a bitmap (so that it can be displayed on any monitor -- not just the monitor where the Stage is) 7) Render the bitmap in the Stage Preview To prevent rendering performance for the Stage to slow to a crawl, you really need Step 5 -- and thus the delay. Best Wishes, Mark

Thanks Mark!

Ah ok I see.

Dear Bruper,

I've been away in France working on a project for the last 12 days. I'm on full time Isadora duty for the next month (at least). I'll respond to your email soon.

Best Wishes,
Mark

Hi Mark,

I'm sorry I fell off of the face of the earth there. This is suddenly working for me. If I figure out how to replicate the issue I was having I'll post again. 🙂 Thanks for all of your help. Best, Matt