Testing the new bezier embedding in the Vectorizer effect options in pre_V6 Studio Artist.
A depository for John Dalton's personal artwork. Studio Artist, MSG, procedural art, WMF, digital painting, image processing, human vision, digital art, slit scan, photo mosaic, artistic software, video effects, computer painting, fractals, generative drawing, paint animation, halftoning, video effects, photo manipulation, modular visual synthesis, auto-rotoscoping, directed evolution, computational creativity, artificial intelligence, generative ai, style transfer, latent diffusion
Fun little experiment. I don't consider it a success, but it does point in the right direction.
Single paint synthesizer preset. I then used a Transition Context with virtual sub-nested keyframes to re-time the paint animation. I'm doing a few clever IpOp effects afterwards to post process it. One of the clever things i'm going to build into Transition Contexts as an option there you can turn on or off as it suits you.
This is a buggy version of an alternative approach. Different non-dynamic brush paint preset.
I then ran the automatic conversion to embedded bezier paths. So you end up with a different single paint action step, where all of the paint strokes are bezier embedded inside of that action step.
The automatic generation works off of each of the individual virtual sub-nest keyframe positions derived off of the Transition Context. The Transition Context contains one real keyframe reference to the original source movie. It's Destination (where it routes its output) is set to Source (as opposed to canvas or style).
The bug is that the original bezier path sizings are not being passed through in the automatic conversion for this particular paint synthesizer parameter setup. Going to dive into the code and clean that up now. Fix will be in V5.5.4.
Xcode is crashing on me multiple times a day. It just can't keep up with Studio Artist 's AI cranking out cpu cycles at lightning speed. We're going to bail on it at some point and move to a unified cross platform development environment that i hope is better able to handle the stress.
Here you go. A slightly better demo of what i am talking about in the previous post (virtual keyframe sub-nesting). I explain in detail on the Studio Artist User Forum how to make it. Check it out here.
I immediately wanted to use Virtual Keyframe Sub-Nesting with the automatic features in Studio Artist V5.5 that let you convert paint actions that use or generate bezier paths into bezier embedded paint action steps. This lets you auto-build key-framed paint animation running a single menu command.
An hour's worth of code refactoring and a continuous coffee drip lead the simple animation test above.
This proves the concept and tests the new code, but doesn't really show off the power of it. I'll put together a better demo of it later.
Fun little experiment using the new virtual keyframe sub-nesting feature in Studio Artist V5.5.3. I'm using a transition context with a single keyframe at the first frame position. I have a movie file key-framed there.
So the idea behind virtual keyframe sub-nesting is that Studio Artist can auto-generate virtual keyframes based off of that one manually specified keyframe (the movie file) at position 1. And then the transition context does what it does, which is generate transition effects between keyframes (virtual keyframes in this situation). So you just saved yourself a ton of work, because you'd have to generate a folder of skip frame images, and then keyframe them all manually at the appropriate positions on the timeline to do what virtual keyframe sub-nesting does for you automatically.
Actually Studio Artist will auto-load a selection of multiple keyframes all in one shot, and then you can run a time line expand command to get there, but you still have to setup all of the skip frame images in a folder to do it the old fashioned way, so you probably never will do that. But now you have no excuse not to experiment with it, since Studio Artist does all the work (notice a theme here we keep re-iterating in V5.5).
So i made a 2 step PASeq. Transition Context action step, followed by Vectorizer action step. I ran it with no sub-nested virtual keyframes first for 120 frames, then sub-nested with a spacing of 4 frames, 8 frames, 12 frames. I was using a linear fade transition algorithm for those. Then i switched to a different transition algorithm, and bumped the spatial extent from 40 to 80 to 120 for the other 120 frame passes.