#x265 — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #x265, aggregated by home.social.
-
My 4K Blurays of Westworld arrived in the mail today. I started copying and re-encoding episode 1 of season 2, because I have already watched all of season 1. It's estimated to take 17 hours. Most episodes are going to take about the same amount of time. 4K video is rough to work with! 😅
I guess it will slow down how fast I watch them ...
-
My 4K Blurays of Westworld arrived in the mail today. I started copying and re-encoding episode 1 of season 2, because I have already watched all of season 1. It's estimated to take 17 hours. Most episodes are going to take about the same amount of time. 4K video is rough to work with! 😅
I guess it will slow down how fast I watch them ...
-
My 4K Blurays of Westworld arrived in the mail today. I started copying and re-encoding episode 1 of season 2, because I have already watched all of season 1. It's estimated to take 17 hours. Most episodes are going to take about the same amount of time. 4K video is rough to work with! 😅
I guess it will slow down how fast I watch them ...
-
My 4K Blurays of Westworld arrived in the mail today. I started copying and re-encoding episode 1 of season 2, because I have already watched all of season 1. It's estimated to take 17 hours. Most episodes are going to take about the same amount of time. 4K video is rough to work with! 😅
I guess it will slow down how fast I watch them ...
-
My 4K Blurays of Westworld arrived in the mail today. I started copying and re-encoding episode 1 of season 2, because I have already watched all of season 1. It's estimated to take 17 hours. Most episodes are going to take about the same amount of time. 4K video is rough to work with! 😅
I guess it will slow down how fast I watch them ...
-
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. -
Got another box of surplus #DVDs to rip. I hadn't ripped anything lately, especially since getting our new mini PC, so this was my first chance to compare #x265 to #AV1 encode on our Minisforum UM890 Pro with a Ryzen 9 8945HS. This thing absolutely rips. AV1 encodes of DVD quality content run at hundreds of fps, depending on the movie. When using Handbrake's best recommended settings and comparing to x265, AV1 goes faster, makes smaller files and looks just as good.
https://handbrake.fr/docs/en/latest/workflow/adjust-quality.html
-
Got another box of surplus #DVDs to rip. I hadn't ripped anything lately, especially since getting our new mini PC, so this was my first chance to compare #x265 to #AV1 encode on our Minisforum UM890 Pro with a Ryzen 9 8945HS. This thing absolutely rips. AV1 encodes of DVD quality content run at hundreds of fps, depending on the movie. When using Handbrake's best recommended settings and comparing to x265, AV1 goes faster, makes smaller files and looks just as good.
https://handbrake.fr/docs/en/latest/workflow/adjust-quality.html
-
Got another box of surplus #DVDs to rip. I hadn't ripped anything lately, especially since getting our new mini PC, so this was my first chance to compare #x265 to #AV1 encode on our Minisforum UM890 Pro with a Ryzen 9 8945HS. This thing absolutely rips. AV1 encodes of DVD quality content run at hundreds of fps, depending on the movie. When using Handbrake's best recommended settings and comparing to x265, AV1 goes faster, makes smaller files and looks just as good.
https://handbrake.fr/docs/en/latest/workflow/adjust-quality.html
-
Got another box of surplus #DVDs to rip. I hadn't ripped anything lately, especially since getting our new mini PC, so this was my first chance to compare #x265 to #AV1 encode on our Minisforum UM890 Pro with a Ryzen 9 8945HS. This thing absolutely rips. AV1 encodes of DVD quality content run at hundreds of fps, depending on the movie. When using Handbrake's best recommended settings and comparing to x265, AV1 goes faster, makes smaller files and looks just as good.
https://handbrake.fr/docs/en/latest/workflow/adjust-quality.html
-
Got another box of surplus #DVDs to rip. I hadn't ripped anything lately, especially since getting our new mini PC, so this was my first chance to compare #x265 to #AV1 encode on our Minisforum UM890 Pro with a Ryzen 9 8945HS. This thing absolutely rips. AV1 encodes of DVD quality content run at hundreds of fps, depending on the movie. When using Handbrake's best recommended settings and comparing to x265, AV1 goes faster, makes smaller files and looks just as good.
https://handbrake.fr/docs/en/latest/workflow/adjust-quality.html
-
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.
-
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.
-
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.
-
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.
-
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.
-
Simple x264/x265 Launcher v3.04:
https://github.com/lordmulder/Simple-x264-Launcher/releases/tag/v3.04 -
A question for any #digital #video experts out there... I'm confused as heck about the results from #libx265 (used via #ffmpeg, not the #x265 tool) regarding quality vs. preset and ratefactor.
I'm far from the first person to be confused by this, but I haven't found any real answers.
First I'll just show some analysis from some test encodes of a file; ssim and ratefactor numbers are coming from the CSV stats output of libx265.
1/x
-
A question for any #digital #video experts out there... I'm confused as heck about the results from #libx265 (used via #ffmpeg, not the #x265 tool) regarding quality vs. preset and ratefactor.
I'm far from the first person to be confused by this, but I haven't found any real answers.
First I'll just show some analysis from some test encodes of a file; ssim and ratefactor numbers are coming from the CSV stats output of libx265.
1/x
-
A question for any #digital #video experts out there... I'm confused as heck about the results from #libx265 (used via #ffmpeg, not the #x265 tool) regarding quality vs. preset and ratefactor.
I'm far from the first person to be confused by this, but I haven't found any real answers.
First I'll just show some analysis from some test encodes of a file; ssim and ratefactor numbers are coming from the CSV stats output of libx265.
1/x
-
A question for any #digital #video experts out there... I'm confused as heck about the results from #libx265 (used via #ffmpeg, not the #x265 tool) regarding quality vs. preset and ratefactor.
I'm far from the first person to be confused by this, but I haven't found any real answers.
First I'll just show some analysis from some test encodes of a file; ssim and ratefactor numbers are coming from the CSV stats output of libx265.
1/x
-
A question for any #digital #video experts out there... I'm confused as heck about the results from #libx265 (used via #ffmpeg, not the #x265 tool) regarding quality vs. preset and ratefactor.
I'm far from the first person to be confused by this, but I haven't found any real answers.
First I'll just show some analysis from some test encodes of a file; ssim and ratefactor numbers are coming from the CSV stats output of libx265.
1/x
-
Oooohhhhh #x265 v3.6 release notes:
"ARM64 NEON optimizations:- Several time-consuming C functions have been optimized for the targeted platform - aarch64. The overall performance increased by around 20%. SVE/SVE2 optimizations"
Thanks, y'all! I love it when codebases start coding to ARM64 NEON! #FFMPEG #FFMPEG7
-
Oooohhhhh #x265 v3.6 release notes:
"ARM64 NEON optimizations:- Several time-consuming C functions have been optimized for the targeted platform - aarch64. The overall performance increased by around 20%. SVE/SVE2 optimizations"
Thanks, y'all! I love it when codebases start coding to ARM64 NEON! #FFMPEG #FFMPEG7
-
Oooohhhhh #x265 v3.6 release notes:
"ARM64 NEON optimizations:- Several time-consuming C functions have been optimized for the targeted platform - aarch64. The overall performance increased by around 20%. SVE/SVE2 optimizations"
Thanks, y'all! I love it when codebases start coding to ARM64 NEON! #FFMPEG #FFMPEG7
-
Oooohhhhh #x265 v3.6 release notes:
"ARM64 NEON optimizations:- Several time-consuming C functions have been optimized for the targeted platform - aarch64. The overall performance increased by around 20%. SVE/SVE2 optimizations"
Thanks, y'all! I love it when codebases start coding to ARM64 NEON! #FFMPEG #FFMPEG7
-
Oooohhhhh #x265 v3.6 release notes:
"ARM64 NEON optimizations:- Several time-consuming C functions have been optimized for the targeted platform - aarch64. The overall performance increased by around 20%. SVE/SVE2 optimizations"
Thanks, y'all! I love it when codebases start coding to ARM64 NEON! #FFMPEG #FFMPEG7
-
Is it just me or is #FFMPEG v7 *way* faster (on #ARM64 at least) when doing multiple things at once? (ie: #nlmeans noise reduction, #crop, then #x265)
I mean these used to take hours and hours on several of my Agatha Christie files (which need noise reduction, crop and encoding). These fly through now at about 30% time reduction per file. Not to mention about 15% smaller size (thanks x265 3.6.x update!)
-
Is it just me or is #FFMPEG v7 *way* faster (on #ARM64 at least) when doing multiple things at once? (ie: #nlmeans noise reduction, #crop, then #x265)
I mean these used to take hours and hours on several of my Agatha Christie files (which need noise reduction, crop and encoding). These fly through now at about 30% time reduction per file. Not to mention about 15% smaller size (thanks x265 3.6.x update!)
-
Is it just me or is #FFMPEG v7 *way* faster (on #ARM64 at least) when doing multiple things at once? (ie: #nlmeans noise reduction, #crop, then #x265)
I mean these used to take hours and hours on several of my Agatha Christie files (which need noise reduction, crop and encoding). These fly through now at about 30% time reduction per file. Not to mention about 15% smaller size (thanks x265 3.6.x update!)
-
Is it just me or is #FFMPEG v7 *way* faster (on #ARM64 at least) when doing multiple things at once? (ie: #nlmeans noise reduction, #crop, then #x265)
I mean these used to take hours and hours on several of my Agatha Christie files (which need noise reduction, crop and encoding). These fly through now at about 30% time reduction per file. Not to mention about 15% smaller size (thanks x265 3.6.x update!)
-
Is it just me or is #FFMPEG v7 *way* faster (on #ARM64 at least) when doing multiple things at once? (ie: #nlmeans noise reduction, #crop, then #x265)
I mean these used to take hours and hours on several of my Agatha Christie files (which need noise reduction, crop and encoding). These fly through now at about 30% time reduction per file. Not to mention about 15% smaller size (thanks x265 3.6.x update!)
-
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
