From Graphic Novel to 30-Minute Animated Film: What I Learned Building an AI-Assisted Production Pipeline

From Graphic Novel to 30-Minute Animated Film: What I Learned Building an AI-Assisted Production Pipeline

David Cole September 20, 2026

0 Comments

When I first created The Lion of God, it was a graphic novel. I knew what the world looked like, how the characters moved, and in many cases I could already see the scenes playing in my head like a film.

What I did not have was an animation studio.

Four years later, I had produced a roughly 30-minute animated fantasy film largely by myself.

The surprising part was not that AI made that possible.

The surprising part was how quickly the process stopped feeling like AI filmmaking and started feeling like filmmaking.

The more control I wanted over the finished movie, the more I found myself dealing with the same problems filmmakers and animators have always dealt with: composition, continuity, performance, timing, screen direction, pacing, coverage, sound, and the question of whether one shot actually works when placed next to another.

AI dramatically reduced the amount of production infrastructure required to create the imagery.

It did not remove the need to direct it.

The Project Began on the Page

The Lion of God began as an independent graphic novel series combining mythology, metaphysics, anomalous experience, science fiction, and dark fantasy.

The graphic novel format gave me something extremely valuable before I ever tried to animate the work: visual development. Characters and locations already existed. Many major story beats had already been illustrated.

In that sense, the graphic novel became an enormous library of concept art, storyboards, character references, compositions, and visual targets.

That turned out to be incredibly useful once I began experimenting with animation. Rather than starting every shot from a blank prompt, I could begin with artwork that already contained a strong creative decision.

The challenge was no longer simply, Generate a Greek warrior standing in a forest. It became much more specific: How do I make this particular image move without destroying what made the image work in the first place? That distinction became increasingly important as the project evolved.

The First Temptation: Generate the Shot

Early AI video tools encourage a very seductive workflow: You create an image, you describe what you want to happen, you press a button, and a few seconds later, you have moving footage.

Sometimes the result is astonishing; other times it is unusable. Usually it is somewhere in between.

For short-form demonstrations, social media clips, or dreamlike imagery, that unpredictability can be part of the fun. For narrative filmmaking, it becomes a problem very quickly. A shot does not exist by itself. The actor has to be standing in approximately the same place when the next shot begins. A weapon needs to remain in the same hand. A character who exits frame left cannot suddenly appear on the wrong side of the next composition. Wardrobe, lighting, geography, facial structure, camera direction, and physical action all begin accumulating continuity requirements.

That is where I learned one of the biggest lessons of the entire project:

Generating a good clip and directing a scene are not the same thing.

The longer the project became, the less useful it was to think in terms of isolated generations. I had to start thinking in shots, then sequences, then editorial structure.

Episode 3 Changed the Workflow By the time I began serious work on The Lion of God #3: Anamnesis, my approach had changed significantly.

Instead of asking an AI video model to invent most of the action inside a shot, I increasingly defined the beginning and ending states myself. I became much more deliberate about keyframes.

If a character needed to raise a weapon, turn, attack, fall, or transition into a different pose, I often found it more effective to create the important visual states first and then use animation tools to bridge the movement between them.

This shifted the process from: Please make something interesting happen. toward: This is where the shot begins. This is where it must end. Help me create the motion between those two decisions.

That was a major turning point. The more frame control I had, the more the AI became a motion tool rather than a substitute director.

Figure 1: Key visual states from Cyrene's lion fight. By defining the start, intermediate, and end poses myself, I could preserve character position, spear direction, lion scale, and the intended choreography while using AI-assisted animation to bridge the motion between those decisions.

Building a Hybrid Pipeline The production pipeline for Anamnesis eventually involved a mixture of tools and techniques. Pika and Adobe Firefly Video were used primarily for motion generation and experimentation. EDI Studio / EDImaker became particularly useful for character performance, frame-controlled transitions, voice-driven animation, and lip synchronization. Adobe Premiere Pro remained the backbone of the edit, while Audacity handled voice capture, cleanup, and preparation.

ChatGPT functioned less as a single-purpose production tool and more as a kind of chief assistant throughout the project. I used it for story development, still-image generation, problem solving, and rapid technical research whenever I needed to learn a new workflow or troubleshoot a production issue. It helped me get up to speed quickly on tools such as Premiere Pro and Pika and frequently served as the bridge between an idea I knew I wanted to execute and the technical knowledge required to make it happen.

The final film also involved traditional voice performance, sound editing, music, visual effects, and a substantial amount of manual editorial work. What mattered was never whether a particular shot was AI-generated or traditionally edited. The only useful que

LINK:	https://creativecow.net/from-graphic-novel-to-30-minute-animated-film-...
	See more stories from creativecow

More from Creative COW