Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unable to specify console color #15722

Open
6 tasks done
WilliamK7 opened this issue Jan 23, 2025 · 2 comments
Open
6 tasks done

Unable to specify console color #15722

WilliamK7 opened this issue Jan 23, 2025 · 2 comments

Comments

@WilliamK7
Copy link

WilliamK7 commented Jan 23, 2025

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.
@zhongfly
Copy link

zhongfly commented Jan 23, 2025

This should be feature request, not a bug.Looklike you choose wrong type.

@WilliamK7
Copy link
Author

WilliamK7 commented Jan 23, 2025

Oops, so is there a way to change the type of this issue or should I open a new one?
Sorry for the inconvenience

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants