niconiconiApr 8

"[...] feel free to hang out in #x264 where we discuss a wide variety of topics that are, in fact, totally x264-related like touhou and starcraft [...]" https://wiki.videolan.org/X264asm/The English equivalent of "Is it #anime? How do I patch KDE 2 on FreeBSD?"

ɯɟʇɹFeb 12
Es siempre interesante descubrir nuevas cosas, o conocimientos, tecnologias, pero llegado a cierto nivel, cansa, agota
Leyendo sobre las (des)ventajas (costos, adopcion, requerimientos de hw, etc) del nuevo estandar que lentamente se esta imponiendo en el mundo de la #transcodificacion de material #audiovisual, parece ser que no deja de ser compleja la decision
Bajo las condiciones actuales, #x264 y #x265 son mejores opciones para los usuarios finales, porque parece que consumen menos, son mas extendidos y soluciones como #jellyfin se llevan muy bien con ellas
Por el contrario, #AV1 no tiene costos de patentes, las futuras tarjetas graficas ya estan añadiendo por defecto soporte desde fabrica, PERO actualmente consume lo suyo, y si no inviertes en una grafica decente, a duras penas podras transcodificar archivos multimedia
BerndAug 28, 2025
I have a weird behaviour of #ffmpeg on #NetBSD: when transcoding a video (either from an existing video or from still frames, doesn't matter) with #x264, everything is fine. But when I encode with #x265, the ffmpeg process sets itself to niceness 20. I can trace the system calls, and it does indeed call setpriority with x265, and not with x264, but I cannot find it in the source code.

This happens with both ffmpeg5 and ffmpeg7 on NetBSD, but not on Ubuntu. I haven't yet tested anything else.

Normally I wouldn't mind if a CPU-hungry encoder runs "nice", but I would like to decide that for myself, and in my current setup, the CPU clock modulation daemon ignores nice processes and so doesn't raise the frequency, and so my encoding runs slow. And non-superusers cannot lower the niceness.

Another weird NetBSD problem. Please help or boost.
AliveDevilJul 10, 2025

Interesting, from my testing it looks like SVT #AV1 Preset 10 (CRF 26) is equivalent to #x264 Preset Veryfast (CRF 22), for one specific movie.

It's the same encoding time, same size, and same XPSNR score.

Marcus AdamsFeb 5, 2025
So I'm doing some pixel peeping to look for differences in #x264 and #AV1 encoding quality and while they've visually been pretty close, I've found one example where AV1 really trounces x264 at smaller size; Hacksaw Ridge. I originally ripped this Bluray with an RF of 20 to x264. Today's rip was to AV1 with RF 22. The smoke really shows how much better AV1 can be. x264 almost looks dithered, or like it's using a smaller color palette. Now extrapolate this out over the whole movie.
Marcus AdamsNov 15, 2024

x265 is considerably more efficient than x264. I just re-encoded the entirety of my copy of Farscape, from the same Bluray source discs. Here's a comparison of the final file size for each copy. Settings were as follows:

Both copies were encoded with an RF of 20, 1080p, framerate same as source. The #x264 copy only had a 160 kbps AAC stereo audio track. The #x265 copy included that, but also included an un-touched DTS-HD-MA surround sound track, as well as commentary audio tracks.

#Media

Show threadLukas OrsvärnJun 4, 2024

Actually, #HEVC doesn’t work either, using #x264 instead. I don’t really understand why they don’t work since from what I’ve read they should have wide support. 🤔

Been learning more #NixOS including #HomeManager so I can set it up as automated as possible. I’m considering learning setting NixOS up to pull the transcode script straight from a #Git repo, that would be cool!

That script now works on the #RaspberryPi 4. My current challenge is setting up #Nix to run it when the machine turns on with #SystemD.

I can’t really get SystemD to do anything at all, which is frustrating. Not sure what I’m doing wrong. 😑 Once that works though I think the system is operational!

ColinFeb 21, 2024
About 6 months ago I got a bee in my bonnet about the quality of current codecs. I ended up doing more than 1000 encodes, comparing various codecs, presets and quality settings. A little over a month ago I wrote something up about it.
https://colinmckellar.com/2024/01/11/video-encoder-comparison/
#AV1 #ffmpeg #x264 #x265
Video encoder comparison – Something Something

DaGeek247Dec 31, 2023

Comparing compression in AV1, x264, and x265

I recently got it into my head to compare the various popular video codecs in an effort to better understand how av1 works and looks compared to x264 and x265. I also had ideas of using a intel video card to compress a home video security setup, and what levels of compression I would need to get good results.... #codec #comparison #quality #encode #av1 #x264 #x265

https://kbin.social/m/selfhosted@lemmy.world/t/733346

Comparing compression in AV1, x264, and x265 - selfhosted - kbin.social

I recently got it into my head to compare the various popular video codecs in an effort to better understand how av1 works and looks compared to x264 and x265. I also had ideas of using a intel video card to compress a home video security setup, and what levels of compression I would need to get good results....

Michal  Sep 17, 2023

I re-encoded my test video with #x265 at the same bitrates and presets, to visually compare with #AV1 in my simple browser tool.

It turns out that the "#hevc in browser" story is much more complicated than with #AV1. It just doesn't work on any browser on my #Android phone - Firefox nor Chrome.

https://caniuse.com/hevc references "wontfix" issues. I guess I'll just compare them in VLC "offline" then, and for web do #x264 instead...

HEVC/H.265 video format | Can I use... Support tables for HTML5, CSS3, etc

"Can I use" provides up-to-date browser support tables for support of front-end web technologies on desktop and mobile web browsers.