[gstreamer-bugs] [Bug 555607] New: subrip subtitles typefind too strict
GStreamer (bugzilla.gnome.org)
bugzilla-daemon at bugzilla.gnome.org
Wed Oct 8 13:24:01 PDT 2008
If you have any questions why you received this email, please see the text at
the end of this email. Replies to this email are NOT read, please see the text
at the end of this email. You can add comments to this bug at:
http://bugzilla.gnome.org/show_bug.cgi?id=555607
GStreamer | gst-plugins-base | Ver: 0.10.21
Summary: subrip subtitles typefind too strict
Product: GStreamer
Version: 0.10.21
Platform: Other
OS/Version: All
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: gst-plugins-base
AssignedTo: gstreamer-bugs at lists.sourceforge.net
ReportedBy: xavierb at gmail.com
QAContact: gstreamer-bugs at lists.sourceforge.net
GNOME version: 2.23/2.24
GNOME milestone: Unspecified
Please describe the problem:
I have a (malformed?) srt file that doesn't get detected as a subtitle file by
gstreamer sub parse.
(whereas it works with other mediaplayers)
it looks like:
=====
1
0: 0:26, 26 --> 0: 0:28, 17
I can't see.
2
0: 0:30, 30 --> 0: 0:33, 22
I really can't see.
3
0: 0:40, 40 --> 0: 0:44, 44
I still can't see anything.
[...]
======
But if I just change the first two lines, filling with '0' instead of spaces:
=====
1
00:00:26,026 --> 00:00:28,017
I can't see.
2
0: 0:30, 30 --> 0: 0:33, 22
I really can't see.
3
0: 0:40, 40 --> 0: 0:44, 44
I still can't see anything.
[...]
============
all works as expected.
Steps to reproduce:
Actual results:
Expected results:
Does this happen every time?
Other information:
--
See http://bugzilla.gnome.org/page.cgi?id=email.html for more info about why you received
this email, why you can't respond via email, how to stop receiving
emails (or reduce the number you receive), and how to contact someone
if you are having problems with the system.
You can add comments to this bug at http://bugzilla.gnome.org/show_bug.cgi?id=555607.
More information about the Gstreamer-bugs
mailing list