2024-11-10, 09:20 PM
(This post was last modified: 2024-11-10, 09:31 PM by Giresharu. Edited 2 times in total.)
This is the correct subtitle effect (without hardware acceleration, consistent with other software)
And this is the effect after enabling Intel QSV
Obviously, the transparency has changed. What’s going on here?
Also, I’d like to ask: to correctly display the specified subtitles in an ASS file, the Windows version of the client can display them by installing the specified font in the system font directory of the PC, but it seems that the web UI does not read the fonts from the PC’s system? And when using fallback fonts, it seems that the font specified in the ASS file is not used, but a random font from the directory is chosen to display (which can be very chaotic for Chinese-Japanese bilingual subtitles). So, with the web UI version, is burning the only option to correctly display ASS subtitles?
And this is the effect after enabling Intel QSV
Obviously, the transparency has changed. What’s going on here?
Also, I’d like to ask: to correctly display the specified subtitles in an ASS file, the Windows version of the client can display them by installing the specified font in the system font directory of the PC, but it seems that the web UI does not read the fonts from the PC’s system? And when using fallback fonts, it seems that the font specified in the ASS file is not used, but a random font from the directory is chosen to display (which can be very chaotic for Chinese-Japanese bilingual subtitles). So, with the web UI version, is burning the only option to correctly display ASS subtitles?