3 ms·
Burning subtitles into the video implies re-encoding. And if you want maintain video quality, you'll have to choose a pretty good quality setting like crf=24 an
by ponderingfish 6y ago
Burning subtitles into the video implies re-encoding. And if you want maintain video quality, you'll have to choose a pretty good quality setting like crf=24 and this will take a lot of time even on H.264/AVC.
You are looking at multiple hours (>2) for a 2-hour movie from my experience. One way to reduce this is to spin up a DigitalOcean droplet (a $80 per month droplet) that'll give you a lot of processing power, finish your encoding in 2-3 hours,and shut it down. It'll save you a lot of headache and time.
Not sure I answered your question, but, hope that helped!
- twic 6y ago> Burning subtitles into the video implies re-encoding In principle, would it be possible to only re-encode the macroblocks affected by the subtitles, leaving the rest of the frame bit-for-bit identical? It's been a long time since i read a video encoding specification, so i don't know if things still work this way.
- beagle3 6y agoMuch harder than it sounds because future macroblocks depend on present ones, and motion vectors mean that over a few seconds, transitive dependency can reach the entire image (and does in panned and zoomed shots) Can possibly work, but depending on movie content might not save all that much encoding.
- _Gyan_ 6y agoWhat would be much better would be to encode an overlay raster stream, which the player can then composite at runtime, like they do with text subtitles. Much faster to encode. Can be toggled. But players need to support it.
- danielheath 6y agoYeah, but the whole point of the exercise is to see subtitles on players that don't even support subtitles; they're definitely not going to support an overlay stream.
- fareesh 6y agoThanks. I'm surprised that there isn't something like lambda where you can just get a really fancy cpu on demand for a quick encoding job.