How bfdestroyeer/color-console-player works
Color console player turns a video file into timed, colored terminal frames. The main workflow validates the input, starts audio through ffplay, creates OpenCV video capture, then starts rendering; a separate writer thread displays ready frames and timing statistics. Rendering uses buffered capture, console dimensions, and a three-frame text buffer. Source excerpts show the capture read and writer behavior, but omit parts of the renderer loop, so uncertain renderer-to-buffer and renderer-to-size interactions are not asserted.
Main entry points: main.cpp Player entry · FrameWriter.cpp Frame writer · TextFrameBuffer.cpp Text frame buffer · FrameRenderer.cpp Frame renderer
Components 10
Playback
- Player entry
src/main.cpp - OpenCV capture
- ffplay
- Buffered capture
src/BufferedVideoCapture.cpp
Frame rendering
- Frame renderer
src/FrameRenderer.cpp
Text frames
- Text frame buffer
src/TextFrameBuffer.cpp - Text frame
src/TextFrame.cpp
Terminal output
- Console dimensions
src/ConsoleWindowSizeService.cpp - Frame writer
src/FrameWriter.cpp
Other components
- User
Connections 11
- User → Player entry: provides video
README.md - Player entry → ffplay: starts playback
src/main.cpp - Player entry → OpenCV capture: opens video
src/main.cpp - Player entry → Console dimensions: creates service
src/main.cpp - Player entry → Text frame buffer: creates buffer
src/main.cpp - Player entry → Frame writer: creates writer
src/main.cpp - Player entry → Frame renderer: starts rendering
src/main.cpp - Frame renderer → Buffered capture: reads frames
src/FrameRenderer.cpp - Frame writer → Text frame buffer: swaps frames
src/FrameWriter.cpp - Frame writer → Console dimensions: reads dimensions
src/FrameWriter.cpp - Text frame buffer → Text frame: creates frames
src/TextFrameBuffer.cpp