I love this. The widely used standards for video compression are focused on compression efficiency, which is important if you’re netflix or youtube, but sometimes latency and low complexity is more important. Even if only to play around and learn how a video codec actually works.

▲ CharlesW 5 days ago | parent [-]

> The widely used standards for video compression are focused on compression efficiency, which is important if you’re netflix or youtube, but sometimes latency and low complexity is more important.

That's a misconception. All modern video codecs (i.e. H.264/AVC, H.265/HEVC, AV1) have explicit, first-class tools, profiles, and reference modes aimed at both low- and high-resolution low‑latency and/or low‑complexity use.

AV1: Improving RTC Video Quality at Scale: https://atscaleconference.com/av1-improving-rtc-video-qualit...

▲ westurner 5 days ago | parent [-]

There are hardware AV1 encoders and decoders.

Objective metrics and tools for video encoding and source signal quality: netflix/vmaf, easyVmaf, psy-ex/metrics, ffmpeg-quality-metrics,

Ffmpeg settings for low-latency encoding:

  # h264, h265
  -preset ultrafast
  -tune zerolatency

  # AV1
  -c:v libsvtav1
  -preset 8
  -svtav1-params tune=0:latency-mode=1
  -g 60

It's possible to follow along with ffmpeg encoding for visual inspection without waiting for the whole job to complete with the tee muxer and ffplay.

GPU Screen Recorder and Sunlight server expose some encoder options in GUI forms, but parameter optimization is still manual; nothing does easyVmaf with thumbnails of each rendering parameter set with IDK auto-identification of encoding artifacts.

Ardour has a "Loudness Analyzer & Normalizer" with profiles for specific streaming services.

What are good target bitrates for low-latency livestreaming 4k with h264, h265 (HDR), and AV1?

	▲	westurner 3 days ago \| parent [-]
		FFmpeg Explorer is made with ffmpeg.wasm: https://github.com/antiboredom/ffmpeg-explorer .. web: https://ffmpeg.lav.io/