How do Medium get away with articles looking like this? This is what the page looks like for me after loading: <a href="https://i.ibb.co/9rQMXLF/Screenshot-20190614-183927.png" rel="nofollow">https://i.ibb.co/9rQMXLF/Screenshot-20190614-183927.png</a>
Under "Segmented Video Upload Processing" they explain how cutting up the video before upload makes it easier to process. Does anyone know how they're maintaining audio sync? Every single time I've tried to cut up (mp4/m2ts) video to re-encode it in parallel, I've had it go completely out of sync.
It seems a bit overkill to spin up a new worker per segment, especially if encountering I/O bottlenecks. Why not make sure to distribute multiple segments to multiple threads on the same (large-enough) worker so it can stitch them all together from the same machine?
Why not show the video as "uploaded" to the user posting the video (and playback from a local copy), and then publish in the background to other users? Latency of 0 :)
In the meantime, I'm still waiting for the option to disable video autoplay. But they wont, because they want to push the narrative that so many users view video-based ads. You know what, we don't view them, we scroll past them. If you really wanted to be honest with advertisers, you would disable autoplay, and then we could really see how many users really click the play button.
Medium has a paywall on this page. Here's a cache.<p><a href="https://web.archive.org/web/20190614024004/https://instagram-engineering.com/video-upload-latency-improvements-at-instagram-bcf4b4c5520a?gi=4db83dc4ce6b" rel="nofollow">https://web.archive.org/web/20190614024004/https://instagram...</a>