#x264 — Public Fediverse posts

"[...] 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/

Trying to setup #Radarr and #Sonarr to stick to #x264 because my relatives have shit systems and wow, simply being able to choose your codec would be so much easier than the byzantine nightmare they have implemented

Trying to setup #Radarr and #Sonarr to stick to #x264 because my relatives have shit systems and wow, simply being able to choose your codec would be so much easier than the byzantine nightmare they have implemented

Trying to setup #Radarr and #Sonarr to stick to #x264 because my relatives have shit systems and wow, simply being able to choose your codec would be so much easier than the byzantine nightmare they have implemented

Trying to setup #Radarr and #Sonarr to stick to #x264 because my relatives have shit systems and wow, simply being able to choose your codec would be so much easier than the byzantine nightmare they have implemented

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.

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.

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.

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.

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.

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.

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.

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

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

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

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

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

Simple x264/x265 Launcher v3.04:
https://github.com/lordmulder/Simple-x264-Launcher/releases/tag/v3.04

#release #simplex264launcher #x264 #x265

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!

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

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

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

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

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

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...

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...

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...

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...

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...

Scheint so als hätte ich #Owncast Settings gefunden, die ganz gut passen könnten.

Morgen dann mal mein #OBS konfigurieren, #Intel #Quicksync Rendering verbraucht #CPU technisch echt nen Witz im Vergleich zu meinen #Ryzen 5 2600X mit #X264.

Jetzt noch das #SteamDeck #XboxSeriesS und #NintendoSwitch an die #CaptureCard binden und dann sollte nichts mehr im Wege stehen.

Energie technisch ist das so viel Effizienter als mit mein Desktop und seiner #GTX1060 bei nahezu selber Qualität. 😂

Scheint so als hätte ich #Owncast Settings gefunden, die ganz gut passen könnten.

Morgen dann mal mein #OBS konfigurieren, #Intel #Quicksync Rendering verbraucht #CPU technisch echt nen Witz im Vergleich zu meinen #Ryzen 5 2600X mit #X264.

Jetzt noch das #SteamDeck #XboxSeriesS und #NintendoSwitch an die #CaptureCard binden und dann sollte nichts mehr im Wege stehen.

Energie technisch ist das so viel Effizienter als mit mein Desktop und seiner #GTX1060 bei nahezu selber Qualität. 😂

Scheint so als hätte ich #Owncast Settings gefunden, die ganz gut passen könnten.

Morgen dann mal mein #OBS konfigurieren, #Intel #Quicksync Rendering verbraucht #CPU technisch echt nen Witz im Vergleich zu meinen #Ryzen 5 2600X mit #X264.

Jetzt noch das #SteamDeck #XboxSeriesS und #NintendoSwitch an die #CaptureCard binden und dann sollte nichts mehr im Wege stehen.

Energie technisch ist das so viel Effizienter als mit mein Desktop und seiner #GTX1060 bei nahezu selber Qualität. 😂

Scheint so als hätte ich #Owncast Settings gefunden, die ganz gut passen könnten.

Morgen dann mal mein #OBS konfigurieren, #Intel #Quicksync Rendering verbraucht #CPU technisch echt nen Witz im Vergleich zu meinen #Ryzen 5 2600X mit #X264.

Jetzt noch das #SteamDeck #XboxSeriesS und #NintendoSwitch an die #CaptureCard binden und dann sollte nichts mehr im Wege stehen.

Energie technisch ist das so viel Effizienter als mit mein Desktop und seiner #GTX1060 bei nahezu selber Qualität. 😂

I thought I was ready to fight the final boss of the stream, but x264 had other plans for me.

The MajorLinux Show: Horizon Zero Dawn (Part 3) (01/11/2023)

https://majorlinux.com/the-majorlinux-show-horizon-zero-dawn-part-3-01-11-2023/

#x264 #Video #Encoder #h264 #OBSStudio #NVENC #Nvidia #HorizonZeroDawn #GuerillaGames #Sony #Nixxes #Streaming #Twitch #YouTube #BlackFediverse #BlackFedi #BlackMastodon #Blerd #PC #Gaming

I thought I was ready to fight the final boss of the stream, but x264 had other plans for me.

The MajorLinux Show: Horizon Zero Dawn (Part 3) (01/11/2023)

https://majorlinux.com/the-majorlinux-show-horizon-zero-dawn-part-3-01-11-2023/

#x264 #Video #Encoder #h264 #OBSStudio #NVENC #Nvidia #HorizonZeroDawn #GuerillaGames #Sony #Nixxes #Streaming #Twitch #YouTube #BlackFediverse #BlackFedi #BlackMastodon #Blerd #PC #Gaming

I thought I was ready to fight the final boss of the stream, but x264 had other plans for me.

The MajorLinux Show: Horizon Zero Dawn (Part 3) (01/11/2023)

https://majorlinux.com/the-majorlinux-show-horizon-zero-dawn-part-3-01-11-2023/

#x264 #Video #Encoder #h264 #OBSStudio #NVENC #Nvidia #HorizonZeroDawn #GuerillaGames #Sony #Nixxes #Streaming #Twitch #YouTube #BlackFediverse #BlackFedi #BlackMastodon #Blerd #PC #Gaming

I thought I was ready to fight the final boss of the stream, but x264 had other plans for me.

The MajorLinux Show: Horizon Zero Dawn (Part 3) (01/11/2023)

