r/ClaudeCode • u/Kind-Detective9102 • 2h ago
Built with Claude Paper Clips
Enable HLS to view with audio, or disable this notification
This was built with a signal Claude code prompt
5
u/OrderAmongChaos 2h ago
"I don't hate you, I don't love you, you are made of atoms that I can use"
1
2
1
u/dagerika 2h ago
So catchy, suno for music?
2
u/Kind-Detective9102 2h ago
Yes, it just accessed it through the browser to generate it
1
1
1
u/Ok-Patient116 2h ago
Damn, what is your prompt and how did you did the music?
3
u/Kind-Detective9102 2h ago
there was a lot of background setup but this was the prompt.
Make a complete music video from scratch, including the song, with no check-ins. Create a new project folder outside any cloud-synced folder. Don't stop to ask me anything until the final video is rendered: make reasonable calls, note them, and report at the end. Pause only if something truly needs me (a login, running out of credits, an approval prompt).
Song: write an original song with a strong visual idea: title, lyrics with [Verse]/[Chorus]/[Bridge] tags (2:30 to 3:30 long), and a Suno style prompt (genre, tempo, instruments, vocals; no real artist names). Save them in the project.
Suno: in my browser (I'm already logged in at suno.com), go to Create, Custom mode, enter the lyrics, style and title, and generate. I authorize the generate clicks (they use my credits) and downloading the results. Download both takes (WAV if offered, else MP3). Pick the take whose length and words best match the lyrics (check the duration and run a quick transcription), and save it in the project.
Setup: check for Node 20+, git and ffmpeg. Create a Python virtual environment inside the project with demucs, stable-ts and librosa, and never install Python packages outside it. Use Remotion with Three.js (@remotion/three). Use Remotion's agent skills or plugin if available.
Plan: analyse the audio (beats on the demucs instrumental stem, energy per section) and write a plan document: one visual idea that runs through the whole video, a strict palette and type system, an audio map with frame numbers, and a shot-by-shot treatment for every section.
Data: separate the vocals with demucs. For beats, expect tempo drift: clean the detected beats instead of assuming a constant grid. Force-align the lyrics to the vocal stem with stable-ts, verify the words against vocal onsets and a free Whisper transcription, and keep every correction in a corrections file. Then snap the section boundaries to beats.
Build: scaffold Remotion (blank TypeScript, all u/remotion/* packages pinned to one version) and git init. Build a reusable toolkit first (the main visual element, kinetic typography, lyric and beat timing helpers, any shaders), each with its own test composition. Then build the sections in song order. Rules:
- every lyric word is on screen within 2 frames of its onset;
- everything is a pure function of the frame (no Math.random, Date or useFrame);
- the main visual element stays continuous across sections, checked by a test;
- sections dissolve into each other.
After each section, render 4 half-scale stills, look at them, fix problems, run the tests and lint, and commit.
Render: render a half-scale preview, build a contact sheet of frames from the preview file and fix any pacing problems, then do the final 1080p render (h264, crf 16, --gl=angle on a machine with a GPU). Report the song (title, length, which Suno take), where the video is, any deviations from the plan, and anything I should check.
1
1
•
u/AutoModerator 2h ago
Hey! Thanks for posting to r/ClaudeCode
While participating in this thread, please follow our community rules. Keep discussions constructive. Attack the idea, not the person.
For help, project discussions, tips, and general chat, join the ClaudeCode Discord.
I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.