Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

That's actually a very good analogy to why Beamr's "minimal bitrate for no quality loss" isn't groundbreaking at all, especially since there is necessarily quality loss in lossy H264 -> H264 encoding.

85% is already a quality number, saying relatively how much quality you are willing to give up for kilobytes in your output JPEG. Similarly, x264's CRF option is a quality number, saying how much quality you are willing to give up for bitrate.

Inevitably Beamr will produce some files that are inefficient, as well as some files that have noticeable banding and banding. The difference is CRF allows adjustments.



Consider applying for YC's Winter 2026 batch! Applications are open till Nov 10

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: