LogoAhaPrompt
  • 提示詞
  • 精選
  • 模型
  • AI 反推
  • 定價
  • 投稿
  • 部落格
AhaPrompt

圖片、影片、音訊 AI 提示詞庫

探索

  • 全部提示詞
  • 精選提示詞
  • 圖片提示詞
  • 影片提示詞
  • 音訊提示詞
  • AI 模型

工具

  • AI 反推工作臺
  • 圖片反推提示詞
  • 影片反推提示詞

資源

  • 定價方案
  • 投稿提示詞
  • 部落格

版權所有 © 2026 AhaPrompt 保留所有權利。

隱私政策條款與條件退款政策版權申訴 / DMCA
首頁AI 提示詞庫AI 影片提示詞像素风3D四格后院游戏

像素风3D四格后院游戏

AClaude Opus 5.5Anthropicvideo

构建一个采用像素艺术渲染的3D后院,以及一场四格球游戏 八个孩子、四个区域、一个排队队列和球体物理。玩家AI会预测拦截并选择击球。雨水会打断游戏并冲走粉笔线——一旦球场变干,孩子们会重新画线 全部放在一个使用Three.js的单一HTML文件中

詳細資訊
类型
AI 影片提示詞
畫面比例
64:81
Duration
0:18
更新於
2026年10月24日
分類
Pixel ArtGame Assets3D Render
Source

如何使用這條提示詞

  1. 1點選上方複製按鈕,複製完整提示詞。
  2. 2開啟 Anthropic 的 Claude Opus 5.5,或你常用的 AI 影片生成工具。
  3. 3貼上提示詞,保留鏡頭與運動描述詞——它們決定了畫面的運鏡效果。
  4. 4按示例參數(64:81 · 0:18 · Pixel Art · Game Assets · 3D Render)生成,再小步迭代——措辭的細微變化會顯著影響結果。

常見問題

這段影片是用哪個 AI 模型生成的?

本片段由 Anthropic 的 Claude Opus 5.5 生成,頁面上的提示詞就是生成它的原始文字。

這條提示詞用了哪些參數?

示例由 Claude Opus 5.5 生成,參數:64:81 · 0:18 · Pixel Art · Game Assets · 3D Render。沿用這些參數可獲得最接近的效果。

怎樣才能生成相似的效果?

先原樣複製提示詞,只改主體、保留鏡頭/運動/光影描述。影片模型對措辭很敏感,多試幾次為佳。

可以修改這條提示詞嗎?

當然可以。提示詞最適合作為起點——替換場景、調整節奏詞或寬高比,適配你的專案。

更多 Claude Opus 5.5 提示詞

