Create Intro — Cinematic Text Intro Generator

Generate a minimal, cinematic video intro: text snaps on over black, holds, fades out — synced to a sound effect. Think IMAX bumper or PlayStation startup, but just clean typography.

What You Need From the User

Ask for these if not provided (defaults in parentheses):

1. Text — What should it say? Can be two lines like "POWERED BY" + "GIR", or a single line. (required)
2. Sound file — Path to an audio file to sync with the text appearance. (optional — silent if omitted)
3. Output path — Where to save the MP4. (default: current working directory)

These have sensible defaults but can be customized:

• Resolution: 1920x1080
• Duration: 4 seconds
• FPS: 30
• Fade-in delay: 0.3s (brief black before text appears)
• Fade-in speed: 0.2s (fast snap-on, like a screen powering on)
• Hold: until 3.0s
• Fade-out: 1.0s ease-out
• Font: System sans-serif (Avenir Next > Avenir > Helvetica > SF)
• Text color: Light gray on black (not pure white — more cinematic)

How to Build It

Step 1: Write the render script

Create a Python script at a temp location (/tmp/intro_render.py). Use the bundled reference at scripts/render_intro.py as the base — read it and adapt to the user's specifications.

Key rendering decisions:

• Two-line text (e.g. "POWERED BY" + "GIR"): top line is smaller (22pt) and dimmer (max 150/255), bottom line is larger (54pt) and brighter (max 230/255). Spaced letters on the bottom line (e.g. "G I R") look cinematic.
• Single-line text: use the larger font size, centered.
• Opacity curve: linear fade-in (fast), quadratic ease-out fade. The snap-on should feel instant — like something powering on, not a slow dissolve.
• Background: pure black (0,0,0). No gradients, no particles, no lens flares. The power is in the simplicity.

Step 2: Render frames

python3 /tmp/intro_render.py

This writes PNG frames to /tmp/gir_intro_frames/.

Step 3: Prepare audio

If the user provided a sound file, delay it to sync with the text appearance (match the fade-in start time):

FFMPEG="/Users/gualo/Downloads/AI COOKUPS/evil-gir-bot/bin/ffmpeg"

"$FFMPEG" -y \
  -i "<sound_file>" \
  -af "adelay=<fade_in_start_ms>|<fade_in_start_ms>,apad=whole_dur=<duration>,afade=t=out:st=<fade_out_start>:d=<fade_out_dur>" \
  -ac 2 -ar 44100 /tmp/intro_audio.wav

The audio fade-out should match the visual fade-out so everything disappears together.

Step 4: Compile to MP4

"$FFMPEG" -y \
  -framerate <fps> -i /tmp/gir_intro_frames/frame_%04d.png \
  -i /tmp/intro_audio.wav \
  -c:v libx264 -preset slow -crf 18 -pix_fmt yuv420p \
  -c:a aac -b:a 192k -shortest -movflags +faststart \
  "<output_path>"

If no audio, omit the -i audio input and audio codec flags.

Step 5: Clean up and deliver

• Remove temp frames from /tmp/gir_intro_frames/
• Remove temp audio from /tmp/intro_audio.wav
• Open the final MP4 with open "<output_path>" so the user can preview it immediately

FFmpeg Location

The FFmpeg binary is at: /Users/gualo/Downloads/AI COOKUPS/evil-gir-bot/bin/ffmpeg

Common Sound Files

These are available in the project for quick use:

• Sync GIR startup: /Users/gualo/Downloads/AI COOKUPS/MVSync-Panel/client/audio/startup.mp3
• Sync GIR build: /Users/gualo/Downloads/AI COOKUPS/MVSync-Panel/client/audio/build.mp3

Style Notes

The whole point is restraint. IMAX and PlayStation intros work because they're confident enough to put simple text on black and let the sound do the work. Don't add:

• Glow effects or bloom
• Moving backgrounds or particles
• Logo images (text only)
• Flashy transitions or camera moves

If the user asks for something fancier, adapt — but the default should always be minimal.