E1 · Environment
5 minClone the course and run the "conferir o ambiente" block.
Done when: The four lines git, python3, node and ffmpeg end in ok, and node --version shows v22 or higher.
Lesson 1 · 12 min
The factory map: from what you have to the right engine
INEMA has one video engine for each case: explainer, demo, documentary, short, publishing. Picking the wrong engine costs hours. In this lesson you turn the table in the Videos area into a command that tells you which one to use, and you get your machine ready for the next seven lessons.
Start the lesson
In this lesson you will
- 1The 14 rows of the "Where to start" table in the Videos area
- 2What every engine has in common: a declared input and a gate before the credit
- 3Check git, Python, Node, and FFmpeg before cloning the engines
- 4In which lesson (or sister course) each engine appears
Goal: pick the right engine for what you have and what you want, with the Videos area table turned into a command.
01From what you have to the engine
Click each step.
Click each block in the diagram to see what it does.
The table comes from the INEMA Videos area (eventos.inema.pro/videos/, "Where to start" section), read on 10/19/2026.
02Three rules that apply to every engine
They are what makes the factory repeatable.
1. Pinned commit
The engines change every week. The labs clone each one from GitHub and check out an exact commit, the same one the lesson's output was captured from.
When you want the new version, change the commit and run the block again: if the output changes, you know it was the engine.
2. Declared input
Each engine reads one file: scenes in JSON, actions.json, a theme in YAML, a script in Markdown. The agent writes that file; the engine does the rest.
Reviewing the file is cheap. Reviewing the finished video is expensive.
3. Gate before credits
Avatar, AI-generated video, and uploading to YouTube sit on the other side of a gate: human approval, a consent form, dry-run mode.
In this course nothing goes past the gate. You learn to get right up to it with everything checked.
Example
explicavideos builds scenes and blocks without touching the avatar studio; only the start command generates video, and --help itself warns about that in capital letters.
03Set up your machine
Clone the course repository into ~/projetos and check the four tools that every lesson uses.
Once · clone the course
mkdir -p ~/projetos && cd ~/projetos git clone https://github.com/inematds/formacao-cinema-ia-fabrica-v72.git
Terminal · check the environment
for c in git python3 node ffmpeg; do printf "%-8s" "$c"; command -v $c > /dev/null && echo ok || echo FALTA; done node --version; ffmpeg -version | head -1 | cut -d' ' -f1-3; python3 --version
Example from the repository
git ok python3 ok node ok ffmpeg ok v24.13.0 ffmpeg version 6.1.1-3ubuntu5 Python 3.12.3
The versions are the ones on this machine. Any Node 22+ and FFmpeg 6+ will do; the line that matters is ok on all four tools.
Install it with your system's package manager (apt, brew) and run the block again. On Windows, run everything inside WSL: the engines call bash, ffmpeg, and Unix paths.
04The table turned into a command
The kit has all 14 rows in qual-motor.py. You pass what you have and what you want; it answers with the engine and the lesson.
Terminal · ask the map
K=~/projetos/formacao-cinema-ia-fabrica-v72/kit python3 "$K/qual-motor.py" --lista | tail -3 python3 "$K/qual-motor.py" tema short; echo "saída: $?" python3 "$K/qual-motor.py" tema podcast; echo "saída: $?"
Example from the repository
frase clipe → musicavideo (fora deste curso (guia da área Vídeos)) video-pronto publicar → yt-pubx (aula 8) 14 linhas Short ou reel 9:16 com gancho Use: MakeShorts ou cardshorts · aprender: aula 5 saída: 0 SEM MOTOR: com 'tema' a tabela tem: explicativo, documentario, short saída: 1
A combination that isn't in the table prints SEM MOTOR and exits with code 1, listing what exists for that input. Use --lista to see the 14 rows.
05The engines in this course and the ones that belong to the siblings
The map covers more than this course teaches. Follow the right link.
1. Here
Explicavideos (lesson 2), video-demonstrativo (lesson 3), docflow and refazvideo (lesson 4), MakeShorts and cardshorts (lesson 5), forja-reel (lesson 6), avatar and consent (lesson 7), yt-pubx (lesson 8).
2. In the siblings
Film with photos and 2.5D camera, and UGC ads: course 2. Brand film from the website: course 5. HyperFrames and Remotion under the hood: course 3.
3. In another program
The 7-step reel, the channel pipeline and the publishing schedule belong to the From chat to agent program: social media on autopilot course.
06Practice
A ready machine and your first case on the map.
E2 · The map answers
5 minRun the "perguntar ao mapa" block.
Done when: The output has 14 linhas, Use: MakeShorts ou cardshorts · aprender: aula 5 with saída: 0 and SEM MOTOR: com 'tema' a tabela tem: explicativo, documentario, short with saída: 1.
E3 · Your case
5 minThink of the next video you need to make. Find its line with --lista and ask the map.
Done when: python3 ~/projetos/formacao-cinema-ia-fabrica-v72/kit/qual-motor.py [tenho] [quero]; echo "saída: $?" → one Use: … line and saída: 0.
07Lesson quiz
The explanation appears after you answer.
Question 1 of 4
You have the link to your app and want to show how to use it. Which engine?
Correct
The line "O link do seu app → Demonstração narrada, clique a clique" points to video-demonstrativo (lesson 3). explicavideos starts from a topic, not from a live app.Not that one
The line "O link do seu app → Demonstração narrada, clique a clique" points to video-demonstrativo (lesson 3). explicavideos starts from a topic, not from a live app.Review: Set up your machineQuestion 2 of 4
Why do the practices clone each engine at a fixed commit?
Correct
The engines change every week. With a fixed commit, the block gives the same captured output; if it changes after you switch the commit, the difference came from the engine.Not that one
The engines change every week. With a fixed commit, the block gives the same captured output; if it changes after you switch the commit, the difference came from the engine.Review: Three rules that apply to every engineQuestion 3 of 4
What is the "gate before credits" in this course?
Correct
Avatar, AI-generated video and the YouTube upload sit behind a gate (approval, consent form, dry run mode). The practices get up to it with the output checked, and stop.Not that one
Avatar, AI-generated video and the YouTube upload sit behind a gate (approval, consent form, dry run mode). The practices get up to it with the output checked, and stop.Review: From what you have to the engineQuestion 4 of 4
You want a 7-step reel with a publishing schedule. Where do you learn it?
Correct
The 7-step reel and the channel pipeline belong to do-chat-ao-agente-redes-v72. Here, lesson 5 handles only the hook and the quality gate of the short.Not that one
The 7-step reel and the channel pipeline belong to do-chat-ao-agente-redes-v72. Here, lesson 5 handles only the hook and the quality gate of the short.Review: Three rules that apply to every engineQuiz complete
You got {a} of {n} right. Get them all right and the lesson is marked as done.Pick an option. The explanation appears after you answer.
08In three sentences
Mapwhat you have and what you want decide the engine; qual-motor.py answers.
Pinned commiteach practice clones the engine at an exact commit so the output holds.
Gatethe practice stops where the engine would spend credits or publish.