Usually for web its a good idea to output to the most widely viewable codec's possible. Just because many browsers manage to expand coverage for "not for web" videos doesn't mean it isn't a good idea to target what is the most broadly playable. Maybe there is a lot that can be done on both sides to meet in the middle but you do have less than standard codecs on both video and audio.
So for audio the most standard is `aac`, and for video that's `libx264` for quality or `h264_nvenc` for gpu accelerated but might come out looking blocky if there is any low light or lot of movement.
This is my goto: `ffmpeg -i "your source file or url" -c:v libx264 -c:a aac out.mp4
MP4s can play on an iphone. It depends on what's in the mp4. Mp4 vs mkv vs webm is like .zip, .rar, .tar.gz. It's just a container format. AV1 and Opus are definitely less standard.
x0x7 1 points 9 months ago
Usually for web its a good idea to output to the most widely viewable codec's possible. Just because many browsers manage to expand coverage for "not for web" videos doesn't mean it isn't a good idea to target what is the most broadly playable. Maybe there is a lot that can be done on both sides to meet in the middle but you do have less than standard codecs on both video and audio.
So for audio the most standard is `aac`, and for video that's `libx264` for quality or `h264_nvenc` for gpu accelerated but might come out looking blocky if there is any low light or lot of movement.
This is my goto:
`ffmpeg -i "your source file or url" -c:v libx264 -c:a aac out.mp4
MP4s can play on an iphone. It depends on what's in the mp4. Mp4 vs mkv vs webm is like .zip, .rar, .tar.gz. It's just a container format. AV1 and Opus are definitely less standard.