Redditology / Review / System 03 of 03
2022Recorded work
Creator · experimental side project
Thumbnail review, assembly and recovery
Review the thumbnail, assemble the video and check the actual output when a production step fails.
- Noah’s contribution
- Noah documented queue states, configured thumbnail workflows and investigated media/output failures.
- Historical stage
- Historical operating walkthroughs and test uploads, with manual review and unresolved defects.
- Part of the business
- Redditology overview ↗
- Airtable
- Make
- Google Slides
- CloudConvert
- Transloadit
- YouTube
- GPT-3
- DALL·E
Inside this system
The workflow
The handoffs
inside the work.
Follow the main path and its branches. Select a step for context; the account below explains what was built, tested or planned.
- Post production queue
Expose suitability, thumbnail and overall readiness states in Airtable. - Prepare thumbnail candidate
Use the manual prompt/keyword path or the later AI-assisted variant. - Generated asset states
Inspect the audio, graphic and clip states associated with the post. - Human thumbnail review
Check spacing and overflow, correct the result and mark it ready. - Correct thumbnail layout
Fix the template/output when spacing or text does not fit. - Assemble ordered video
Send ordered clips, thumbnail and publication metadata to the downstream assembly job. - YouTube test upload
Carry the rendered video and its title/description through the upload path. - Inspect final output
Review the published test’s content and metadata; defects still required correction. - Trace a missing or failed output
Check downstream service jobs and asset states even after Make reports success.
Key records
The information
that carries forward.
| Record | Information | Purpose |
|---|---|---|
| Post queue | Selection, thumbnail and overall production states | Expose the operator’s next action. |
| Thumbnail | Image prompt, emphasized phrase and template output | Prepare a visual that can be inspected before use. |
| Generation state | Audio, graphic and video outcomes | Identify which stage produced or failed to produce an asset. |
| Assembly job | Ordered clips, thumbnail and publication metadata | Trace the final conversion and upload handoff. |
Inside the system / 01
Readiness is an operating decision
One operating version used Airtable states for low-quality material, long titles and posts awaiting a thumbnail prompt. Prompt and keyword entry were manual in that walkthrough. Other versions generated a suggested phrase and image prompt from examples using GPT-3, then produced imagery with DALL·E.
Those are evolving versions of the same responsibility. Generating the image did not remove the review gate. The operator inspected the result, corrected spacing or text overflow and marked it ready before it fed the larger sequence.
Inside the system / 02
Inspect the complete path to the output
The asset table exposed audio, graphic and video progress. An operator could manually push a post through a stage when needed. After the individual clips were numbered, the assembly request carried their order and the thumbnail into Transloadit, followed by the YouTube upload path.
The operating guide explained a particularly useful failure case: Make could report success while a later Transloadit job failed. If the video never appeared, the investigation had to continue into the downstream service instead of stopping at the first green status. Conversion credits and automation-operation usage were also practical operating constraints.
Inside the system / 03
Test output made defects visible
Recorded defects included missing replies, thumbnail layout problems, title and description handling, and upload errors. One test upload was deleted during the walkthrough because its description needed correction. That is evidence of output inspection and recovery during development.
Audio normalization was another unfinished area. The separate investigation compared per-comment processing with the desired whole-video result and explored different settings, but did not establish a final loudness solution. A later n8n recreation was blocked on iteration into the required JSON body, with multipart requests still to address.
Inside the system / 04
The experiment’s result
The project combined reusable media generation with ordered assembly and operator controls. A completed generation step still needed a visual check and verification of the final upload.
The project remained an experiment in generated media and workflow orchestration, with manual review and continued development.
Within Redditology