guilty57 9 Posted April 29 Posted April 29 After the update to version 3.5.31, external .ass subtitles attached with custom font seem vertically stretched and bigger. Also they are at the bottom instead of at the vertical margin set. No problem with version 3.5.28 but v3.5.31 and v3.5.32 has. I don't see a necessity to upload server log. Screenshots and subtitle file attached. Video Info: Format : Matroska Format version : Version 4 File size : 9.86 GiB Duration : 1 h 31 min Overall bit rate : 15.5 Mb/s Frame rate : 23.976 FPS Encoded date : 2025-02-16 10:52:01 UTC Writing application : mkvmerge 89.0 ('And the Melody Still Lingers On (Night in Tunisia)') 64-bit Writing library : libebml v1.4.5 + libmatroska v1.7.1 Video ID : 1 Format : HEVC Format/Info : High Efficiency Video Coding Format profile : Main@L5@Main Codec ID : V_MPEGH/ISO/HEVC Duration : 1 h 31 min Bit rate : 14.7 Mb/s Width : 3 840 pixels Height : 1 600 pixels Display aspect ratio : 2.40:1 Frame rate mode : Constant Frame rate : 23.976 (24000/1001) FPS Color space : YUV Chroma subsampling : 4:2:0 Bit depth : 8 bits Bits/(Pixel*Frame) : 0.100 Stream size : 9.39 GiB (95%) Language : English (US) Default : Yes Forced : No Color range : Limited Color primaries : BT.709 Transfer characteristics : BT.709 Matrix coefficients : BT.709 Flight Risk (2025) [2160p] [WEB-DL] [EAC3 5.1] [APEX].tur.ass
visproduction 360 Posted April 30 Posted April 30 .ass options: ScaledBorderAndShadow: Specifies whether to scale the subtitle's outline and shadow according to the screen resolution. yes means yes, no means no scaling. see: https://en.pyvideotrans.com/srtvttass#_1-script-info-section
Solution guilty57 9 Posted Friday at 11:09 PM Author Solution Posted Friday at 11:09 PM (edited) This issue is nothing to do with script option called "ScaledBorderAndShadow". The problem isn't about border or shadow as clearly seen in the screenshots. I rollback to version 3.5.28 and disabled auto update option for PlayStore for now. The problem doesn't exists. I hope the problem is solved in the next updated version. Edit: In version 3.5.36, the issue has been fixed. Updated and checked. No problem. Edited Friday at 11:17 PM by guilty57 1
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now