Due to an influx of spam, we have had to impose restrictions on new accounts. Please see this wiki page for instructions on how to get full permissions. Sorry for the inconvenience.
Admin message
The migration is almost done, at least the rest should happen in the background. There are still a few technical difference between the old cluster and the new ones, and they are summarized in this issue. Please pay attention to the TL:DR at the end of the comment.
I configure the size of subtitles in totem so i can watch them comfortably.
It works fine with most of my videos (with external .srt file) but with high resolutions ones (like 1280x720) subtitles are too small.
I think the size of subtitles should not be dependent of the resolution of the video played.
Designs
Child items ...
Show closed items
Linked items 0
Link issues together to show that they're related.
Learn more.
How does this help? The problem is that the subtitle overlay is rendered before the video is fed to the videosink, and any upscaling is (usually) done in hardware and/or by the xv extensions in the video sink.
It's hard to fix unless we do the scaling always in software (and even then it would need changes in the way playbin works).
As I commented in http://bugzilla.gnome.org/show_bug.cgi?id=340887#c17, subtitle renderer can get information about media resolution, and I implemented that subtitle render scale text size as media resolution.
But issue is remained that video sink element can change aspect-ratio, as tim told.
Subtitles is correct sized now, but we need to get the fonts with a better resolution. When we open a video with a small resolution, the fonts seems a little bit ugly. It not happens with big resolutions' videos.
We know what's needed, but this is not really fixable at the GStreamer level at the moment. Some work that might help fix this may be done soon though. (It can be fixed at the application level though if the application takes care of rendering/overlaying the subtitles itself, which is usually only realistic if the videosink is hardcoded to something suitable).
We added to the OverlayCompositionMeta parameters the destination windows size. Currently pango textoverlay, will render bigger if this parameters is found. This requires a videosink that support the overlay (atm only glimagesink and supposedly vaapisink).