[Mylenium]

Put them in one comp and animate the opacity of the top layer. create a simple cycle that covers 2 frames and then use a “loopOut(“cycle”,0) expression. Turn off interpolation on the keyframes. another option might be using the strobe effect on the top layer with the “make layer transparent” option.

Mylenium

[Pour Myl

[Mylenium]

Put them in one comp and animate the opacity of the top layer. create a simple cycle that covers 2 frames and then use a “loopOut(“cycle”,0) expression. Turn off interpolation on the keyframes. another option might be using the strobe effect on the top layer with the “make layer transparent” option.

Mylenium

[Pour Myl

[Mylenium]

It largely depends on how much disk space you have and at which bit depths you work. Quicktime Animation is quite good for most stuff, but it’s only 8bpc. For 16 bpc you’d need other codecs, such as BMD’s or Microcosm. Another option is using image sequences. Both TIFF and PSD can use dynamic compression and work at all bit depths.

Mylenium

[Pour Myl

[Mylenium]

Just import the entire old project into the new one and then delete all the redundant comps.

Mylenium

[Pour Myl

[Mylenium]

I know them, but I never use them for serious production. Since they were originally created for doing near realtime VJ stuff, they sacrifice quality for speed and as much as it pains me, I can’t take the risk of using them for paid work. You know, the glitches they have may be funny and give that grunge feeling on a live show, but just look out of place on a mostly clean industrial vizualisation DVD ;O). I’m always assuming other people also place quality (in a mere technical sense, I’m not gonna pretend that I’m a great artist) before speed, so I usually don’t recommend using Pete’s tools.

Mylenium

[Pour Myl

[Mylenium]

This may be specific to text layers. Perhaps CC Cylinder cannot properly see their layer boundaries. Try to pre-compose, this should fix it.

Mylenium

[Pour Myl

[Mylenium]

Effects –> Time –> Echo. You might need to apply this on a duplicate of your original footage to bring out all bright spots and then use a blend mode such a screen to achieve the desired effect.

Mylenium

[Pour Myl

[Mylenium]

Quite honestly I haven’t tested that yet, so I left it out. Coming from the 3D world I know the limitations of OpenGL and even pixel shaders (what OpenGL 2.0 is all about) don’t change that. In general I don’t consider any OpenGL rendered stuff as “production ready”, not in 3D nor in 2D. Anyway, I doubt that your hardware is to blame for the slowness.

OpenGL can only optimize comparably few things, so if you are using lots of nesting and non-accelerated effects, you loose the speed advantage, or moreover give yourself a hard time because there is always at least an extra step involved in translating the software render buffer and OpenGL buffer back and forth. This would explain accelerated renders being slower than software-only stuff. The same can happen when using multiple accelerated effects – if your graphics card cannot hold all buffers, they will be temporarily cached as software buffers before the next processing step , adding additional overhead. You should only use OpenGL for straightforward things like interactive color correction where OpenGL can literally “burst” free its power.

Mylenium

[Pour Myl

[Mylenium]

Try CC Cylinder

Mylenium

[Pour Myl

[Mylenium]

Thanks for all your compliments. One question: Is my voice halfway bearable from the point of a native English-speaking person?

Mylenium

[Pour Myl