https://forum.videohelp.com/images/imgfiles/NAK7p9v.png
Against black/dark backgrounds, the edges of the subtitles look really grainy. Is there anything I can do to fix that? Specifically, I'm trying to emulate the look of these subtitles as much as possible:
https://forum.videohelp.com/images/imgfiles/fhgGLGU.png
The bottom image looks much better, and it doesn't have that grainy look around the edges of the words. I exported the CLUT from the bottom image's DVD and imported it into the top one (my DVD) and used dvdsubedit to make sure the transparency/colors were the same, but the top image is how it ended up looking afterwards.
+ Reply to Thread
Results 1 to 19 of 19
-
Last edited by wubikens; 21st Feb 2015 at 00:33.
-
I got that too, I think the grey bits are supposed to be translucent but it doesn't actually work and you end up with grey instead.
-
Have you tried updating to the latest version? I can't seem to duplicate the problem any more. (I have the old version with the artefacts, and the srt it was made from and yet there's no little grey bits on the new version no matter what settings I use)
-edit- Oh, I'm using Subtitle Edit, do I even have dvdsubedit...
-edit2- yup, just remade them with the old version and the little grey bits came back...Last edited by ndjamena; 21st Feb 2015 at 06:28.
-
I'm taking my SRT subs (this is their original format), putting them in Sub Edit, exporting as VobSub, and then authoring those with my DVD through Subtitle Creator's wizard. These are my Sub Edit settings:
https://forum.videohelp.com/images/imgfiles/XsLWhdY.png
I'll edit the colors post-authoring with dvdsubedit. -
If you mux the subtitles into an MKV or MP4 and play them back before touching them with Subtitle Creator, do they play back properly?
You may be allying a palette to subtitles where it doesn't belong. -
Try exporting them as SUP subtitle files (or converting the VOBSubs to SUP within SubtitleCreator) and then authoring directly using Muxman, skipping SubtitleCreator's Authoring Wizard. Then afterwards fix the colors in PGCEdit or DVDSubEdit. SubtitleCreator's Authoring Wizard isn't very good and is known to mess up subs.
Last edited by manono; 21st Feb 2015 at 14:18.
-
Still had the issue when manually adding the subtitles without the use of Subtitle Creator.
Using MaestroSBT seems to eliminate the issue, and makes my subs look fantastic. However, my timings keep getting screwed up whenever I use Maestro. I have my timings exactly how I want them, but Maestro keeps asking me for an FPS in/out. Is there any way to use Maestro but keep my timings the way that they are? -
Are you being intentionally vague? Exactly what did you do? Manually adding the subs to what? Created how? Added them into what program?
However, my timings keep getting screwed up whenever I use Maestro.
...but Maestro keeps asking me for an FPS in/out. -
Thank you for your help! And I apologize for the vagueness.
1. I just did method 2 of this guide. I tried doing what you recommended in your other reply, authoring directly with Muxman and then importing the CLUT I wanted to use with PGCEdit and then editing the colors and transparency with dvdsubedit. I skipped using Subtitle Creator altogether.
2. I have an .ssa file that I'm importing into Maestro, with correct timings. When I export this file with Maestro into a .son format, the timings are changed. Even if I pick the same input/output fps, the timings will be different. You actually helped me with something similar previously. Thing is, when I do the 29.97 > 30 conversion in Maestro, it doesn't work (the timings are off). But when I do it in SubtitleCreator or Subtitle Edit, the timings are correct. I have two sets of .ssa files:
(a.) One with my original timings, before I convert the FPS from 29.97 > 30.
(b.) One with my converted timings, after doing 29.97 > 30.
I've tried putting both through Maestro. Like I mentioned up above, when I put the (a.) subtitles in Maestro with an input FPS of 29.97 and an output of 30, it doesn't convert it with proper timings the way that SubtitleCreator and Subtitle Edit do. When I put the (b.) subtitles in Maestro with input and output FPS of the same value (29.97 for both fields), it still changes the timings.
3. I actually read the Maestro guide you wrote and tried setting the input/output frames to the same setting, but the timings still get changed.
Edit: Would it actually be possible to convert the time code of my .ssa to the .son file Maestro creates? The amount of dialogue lines are the same, and I could do it manually through Sub Edit I suppose (changing the times for each line of dialogue, one at a time). But is there a program that could do it automatically?Last edited by wubikens; 21st Feb 2015 at 23:47.
-
In Subtitle Edit:
File -> Import Images ...
Drag-drop the images
Rigth Click -> Import new time codes )(select the .ssa)
Rigth Click -> Export -> Vobsub -
-
Looks like I jumped the gun a bit. The subtitles were timed right at the beginning, but became gradually out of sync towards the middle/end (slightly faster than they should have been). It seems as if the time code isn't being properly applied to the VobSubs from my .ssa/.srt files.
-
Sounds odd. Same number of subtitles in srt/ssa/vobsub? Perhaps open .idx in Notepad and compare timestamps with .srt/.ssa?
-
Correct, the number of subtitles is the same. I figured out what was causing the issue, thankfully. But now I have one last problem:
https://forum.videohelp.com/images/imgfiles/W5HhIfv.png
Maestro isn't rendering some of the punctuation marks properly. Like for instance, the above picture, there should be two en dashes (–) but instead this happens. Sometimes it'll do the same thing for commas and apostrophes. Anything I can do to fix that? -
If the source is an srt or ssa/aas file try forcing it to save as ANSI. Or see if you can try converting between ANSI and UTF-8.
Or find a setting somewhere to get the program to properly interpret between ANSI and UTF-8.
http://www.alanwood.net/demos/ansi.html
en dash = ANSI 150
em dash = ANSI 151
anything above 127 in UTF-8 is considered a two byte character.
http://www.w3schools.com/charsets/ref_utf_punctuation.asp
en dash = UTF-8 8211
em dash = UTF-8 8212 -
Thanks, that fixed it. Just opened in notepad and switched from UTF-8 to ANSI.