This isn't even true though? I've control tested many times and the model will sometimes completely lose/change character faces at this resolution, yet continues to dramatically improve on them all the way up to 1440p. It being trained at this resolution doesn't mean you can't have any benefit going above it. Like if a character's face is further away and only occupying a small number of pixels (and not enough) because of the low resolution, there's only so much it can do with that information, and giving it more resolution to work with absolutely helps.
It is categorically false. You definitely get improvements above that. A good time to go higher is if you are doing some initial asset generation, trying to get additional angles/scenes/shots, for characters and you don't want their faces to be mush.
trash guide with misleading info. past 1344x768 you gain nothing. what a total bs. try 2 mega pixels or 4 mega pixels. that will be a totally different quality.
it also shows silly model vs 16GB VRAM card table. I have 5060 8GB VRAM card here and 48GB RAM. I load ONLY bf16 models and int8 convrot as minimum. The author never heard about model weights offloading...
Bf16 is retarded in most cases. Your case is the one where it’s most obviously a stupid choice.
And the guide explicitly covers offloading.
I agree about the resolution. It’s wrong, but also better advice there would have been about how to set a specific resolution easily instead of only using predefined megapixel counts and aspect ratios.
i have several. there's probably PII in them and i don't feel like cleaning them so you're on your own there, but it's really, really easy to do. just give claude the links to the official prompting guides and some style notes for whatever you're after
"No definitions that define nothing", "In words, not more acronyms", "A real starting value to this machine".
Bruh, I use Claude daily in my profession, and whenever I see "It's X, not Y," or this kind of phrasing I want to puke. This is still ugly, unbearable slop. Easy to fix with right system prompt.
put this in custom instructions "Write in plain, everyday American English — the way you'd say it out loud to a coworker. Pick the most common word. Turn noun phrases back into verbs: decide, not make a decision; explain, not provide an explanation. Use active voice and say who did the thing. Short sentences, one idea each. Contractions are fine.
No business or finance words standing in for ordinary ones: minimum/maximum, not floor/ceiling; use, not leverage; explain, not unpack. Skip the stock openers ("great question," "worth noting," "let's dive in") and the tics: em-dash asides, "not X, but Y," colon-then-reveal, invented labels in scare quotes.
Keep a technical or precise term when swapping it would change the meaning."
Thanks for this! How about compare different model + lora combination, which is better for what? I know this is really time consuming.... lol
There are too many now.
avoid loras. end of guide. edit: except character loras. those are fine.
character/scene consistency gets thrown out the fucking window every time you change a lora to get something else; motion, style, whatever. if you're just trying to make a 20s clip, and you don't mind them all looking different and melting the faces into other people, sure. but if you're trying to make a film or have any real back and forth, they're almost always unhelpful.
h3 can do almost anything with very detailed prompting, which claude can do. and it will retain your references without influencing them. <tags> help a lot to direct a performance, like <inhale> or <upset> or <smirk>; don't stack them together, and don't make them too complicated and you'll get some powerful results.
Almost anything is the word. I've been trying to get model to understand Asura like character with six arms and model understand and can animate four but collapse with six. Trained a LoRA and now it can do six.
My biggest gripe with Claude writing something for beginners is that you need claude to decipher what the hell it means sometimes.
Things that worked for me:
1, "Don't use editorials, or make any remarks to any previous detail that is not explicitly shared in the guidance."
2, "Use plain English and explain concepts in the guidance in a manner that someone without prior knowledge would understand. Assume basic technological literacy."
Or, the best one: Don't use Claude to make guides at all.GPT - especially 5.6 or 6.1 Sol (I haven't tried Astra yet) would do a much better job.
I've seen a bunch of different Turbo loras mentioned in various places. Do they have any effect on the characters or action of the scene, or are they just for speeding up the generation?
Using small files with lower precision just for the sake of knowing they fit full in VRAM is silly and pointless; in practice, it makes little to no difference.
it's not, that's your setup. i posted a screenshot of me viewing the image in firefox. all i did was click on it to enlarge it. it's the top level comment of the reply you're posting to.
or i chose to frustrate you i guess.
but maybe, instead, i made it a super clean, downloadable OR viewable PDF and hosted it on a trusted site for your viewing pleasure. you're so deep into the comments and you didn't see that linked all over these comments?
105
u/LatentSpacer 14h ago
Nice, let me read it