mpv-player / mpv-player/mpv

Unable to specify console color

Open
#15,722 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

meta:feature-request
Dominant language
C
Stars
37k
Forks
3.5k
Avg merge
1d 10h
Merged PRs (30d)
22

Description

mpv Information
mpv v0.39.0-625-gdf3872e3 Copyright © 2000-2025 mpv/MPlayer/mplayer2 projects
 built on Jan 23 2025 00:09:04
libplacebo version: v7.350.0 (v7.349.0-30-g056b852-dirty)
FFmpeg version: N-118350-ge20ee9f9a
FFmpeg library versions:
   libavcodec      61.31.101
   libavdevice     61.4.100
   libavfilter     10.6.101
   libavformat     61.9.106
   libavutil       59.55.100
   libswresample   5.4.100
   libswscale      8.13.100
Other Information
- Windows version: 10.0.19045.5435
- GPU model, driver and version: 3060ti, 560.94 Game Ready
- Source of mpv: shinchiro
- Latest known working version: Before commit 19537a4
- Issue started after the following happened: commit 19537a4
Reproduction Steps

set osd-color in mpv.conf and the console will inherit the color

Expected Behavior

The console color can be changed using script-opts-append = console-font_color=FFFFFF

Actual Behavior

While the stats page can independently set its color using script-opts-append = stats-font_color=FFFFFF, the console doesn't have an option to modify its color

Log File

Unnecessary

Sample Files

No response

I carefully read all instruction and confirm that I did the following:
  • I tested with the latest mpv version to validate that the issue is not already fixed.
  • I provided all required information including system and mpv version.
  • I produced the log file with the exact same set of files, parameters, and conditions used in "Reproduction Steps", with the addition of --log-file=output.txt.
  • I produced the log file while the behaviors described in "Actual Behavior" were actively observed.
  • I attached the full, untruncated log file.
  • I attached the backtrace in the case of a crash.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by inspecting commit 19537a4 and the console option handling for osd-color and script-opts-append. Reproduce the behavior with mpv.conf and verify that a console-font_color option can independently control the console color without changing the stats page behavior.

Written by the indexing model from the issue text.

Assessment

Tech stack
c
Domain
cli
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.