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

UI is all stretched since a recent update #14249

Closed
6 tasks done
RaylaLe100 opened this issue May 27, 2024 · 3 comments
Closed
6 tasks done

UI is all stretched since a recent update #14249

RaylaLe100 opened this issue May 27, 2024 · 3 comments

Comments

@RaylaLe100
Copy link

mpv Information

mpv v0.38.0-dirty Copyright © 2000-2024 mpv/MPlayer/mplayer2 projects
 built on May 23 2024 10:29:03
libplacebo version: v6.338.2
FFmpeg version: n6.1.1
FFmpeg library versions:
   libavutil       58.29.100
   libavcodec      60.31.102
   libavformat     60.16.100
   libswscale      7.5.100
   libavfilter     9.12.100
   libswresample   4.12.100

Other Information

  • Linux version: EndeavourOS
  • Kernel Version: 6.9.2-arch1-1
  • GPU Model: 2d:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Navi 23 [Radeon RX 6600/6600 XT/6600M] [1002:73ff] (rev c1)
  • Mesa/GPU Driver Version: OpenGL version string: 4.6 (Compatibility Profile) Mesa 24.0.8-arch1.1
  • Introduced in version: less than a month ago
    image

Reproduction Steps

No reproduction steps are needed, the bug appears as-is.

Expected Behavior

Having a normally-sized UI.

Actual Behavior

The UI is stretched vertically (almost 2:1 I would say)

Log File

output.txt

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

llyyr commented May 28, 2024

--script-opts=osc-vidscale=yes See #14158 for info

@na-na-hi
Copy link
Contributor

na-na-hi commented May 28, 2024

[ 0.006][v][osd/libass] libass source: commit: 0.17.2-0-gcbb48cc4f2f076300004b8b06a86bec55281d0c2-dirty
[ 0.223][v][sub/ass] fontselect: (sans-serif, 400, 0) -> /usr/share/fonts/noto/NotoSans-Condensed.ttf, 0, NotoSans-Condensed

libass/libass#770

--script-opts=osc-vidscale=yes See #14158 for info

That's not it. The default behavior is unchanged and that option isn't set according to the log.

@llyyr
Copy link
Contributor

llyyr commented May 28, 2024

The change was made because VSFilter does not consider width when selecting a font

Ah, so just libass shooting itself in the foot again

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

5 participants