Video yükleniyor...

Video Yüklenemedi

Ana Sayfaya Dön

Straight from AI video production #10 Describe the LIGHT. It's the difference between a snapshot and cinema. Light isn't a background info but it's the emotion of the shot. The same scene reads tender, threatening or nostalgic depending on nothing but the lighting you write. Leave it out and...

12,104 görüntüleme • 2 ay önce •via X (Twitter)

13 Yorum

HOON profil fotoğrafı
HOON2 ay önce

Sorry for what I did to you guys 😅 @Amystreet @NickyScanz @niran7 @Pedromiranda @mert @therealchaseeb @vibhu @VibNorman @rajgokal @toly

QV profil fotoğrafı
QV2 ay önce

VibNorman character design here is 🔥

HOON profil fotoğrafı
HOON2 ay önce

What do you think @VibNorman

chase profil fotoğrafı
chase2 ay önce

@o00Q00o @VibNorman We should kill him off soon

QV profil fotoğrafı
QV2 ay önce

@HOONIGALL @VibNorman 😭

simon (blkn/acc) profil fotoğrafı
simon (blkn/acc)2 ay önce

ok very bullish on the idea of creating commercials and videos for a fraction of the cost of what old hollywood is paying

Squig (GME arc) profil fotoğrafı
Squig (GME arc)2 ay önce

banger!!

MartinVMorales profil fotoğrafı
MartinVMorales2 ay önce

this is getting way better w time 🔥

naman profil fotoğrafı
naman2 ay önce

is this what being on acid feels like?

HOON profil fotoğrafı
HOON2 ay önce

Sometimes I feel like I'm permanently on LSD with all the things in my head 😂

BM profil fotoğrafı
BM2 ay önce

was this one prompt? one generation?

HOON profil fotoğrafı
HOON2 ay önce

No It's multishots mixed with continued shots edited together

Ahmed Bagatov profil fotoğrafı
Ahmed Bagatov1 ay önce

Who's singing?

Benzer Videolar

📖THE JSON PROMPT TRICK THAT TURNS SEEDANCE 2.0 INTO A FILM STUDIO Everyone uses the same tool. Almost nobody uses it the right way. The difference isn't talent. It's structure. A normal prompt tells the model what to show. A JSON prompt tells it how to think — what the camera is doing, where the light is coming from, how fast the scene breathes, what emotional weight the color carries. Look at the pink ceremonial elephant rising from the water at golden hour. Normal prompt gives you an impressive creature. JSON gives you a frame that feels like it was pulled from a $40M fantasy film — the texture on the skin, the mist sitting low on the water, the way the warm light wraps around the gold ornaments. Same concept. One prompt format separates the two outputs completely. The Aztec jaguar in the jungle — normal prompt renders the creature. JSON builds the world around it. The glowing sun symbol on its chest, the waterfall in the background catching green light, the low camera angle that makes it feel genuinely threatening. Structure is the skill. The tool is just executing what you give it. • Step 1 — Describe your scene in one sentence, exactly what you see in your head • Step 2 — Open Claude and ask it to convert your sentence into a JSON prompt with these fields: subject, setting, camera angle, light source, texture detail, emotional tone, motion type, color palette • Step 3 — Paste the JSON directly into Seedance 2.0 and generate three variations • Step 4 — Take the strongest clip into CapCut or Premiere Pro, add ambient sound, and export The output gap between these two approaches is not small. It's the difference between content that gets scrolled past and content that gets saved 📥A different AI opportunity lands tomorrow. This one surprised me too. 🔖The full guide is waiting below. The creators who find it first win.

Zentrix⌚️

22,088 görüntüleme • 3 ay önce

context engineering vs graph engineering. every few months the list gets a new word and everyone treats it as a replacement for the last one. these two are not on the same list. one decides what the model sees this turn, the other decides what exists at all. the cleanest way to tell them apart is to ask what a single unit of work looks like. > context engineering is the window the window opens empty, every single time. you assemble what goes in it. the prompt, the docs, the history, the tool results. the assembling is the work. the window only grows. it never shrinks on its own, so eventually something gets dropped. usually from the middle. usually without telling you. then the turn ends and the window is thrown away. not archived, thrown away. the next turn opens empty again and you re-explain what you already explained. good context engineering is knowing what to leave out, not what to pack in. the unit of work is one window. > graph engineering is the structure the same material arrives from the same sources. instead of packing it into a window, you pull entities out of it, resolve the duplicates into one node, and write typed edges between them. nothing here is stored as text you hope to find again. it is stored as a thing with a name and its connections to other things. when the turn ends, the graph is still there. the next turn does not start from zero. it starts by querying what already exists, and the query walks edges instead of guessing at similarity. good graph engineering is deciding what counts as the same thing twice. the unit of work is one relationship. > they are not alternatives the graph is what refills the window. context engineering decides what fits. graph engineering decides what there is to choose from. remove the graph and every session starts blind. remove the context work and the best structure in the world arrives as an unreadable dump. that also tells you which one broke. the answer drifted from what you actually said, or forgot something from this same session. that is the window. the answer is coherent but invents a connection that does not exist, or cannot join two facts it has clearly seen. that is the structure. people debug the prompt because the prompt is the easiest thing to edit. it keeps taking the blame for failures that live a layer down. save this - then read the full breakdown below

Hanako

19,160 görüntüleme • 2 ay önce