From 73f521c404da26b32e78d260e79d049170d4500c Mon Sep 17 00:00:00 2001
From: adam <adam@noreply.localhost>
Date: Fri, 2 Aug 2024 15:18:25 -0400
Subject: [PATCH] Update 'process'

---
 process.md | 64 +++++++++++++++++++++++++++++++++++++++++++++++++-----
 1 file changed, 58 insertions(+), 6 deletions(-)

diff --git a/process.md b/process.md
index 07ee75f..5d1fd3f 100644
--- a/process.md
+++ b/process.md
@@ -1,6 +1,58 @@
-# Process
-
-1. make a ticket (tagged Video) on the videos kanban https://gitea.arg.rip/beefhavers/_management/projects/7
-1. initialize bookkeeping (this step can be slash should be much more automated)
-1. write script - use placeholderVO
-1. editing phase
\ No newline at end of file
+# Process
+
+## make a ticket
+(tagged Video) on the videos kanban https://gitea.arg.rip/beefhavers/_management/projects/7
+
+## initialize bookkeeping
+
+1. make a repo under beefhavers. note to self, make a template repo that has script.md and credits.txt
+1. make a matrix room
+1. hook that matrix room up to that repo
+1. pull the repo on your computers, to start working
+1. make a jenkins flow. I would like nightly renders when .blends are changed, and when script.md is updated
+
+## write script
+
+make use of placeholder VO to hear it spoken back to you. Do as much conceptualizing as possible here.
+
+## financial commitment
+
+i.e., spend money on a voice actor. with "what apple hath wrought" we tried to move this to the end of production. It caused problems (gave me an entirely new editing pass to undo my old work on timings), and brought me zero benefit. This is a good place to leave a script to languish, ideally while you do your real job.
+
+## production proper
+
+once the VO is back, we begin editing in earnest. When I had an editor, I had her send me a render 2x/week. But she used capcut (boo).
+
+### drop in script elements
+
+VO, then split it up with title cards
+
+### flesh out with visual aids/etc
+
+it's surprising how long this takes 😅 but this is also the creative part, so it can't be automated
+
+### drop in a-roll and meta-plot
+
+I predict a lot of "i wrote this in the summer so now I need winter a-roll", and vice versa
+
+### crediting pass
+
+sort the credits by appearance order, strip out the unused ones, and start generating and dropping in crediting cards. Actually you should probably do this whenever you drop something in, or move it around. :thinking: 
+
+## finalization
+
+### description.txt
+
+what description will be going up? usually just a tagline, special credits (voice actor, editor), credits.txt, and colocation links
+
+### thumbnail
+
+youtube won't let you, but peertube and rumble will.
+
+## ship it
+
+upload, promote, party!
+
+## post-mortem
+
+toss those notes in its matrix room (and wherever else). it's a bit of a strange practice since you're a 1-man team, but it's always good to take time to reflect.
\ No newline at end of file