using Qlab with madmapper HELP

[christin...@asl.org]

we have created in mad mapper a masked surface (in this case a hand) with a video clip that successfully shows in the shape of the hand. Now, we would like to hook this up with Qlab, and create a cue which plays our footage in hand shape. This seemed like it would be straightforward, but we are stuck. We know about syphon, but exactly which surfaces, outputs etc do we need to set up? Does Qlab need the footage and madmaper just needs to provide the map? or should the video Q in cue lab just find the mad mapper clip for us? confused? me too. help! our show is soon!

[Drew Schmidt]

Create a new surface on qlab where the output is Syphon. Make sure the size of your surface is the size of your madmapper input/output.

Then in madmapper select qlab as the source

[christin...@asl.org]

thanks, will try and then I'll get back to you!
Christine

[Drew Schmidt]

No problem!

When creating a new surface, press the [ + ] button and select Syphon to assign that screen.

You can also setup MadMapper to automatically select syphon as the initial input as well as automatically startup with the output on (This can sometimes be a problem if your extra displays aren't connected, then the output will show up over everything else. In this instance, just press Cmd+T to turn it off).

I like to then put an AppleScript cue as a startup cue in QLab to open the MadMapper file

For example...

tell application "Finder" to open POSIX file "/users/{your user name}/Desktop/SomeFolder/TheFile.mad"

[Greg Leeper]

If you want mad mapper to be the source, or first in the chain, you need to tell it to output to syphon, not a screen.

Then in camera prefs in Qlab you will see Mad Mapper show up as a camera input.

To go the other direction create a new surface in Qlab video prefs and assign a screen to it: Syphon will show up as an option.

Then in mad mapper you can choose Syphon as in input option.

In both cases Qlab may require you to stop, reset, and trigger cues from the beginning for the changes to work.

I'm looking at Syphon working in both directions at the same time: MM sending it's test pattern to Qlab as a camera input, then Qlab sending it back to MM via Syphon by assigning the surface for my camera cue to the one I've designated as Syphon out of Qlab.