I am working on a website that has video hosting capability. Users can upload video files and i will generate multiple versions with different qualities or just audio, thumbnails and things like that.<p>I have chosen the mp4 container because of how widely supported it is. To prevent users having to fetch whole files, i use the fast start option, where the container's metadata is written at the beginning of the file, instead of at the end.<p>Next, I have picked h264 codec because of how widely supported it is. VP8/VP9/AV1/x265/x266 are certainly better but the h264 software encoding is often beating hardware encoding due to highly optimized and time-proven code and supported hardware. And the uploaded videos are already compressed, users won't be uploading some 8k raw videos where most advanced codes would be useful for preserving "quality".<p>For audio, i have picked opus codec. Seems like good value over others. Not much else to add.<p>I run the ffmpeg to convert video with command like this:<p>ffmpeg -hide_banner -loglevel error -i input.mp4 -g 52 -c:v h264 -maxrate:v vbr -bufsize vbr -s HxW -c:a libopus -af aformat=channel_layouts=7.1|5.1|stereo -maxrate:a abr -ar 48000 -ac 2 -f mp4 -movflags faststart -map 0:v:0 -map 0:a:0 output.mp4<p>where vbr is video bitrate like 1024k(1mbps), abr is audio bitrate like 190k and HxW is video dimensions in case of resizing.<p>I wonder how are folks that handle video encoding process and generate their videos?<p>How did you pick your settings, what issues have you encountered and any tips you can share are certainly appreciated.<p>Quite a niche segment when it comes to operations and not being merely consumer/customer.
Video codec transcoding is very CPU resource expensive. If you do a lot of it, you should be looking into doing hardware-accelerated transcoding.
<a href="https://trac.ffmpeg.org/wiki/HWAccelIntro" rel="nofollow">https://trac.ffmpeg.org/wiki/HWAccelIntro</a><p>My ffmpeg how-to/examples/scratchfile can be viewed here:
<a href="https://paste.travisflix.com/?ce12a91f222cc3d7#BQPKtw6sEs9cECW7ZZgjthcpj4eyWsao1EHNn8tBTVyj" rel="nofollow">https://paste.travisflix.com/?ce12a91f222cc3d7#BQPKtw6sEs9cE...</a>
Generally when you are hosting videos you don’t pick one set of transcoding settings and stick with that. You transcode many many renditions and then serve up the appropriate one depending on the client. It’s quite difficult and expensive in terms of both processing and storage. This is why it is so difficult to unseat the incumbent platforms like YouTube. It’s also why so few people do this on their own.
Last 3 years I traveled extensively and had limited and flakey bandwidth.<p>You should have a low bandwidth setting that also uses new codecs.<p>Like 64kbit stereo opus is to my ears almost imperceptible to CD audio. I think listening tests by professionals recommend using between 64kbit to 96kbit for perfect audio.<p>Anything beyond is a waste unless we are talking about more than stereo.<p>Also if you want, you can use mpeg dash to stream video. Here you encode video into small series of chunks/files. When player can't handle high bandwidth, it can switch to lower bandwidth automatically, and vice versa. This is what YouTube and any professional places do. This will also help prevent users from easily downloading complete video. The trick is that you will need to ensure all videos are split on same key frame, so either use two pass encoding, or define that every ?3? seconds exactly is a new video file.<p><a href="https://www.cloudflare.com/en-ca/learning/video/what-is-mpeg-dash/" rel="nofollow">https://www.cloudflare.com/en-ca/learning/video/what-is-mpeg...</a>
> How did you pick your settings, what issues have you encountered and any tips you can share are certainly appreciated.<p>The settings are picked based on what format, resolution, bitrate, and codec I'd like. I don't think this is something you need to spend time nitpicking, admittedly. :)<p>You mention you're working on a site for video hosting. Have you thought about how you're going to deliver video at scale? Sending video over the wire is super expensive and your costs will probably increase faster than your revenue, unless you're charging out the gate. Cloudflare has some plans which let you deliver for nearly free, but your content needs to be fairly static.<p>Good luck! Don't sweat the small stuff - just keep building.
For synchronized group watching I typically encode to h264 and aac in mp4. Video: render subtitles if available, downscale to 720p if larger, ensure yuv420p, encode with: preset slow, crf 24, and tune animation or film as appropriate. Copy audio if aac, 2 channel, and bitrate is less than 160k otherwise: force 2 channel, encode at 128k. Fast start is needed otherwise I'd use a separate program to put the "header" at the start.<p>As for your command line, what do you think -g 52 does? Why do you give conflicting audio channel settings?
Your choice of codecs is odd. If you decided you need h.264 for compatibility, that also means you need AAC and burned-in subtitles/captions or you lose all of h.264's broad support to missing audio and text support.<p>If you can restrict support to just current Android, Chrome, and Firefox, you can use VP9, Opus, and SRT. Willfully-outdated platforms like Apple and Roku have screwed over everyone.
There's one thing I learned from asking questions like this. You never get a satisfying answer, and you ultimately have to <i>just pick something</i>. This is not about the quality of answers, this is just how the world works. No definitive solutions, just compromises
Go on a specialized video forum and not just ask on HN. Example: <a href="https://www.video-dev.org" rel="nofollow">https://www.video-dev.org</a>
If you're building a product, maybe use a CDN during MVP phase while you validate?<p>Don't think your end customers will care who's serving the video?
If you want browser-friendly video, look into HLS, simply MP4 with faststart is not enough. Plenty of ffmpeg snippets around.<p>Care to share what the site is?