9 ms·
> rendering subtitles at the output resolution is better than rendering them at the video resolution I would like to know what's wrong with this approach. I wa
by derefr 10y ago
> rendering subtitles at the output resolution is better than rendering them at the video resolution
I would like to know what's wrong with this approach. I watch a lot of commentated speed-run videos: that's often something like ~244p video, plus soft subtitles. The subtitles get rendered at the source resolution (presumably, into the video framebuffer) and then upscaled along with the image, forcing them to be a tiny blurry mess instead of the crisp, readable text they could be.
- kazinator 10y agoMaybe nothing is wrong; just that maybe it's not always strictly better. Suppose you are asked to form a plan for adding subtitle support to some unfamiliar video platform. It's probably best to start with an open mind about where in the pipeline subtitles will be composed with the video.
- akiselev 10y agoI think that point should be amended to say "rendering subtitles at the output resolution is always better than rendering them at the video resolution." You don't want to upscale 244p soft subtitles to 1080p but you do want to default to giving video authors creative control over how the subtitles are displayed. The ASS subtitle format allows for some very complex styling that can be used as an artistic element in video (or just to make sure there's proper contrast, can be read by color blind people, character differentiation, etc.) so you generally don't want to assume anything. There's also the issue of coordinates for where the subtitles are supposed to be that all go to shit if you render them on a transformed (up/downscaled) frame.
- haasn 10y agoThis comment is pretty much what I was going for. I've reworded it to make it clearer. The issue you can run into in practice is stuff like softsubbed signs, which can clash and look out of place with the native video if you render them at full res. There's also a related issue, which is that if you're using something like motion interpolation (e.g. “smoothmotion”, “fluidmotion” etc. or even stuff like MVTools/SVP), softsubbed signs will not match the video during pans etc., making them stutter and look very out-of-place - the only way to fix that is to render them on top of the video before applying the relevant motion interpolation algorithms. Personally I've always wished for a world in which subtitles are split into two files, one for dialogue and for signs, with an ability to distinguish between the two. (Heck, I think softsubbed signs should just be separate transparent video streams that are overlayed on top of the native picture, allowing you to essentially hardsub signs while still being capable of disabling them) Also, sometimes, rendering at full resolution is prohibitively expensive, e.g. watching heavily softsubbed 720p content on a 4K screen.
- JoshTriplett 10y ago> There's also the issue of coordinates for where the subtitles are supposed to be that all go to shit if you render them on a transformed (up/downscaled) frame. Sure, you have to transform the coordinates to the output. But still, better to render fonts at the final resolution; they'll always look better than if scaled after rendering.
- akiselev 10y ago> Sure, you have to transform the coordinates to the output. But still, better to render fonts at the final resolution; they'll always look better than if scaled after rendering. The font will look better but you have zero guarantee that the subtitles will be better too. Furthermore, you will lose any artistic value that the creator intended. For example, go get the Russian movie Night Watch and watch it with the original subtitles hardcoded and as a separate file. The director insisted on doing the subtitles himself and he used them for great artistic effect throughout the movie [1]. Watch it with scaling and aspect ratio stretching to see how nicely rendered, crisp high resolution fonts can be inferior to a pixelated, stretched version created with intent by an artist. [1] http://readingsounds.net/wp-content/uploads/2015/12/NightWatch-Header.jpg http://readingsounds.net/wp-content/uploads/2015/12/NightWat...
- jheriko 10y agothe point is precisely that it is more complicated than this obvious interpretation. whilst i don't necessarily agree... i do agree that if you want to conform to specs then you can't go thinking this way.
- CoolGuySteve 10y agoIt's also missing the most common error I see: conflating subtitles with closed captions. Closed captions are positioned on the screen to indicate who's talking, have descriptive audio for sound effects, and should be in a high contrast easy to read font (most people with hearing deficiencies also have problems seeing, ie: out of date prescriptions for both hearing aids and eye glasses). As far as I know, QuickTime does it right but the Apple TV, Netflix, and YouTube fuck it up, but that's because I helped write the QuickTime one way back.
- deadmutex 10y agoAFAIK, The YouTube implementation does all of those. Here is a demo: https://www.youtube.com/watch?v=BbqPe-IceP4 https://www.youtube.com/watch?v=BbqPe-IceP4 Please do not spread falsehoods. Disclamer: I work at YouTube.
- deoxxa 10y agohttp://take.ms/fwwhx http://take.ms/fwwhx That is frustratingly poor contrast.
- deadmutex 10y agoThis might be because you might have changed your settings for CC in the past. Here is what mine look like http://imgur.com/HLIVXQ6 http://imgur.com/HLIVXQ6 You can click settings again to change font sizes, font family, colors, etc.
- smnscu 10y agoI have to change my CC settings every damn couple of days because they revert to the same white-on-white 400% bullshit. So thanks for that.
- deadmutex 10y agoI am not sure, but the screenshot I submitted seems to be the default settings. However, software that is 100% perfect is pretty much impossible to write, and if you think there's a systematic issue, please file a bug, so it can help others in same situation.
- deleted 10y ago[deleted]
- the8472 10y agoIn fact, rendering subtitles at the display resolution is one of the big selling points of the xy-subfilter + madvr renderer combination. The only practical downside I have noticed is that accurate rendering of subs containing complex vector graphics or effects (ASS supports that) at > HD resolutions takes a lot of CPU time, sometimes more than a single core can handle in realtime. There probably is a lot of potential for optimization, but those are hobby projects for their maintainers.