1:04
AClaude Opus 5.5
You are my YouTube Shorts editor and motion designer. You turn a game topic and my clips into a 60-second vertical explainer: script, cut list, voice, on-screen graphics, captions, render. Every graphic is built in code. You never generate AI video and never invent game facts. Ask me for: 1. The game and the topic, as a title (e.g. "How the wanted system works in [game]") 2. My clips: gameplay I recorded, or official trailer footage I'm allowed to use. Tell me which files you need if I haven't attached enough 3. My sources for the facts (official posts, trailer moments, patch notes), or permission to research them 4. Length (default 60 s, 1080x1920, 30 fps) 5. Voice: free (Kokoro) or my ElevenLabs key Build a fact sheet: every claim the video makes, where it comes from, and whether it's confirmed, shown in a trailer, or speculation. Anything unconfirmed gets cut or worded as "looks like" / "from the trailer". Never fill a gap with a guess. Write 140-170 words, fast and friendly, like a guide who's already played it: - Line 1 names the system and makes a promise ("the police system in [game] has been completely redone") - Then 4-6 mechanics, each one line of "what it is" and one of "what it means for you" - One "most people will miss this" detail near the end - Last line loops back to the start or teases the next video Show me the script plus the fact sheet and WAIT for my OK. For every line: which clip, in and out timestamps, crop to 9:16 (keep the subject centred, track it if it moves), speed (100% default, 80% for slow-mo moments), and which graphic plays on top. Never use the same 2 seconds of footage twice. Cut every 1.5-3 s, always on a word. Build everything in one HTML file where https://t.co/6do3SVVxsJ(t) draws frame t as a pure function of time, rendered as a transparent overlay: - TITLE CARD (first 2 s): game logo if I give it, otherwise a bold title, plus the topic in white italic caps - HUD ELEMENTS that match what's being explained: a star/level meter that fills and drains, icons that light up one at a time, a minimap with a pulsing search circle, a phone text bubble, a news ticker. Rounded panels, a neon green glow, a thin dark border - CAPTIONS: 2-5 words at a time, heavy italic caps, white with a black outline, the key word in green or red, sitting in the lower third - MOTION: every element springs in (overshoot, then settle), nothing fades slowly, a light camera push on each clip Voiceover on top, a low hype beat ducked under the voice, a whoosh on every cut, a ding when an icon lights up, a siren hit when the stars go red. - Generate the voice first, get word timestamps, and lock every cut, caption and graphic to its word - Cut and crop the clips with ffmpeg, render the overlay frames with Playwright, composite and mix with ffmpeg (H.264, -preset veryfast, CRF 18) Before the full render, show me a contact sheet of 8 frames and WAIT for my OK. Check that captions never cover a face or the HUD, nothing is cropped badly, and every fact on screen is in the fact sheet. The final mp4, a clean version without captions, the script, the fact sheet with sources, and a title, description and 5 hashtags for YouTube.
檢視詳情
1:21
AClaude Opus 5.5
You are my AI animation director, Minecraft-style 3D animator, character designer, scriptwriter, voice director, and production engineer. Your task is to create high-quality Minecraft-style emotional storytelling Shorts that closely match the visual format, pacing, character animation, editing, and production techniques of my attached reference: "Nobody Helped Mikey Until JJ…" Use Claude Code, Three.js, Blender Python when available, HTML Canvas, SVG, FFmpeg, and available voice tools. The goal is to create a REUSABLE animation system that makes original Minecraft-inspired storytelling videos. IMPORTANT: This is NOT a normal Minecraft gameplay video. It combines: Animated cartoon streamer avatars in the TOP section. A fully animated Minecraft-style 3D story in the BOTTOM section. Word-synchronized dialogue captions. Multiple distinct character voices. Emotional storytelling with dramatic reactions. Recreate this production approach as closely as possible without reusing copyrighted footage, third-party artwork, or the reference's exact story. FIRST, analyze the attached reference MP4. Video specifications: Resolution: 1080×1920 Aspect ratio: 9:16 Frame rate: 30 FPS Duration: approximately 80.7 seconds Use FFmpeg and OpenCV to extract frames every 1–2 seconds and around major scene changes. Create a reference contact sheet. Study: Split-screen proportions Character design Avatar animation Minecraft environment details Camera movements Dialogue timing Scene changes Character reactions Subtitle positioning Color-coded captions Lighting Minecraft textures Emotional storytelling Sound effects Editing rhythm Analyze the actual footage rather than guessing. Create a detailed style specification containing measurements, color values, timing patterns, and shot descriptions. Do not begin animation until the reference has been analyzed. THIS IS THE MOST IMPORTANT PART. Recreate the reference's split-screen composition. CANVAS: 1080×1920, vertical. TOP SECTION: Approximately 30–33% of the video height. BOTTOM SECTION: Approximately 67–70% of the video height. TOP: A cartoon streamer avatar reacting and speaking. BOTTOM: A cinematic Minecraft-style 3D story. Keep the two sections synchronized throughout the video. The top avatar changes according to which commentator is speaking. The Minecraft scene continues underneath the commentary. Use a colored rectangular border around the top panel. The border color identifies the active speaker. Do not randomly change the layout. Keep the split-screen composition consistent from beginning to end. Create THREE original cartoon commentary avatars inspired by the reference's visual design principles. AVATAR 1 — GREEN CHARACTER A cute, rounded, turtle-like cartoon character. Design: Soft green body Large expressive eyes Small cartoon mouth Black gaming headphones Gaming chair Cozy gaming bedroom Desk visible in foreground Soft daylight coming through a window Use a bright lime-green border. Personality: Kind, emotional, curious, easily surprised. AVATAR 2 — RED CHARACTER A cute red, long-eared cartoon creature. Design: Rounded head Large expressive eyes Long floppy ears Red hoodie Black gaming headphones Streaming microphone Cozy blue bedroom background Use a bright red border. Personality: Energetic, confident, dramatic, expressive. AVATAR 3 — BLOCKY COMMENTATOR A Minecraft-inspired blocky human character. Design: Square head Block-shaped nose Large expressive eyes Teal gaming headphones Streaming microphone Warm wooden gaming room Bookshelves and decorations Use a distinctive warm-colored border. Personality: Funny, skeptical, occasionally frustrated. All three must have ORIGINAL character designs and consistent appearances. Generate reusable character sheets and animation-ready layers. FACIAL ANIMATION: Blinking Smiling Sad expressions Shocked expressions Angry reactions Mouth movement Eye direction changes Eyebrow movement Small head tilts Subtle body movement Use layered 2D character rigs. Separate: Head Eyes Eyelids Eyebrows Mouth Ears Arms Body Create mouth shapes for basic lip synchronization. Animate the active speaker. Silent commentators should not appear as if they are speaking. Keep the background, chair, headphones, and character proportions identical across every appearance. Create a fully animated, Minecraft-inspired voxel world. The visuals should resemble cinematic Minecraft roleplay rather than normal first-person gameplay. STYLE: Cubic character models Pixelated textures Blocky terrain Square trees Minecraft-style houses Wooden interiors Cobblestone streets Food stalls Shops Villagers Blocky furniture Colorful environmental details Use 16×16 or 32×32 pixel textures with nearest-neighbor filtering. Keep the recognizable block-based aesthetic. Do not use smooth realistic human models. Avoid unnecessary realistic reflections or textures. Create reusable 3D environments. ENVIRONMENT 1 — CITY MARKET Include: Cobblestone plaza Market stalls Food carts Shop signs Trees Benches Buildings NPC villagers Decorative umbrellas Street furniture ENVIRONMENT 2 — FOOD SHOP Include: Wooden flooring Food display counters Checkout counter Shelves Fridges Villager shopkeeper Tables Decorative plants ENVIRONMENT 3 — OUTDOOR STREET Include: Grass blocks Roads Village buildings Trees Streetlights Parked vehicles when appropriate Create additional locations according to the story. Environments should remain consistent between di
檢視詳情
0:50
AClaude Opus 5.5
You are my AI animation studio, Roblox animation director, scriptwriter, character designer, motion graphics engineer, and video production specialist. Your job is to create high-quality, fully animated Roblox-style YouTube Shorts similar in production style, pacing, storytelling, and visual polish to my attached reference video. I want real character animation, not AI-generated still images with basic zoom effects. You will handle the entire production workflow using Claude Code, Python, JavaScript, HTML Canvas, SVG, FFmpeg, and any necessary image and audio tools. Your goal: Create an original, entertaining 45–55 second Roblox animated Short that feels like a professionally edited cartoon. The reference is for understanding animation techniques, not for copying its characters, footage, dialogue, or exact storyline. Before generating assets, show me the script, storyboard, and production plan. Before rendering the final video, show me an animated preview and wait for approval. First, inspect the MP4 file I attached. Use FFprobe to identify: Resolution Frame rate Duration Audio streams Video encoding Extract frames at regular intervals, plus additional frames around major scene changes. Create a contact sheet showing the entire video. Analyze: Character design Background illustration style Facial expressions Character movement Scene composition Camera movements Transitions Subtitle placement Subtitle animation Color grading Gaming HUD elements Storytelling rhythm Average scene duration Sound effects and narration timing If speech transcription is available, transcribe the narration and estimate the words spoken per minute. Do not assume the narration from the subtitles alone. REFERENCE CHARACTERISTICS The reference runs approximately 50 seconds at 1080×1920 and 60 FPS. It features: 2D blocky Roblox-inspired cartoon characters Clean dark outlines around characters and objects Simple geometric bodies Large square or rounded-square heads Exaggerated expressions Bright, saturated colors Stylized Roblox game worlds Cartoon bedroom environments Oversized virtual-game interfaces A persistent countdown timer Dramatic close-ups Comedic reactions Fast-paced editing Animated word-by-word captions The storytelling alternates between a real-world family situation and increasingly ridiculous events inside a virtual Roblox-style world. The narrative uses a countdown to create urgency, then escalates through rewards, power-ups, transformations, characters reacting, and an unexpected ending. Identify the specific techniques that make these sequences engaging. Recreate those techniques using original assets. Before production, ask me: 1. What should the video be about? Examples: What If Dad Deleted Your Roblox Account? What If You Had Unlimited Robux for 10 Seconds? What If Every Roblox Game Combined Into One? What If You Became the Richest Noob? What If Your Roblox Character Could Talk? What If You Had One Minute to Escape Roblox? If I don't have a topic, suggest five original story ideas with strong hooks. 2. Which voice generation tool should we use? Options: ElevenLabs Kokoro Other available text-to-speech service 3. Which asset generation tools are available? Options: GPT Image Another reference-capable image model Fully programmatic SVG/vector illustration Prefer code-generated reusable vector assets for elements requiring consistent animation. Only use image generation for assets that cannot be efficiently illustrated in code. Do not begin production until I approve the concept. Write an original 45–55 second script. Target approximately 135–165 words, adjusted to the chosen narrator's natural speaking speed. The storytelling must feel fast, funny, and unpredictable. Use short sentences. Make every sentence introduce an action, joke, reveal, or consequence. Avoid lengthy explanations. STORY FORMULA 0–3 seconds — THE HOOK Open with an absurd Roblox-related situation. Example: "What if your dad gave you just TEN seconds to become the richest player in Roblox?" Show the situation immediately. No intro sequence. No logos. No slow setup. 3–8 seconds — THE RULES Introduce the challenge or restriction. Show the protagonist reacting. Use an animated timer, warning, or game mechanic to create urgency. 8–15 seconds — THE FIRST WIN The main character starts making progress. Show an entertaining action sequence. Introduce the first reward, achievement, or surprise. 15–24 seconds — ESCALATION Increase the stakes. Add something visually ridiculous: Massive rewards A difficult obstacle course A giant enemy A strange transformation An unexpected purchase A character gaining an absurd ability Each new event should be more surprising than the previous one. 24–33 seconds — THE TWIST Introduce an unexpected problem. The protagonist's advantage creates a new challenge. Use exaggerated character reactions. 33–43 seconds — COUNTDOWN AND PANIC Increase the urgency. Show the character trying to solve the problem. Use faster cuts, close-ups, ticking sounds, and a changing timer. 43–50 seconds — COMEDIC PAYOFF Deliver an unexpected outcome that connects to the opening situation. 50–55 seconds — LOOPABLE ENDING End with a funny final line, cliffhanger, or question. Where possible, make the last scene visually connect to the beginning so the Short loops naturally. SCRIPT REQUIREMENTS Every line must be visually actionable. Do not write narration that cannot
檢視詳情
1:27
AClaude Opus 5.5
ROLE You are a senior motion designer, map illustrator, gaming researcher and documentary scriptwriter. You build fully code-animated "map tour" explainer videos for a faceless GTA 6 channel. Every frame is rendered from code you write. No AI video generators, no re-uploaded trailer footage, no Rockstar logos, artwork or characters. GOAL Produce one finished map-tour video: 80–90 seconds, 1920×1080, 30fps (plus an optional 1080×1920 vertical cut). A getaway car drives a route across your own illustrated map of Leonida, stopping at each location on a topic list. Every stop gets a highway-sign title, a "case file" card with an illustration, three facts, a source line and an honesty stamp. It ends on a question that drives comments. INPUTS (ask me for anything missing, never guess) - Topic: [e.g. "Every heist spot we've seen in GTA 6" / "Every animal and where to find it" / "Every region and its real-world match"] - My voiceover file (ElevenLabs), or ask me to approve a script first - Channel handle, and the end-card question - Output format: landscape, vertical, or both STEP 1: RESEARCH (accuracy is the brand) - Search the web for every location on the topic. Use only official Rockstar material (trailers, the Extended Look, official screenshots, the Newswire, store listings) and reputable hands-on previews (IGN, Game Informer, Edge, GamesRadar). - For each item, record: what it is, where it is (only if actually shown), the source and its date, and a status: CONFIRMED (Rockstar showed it), SHOWN (seen in a preview or demo), REPORTED (press only) or MAYBE (a single outlet). - If the location isn't shown, the item gets a "LOCATION NOT SHOWN" tag. Never place a pin somewhere that's only a guess. If you approximate, label it "approx. position". - Save everything to research.md with links. Show me the list before writing the script. STEP 2: SCRIPT (documentary tone, about 2.6 words per second) 1. Hook (0–9 s): "Let's go through every [topic] we've seen in GTA 6, before it finally comes out." 2. Sources (9–14 s): name where the info comes from, and promise to flag anything unconfirmed. 3. Stops: one per item, 6–9 seconds each. "Stop one: [name]." → one vivid detail → one practical line or payout note. Say the status out loud when it's weak ("Only one outlet has reported this one, so treat it as a maybe."). 4. The big one: save the most exciting item for last, 12–16 seconds. 5. Twist: a broad truth that zooms out ("You can rob pretty much anything"). 6. Question: "Which one are you [doing] first?" Write in plain words. No hype words, no "smash that like button". STEP 3: THE MAP (build once, reuse in every video) - Build it in code: a stylized Florida-shaped peninsula from your own polygon (about 30 control points with seeded noise wobble so the coast looks hand-drawn), plus a chain of 20+ small islands for the Keys curving southwest, a thin barrier-island strip for Vice Beach, a big lake in the middle and a river running south from it. - Prerender it once to an offscreen canvas at 3 px per map unit, then draw it every frame with a camera transform (pan and zoom). Never redraw the geography per frame. - Look: - Ocean: radial gradient #2f8fe0 → #1553a6, with faint moving wave strokes at 6% opacity. - Shallow water: a cyan glow around every coast (#5fd0ee, 60 px blur). - Coast: a pale sand rim (#f3e6a8). - Land: #cfe07a, with 150+ soft patches of lighter and darker green. - Wetlands: #9fcf74 with short horizontal marsh strokes. - National park: #8fbf62. - City: a light grey area (#e9e9ee) with a fine street grid. - Roads and highways: cream lines. - Region labels in heavy rounded sans (Montserrat 900), white with a soft navy outline, each with its real-world match underneath, e.g. "VICE CITY / (MIAMI)". Use only region names Rockstar has published. STEP 4: ANIMATION LANGUAGE - Camera: open wide on the whole state (zoom so the full map fits), then glide down to the first stop. Each new stop is a smooth 1–2 s ease-in-out pan and zoom. Pull back to the full state for the twist. - Getaway car: a top-down red car icon (body, lighter roof, dark windows, headlights) that follows the route polyline by distance and rotates along the road direction. It eases between stops and pauses at each one. - Route line: the full route as a faint dashed pink line; the travelled part as a solid hot-pink line (#ff2e7e) with a soft glow. - Pins: a teardrop pin that drops in with a back-ease bounce and a pulsing ring. Yellow with "?" plus a "LOCATION NOT SHOWN" tag for unknown spots; pink with "$" plus a location tag for known ones. - Highway sign (top left): a green road sign (#0d7a3f) with a white inner border, a number shield, "STOP 1 OF 6", and the title in a heavy highway-style font (Overpass 900). A handwritten note card under it in a marker font (Permanent Marker) with a 3–5 word quote from the script. - Case file card (right side): an off-white paper card sliding in from the right with a sl
檢視詳情
0:11
AClaude Opus 5.5
Ask me for: the accent colour, a song (mp3), the words for the 3 text moments (search query, card title, toast). If I skip any, use the defaults: lime #C6F432, any 120-130 BPM electronic track, "motion study 07" / "Every frame is code" / "Rendered from one file". One black shape (#0e0e10) on a warm light stage (#f4f4f1 to #e1e1dc radial). It never cuts: every UI state is born out of the one before it. White text, Geist for UI, Geist Mono for numbers and labels. The accent appears only where something turns on. A macOS cursor drives every change with real clicks and one real drag. Every morph uses one curve: cubic-bezier(.45,0,.15,1). Pop-ins use a closed-form spring with a tiny overshoot. Text rises through a mask line, it never fades in. The camera zooms per state so each state fills about 60% of the frame, and creeps slowly through every hold. Banned: crossfades, hard cuts, bouncy easing, particles, glows, gradients on UI chrome, holds over 1 second, anything that looks like a template. 120 BPM grid, 24 beats, then the whole film is time-warped onto the real song's beat. Generate pill → click → shrinks into a spinner circle → grows into a toggle → click, the knob springs right and the track turns accent → stretches into a slider → drag the knob from 15 to 85, the number counts → widens into a ⌘K search bar, the query types itself → unfolds into a chart card, 7 bars spring up one per 1/8 beat, the last one in accent → click the accent bar, it pulses → folds into a toast with a check → back into the Generate pill. Last frame = first frame, cursor included. 1. One HTML file, square 1440x1440. Every style is computed from time inside seek(t): no CSS transitions, no timers, no state between frames. 2. The shape is one div. Width, height, radius and colour are keyframe tracks [[t, value]] eased with the one curve. Each state's content is its own layer with its own in / out window inside the shape. 3. Camera: one scale track around the centre, plus a 1.2% sine creep over the whole loop. 4. Cursor: a track of screen positions for the free moves; during the drag its position is computed from the same function that places the knob, scaled by the camera. 5. Beats: analyse the song with numpy (onset envelope, autocorrelation for BPM, align to the kicks, find the drop). Put the drop on the chart bars springing up. 6. Render with Playwright: 60 fps, 4 subframes averaged per frame for motion blur, piped to ffmpeg x264. Then one real SFX per event (click, select, typing, whoosh), placed by its measured peak, quiet under the music, loudnorm to -14 LUFS. - If the cursor follows its own keyframes during the drag, it slides off the knob. Derive both from one function. - Retiming every key to a 129 BPM song breaks the grid. Author at 120 BPM and warp time once: t * (12 / 11.146). - A 300 px pill at zoom 1.7 looks lost in a 1440 frame. Size the zoom per state, about 60% of the width. - A frame-diff pop scan flags the fast morphs. Check each flag by eye: a moving edge is fine, a jumping layer is not. Ask me for the inputs, then show me the state list on the beat grid before you write any code.
檢視詳情
0:18
AClaude Opus 5.5
Make a loading spinner: my mascot runs inside a rotating ring, 'Loading...' dots underneath
檢視詳情
0:24
AClaude Opus 5.5
Ask me for my story in one line: who the mean character is, the danger he's in, and the 2-3 people he wronged. If I have no idea, pitch me 3 and let me pick. Length 25-60 s. Every character, skin and block is mine, drawn in code: never JJ, Mikey, Maizen characters or Mojang textures. A 1080x1920 30 fps Minecraft-style story Short, built entirely in Blender from code, $0, with no game assets and no AI video. Split screen: - The top 640 px is the talking avatar of whoever speaks: that character sitting in a dark gaming room with a headset. It sits behind a 14 px border in the speaker's colour, with an 8 px dark divider under it. - The bottom 1080x1280 is the block animation. Each character owns one colour (purple 176,90,255 / orange 255,160,40 / pink 255,100,170) for the border, the headset cups, the room LEDs and their key caption words. The world is 16x16 pixel blocks with hard nearest-neighbour pixels: grass, dirt, stone, logs, leaves, planks, water and ore. The sky runs from 178,214,255 at the horizon to 96,156,245 overhead, with flat white box clouds. Light comes from a warm sun, using the Standard view transform. Captions show one word at a time in UPPERCASE, Montserrat Black at 96 px: white, with a 12 px black outline and a soft black shadow 4 px right and 7 px down. Key words (help, the wronged thing, bye, like, subscribe) are in the speaker's colour. The caption sits just under the divider. Pure dialogue, no narrator. Flashbacks are sepia with a FLASHBACK tag. Banned: JJ/Mikey/Maizen look-alikes, Mojang skins or textures, smooth interpolation, motion blur, depth of field, the Filmic or AgX look, any shot over 2.5 s, and any frame where nothing moves. Length: 25-60 s, about 13 lines per 25 s. Cut every 0.7-2.3 s (median 1.3 s), about 18 shots per 25 s, at least 3 different places. 0 s: the mean character is already in danger (hanging off a cliff, trapped, sinking) and screams for help, wide then close → helper 1 walks in, low angle looking up at them, and their line hints at what he did → FLASHBACK in a new place, 2-3 shots: he does the mean thing, laughs, and it lands with a big physical payoff (something blows apart, smashes or splats); it ends on the victim crying over it → back: he begs ("I'm sorry! I was joking!"), the helper says one cold line, waves and walks off → helper 2, same shape, a different place and a different wrong → the last refusal, then the danger lands: a hand slips, a top-down shot, he falls → falling with him, his final line asks for a like and a subscribe to save him. 1. Tools (all free, all local). Install what's missing and tell me what you installed: - Blender 4.2 or newer as the portable zip, run headless: `blender -b --factory-startup --python build .py -- MODE OUT [F0 F1]`. Modes: stills, final (F0 F1 re-renders a range), avatars. - Python with numpy, Pillow and soundfile. - FFmpeg. - faster-whisper large-v3-turbo (int8 on the CPU). - kokoro-onnx with kokoro-v1.0.onnx and voices-v1.0.bin. - Montserrat. - A free sad piano bed and about 12 free SFX: whoosh, pop, boom, impact, poof, sting, riser, gasp, footsteps, plus whatever the story needs. 2. Voice (Kokoro, free): - Show me the script before recording. Write screams with "!" and keep lines short. - Render every line on its own. Trim it at 0.01 amplitude, keeping 10 ms before and 50 ms after. - Pitch it up with asetrate, then atempo back down, so the speed stays the same. - Kid voices: - af_heart, speed 1.14, +1.5 semitones (the main kid) - am_echo, speed 1.08, +3 (a boy) - af_bella, speed 1.1, +2.5 (a girl) - am_puck pitched up sounds bad. - Gaps after lines: - 0.2-0.45 s normally - 0.7-1.2 s where the action needs room (the blast, the slip) - 0.9 s of tail at the end - Store each line's speaker, text, flashback flag, t0 and t1 in lines.json. 3. Timing: - Run faster-whisper with word timestamps and the script as initial_prompt, then align the words to the script with difflib. - Every cut, pose snap, face swap, prop and SFX hangs on a word, never on a fixed second: - Cuts go 0.06 s before their word. - Reaction shots go 0.12 s before a line. - Flashbacks start 0.3 s before their first line. - Mouth track, one value per 30 fps frame: - The mouth is open when the RMS is over (70th percentile - 15 dB) AND over half the max within ±3 frames. - Hold every state at least 2 frames. - Break any open run longer than 7 frames with 2 closed frames every 6. 4. Textures: - Every texture is 16x16, drawn in Pillow. Jitter each pixel ±3-8 so it isn't flat. - Base colours: dirt 134,96,67, grass 98,160,58, stone 126,126,128, leaves 62,122,40, planks 150,120,76 (a darker line every 4th row), water 70,112,210. - Grass has a top texture, a side texture (green to 3-5 px, then dirt) and a dirt bottom. - Every image texture uses Closest interpolation with Extend. 5. World (a voxel mesher): - A dict maps (x, y, z) to a block type. - Emit one quad only for faces with no neighbour. Water emits only its top face, dropped 0.12. - Merge all quads of one texture into one mesh, giving every quad UVs 0..1. - Build each place 200 units apart on x (the cliff at 0, flashback 1 at 200, flashback 2 at 400, the avatar room at 600). - Split the merged meshes per place with bmesh by face centre. Keyframe hide_render only when the active place changes, or the other sets float on the horizon. - Trees: a 4-6 block log with a diamond of leaves. Scatter 1-block flowers. Ore specks go in walls the camera passes. 6. Characters (unit P = 1/16): - Body pivot 12P up. Torso 8x4x12P. Head an 8P cube on a neck pivot at the top of th
檢視詳情
0:56
AClaude Opus 5.5
A 1080x1920, 60 fps, 40-45 s vertical Short in the style of the big 2D "What if" kid Roblox story channels: flat 2D cartoon cut-outs animated like motion graphics, drawn entirely on an HTML canvas in code. Not 3D, not AI images. Characters: one blocky game-avatar rig shared by the whole cast. - At scale 1: square head 216x200 px with 56 px round corners, body 152x154, arms 62x132 with 56x46 hands, legs 72x142, shoes 84x42. Draw them at scale 1.0-2.4. - Every shape has an 8 px #2a1b3d outline and one darker flat shade on one side. - One look each. The kid hero ("you"): backwards blue cap #2e88ee, orange hair #f27b2c, yellow shirt #ffc934 with a pixel heart, blue pants #3f66cf. Mom: red-brown ponytail, round glasses, gold hoops, teal cardigan #2bb3a3, purple pants #6b3fa0. One or two side characters (a dentist, a teacher, a little brother). - Faces carry the comedy. Eyes: normal, happy arcs, huge, star, spiral, closed, narrow. Brows: up, worry, angry, flat. Mouths: smile, grin, o, scream, wavy, flat, smirk, tongue, chew, wide. Plus blush, sweat drops and sunglasses that drop in. Blink for 0.1 s about every 1.6 s. Sets: bright flat places (bedroom, classroom, dentist, a boss office, a game world with floating blocks over a checkered baseplate) in saturated colours with thick outlines, nothing photographic. Motion: something moves on every line, and the picture changes every 1-3 s. - Things arrive with a squash (0.72, 1.12, 0.95, 1 over 0.3 s), an overshoot ease or a white poof cloud, never a plain fade. - The camera pushes in 5-15% per shot and shakes (decaying over 0.35 s) on every hit. Fake game UI over the world: - A HUD counter pill (236x92, centred at x 540, y 196) that tracks the story: a timer, a respawn count, a currency count. - "[SYSTEM]" chat lines, a player chip, a clock chip, shop cards, and pop-up toasts (88 px tall pills at y 330). - A SUBSCRIBE button with a cursor hand. Captions: - 1-3 words at a time in Lilita One 124 px, centred at y 1290, max 980 px wide. - White with a 24 px #1c1030 outline and a soft shadow, popping from 55% to 100% in 0.16 s. - Key words in caps and colour: red #ff5165, green #5dff8f, yellow #ffd23f, pink #ff7ad9, cyan #7debff, orange #ffa53d, purple #c49bff. - No full stops on screen, ever. Banned: real logos or real creators' characters, AI stills, a frame that holds still for more than 1 s, world text on the caption line (y 1230-1350), whispered narration.
檢視詳情
瀏覽全部 Claude Opus 5.5 提示詞探索AI 影片提示詞