https://majorlinux.com/the-majorlinux-show-horizon-zero-dawn-part-3-01-11-2023/

#x264 #Video #Encoder #h264 #OBSStudio #NVENC #Nvidia #HorizonZeroDawn #GuerillaGames #Sony #Nixxes #Streaming #Twitch #YouTube #BlackFediverse #BlackFedi #BlackMastodon #Blerd #PC #Gaming

I thought I was ready to fight the final boss of the stream, but x264 had other plans for me.

The MajorLinux Show: Horizon Zero Dawn (Part 3) (01/11/2023)

https://majorlinux.com/the-majorlinux-show-horizon-zero-dawn-part-3-01-11-2023/

#x264 #Video #Encoder #h264 #OBSStudio #NVENC #Nvidia #HorizonZeroDawn #GuerillaGames #Sony #Nixxes #Streaming #Twitch #YouTube #BlackFediverse #BlackFedi #BlackMastodon #Blerd #PC #Gaming

I thought I was ready to fight the final boss of the stream, but x264 had other plans for me.

The MajorLinux Show: Horizon Zero Dawn (Part 3) (01/11/2023)

https://majorlinux.com/the-majorlinux-show-horizon-zero-dawn-part-3-01-11-2023/

#x264 #Video #Encoder #h264 #OBSStudio #NVENC #Nvidia #HorizonZeroDawn #GuerillaGames #Sony #Nixxes #Streaming #Twitch #YouTube #BlackFediverse #BlackFedi #BlackMastodon #Blerd #PC #Gaming

I thought I was ready to fight the final boss of the stream, but x264 had other plans for me.

The MajorLinux Show: Horizon Zero Dawn (Part 3) (01/11/2023) https://www.youtube.com/watch?v=gLwq_IibOWI

#HorizonZeroDawn #PC #OBS #x264 #Streaming #Twitch #Gaming

I thought I was ready to fight the final boss of the stream, but x264 had other plans for me.

The MajorLinux Show: Horizon Zero Dawn (Part 3) (01/11/2023) https://www.youtube.com/watch?v=gLwq_IibOWI

#HorizonZeroDawn #PC #OBS #x264 #Streaming #Twitch #Gaming

STILL Trying to compile all the appropriate #FFMPEG #libraries statically and then FFMPEG 5.1 on #macOS.

(Please don’t tell me #macports or #homebrew! I want a portable #static build WITH ENABLE_HDR10_PLUS=ON, HDR, and other flags)

Been at it for 3 days and always some other problem with a dependency - or STUPID things like #x264’s lack of a “—disable-shared” flag to the ./configure! 😡

Sometimes it’s #arm64 #compile issues, others it’s the #intel! ARGH!

I thought I was ready to fight the final boss of the stream, but x264 had other plans for me.

The MajorLinux Show: Horizon Zero Dawn (Part 3) (01/11/2023) https://www.youtube.com/watch?v=gLwq_IibOWI

#HorizonZeroDawn #PC #OBS #x264 #Streaming #Twitch #Gaming

I thought I was ready to fight the final boss of the stream, but x264 had other plans for me.

The MajorLinux Show: Horizon Zero Dawn (Part 3) (01/11/2023) https://www.youtube.com/watch?v=gLwq_IibOWI

#HorizonZeroDawn #PC #OBS #x264 #Streaming #Twitch #Gaming

I thought I was ready to fight the final boss of the stream, but x264 had other plans for me.

The MajorLinux Show: Horizon Zero Dawn (Part 3) (01/11/2023) https://www.youtube.com/watch?v=gLwq_IibOWI

#HorizonZeroDawn #PC #OBS #x264 #Streaming #Twitch #Gaming

I thought I was ready to fight the final boss of the stream, but x264 had other plans for me.

The MajorLinux Show: Horizon Zero Dawn (Part 3) (01/11/2023)

https://majorlinux.com/the-majorlinux-show-horizon-zero-dawn-part-3-01-11-2023/

#HorizonZeroDawn #PC #Gaming #Streaming #Twitch #OBSStudio #x264

I thought I was ready to fight the final boss of the stream, but x264 had other plans for me.

The MajorLinux Show: Horizon Zero Dawn (Part 3) (01/11/2023)

https://majorlinux.com/the-majorlinux-show-horizon-zero-dawn-part-3-01-11-2023/

#HorizonZeroDawn #PC #Gaming #Streaming #Twitch #OBSStudio #x264

I thought I was ready to fight the final boss of the stream, but x264 had other plans for me.

The MajorLinux Show: Horizon Zero Dawn (Part 3) (01/11/2023) https://www.youtube.com/watch?v=gLwq_IibOWI

#HorizonZeroDawn #PC #OBS #x264 #Streaming #Twitch #Gaming

OOoohh! I just statically compiled AtomicParsley for Synology doing the same instructions except adding "LDFLAGS=-static " to the #make command. It worked!

Okay, so I did #FFMPEG earlier, #x264 / #x265, and now I did #MP4Box and #AtomicParsley!

My workflow is almost complete on #Synology!

I'm also completely thrilled that - after installing Docker Desktop - it was this easy!

OOoohh! I just statically compiled AtomicParsley for Synology doing the same instructions except adding "LDFLAGS=-static " to the #make command. It worked!

Okay, so I did #FFMPEG earlier, #x264 / #x265, and now I did #MP4Box and #AtomicParsley!

My workflow is almost complete on #Synology!

I'm also completely thrilled that - after installing Docker Desktop - it was this easy!