Manual · Overview
Manual
The complete operating reference for AI Art Engine 7.3, organized into six parts by workflow. This page covers preparation and core concepts; everything else is under “Manual chapters” below or in the sidebar. Wording follows the in-app UI — switch the app to English under Settings → General → Language. Video walkthroughs are on Bilibili.
1. Overview & preparation
AIArtEngine is an agent-native AI art asset engine for short drama, advertising, games and e-commerce. Projects and media live in a local directory you choose; text / image / video / audio generation runs through the model providers you configure (OpenRouter, OpenAI, DeepSeek, Zhipu, Kimi, xAI, Google, vLLM, Ollama, LM Studio, Volcengine Ark, Kling, MiniMax, Tongyi Qianwen, ModelScope, ComfyUI, MagicRouter, …), and 3D model generation supports Meshy, Tripo, Rodin (Hyper3D), Luma AI and Lux3D. Spatial world generation (turning text or reference images into an explorable 3D world) supports World Labs (Marble). OpenRouter additionally offers decision models (the Decisions API), configured per modality like text / image / video. Use One-Click Workflow to turn a template or a plain-language request into a reusable host asset, then drag it onto the canvas to keep building.
First-time setup
- Install the package for your platform from the download page or GitHub Releases.
- After launching, open Settings, add a model provider with its key, then fetch and tick the models you want.
- (Optional) Under Object storage configure Volcengine TOS / Alibaba Cloud OSS / Tencent Cloud COS / Amazon S3–compatible (only one can be enabled at a time) so large files such as reference videos can be exposed as URLs.
- Back on the home page, create a project and enter the workspace; try “One-Click Workflow” in the top bar, or create a script / shot the traditional way.
2. Core concepts
Spend two minutes on the words below and every screen afterwards will make sense. Data in this app is organized as project → shot / episode → node graph → asset: the project is the container, the node graph is the workshop, and assets are what comes out of it.
Project
Everything that belongs to one piece of work, stored in a local directory you pick
yourself, with project.json at its root. Media never leaves your
machine — copy the whole folder to move to another computer.
Asset
The umbrella term for every output and piece of media in a project: scripts, beat tables, storyboard images, anchor images, video, audio, 3D models and host assets. Browse and drag them all from the asset library.
Host asset
A reusable component produced by One-Click Workflow. The outside exposes only boundary inputs / outputs, while double-clicking dives into the full inner node graph for fine-tuning. Build once, reuse across projects.
Node graph
The canvas where nodes and links describe “input → generate → output”. It is the shared foundation of scripts, shots, canvases, the director stage and host assets.
Port
A node's inlet or outlet. Ports strictly distinguish singular from plural:
image / images, video / videos,
text / texts. Different types never connect, and
singular can't go into plural. Round ports are usually a single
out; square ports are lists (out-all).
Episode / shot / beat
An episode is made of several shots; a script is first
split into a beat breakdown table, then landed onto concrete shots. These
use the dedicated port types world / worldEntities /
beat, which must not be mixed with plain text.
Anchor image
A single reference image split out of a 9-grid / 4-grid sheet, cell by cell. It locks a character's face, outfit and setting so every later storyboard stays consistent — this is the key to keeping a short drama from “changing faces”.
World element
A reusable setting entry: character, scene, prop. Attached to an episode and shared by every shot, so you don't re-describe the same thing in every setup — another way to keep consistency.
Director stage
A 3D stage: place models, light the scene and frame the camera, then
capture blocking shots or record motion video, which come
out of the two square ports out-shots / out-actions.
Final timeline
A multi-track editing panel: drag node outputs or imported media onto tracks, arrange the order, line up audio, then preview and export the finished film.
Asset package .aipackage
A format that packages assets together with their dependencies for export, so you can migrate to another machine or share with collaborators — importing restores everything as it was.
2.1 How a short drama actually runs
With the concepts above in place, the full data flow of the short-drama pipeline reads:
- Script → broken down by a text model into a beat breakdown table (beat).
- Beat → 9-grid storyboard table: one node generates a 3×3 sheet, then 9 anchor images are split out cell by cell and upscaled.
- Anchor images → 4-grid motion storyboard table: 2×2 sheets per group, split into 36 motion cells and upscaled.
- Motion cells → motion prompt table (36 entries) → 36 motion videos.
- Four director review nodes, review1~review4, sit along the way; anything below standard can be sent back for a re-run.
- Videos → arranged on the final timeline → export the finished film.
Manual chapters
Read them in workflow order, or jump straight to the part you need.