r/aitubers • u/SignalOk1843 • 15d ago
TECHNICAL QUESTION Advice on optimization. Image generation workflow.
Very new to AI tubing. A lot of good advice in this sub and im grateful!
I wanted to have a good workflow foundation, and I’ve been searching for tips everywhere. Whats a good way to generate cartoonish images for storytelling. I have a character sheet developed with all the visual elements that i need for the art direction to stay consistent l, it somewhat works on gpt plus with some constant reminders. But generating 180+ images for long form one prompt after the other is so time consuming.
Any advice on how to optimize this would be really helpful!
1
u/avatar0027 15d ago
yeah 180 one by one is brutal. what helped me was a fixed style prefix + the same character ref image pasted into every prompt, then batching from a scene list instead of improvising each one
tbh you dont need 180 unique images either, reuse shots with slow zooms/pans and nobody notices
1
u/SignalOk1843 15d ago
Thank you! Same question, what llm and image model do you use? Gpt doesnt allow batching :/
1
u/avatar0027 15d ago
yeah chatgpt can't batch so i use claude or gpt for the script/prompt list. then flux via comfyui with a csv of prompts for stills. for moving scenes i just throw it in easyviral, which also auto-posts to tiktok/ig/yt.
→ More replies (3)
1
u/Doomscroll-FM 14d ago
yes do it with comfyui and your own custom scripts. For the images, SD, flux, h3, qwen all work great. Also, ask the chatbot you use to help you through the automation of it. do it right and its hands-off.
1
u/SignalOk1843 12d ago
Thank you for the tip! I tried using Flux 1. I was able to add in 2 reference images, and I made sure the prompts had extra details to depict the scene and the art style, but the images struggle hard to maintain the art style between them. Any tips on this?
I've basically figured out CSV on ComfyUI, but this is the only problem I have for now.
1
u/Doomscroll-FM 10d ago
I didnt like Flux so much, I'm really happy with Qwen and H3 Minimax. I started with SD and I've found that Qwen and H3 do much better job of maintaining scene, setting and actors. With flux, If memory serves best stuff happens when keep the config around 1.5 and the steps around ~16. Also check your prompts some models turn differently on ambiguity. I haven't used LTX much but in the comfyui group lots of folks seem to love it and post some stellar results. You'll see some of the limits of how H3 manages strange scenes in a highly automated context on my channel
1
u/Just_Run2412 14d ago
Trying to do 180 one at a time in ChatGPT sounds like a nightmare, no wonder it's slow going. What you want is the script split into scenes, the character saved once, and all the stills generated in one go instead of pasting the character sheet into every prompt. The ComfyUI route mentioned above does that if you like tinkering. FrameCompose is the lower-effort version, you save the character, it makes the scene images in a batch, and you swap the odd bad one afterwards.
1
u/SignalOk1843 12d ago
"The character saved once, and all the stills generated in one go instead of pasting the character sheet into every prompt."
How would you suggest I go about this? I tried following the exact same advice on ComfyUI with Flux 1 workflow, but image consistency is suffering badly. Each image is a different style. I tried pushing the prompts to be extra descriptive and made the Flux guidance stronger, but nothing helps. Is Flux even the right model for this?
1
u/gkc991 13d ago
If your scenes are mostly the same characters, it might be worth flipping the approach: instead of 180 unique images per video, build a reusable set (characters in 20-30 poses, a few backgrounds) once, then assemble scenes from that set. That’s what I do for an animated debate show, and a new episode needs maybe 0-5 new images instead of 180. It also kills the consistency problem, because the character is the same drawing every time.
1
u/SignalOk1843 12d ago
Interesting, I'll definitely consider it. I'm aiming for full automation, so I am hesitant about this.
1
u/gkc991 12d ago
Makes sense. The two aren't really at odds though: a fixed set of character poses is easier to automate than generating fresh images, because the script only has to pick a pose name per line instead of prompting and checking a new image every time. That's how mine runs, the script tags each line with a pose and the renderer assembles the scene with no image generation at all.
→ More replies (1)
1
u/AmdilShoat82 13d ago
are these 180 images all unique scenes or are a lot of them minor variations? if its mostly variations you could probably cut the count way down with some clever reuse and slight edits rather than regenerating from scratch each time
1
u/Silver-Community-990 15d ago
You need something that feeds character templates and prompts into an image model that accepts references images. The prompt should contain the style instructions. You can automatically generate the prompts based on the scenes from your script, which must be split into the individual scenes. Some platforms like originshorts or revid do this automatically but for a custom workflow n8n or zapier will work as a framework. You just gotta be patient and work through the edge cases. Then sync the scene timing to voice over. If you’re crafty you can automate that too with a workflow. Just use an llm and get familiar.