mpv-player / mpv-player/mpv

'bgra8' does not support PL_FMT_CAP_STORABLE libplacebo warnings

Open
#17,896 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

os:linux
Dominant language
C
Stars
37k
Forks
3.5k
Avg merge
1d 10h
Merged PRs (30d)
22

Description

mpv Information
mpv v0.41.0 Copyright © 2000-2025 mpv/MPlayer/mplayer2 projects
 built on Feb 11 2026 22:07:06
libplacebo version: v7.360.1
FFmpeg version: n8.0.1 (runtime n8.1)
FFmpeg library versions:
   libavcodec      62.11.100 (runtime 62.28.100)
   libavdevice     62.1.100 (runtime 62.3.100)
   libavfilter     11.4.100 (runtime 11.14.100)
   libavformat     62.3.100 (runtime 62.12.100)
   libavutil       60.8.100 (runtime 60.26.100)
   libswresample   6.1.100 (runtime 6.3.100)
   libswscale      9.1.100 (runtime 9.5.100)
Other Information
- Linux version: Arch Linux
- Linux kernel Version: 7.0.2-arch1-1 #1 SMP PREEMPT_DYNAMIC Mon, 27 Apr 2026 18:22:44 +0000 x86_64 GNU/Linux
- GPU Model: 00:02.0 VGA compatible controller [0300]: Intel Corporation Skylake-U GT2 [HD Graphics 520] [8086:1916] (rev 07)
- Mesa/GPU Driver Version: OpenGL version string: 4.6 (Compatibility Profile) Mesa 26.0.5-arch1.1
- Window Manager and Version: LXDE via Openbox 3.6.1-14 with X.Org 21.1.22-1
- Source of mpv: Arch Linux's packages, version 1:0.41.0-3
- Latest known working version: I forgot in which version the warning first appeared.
- Issue started after the following happened: Updating mpv to a newer version with pacman
Reproduction Steps

mpv shows lots of [vo/gpu-next/libplacebo] Masking `storable` from wrapped texture because the corresponding format 'bgra8' does not support PL_FMT_CAP_STORABLE warnings if I open a file or perform actions such as toggling fullscreen or resizing the window.

$ mpv --no-config /tmp/tmp.png 
● Image  --vid=1  (png 33x37)
VO: [gpu-next] 33x37 rgba
[vo/gpu-next/libplacebo] Masking `storable` from wrapped texture because the corresponding format 'bgra8' does not support PL_FMT_CAP_STORABLE
[vo/gpu-next/libplacebo] Masking `storable` from wrapped texture because the corresponding format 'bgra8' does not support PL_FMT_CAP_STORABLE
[vo/gpu-next/libplacebo] Masking `storable` from wrapped texture because the corresponding format 'bgra8' does not support PL_FMT_CAP_STORABLE
V: 00:00:00 / 00:00:00 (0%)
Expected Behavior

I expect to not see these warnings or to know a setting to hide them.

Actual Behavior

These warnings appear very often and make it difficult for me to see other important warnings. mpv works fine for me and I don't notice any problems except the verbose messages. In older mpv versions (I don't remember which ones), I didn't see the warnings.

Log File

output.txt

Sample Files

It happens with all files, e.g. <<< "P1 1 1 1" cat >| "$XDG_RUNTIME_DIR/tmp.pnm" && mpv --no-config "$XDG_RUNTIME_DIR/tmp.pnm"

I carefully read all instruction and confirm that I did the following:
  • I tested and confirmed that the issue exists with the latest release version or newer.
  • 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 reproducing the warning with mpv --no-config /tmp/tmp.png and inspect the attached output.txt, focusing on the gpu-next/libplacebo texture-format message. Trace where the bgra8 storable capability is masked and determine whether the repeated warning can be avoided without hiding other important warnings; the issue is done when the reproduction no longer emits the repeated messages.

Written by the indexing model from the issue text.

Assessment

Tech stack
c
Domain
computer-graphics
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.