Speaker A
If you make videos with Claude code, you know [music] the feeling. You describe the film you want, but you don't see what Claude made until it renders.
A creator presents VideoHub, a free open-source tool that previews Claude Code videos instantly without rendering, lets you annotate frames, and sends notes to Claude for fixes.
Key Takeaways
- Previewing videos without rendering and annotating frames visually greatly speeds up Claude Code video editing.
- VideoHub is free and open source, and setup can be handled almost entirely through Claude Code.
- Configuring Claude to preview first and render only on request prevents wasteful full re-renders.
What the video covers
- Rendering a full video to check a one-second fix wastes minutes, and describing visual problems to Claude in text is inefficient.
- VideoHub plays videos directly from their code, so creators can preview and step through frames without rendering.
- Users annotate specific frames by drawing on them and writing short notes, which capture the exact time and a screenshot of the issue.
- Pressing send gives Claude all annotated notes with their images, Claude fixes the code, and the preview reloads automatically.
- Final renders run once in the background, limited to one at a time to keep the computer usable, and can use GPU encoding for speed.
- An 8-minute film rendered in about 8.5 minutes in the creator's test, roughly real-time.
- The tool organizes a workspace with folders for films, outputs sorted by day, sounds, thumbnails, and an archive.
- Additional utilities include a disc cleanup tool that uses the recycle bin, a sound mixer, and a thumbnail studio.
- Installation is done by asking Claude Code to install it from the GitHub repository, which checks for node and ffmpeg and asks setup questions.
- The creator admits the tool was built with Claude Code and may have bugs, suggesting users ask their own Claude to diagnose and fix issues.
Chapters
- 00:00The Problem with Rendering Claude Code Videos
- 00:37Introducing VideoHub
- 00:53Previewing Without Rendering
- 01:50Annotating Frames and Sending Notes to Claude
- 02:40Final Rendering and Performance
- 03:20Workspace Organization and Extra Tools
- 04:00Installing VideoHub with Claude Code
- 04:50Setup Steps, Limitations, and Closing
Full Transcript — Download SRT & Markdown
Speaker A
[music] And that's where the fun ends. One word comes in a second too early.
Speaker A
And to check the fix, you render the whole film again. 1 second of problem, 8 minutes of waiting. I've watched more progress bars this month than actual videos. Then you explain the mistake to Claude in text. [music] Around 4 minutes
Speaker A
10, the second screen goes black. Claude fixes it beautifully [music] on the wrong frame and tells you it's fixed with a lot of confidence. So, you render again. I ran into every single one of these while making the videos on this
Speaker A
channel. So, I built a tool to fix them. [music] It's called VideoHub. Now, I could put it on school for $40 a month and buy a Porsche instead. It's free.
Speaker A
It's open source and the link is in the description and I'll tell you why at the end of the video. The idea is simple.
Speaker A
VideoHub plays the film straight from its code. no [music] render. You open it, it plays, and you can step through it frame by frame like a video editor that never had to wait for anything. And instead of describing the problem, you
Speaker A
point at it. [music] You click on the frame, draw a circle around what's wrong, and write one line. That note knows the exact time, [music] the exact frame, and it keeps a picture of what you circled. So around 4 minutes 10
Speaker A
finally becomes this frame, this thing. When you're done, you press send to Claude. Claude reads every note with its picture, fixes the code, and the preview you have open reloads by itself. You're watching the fix before you've even
Speaker A
finished reading Claude's reply. Here's how that went with my last video, the 8-minute comparison of Fable 5.2 and Opus 5.5. I left 53 notes on the first version. I'm a very relaxed reviewer, as you can tell. Only when I was happy did
Speaker A
I say render it. The whole film rendered once in the background in about 8 and 1/2 minutes. It also keeps your computer usable while it renders. Only one render runs at a time. It limits how much of the processor renders can take while
Speaker A
you're working. And if memory runs low, it slows the render down instead of letting everything crash. And if you just need your computer back for a minute, one shortcut pauses every [music] render. It also keeps everything in one place. When you install it, you
Speaker A
get one workspace folder with your films, every finished video, your sounds, and your thumbnails, each in its own folder. And every render lands in an outputs folder, sorted by day, so you [music] never have to dig for the final
Speaker A
version again. There's also a disc cleanup that shows you what can safely go and moves it to the recycle bin, never straight into the void. A sound mixer to turn the music down, [music] and a thumbnail studio where you sketch
Speaker A
a thumbnail and send the sketch to Claude. Installing it is the easy part. Download it from GitHub, open the folder in Claude Code, and say, "Install VideoHub for me." And if you don't know much about computers, it's even easier.
Speaker A
Just give Claude Code the link to the repository and say, "Install this for me." You never type a single command. It works on Windows 10 and 11. Here's what happens step by step, so nothing feels like magic. First, Claude checks that
Speaker A
your computer has the two things VideoHub needs. node, [music] which runs video hub itself, and ffmpeg, which turns frames into a video file. If one is missing, it tells you exactly what to install. [music] Then it asks you a few
Speaker A
simple questions. The first one is where your video work should live. You pick one folder, and VideoHub makes a place inside it for your films, your finished videos, your sounds, your thumbnails, and an archive so everything stays in
Speaker A
one place. Next, if your computer has a graphics card that can encode video, it asks if renders should use it. Say yes.
Speaker A
The frames go straight from the film to the video file without being compressed in between, [music] so it's faster and it doesn't lose any quality. Here's what that changed for me. In October, a 9-minute 3D film took almost an hour to
Speaker A
render. Now, an 8-minute film takes about 8 1/2 minutes, about as long as it takes to watch it. That's an hour back on every film for every Claude Code user. So yeah, Anthropic should be paying me for this. It also asks if it
Speaker A
should add a small rule to Claude's settings. Preview first, [music] render only when you say so. That's the rule that stops Claude from rendering your whole film after every fix. Say yes to that one, too. The last questions are
Speaker A
the easy ones. a desktop shortcut, whether VideoHub should start with Windows, and whether to add a 10-second example film so you can try everything before you make your own. While you answer, setup does the boring part for you. It builds the small helper that
Speaker A
keeps renders from freezing your computer, and it connects VideoHub to Claude Code, so Claude can read your notes and start renders by itself. When it's [snorts] done, open VideoHub from the desktop, start a new Claude Code session, and that's it. Now, a small
Speaker A
confession. VideoHub was written with Clawed Code, too. So, it's held together with tape and hope. If you run [music] into a bug, don't be too surprised, but it works. And most of the time, you'll only use two parts of it. The notes and
Speaker A
the render. And those are the parts I use every day. [music] And if something does break, you don't have to wait for me. Just tell your own Claude what happened. It can read the code, find the problem, and fix it. So, the new routine
Speaker A
is watch it, point at what's wrong, let Claude fix it, and render once. I use it for every video on this channel now. The link is in the description. And if you find a bug, you know what to do. Leave a
Speaker A
note, and I promise to tell you why it's free. This is the reason.
Topics:Claude CodeVideoHubvideo editingAI videorenderingopen sourceFFmpegworkflowframe annotationtutorial
