How derstgamd/infinity_bd works
A small Flask service accepts a video URL, uses yt-dlp to resolve its audio stream, and runs FFmpeg to transcode that stream into MP3 chunks for the requester. The separate ping endpoint reports whether FFmpeg and the optional cookie file exist. Runtime behavior is concentrated in app.py; the repository does not include the FFmpeg binary or cookie file, so these are shown as external resources.
Main entry points: app.py Flask routes
Components 11
HTTP service
- Flask routes
app.py - Health check
app.py
Audio streaming
- Stream handler
app.py - URL resolver
app.py - yt-dlp
- FFmpeg
- MP3 response
app.py
Other components
- HTTP client
- Video source
- Cookie file
- FFmpeg binary
Connections 14
- HTTP client → Flask routes: sends request
- Flask routes → Health check: dispatches
- Flask routes → Stream handler: dispatches
- Health check → FFmpeg binary: checks existence
- Health check → Cookie file: checks existence
- Stream handler → URL resolver: resolves URL
- URL resolver → yt-dlp: extracts info
- yt-dlp → Video source: retrieves metadata
- yt-dlp → Cookie file: uses if present
- yt-dlp → URL resolver: returns stream URL
- Stream handler → FFmpeg: starts transcoding
- FFmpeg → FFmpeg binary: runs binary
- FFmpeg → MP3 response: writes MP3 chunks
- MP3 response → HTTP client: streams response