Thank you for all the suggestions. The programmer is actively working on these now, and I'm going to prioritize the list in response to what you've said above. You can look forward to more news on this by the end of August.

Best Wishes,

Mark

zoomer

chopper

motionblur

timeblur

zoomer

effectmixer

I hope it isn't too late to add my wish list for updated FFGL plugins. Here are the ones I am using in my current projects. Many thanks!

dots

slit scan

interlacer

tile

solarize

contrast adjust

threshold

video inverter

difference

effect mixer

motion blur

directional blur

time blur

lionel blur

gaussian blur

This approach will be limited by the size of the RAM (there is no limit check for that though at the moment).

In addition, the frames could be jpeg–encoded to conserve CPU memory, as shown in this example:

ioio

Any chance you would switch to using the openCV library for eyes++, it also has a lot lot lot of other great functions and would be an incredible addition to Isadora (Izzy would need a few more types to deal with it but nothing it does not deserve and could not make use of). Although much of the work is CPU, there is a lot of stuff that is now GPU accelerated, it is all cross platform and BSD license. 

Alternately there are always compute shaders for the GPU or openCL/CUDA acceleration that are widely adopted and work well.

Fred

I want to do a bit of "thinking out loud" regarding some of the plugins you're requesting.

I'll break them into two groups:

**Group A: Requires GPU Readback -- Eyes, Calc Brightness**

I'm going to need to do some research to see how much of a performance hit something like Eyes and Calc Brightness are going to impose. In those cases, you will need to read from the GPU to the GPU, which is just the absolute worst thing to do when what your goal is performance. GPUs are very good at accepting data _from_ the CPU, but _giving it back_ is not what they're designed to do. (I'm not saying it can't be done, just wondering how much it will affect performance.)

**Group B: Requires Loads of GPU Memory – Buffer, Shimmer**

These actors concern me a little because of the limited memory on a graphics card – at least when compared to a CPU. The worst case scenario is if you're exclusively processing full HD video (1920x1080) -- each frame is about 8MB. The GPU memory is going to disappear pretty fast if you start using the Buffer actor to keep those massive textures in memory. 

The card in my recently bought retina display is 2048MB. That means a total of 256 frames of video. Each Stage output uses 2 to 6 frames depending on what you're doing. Every FFGL effect you use eats one more frame of GPU memory.

I mean, I quire certain it can be done. But that GPU VRAM is going to dry up really quickly. At the very most, the number of frames you could put in the buffer (again, full HD) would hover somewhere just over 225 (given a few stages and playing a few movies, etc.). That's 9 seconds of video at 25fps, and 7.5 seconds at 30fps.

Not a lot. But maybe that's all you're expecting?

Best Wishes,

Mark

Calc Brightness

QC Filmstock is also great... for adjusting video to look like film with parameters Saturation, Contrast, Grain and Vignette.

Kinect...?

thanks Mark!

Freeze

Video Delay

Blur(any kind)

GPU Accumulator with arbitrary amount of frames

GPU PhotoShop-like blending modes

--8