After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 629451 - assrender: two cases where it doesn't use embedded fonts
assrender: two cases where it doesn't use embedded fonts
Status: RESOLVED OBSOLETE
Product: GStreamer
Classification: Platform
Component: gst-plugins-bad
1.4.3
Other Linux
: Normal normal
: git master
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2010-09-12 19:36 UTC by Hammered
Modified: 2018-11-03 13:06 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Hammered 2010-09-12 19:36:48 UTC
I found two cases where assrender doesn't use the embedded fonts to render the text.

First case:
1. Create a sample matroska file with mkvmerge that has a video track, an ASS track and an SRT track in that specific order. Also embed the fonts that the ASS track uses and make sure that these fonts don't exist in the system folder.
2. Launch the file in Totem. Notice that the subs will be rendered properly and the embedded fonts will be used correctly.
3. Change the Subtitles(through Totem's menu) to the SRT track. Allow it to render a line of text and then change it back to the ASS track. Observe now that the rendered subs aren't using the embedded fonts.

Second case;
1. The same as above number 1 but the tracks are in this order: video, SRT, ASS
2. Launch the file in Totem and change to the ASS track. Notice that the subs don't use the embedded fonts.


I use Debian Squeeze(testing) amd64.
Comment 1 Tim-Philipp Müller 2010-09-13 08:00:12 UTC
Could you make those files available by any chance?

Any chance you could test those with current versions of GStreamer (esp. gst-plugins-bad) - I don't think squeeze has the latest assrender/playbin2 versions.
Comment 2 Hammered 2010-09-13 22:43:18 UTC
Here is a file[1] that tests the first case. I won't provide one for the second case because it is directly linked to the first case. Also it is quite trivial to change the track order of this file with mkvmerge.

Also I upgraded today to Debian Unstable (sid) but unfortunately the gstreamer-plugins-bad is still 0.10.19.

Also: -good:0.10.24
      -base:0.10.30
      -ugly:0.10.115
      libgstreamer: 0.10.30

(the bugzilla server didn't allow this big file)
[1]http://hotfile.com/dl/69142091/7820950/multiple-subs-tracks.mkv.html
Comment 3 Hammered 2010-09-22 17:37:05 UTC
any news on this?
Comment 4 Fabio Durán Verdugo 2010-11-05 03:35:45 UTC
Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for.
Thanks!
Comment 5 Tim-Philipp Müller 2010-11-05 08:31:43 UTC
Re-opening, test file has been provided.
Comment 6 Tim-Philipp Müller 2010-11-05 08:34:19 UTC
I can confirm the issue. It seems to be some kind of race condition or problem with sparse stream handling. Even just doing gst-launch-0.10 playbin2 uri=...  will sometimes show the subtitles with comic-style font and sometimes a normal font. Or maybe that's just because the 'default' subtitle stream selection isn't deterministic? However, I also can't select the comic-style subs in totem, so something is definitely wrong.
Comment 7 Andreas Frisch 2014-11-09 17:15:58 UTC
*bump* this issue persists in gstreamer 1.4.3

log excerpt:
0:00:00.626197924   621 0x73a1e060 DEBUG              assrender gstassrender.c:1787:gst_ass_render_event_text:<renderer> got TAG event
0:00:00.626444405   621 0x73a1e060 DEBUG              assrender gstassrender.c:1510:gst_ass_render_handle_tags:<renderer> TAG event has attachments
0:00:00.626844516   621 0x73a1e060 DEBUG              assrender gstassrender.c:1551:gst_ass_render_handle_tags:<renderer> registered new font HUMASNM_.TTF
...
0:00:00.932653701   621 0x73a1e060 WARN       assrender_library gstassrender.c:205:_libass_message_cb:<renderer> fontconfig: Selected font is not the requested one: 'Bitstream Vera Sans Mono Bold' != 'Humana Sans Md ITC TT'
0:00:00.932794590   621 0x73a1e060 LOG        assrender_library gstassrender.c:211:_libass_message_cb:<renderer> Font info: family 'Bitstream Vera Sans Mono', style 'Bold', fullname 'Bitstream Vera Sans Mono Bold', slant 0, weight 200
0:00:00.932956109   621 0x73a1e060 LOG        assrender_library gstassrender.c:211:_libass_message_cb:<renderer> fontconfig_select: (Humana Sans Md ITC TT, 200, 0) -> /usr/share/fonts/tuxtxt.ttf, 0

instead it just selects a random ttf it finds
it's most certainly a race condition because on my fast pc i've seen it actually using the embedded font every now and then.
gonna try to provide logs for success and fail cases and try to find the differences tomorrow
Comment 8 Andreas Frisch 2014-11-18 10:08:32 UTC
logs were totally inconclusive, nothing more to be found in there other than what's already in the last comment
Comment 9 GStreamer system administrator 2018-11-03 13:06:40 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/gstreamer/gst-plugins-bad/issues/26.