Resolume Forum

Why not just set the in/out point for a clip.
Ensure layer transport controls are visible and scroll your mouse wheel over them.

Or, to sample the comp/camera, click record for a few seconds and do the above on the freshly inserted clip.

Currently working on the strobe and multi placement, there should be something to test this week, latest the next. But i make a note of the sampler.

Earlier in this thread I suggested a Matrix Digital Rain type effect that takes the luma of a video and replaces it with falling digits.

Well with a (Shader) toy and a touch of magic it can be done in realtime in Resolume:

Would you mind posting the plugin?

There is no plugin (apart from Spout) involved. Links to everything needed above.

You'll need Magic Visuals (beta 1.5)
Copy (taking note of the licence) the shader code and paste into a text file.
In Magic, load a video and your saved shader code into a Video and GLShader module.
Connect Video->GLShader->Magic and set the window to output to spout
Load a spout source in Resolume

How about a dummy FFGL with like 16 parameters for using Resolume's awesome beat clock or FFT to send OSC parameters to other software. You could have an .ini file to name the parameters. I do this now with some random effect on the comp and bypass it so it doesn't eat CPU, but the names don't relate to anything.

This isn't FFGL... but there's some live-typing Flash plugins that do that nicely.
http://emaqdesign.com/video_loops_flash.html

well i dunno if you guys are checking out this thread or not but a kaliedoscope plugin will be damn good...i know resolume have already got one but its not that rad. The after effects plugin cc kalieda is what i am talking about its wonderful and making live transformation to any video or image in real time will be just awesome.

already done see this thread, really a great plugin.

viewtopic.php?f=5&t=10008&p=38669&hilit ... ope#p38669

j4s0n.c wrote:How about a dummy FFGL with like 16 parameters for using Resolume's awesome beat clock or FFT to send OSC parameters to other software. You could have an .ini file to name the parameters. I do this now with some random effect on the comp and bypass it so it doesn't eat CPU, but the names don't relate to anything.

Managed to cobble something together to do exactly this (apart from the .ini bit unfortunately). This is my first ever FFGL code, so if anyone has suggestions to improve it I'm keen to hear them.