In DOM version 2.9.37, when there's a line with a mixture of words in italics and regular font, the entire line is replicated three times.
As far as I can tell, it worked OK in version 2.9.30, so the bug must have crept up somewhere between those versions.
For example, this source:
-<dcst:Subtitle TimeOut="00:09:23:22" TimeIn="00:09:20:20" FadeDownTime="00:00:00:00" FadeUpTime="00:00:00:00" SpotNumber="144">
-<dcst:Text Direction="ltr" Halign="center" Valign="bottom" Vposition="10">
der
<dcst:Font Italic="yes">New York Times</dcst:Font>
landete.
</dcst:Text>
</dcst:Subtitle>
results in a burnt in subtitle like this:
New subtitle bug
-
- Posts: 53
- Joined: Wed Sep 09, 2015 5:35 am
Re: New subtitle bug
Hi
I'm not sure if it's DoM's bug. it happend to me 2 days ago but i think it was my mistake.
two example's i've made today,
the first is with an srt source and the second with xml source
I'm not sure if it's DoM's bug. it happend to me 2 days ago but i think it was my mistake.
two example's i've made today,
the first is with an srt source and the second with xml source
You do not have the required permissions to view the files attached to this post.
-
- Posts: 62
- Joined: Thu Aug 04, 2016 12:24 pm
Re: New subtitle bug
I don't know what kind of mistake would cause that kind of behaviour... ?!
Anyway, I tried reverting to version 2.9.30 and the problem immediately went away. I then re-installed 2.9.37 and the problem came back. So toggling back and forth between the versions makes it completely clear to me that it must be a bug in the later version.
I haven't downloaded and kept any versions between 2.9.30 and 2.9.37, so I can't tell exactly in which version the problem first appeared.
Anyway, I tried reverting to version 2.9.30 and the problem immediately went away. I then re-installed 2.9.37 and the problem came back. So toggling back and forth between the versions makes it completely clear to me that it must be a bug in the later version.
I haven't downloaded and kept any versions between 2.9.30 and 2.9.37, so I can't tell exactly in which version the problem first appeared.
-
- Site Admin
- Posts: 2528
- Joined: Thu Nov 14, 2013 2:53 pm
Re: New subtitle bug
Hi Anders,
Thanks for looking into this. It should be fixed in 2.9.38; let me know if you have problems with that version.
Thanks for looking into this. It should be fixed in 2.9.38; let me know if you have problems with that version.
-
- Posts: 62
- Joined: Thu Aug 04, 2016 12:24 pm
Re: New subtitle bug
Yes, a quick test indicates that the problem has indeed been solved in version 2.9.38 !
-
- Posts: 62
- Joined: Thu Aug 04, 2016 12:24 pm
Re: New subtitle bug
Sorry to disturb again, but the case where regular and italic fonts are mixed on the same line seems to be almost impossible to get right.
Same subtitle source as before, but this time soft = NOT burnt in. DOM version is 2.9.38 and playback is by Easy DCP player version 3.4.5.
Lots of unwanted space between words!
Same subtitle source as before, but this time soft = NOT burnt in. DOM version is 2.9.38 and playback is by Easy DCP player version 3.4.5.
Lots of unwanted space between words!
-
- Site Admin
- Posts: 2528
- Joined: Thu Nov 14, 2013 2:53 pm
Re: New subtitle bug
Can you share the input file for these subs?
-
- Posts: 62
- Joined: Thu Aug 04, 2016 12:24 pm
Re: New subtitle bug
I've made a very small test project that I can share, and which will illustrate the problem:
First, I made a very simple subtitle file consisting of only one item:
1
00:00:01,000 --> 00:00:09,000
Testing is <i>really</i> fun!
This is the <i>second</i> line!
Then, I read that .srt-file into Subtitle Edit, and saved it as D-cinema SMPTE 2010. This is the result:
<?xml version="1.0" encoding="UTF-8"?>
<dcst:SubtitleReel xmlns:dcst="http://www.smpte-ra.org/schemas/428-7/2010/DCST" xmlns:xs="http://www.w3.org/2001/XMLSchema">
<dcst:Id>urn:uuid:8cf3bad5-812c-4371-a825-67cf9ba79db6</dcst:Id>
<dcst:ContentTitleText>Test film</dcst:ContentTitleText>
<dcst:AnnotationText>This is a subtitle file</dcst:AnnotationText>
<dcst:IssueDate>2016-08-29T10:42:26.000-00:00</dcst:IssueDate>
<dcst:ReelNumber>1</dcst:ReelNumber>
<dcst:Language>en</dcst:Language>
<dcst:EditRate>24 1</dcst:EditRate>
<dcst:TimeCodeRate>24</dcst:TimeCodeRate>
<dcst:StartTime>00:00:00:00</dcst:StartTime>
<dcst:LoadFont ID="Arial Rounded MT">urn:uuid:3dec6dc0-39d0-498d-97d0-928d2eb78391</dcst:LoadFont>
<dcst:SubtitleList>
<dcst:Font ID="Arial Rounded MT" Size="35" Weight="normal" Color="FFFFFFFF" Effect="border" EffectColor="FF000000">
<dcst:Subtitle SpotNumber="1" FadeUpTime="00:00:00:00" FadeDownTime="00:00:00:00" TimeIn="00:00:01:00" TimeOut="00:00:09:00">
<dcst:Text Vposition="15" Valign="bottom" Halign="center" Direction="ltr">Testing is <dcst:Font Italic="yes">really</dcst:Font> fun!</dcst:Text>
<dcst:Text Vposition="10" Valign="bottom" Halign="center" Direction="ltr">This is the <dcst:Font Italic="yes">second</dcst:Font> line!</dcst:Text>
</dcst:Subtitle>
</dcst:Font>
</dcst:SubtitleList>
</dcst:SubtitleReel>
I now made a very simple project in DOM, only overlaying this single subtitle on a still image (some colour bars). It looks absolutely OK in the preview. I UNchecked the "Burn Subtitles into Image" option to get a DCP with soft subtitles.
Playing back the DCP in Easy DCP Player gives the following result:
Do you need any more information, Carl?
First, I made a very simple subtitle file consisting of only one item:
1
00:00:01,000 --> 00:00:09,000
Testing is <i>really</i> fun!
This is the <i>second</i> line!
Then, I read that .srt-file into Subtitle Edit, and saved it as D-cinema SMPTE 2010. This is the result:
<?xml version="1.0" encoding="UTF-8"?>
<dcst:SubtitleReel xmlns:dcst="http://www.smpte-ra.org/schemas/428-7/2010/DCST" xmlns:xs="http://www.w3.org/2001/XMLSchema">
<dcst:Id>urn:uuid:8cf3bad5-812c-4371-a825-67cf9ba79db6</dcst:Id>
<dcst:ContentTitleText>Test film</dcst:ContentTitleText>
<dcst:AnnotationText>This is a subtitle file</dcst:AnnotationText>
<dcst:IssueDate>2016-08-29T10:42:26.000-00:00</dcst:IssueDate>
<dcst:ReelNumber>1</dcst:ReelNumber>
<dcst:Language>en</dcst:Language>
<dcst:EditRate>24 1</dcst:EditRate>
<dcst:TimeCodeRate>24</dcst:TimeCodeRate>
<dcst:StartTime>00:00:00:00</dcst:StartTime>
<dcst:LoadFont ID="Arial Rounded MT">urn:uuid:3dec6dc0-39d0-498d-97d0-928d2eb78391</dcst:LoadFont>
<dcst:SubtitleList>
<dcst:Font ID="Arial Rounded MT" Size="35" Weight="normal" Color="FFFFFFFF" Effect="border" EffectColor="FF000000">
<dcst:Subtitle SpotNumber="1" FadeUpTime="00:00:00:00" FadeDownTime="00:00:00:00" TimeIn="00:00:01:00" TimeOut="00:00:09:00">
<dcst:Text Vposition="15" Valign="bottom" Halign="center" Direction="ltr">Testing is <dcst:Font Italic="yes">really</dcst:Font> fun!</dcst:Text>
<dcst:Text Vposition="10" Valign="bottom" Halign="center" Direction="ltr">This is the <dcst:Font Italic="yes">second</dcst:Font> line!</dcst:Text>
</dcst:Subtitle>
</dcst:Font>
</dcst:SubtitleList>
</dcst:SubtitleReel>
I now made a very simple project in DOM, only overlaying this single subtitle on a still image (some colour bars). It looks absolutely OK in the preview. I UNchecked the "Burn Subtitles into Image" option to get a DCP with soft subtitles.
Playing back the DCP in Easy DCP Player gives the following result:
Do you need any more information, Carl?
-
- Site Admin
- Posts: 2528
- Joined: Thu Nov 14, 2013 2:53 pm
Re: New subtitle bug
Thanks. DoM does not really change that input subtitle much in the output; the interesting part is:
That rendering just looks wrong to me... can anybody check a file like this on a projector?
Code: Select all
<Text VAlign="bottom" VPosition="10">
<Font Italic="no">This is the </Font>
<Font Italic="yes">second</Font>
<Font Italic="no"> line!</Font>
</Text>
<Text VAlign="bottom" VPosition="15">
<Font Italic="no">Testing is </Font>
<Font Italic="yes">really</Font>
<Font Italic="no"> fun!</Font>
</Text>
-
- Posts: 62
- Joined: Thu Aug 04, 2016 12:24 pm
Re: New subtitle bug
Well, dumping out the relevant part of the .mxf-file gives the following result, except that I have replaced all the spaces with "@"-characters to make them stand out.
My guess is that any spaces present between <dcst:Text> and </dcst:Text> are significant and will be rendered by the player. No matter if they are enclosed by Font-tags or not...
<dcst:Text@Valign="bottom"@Vposition="10">
@@@@@@@@@@<dcst:Font@Italic="no">This@is@the@</dcst:Font>
@@@@@@@@@@<dcst:Font@Italic="yes">second</dcst:Font>
@@@@@@@@@@<dcst:Font@Italic="no">@line!</dcst:Font>
@@@@@@@@</dcst:Text>
@@@@@@@@<dcst:Text@Valign="bottom"@Vposition="15">
@@@@@@@@@@<dcst:Font@Italic="no">Testing@is@</dcst:Font>
@@@@@@@@@@<dcst:Font@Italic="yes">really</dcst:Font>
@@@@@@@@@@<dcst:Font@Italic="no">@fun!</dcst:Font>
@@@@@@@@</dcst:Text>
My guess is that any spaces present between <dcst:Text> and </dcst:Text> are significant and will be rendered by the player. No matter if they are enclosed by Font-tags or not...
<dcst:Text@Valign="bottom"@Vposition="10">
@@@@@@@@@@<dcst:Font@Italic="no">This@is@the@</dcst:Font>
@@@@@@@@@@<dcst:Font@Italic="yes">second</dcst:Font>
@@@@@@@@@@<dcst:Font@Italic="no">@line!</dcst:Font>
@@@@@@@@</dcst:Text>
@@@@@@@@<dcst:Text@Valign="bottom"@Vposition="15">
@@@@@@@@@@<dcst:Font@Italic="no">Testing@is@</dcst:Font>
@@@@@@@@@@<dcst:Font@Italic="yes">really</dcst:Font>
@@@@@@@@@@<dcst:Font@Italic="no">@fun!</dcst:Font>
@@@@@@@@</dcst:Text>