Note that H.264 and H.265 are the video compression standards and x264 and x265 are FOSS video encoding libraries developed by VideoLAN.
Important distinction, thanks for clarifying because I always forget!
x265 no contest, all day every day. Then again we should probably be migrating to AV1 ASAP
I think it has to reach a bit more device saturation before encoders jump to it. But yeah AV1 is much better for everyone. Having AOM there to work on it and protect it is a good bonus. Pirates and Netflix on the same team there lol
I guess I'll have to see if my TV really can decode AV1 then, as my nvidia shield definitely won't
The trouble with AV1 is that it's about a decade behind h.265 in terms of hardware support. Most people aren't upgrading their gpus every single generation, so by the time AV1-compatible hardware starts to see significant market share, it's pretty likely that h.266-compatible hardware will be on the market as well.
Of course, there's also software encoders; but benchmarks of current software encoders put av1 anywhere between 50-1000x slower than x265 for comparable quality and bitrate.
It's definitely cool that people are working on a royalty-free video codec, but h.265 is the undeniable king for the time being.
I'd agree with you except that my LG CX already supports AV1. Now I don't know the numbers, but I do know these LG OLED TVs are pretty popular
No arguments about it being a good TV, but the vast majority of people do not have shiny new LG oled TV's. Hell, most people are still using old 1080p lcd's without any smart TV features, and the people who have got new TV's over the past few years tend to skew heavily towards buying relatively cheap 4k TV's that may not have any smart TV features (after all; if i already have a roku/apple tv/chromecast/etc that covers all of my streaming needs, why would I pay a huge premium to get these features a second time?)
yeah but don't most streaming services already provide multiple formats depending on client compatibility? HEVC is cool and all and AFAIK pretty much a requirement for anything UHD, but if Netflix et al can instead send AV1 (like they could if I ran netflix directly on my TV) then that would further reduce their bandwidth requirements. I don't know how long it will take for AV1 to achieve enough market penetration for it to be worth it to them, but here's to hoping it'll be sooner rather than later
Netflix rolled out av1 support for a handful of Samsung smart TV's about a year and a half ago, then kinda shoved the project under the rug and never mentioned it again. My guess is that the added costs of having to store their entire library twice plus having to re-encode everything made it uneconomical. Besides, av1 doesn't have a bandwidth advantage over h.265; all of the comparisons that Google likes to use to show off the codec are av1 vs h.264, which is pretty sneaky and misleading imo.
H265 is objectively superior in just about every way UNLESS you're trying to play it on hardware that doesn't support it. The only reason to use H264 is for broad compatibility.
The issue is more political than technical. Hopefully AV1 will fix that.
Pretty sure it's just more of a hardware age issue. Smart TV makers don't put much effort into their firmware, so if they don't support a codec now they probably won't support it ever. Devices made before a certain year probably won't ever support H265. I suspect we'll run into the same thing with AV1, unfortunately. It's another objectively superior codec that will have compatible issues. 🤷
Except h265 is only ever used for 4k outside piracy. This is because Codec licensing issues.
Once it's conceivable to do so, it would make sense for Netflix to announce it won't make new Netflix ports for TVs without AV1.
It's not necessary hardware compatibility but also software compatibility. Both are proprietary.
Also HEVC isn't supported by browsers for that reason.
also its not just pure "compatibility", but I had a time when I played vids to my TV over an old laptop (from around 2015). Worked like a charm. But some x265 vids went into full-on stutter mode in scenes where a lot of stuff was happening... was more a nuisance than a dealbreaker, but still, preferred x264 versions if I could get them
Sounds like your TV isn't fully compatible with x265. You can get around that by using a modern streaming stick that supports it.
Agreed. I've had problems playing h.265 on other devices, streaming, etc, where 264 would work fine.
amen. I just discovered AV1 so that seems cool as far as space saving goes
I just wish we had more AV1 releases
It's not like a ton of people have compatible hardware anyway. It'll eventually become more common as more uploaders can encode and downloaders can decode.
As far as I know most uploaders prefer software encoding for the best result. Even with the most advanced encoder (e.g. SVT-AV1) and the latest hardware, that becomes a taxing task with AV1.
Neither. AV1 if available, if not I download a high quality x264 copy and do my own transcode. AV1 is high quality with smaller file sizes, but isn't very common right now.
Where have you ever found AV1? I've literally never once seen it in the wild. It seems awesome though, I would definitely choose that over anything else
It really is awesome. Lots of leaps forward for AV1 recently. It encodes faster than x265 in some situations with so much space saved. It's still in the early stages, really, and the compression isn't perfect, but for video streaming purposes, I'll take it over x265 any day.
It encodes faster than x265 in some situations with so much space saved
on ffmpeg?
I tested it like 6months to a year ago I think, and it had similar storage requirement at similar visual fidelity but transcoding took what seemed 5x to 10x the time
/e: for future reference, I'm testing a transfer to transcoding to AV1 instead of hevc
ffmpeg -i /path/to/infile -c:v libsvtav1 -preset 9 -svtav1-params tune=0:enable-overlays=1:scd=1:scm=0:fast-decode=1 -crf 50 -g 240 -pix_fmt yuv420p10le /path/to/outfile
These are a mix of what I read here:
https://gist.github.com/BlueSwordM/86dfcb6ab38a93a524472a0cbe4c4100
and here:
https://trac.ffmpeg.org/wiki/Encode/AV1
general gist:
preset is encoding speed, higher is faster, this setting gets me a bit faster than what i had my hevc encode set up
tune=0 tunes for being good looking
fast-decode lessens cpu use on decode
crf 50 seems fine for my use
-g 240 changes keyframe insertion to every 240 frames
-pix_fmt yuv420p10le gives 10bit color depth which helps with dark scenes and doesn'T cost much space
On ffmpeg, yeah. I can get close to real-time encoding with the new version of libsvtav1 and I save space with around the same visual fidelity as x265, at least, in my experience. If you want to try it out, I recommend using the ab-av1 tool, which automatically finds the best CRF to VMAF for encoding.
edit: Transcoding speeds, I don't find that it's slow, even if I'm using software for transcoding, though I've only been using it for my Jellyfin server for about a month or so.
how is the support for AV1 on devices? can most play it back? does plex support it?
"Most 2020 and newer 4K TVs have AV1 HW decoding support.
Apple hasn't added AV1 hardware to any of their devices yet but they are easily capable of software decoding 1080p AV1.
These smartphone chips support AV1 hardware decoding: MediaTek Dimensity 1000 and newer All Google Tensor chips Samsung Exynos 2200 Qualcomm Snapdragon 8 Gen 2
Streaming devices with HW AV1 support: Amazon Fire TV Stick 4K Max Amazon Fire TV Cube 3rd Gen Google Chromecast with Google TV HD Onn. Google TV 4K Streaming Box Xiaomi TV Stick 4K Xiaomi TV Box S 2nd Gen
Roku Streaming Stick 4K 3820 Roku Streaming Stick 4K+ 3821 Roku Ultra 4800 Roku Ultra LT 4801 Roku Ultra 4802 /!\ Roku is not recommended for anime since it apparently does not support ASS or PGS subtitles
PC stuff: CPUs: Intel's Tiger Lake (mobile 11th gen), Rocket Lake (desktop 11th gen) and newer support AV1 HW decoding. AMD's Rembrandt (mobile 6000 series), Raphael (desktop 7000 series) and newer support AV1 HW decoding. 10+ year old desktop computers with a decent CPU are capable of software decoding 1080p AV1.
GPUs: Nvidia's RTX 3000 series and newer support AV1 HW decoding. AMD's RX 6000 series (except RX 6400 / 6500 XT) and newer support AV1 HW decoding. All Intel ARC GPUs support AV1 HW decoding.
People can use YouTube to check for AV1 hardware support on their current devices. Just turn on Stats for Nerds and play a video. It will show you the codec you're using and YouTube defaults to AV1 if your device supports it. If your CPU usage is low during playback, it's successfully using the HW decoder." also yes plex supports it afaik.
Dunno about Plex, but Jellyfin supports AV1 direct play just fine. Just not on Roku, which I mainly use it on. I'm a small-time contributor on the Roku version, though, and there's progress towards AV1 support, at least.
rav1ne and dav1nci on 1337x
Good looking out. Been using primarily usenet and haven't seen anything pop with AV1 encoding.
1337x, search for AV1. There's not that much right now, but I'm starting to see more of it.
For now its x265. Though later on itll be av1.
Wow I never heard of AV1 before, it sounds really promising!
For some reason plex doesn't support it yet, though jellyfin does at least
I just heard about it a few minutes ago and it seems really nice too. Especially with all the space it saves.
I was trying to start getting some movies in 4k to take full advantage of my new 4k tv other than gaming, but honestly the sheer size of 4k films has me staying with 1080 for at least a little more
AV1 we should have more hardware acceleration in the future. AVIF is also promising.
AVIF is a great format, but I'm still salty over what Google did to JPEG XL. If at least Firefox adds support I will use JPEG XL on my websites with AVIF as fallback. Oh yeah, and then we have MS Edge that doesn't even support AVIF yet lol.
Now with SVT-AV1, its debatably as fast or faster than HEVC
AVIF is just AV1 but for images. Doesn't seem to relate much with movies
The first time I grabbed a 1080 265 and it was almost half the file size of a 264 I had and the quality was visually the same, I knew I could never go back.
x265 is just objectively better than x264. I'm not sure what's to poll. It really comes down to the encoder themselves which ends up a better result. x265 has a minor draw back in that it's new and older things don't naturally support it and a decent draw back in that it takes more CPU power to decode the stream for playback. Other than that though x265.
The various quality though comes from inexperienced or lazy encodes for both formats being available. I have such a pet peeve for someone taking a x264 encode and uploading it in x265 with like a 2% file size reduction and talk about how much better it looks. And the general downloader eats it up because 'x265 gud' to a certain degree. It hurts because then that typically becomes all you can get and no conversion is truly lossless so even re-encoding them myself can take a lot of work to get the reduction without quality loss. I've seen x265 480p encodes that end up with bigger files sizes than if you encoded the shit in AVI, because they seem to think low CFR and 265 is instant quality at a "better" size. If you take the time to really dial in the settings, run it at a slower speed, and understand what type of content you're encoding you can get an incredibly high quality small file. But that takes a decent amount of knowledge and a lot of patience. That's what really sets apart good encoders/releases.
Idk the fix. It doesn't help there's also people convinced a larger file size has inherently better quality. Like seeing a bluray 1080p rip in x265 that's a larger file than an entire bluray disc can hold drives me up a wall because usually it's one of the more seeded files. Like obviously people uploading and tagging 4k lossless files know what they are providing, those files are needed for the proper encodes to eat up.
But RARBG tagged releases were amazing quality. You typically had to go up a few gigs for similar quality from another release. Pahe can really nail some tv shows. Few other encoders back in the day. YIFY/YTS are amazing for the size, but you are giving up some quality. But you can't beat a 1.5gig movie that is better than streaming quality at times.
Yeah, I don't get the poll. Why would anyone use x264 I don't know!
The general pattern is that 4k will be x265 and 1080P encodes with DV / HDR10 need to be x265.
But non HDR / DV 1080P and below is x264.
That's what the encoders on the cabal trackers are doing.
If it's patent-encumbered, it doesn't exist as far as I'm concerned.
I wouldn't even know it was patented if it wasn't for windows trying to charge $0.99 over it but is definitely better to know sooner than later. What's your preferred encoding?
Since having a device that can natively watch x265 I only get that format now. I’m not sure of the quality is better vs x264 but for TV shows the disk space reduction makes up for any quality loss. Movies might be different and it depends on the film but I’m still only getting 1080p rips so again maybe the quality is that important compared to 4K?
I am 100% in on 265, I've gotten my Plex users to upgrade to newer devices or they can have transcoded video.
I would love to migrate to AV1 in a few years, but that's a ways out.
4K x264 rips (the few that are out there) are hilariously big compared to the same quality 4K x265 rips
Because of this post, I reencode a BD rip I made using handbrake to see how small the output file would be. I used the 4k av1 fast profile, but changed the audio tract to passthrough. Holy crap, 44gb down to 1.5gb. what black magic is this?
AV1 is very efficient (around twice as good as h264), but a filesize that low was almost definitely because the default encoding settings were more conservative than the ones used to encode the blu-ray. The perceptual quality of that 1.5gb file will be noticeably lower than the 44gb one
I've recoded a bunch of x264 to AV1 and routinely gotten file sizes that are 10-15% of the original file size (a little more than 1/10th the original size)
What I've found is that source content often has a lot of key frames. By dropping key frames down to one per 300 or one per 150 frames (one per 10 or 5 seconds for 30fps) and at scene changes, you can save a LOT of space with no loss of quality. You do give up the ability to skip to an arbitrary point in the content, however. You may have to wait a few seconds for rendering to display if you scroll to an arbitrary point in the content.
If you're just watching the content straight through, no issues. I set CRF to achieve 96 VMAF and I can't tell any difference in quality between the content with that setup.
I had one corpus of content that I reduced from 1.3 TB down to 250 GB after conversion.
Unfortunately, only the most recent TVs have AV1 playback built in, and the current Fire sticks, Chromecast don't have support for playback from a LAN source. I'm hoping the next crop of Chromecast and similar devices get full support, I'm assuming it's just a matter of time until AV1 decoding is included in every hardware decoder since it's royalyy-free.
AV1 is the shit. Still doesn't have broad support on consumer devices yet, but it will come.
Yeah doesn't work on my Roku lol so back to x265
AV1 when available for everything other than 3d content which is ideally x265.
Honestly it blows my mind that x264 is still as popular as it is.
x264 is still popular because lots of active devices (mainly TVs and smartphones) still don't have native support for x265.
People need to upgrade their shit
Remember how long DivX/XviD hung on for, it's all down to device compatibility.
From a place of ignorance: why is x265 better for 3d and not AV1?
Strictly because the tooling doesn't exist in an easy enough way to go from blu-ray -> full-sbs encode at this point.
I'm constrained by knowledge to only use tools like BD3D2MK3D to create full-sbs encode in x265 which I watch in VR.
If AV1 were an option in this tool I'd consider it, but the additional encoding time might not be worth it to me as the person actually encoding the files.
If anyone has knowledge of F-SBS or F-OU AV1 content or tooling please let me know as I'd be glad to learn.
x265. I do my own rips usually.
Do you use handbreak to do it? And what settings? Is it something that needs to be played around with to see how output is, so doing small segment to determine what is ideal?
No, I use Simple x264/x265 encoder in combo with MeGUI (do the avs in MeGUI, the encode on Simple x264/x265 encoder).
Yeah, you have to play around with it to see what quality suits you. And yes, that takes a looooot of time. Doing small segments will give you a general idea, but the end result may greatly differ in movies with a lot of fast moving action scenes. So, it's best to just encode the whole thing (2 pass, I use the very slow preset, but I'm nuts), view the results and just go from there.
H.265. The file size difference is impressive, and without a noticeable loss of quality, if any.
I've actually had a season of Better Call Saul in h.264, which was 10gb and another one in AV1, which was 1gb and the AV1 seemed to look better
For now, H.265, but I really hope AV1 support improves in the near future.
A lot of comments suggesting AV1 has better compatibility than h265. In my experience the opposite is true. H265 is supported by all of my devices including Plex on my smart TV without transcoding, whereas AV1 makes everything have a fit trying to play it. Am I doing something wrong?
AV1 seems like a more open successor to HEVC/x265 and since it's quite new compared to that only new devices are just starting to support it through hardware decoding/encoding
Looks like it glitched and posted your comment multiple times, at least on my end it looks like it.
me when AV1seemss like a more open successor to HEVC/x265 and since it’s quite new compared to that only new devices are just starting to support it AV1seemss like a more open successor to HEVC/x265 and since it’s quite new compared to that only new devices are just starting to support it AV1seemss like a more open successor to HEVC/x265 and since it’s quite new compared to that only new devices are just starting to support it AV1seemss like a more open successor to HEVC/x265 and since it’s quite new compared to that only new devices are just starting to support it AV1seemss like a more open successor to HEVC/x265 and since it’s quite new compared to that only new devices are just starting to support it AV1seemss like a more open successor to HEVC/x265 and since it’s quite new compared to that only new devices are just starting to support it AV1seemss like a more open successor to HEVC/x265 and since it’s quite new compared to that only new devices are just starting to support it AV1seemss like a more open successor to HEVC/x265 and since it’s quite new compared to that only new devices are just starting to support it AV1seemss like a more open successor to HEVC/x265 and since it’s quite new compared to that only new devices are just starting to support it AV1seemss like a more open successor to HEVC/x265 and since it’s quite new compared to that only new devices are just starting to support it AV1seemss like a more open successor to HEVC/x265 and since it’s quite new compared to that only new devices are just starting to support it AV1seemss like a more open successor to HEVC/x265 and since it’s quite new compared to that only new devices are just starting to support it AV1seemss like a more open successor to HEVC/x265 and since it’s quite new compared to that only new devices are just starting to support it AV1seemss like a more open successor to HEVC/x265 and since it’s quite new compared to that only new devices are just starting to support it AV1seemss like a more open successor to HEVC/x265 and since it’s quite new compared to that only new devices are just starting to support it AV1seemss like a more open successor to HEVC/x265 and since it’s quite new compared to that only new devices are just starting to support it AV1seemss like a more open successor to HEVC/x265 and since it’s quite new compared to that only new devices are just starting to support it AV1seemss like a more open successor to HEVC/x265 and since it’s quite new compared to that only new devices are just starting to support it
My name?
Jugemu Jugemu Go-Kō-no-Surikire Kaijari-suigyo no Suigyō-matsu Unrai-matsu Fūrai-matsu Kū-Neru Tokoro ni Sumu Tokoro Yaburakōji no Burakōji Paipo Paipo Paipo no Shūringan Shūringan no Gūrindai Gūrindai no Ponpokopii no Ponpokonaa no Chōkyūmei no Chōsuke
Search for the user Infinity on TorrentGalaxy
They are re-uploading a lot of RARBG 1080p x265 releases but have are also releasing new movies / tv shows under their own tag with very similar quality and file sizes.
For some unknown reason Infinity strips off the subtitles from the releases. I like a good subtitle track with my release...
On his own releases he's started embedding the subtitles which is nice.. but yes i admit a lot of his rarbg uploads are missing the subs... I generally remux the rarbg ones with the english sub track so it's annoying when they aren't there.. I've had good luck grabbing them from subscene though.
Same here. That’s why I usually tried to get RARBG releases when available. I knew they would have subtitles. Definitely a pain to match and find them later.
As a cinematographer, h.265 is superior in every way. That being said I don't mind watching other formats, as long as their is a reasonable bitrate I'll even watch 720p content
DivX using since 2004, no regrets
- The Chad DivX/XviD user
X265 all day long. Changed out most of my rips and gained terabytes of space back with no loss in quality.
It's amazing being able to hold an entire season of a show in the space that just a couple episodes at 264 would have used.
HEVC Matroska forever ♥
Strange, confusing asymmetry in your title.
10 bit HEVC allows for some crazy good compression ratio. I love it. Put it into an mkv with chapters and externalized series op and ed I can remove and ignore - perfect.
8 bit AVC mp4 for compatibility - if that's the goal.
For acquisition - I'll take what I can get.
I prefer av1 to h265. h264 can play on anything, and while its debatable whether av1 is better than h265, av1 is supported in all browsers and gaining hardware support rapidly.
Also, av1 is a much smaller file size. In some cases, literally half.
Depending on the original source codec, yes, but h265 can do that as well. For me the nice part is the firefox browser support and increasing device support. h265 seems to be stuck in patent hell and not going anywhere.
All my content is converted to CPU encoded x265. Size is MUCH smaller and quality better than GPU encoded x265. My preference is to get remux copies of the content and then encode it myself.
Could you share your encoding settings?
Let's see if this works:
I don't keep 4k content, I find that 2k encodes for the stuff I really want at high fidelity is enough with Nvidia upscaling (Nvidia shield). Plus surprisingly some of my 2k files are no larger than 1080p.
Can i ask what sort of size you're getting with your settings?
Thank you! Are these settings for Handbrake?
Yes sir, I use Tdarr with Handbrake CLI to batch process everything.
If the original encoding is 265. Then 265
If its a high quality 264 encoding, then I'll transcode to 265
Otherwise I stick to 264
Any bitrate cutoff you'd recommend for converting to h265? I recently turned tdarr off because I've been downloading older shows that get absolutely mangled by it
I wish 1080p h265 web-dls were more common. No lossy encoding and multiple streaming services have 1080p h265 available. But I have only seen like a couple release groups do it and most torrent sites don't have them
I've seen those a lot lately on 1337x, but they should still be more common.
look for user "QxR" on 1337x. similar quality and size to rarbg x265. altough you might not find everything you are looking for
Do you know of any way to search 1337x for torrents from specific user?
not that i know of. luckily he appends his releases with his username, so just use the website's general search and input "qxr + what you are looking for"
pretty sure there is a search on the users profile if I'm not mistaken
can't seem to find it
Unfortunaty not, only the global search
pretty sure there is a search on the users profile if I'm not mistaken
H.265 tends to struggle with older, film grain heavy content in my experience, but for newer stuff it wins hands down.
I prefer HEVC, because my media server can transcode it quite easily and it takes way less space than h.264
X265, obviously. AV1 is getting more and more common, so that'll be my next stop.
i have always wondered the difference between the two encodings (beyond the obvious filesize). thanks!
i am also still lamenting the shutdown of RARBG. :(
Both allow for various degrees of parametrization between compression rate, quality, and performance. HEVC/H.265/x265 is just better at it - it allows for better compression at the same quality. Same for 10 bit. Same for AV1.
If you want maximum compatibility to players/playback you take 8 bit AVC/H.264/x264.
Maybe something isn’t right in my setup but I see a noticeable difference in quality between the two. If I have two different files of one movie, one H265 and one H264, I find the H264 picture looks better most of the time
That's not really a measure of the codec, but rather a measure of the encoder. A lot of x265 encoders are awful. They go with x265 for the smaller file sizes and over-compress it, similar to the old YIFY. Groups that use x264 already aren't as concerned with file size (if they were, they'd use x265), and choose settings that optimize for quality.
Do you know any good x265 encoders on top of your head?
Tigole. QxC and UTR. On 1337x
Same size?
H265 should always be smaller for comparable quality to an H264 file due to the better compression (as shown in OPs image)
Is your client compatible with h265? If not, the video may be getting converted with a loss of quality in the process.
HEVC looks better with the same filesize
There's not necessarily a quality difference. It's just a file size for the quality difference
What happened to RARBG? I'm out of the loop
They shut down last month.
My server has a hard time with x265, they constantly stutter when I try to play them through jellyfin
I don't have any issues. Have you got a semi recent GPU in your server?
I like it because it doesn't transcode at all.
No gpu at all. It's an old corporate server I recycled
well yeah there's your problem, you'll want something with a hardware x265 decoder
X265 works fine for me with Roku, but I prefer x264 for 1080, av1 or 265 for 4k.
Same here, not 100% sure I think it's because of a lack of hardware H.265 decoding (in my case, at least)
I can't tell the difference
The picture quality will be pretty much the same or identical, but the 265 file will be about half the size compared to 264. That's the main benefit of h.265 is smaller file sizes without much if any loss in quality.
x265 because all of my devices support it. Once they release a Nvidia Shield TV like device that supports AV1 I'll change once again.
Maybe in the future AV1 will even get faster with the better implementations. It's a great codec just sad that the older Raspberry Pi's just hate x265.
I'm using a pi4 as a media center so 265 as it can cope with 2160p
Wait, does the pi4 support 265 now? I meddled around with it a few years ago, and it always had to transcode 265 to 264.
yeah, it plays 2160p x265 media nicely. Doesn't do Dolby Vision tho, play smooth but colour is off.
Not sure of your use case but shouldn't it only matter what your client (Roku, Fire stick, etc) is capable of playing or are you using the Pi as a client? If the former, the Pi should just act as a file server regardless of the format (provided it's all compatible with the client) while the latter will cause the media to be converted if it can't be played directly.
It might have been an issue with my set-up. I was trying to use the Jellyfin web version from my computer, which probably was not serving the files correctly. I'll have to test again soon to see whether fixes were made in the last 2 years for it :)
Never mind. It's because I was using Firefox, which doesn't support x265 due to licensing issues.
My old ass computers sadly can't handle h265 well so I tend to stick to h264. Moreover, my beamer cannot handle 4K or HDR so that makes more sense overall
Sounds like a time for upgrade
I mainly download x265. I have a few AV1 4K here and there but for now will still to HEVC till AV1 get more widely adopted
I’m a bit of a layman in regard to video codecs, what’s the actual difference?
So basically, quality can differ across them but most of the time you're gonna be happy with how it looks. But where it makes a bigger difference is file sizes. That's the main reason why I care
I have a personal Jellyfin server, and I usually reencode from x264 to AV1. Though if it's a matter of choosing a source, I always go for x264 for the least compression.
can you use AV1 as the source on jellyfin or does that not work out?
What are your steps for the reencoding to av1? Do you use ffmpeg? What's your command & options?
x265 because I like the file size and am satisfied with the quality.
My opinion is based on Rarbg, that was the only time I paid attention. but x265 for sure.
I prefer AV1. The improvement of H.265 over H.264 is not uniform. It takes a lot of effort to get consistent results across content and content types.
I just finished moving all my media to x265 and saved 7TB in the process. Quality looks plenty good to me but I always start from a remux if I can. Totally Worth it for the extra space.
I prefer 265 for efficiency BUT there's a certain nostalgic warmth with 264 over-compressed fuzz. Same deal as with vinyl records. It was such an improvement on xvid back in the day....
Ah yes, you see these are number terms that indicate how videos are encoded. I absolutely understand how to feel with this post and are worthy of participating in the smart discussion in the comments.
imposter syndrome aside, left is a nice grid, right is a really really bad attempt at drawing a golden ratio. Sure left is better to maintain average quality. Why are people talking about converting to one and then the other? Why is the golden ratio one not symmetric!
I know this is a joke but if anyone is curious, the grids indicate how the compression works with each format.
Im far from an expert, but what I've picked up over the years is that videos are compressed by analyzing changes from one frame to the next. If two frames display the same colors in the same grid, the algorithm will recognize this and eliminate the duplicate information (i.e. this 10x10 pixel square is all red for the next 10 frames so record this grid square as red once and use that recorded value 10 times) and only storing what's changed from one frame to the next. With x264 the grid sizes are fixed so some duplication occurs and you have to store information for every grid. With x265, the grid size can scale as needed so you can store more information in a single 'container' (i.e. this 100x100 pixel square is all red for the next 10 frames) allowing compression to be more dynamic when it needs to be leaving you with smaller file sizes.
The joke was precisely that i was to dumb to properly understand this post. Thank you very much for your explanation. I definitely see the benefits x265 can have now. And i may actually use that knowledge when i see download files for both codecs.
I take it the images in the post aren’t the greatest reference then as one of the squares contains both background a portion of a face.
Makes me wonder what ai will allow us to do in the future knowing exactly what information can be compressed and what focus points must remain highest quality.
x265 for long term storage. Far better quality for the size.
That said, I have a lot of devices that can't handle x265 but can handle x264. If compatibility is a consideration x264 is what I'll use.
x265 doesn't work for some hardware scenarios for me (e.g. files served up by UMS from my PC don't play properly on LG TV or using the standard media player on Roku). So I have to use x264 for anything that I won't be watching on a computer or via Stremio.
1080p x265, 720p x264
x265 all the way, it uses less storage but can still look good.
I'd like to have the hard drive space for x264, but as I don't I prioritise 265. If I do download 264 I then use tdarr to convert it to 265 myself.
Curious, Im pretty new to with encoding, but wouldnt going from 264->265 (lossy to lossy) cause further quality loss? I know you arent supposed to do that with audio, did it hurt your video quality at all?
This is accurate as you're making a copy from a copy. Better to download a remux and then convert that.
Yes, but I prioritise hard drive space over quality. There's occasionally artifacting and whatnot, but I don't have the space to download everything in super high quality.
I'm on the same opinion as you, I'm super sad we lost all HEVC encodes just for 1 and 2 GB for a movie is amazing, and it is 1080p which is perfectly enough. There is nothing which will replace that for a while, I can imagine.
I prefer whatever codec my hardware supports. Currently Pi 4 does both your options so I don't care which. x265 has slightly smaller file size for the same quality wish is nice.
I've been using x265 exclusively for all my media needs, except on the rare occasions where only x264 was available. PSARips releases are x265 only
The one most browsers supports.
H.265 whenever i can use it
x265 for 4k hdr
x264 for 1080
H.265 hands down.
On torrentgalaxy there is a new group called infinity. They are slower that rarbg was but no big deal. Also don't think they do everything but enough.
Maybe it's adoption or otherwise but so far H265 content has always had its bitrate down in the gutters compared to its H264 sibling. Quite high bitrate is the deciding factor nowadays amongst the hepas of rubbish floating around. Will wait and see how it goes.
Shit, I like HEVC in theory for the compression especially but it’s copyrighted bullshit or whatever.
I use Plex with lifetime pass on my QNAP NAS and it has to hardware transcode HEVC to a playable format because of said copyrighted bullshit.
It doesn’t affect me that much unless I’m trying to jump around on the media as it will need to load. The other thing is that you can have Plex save transcodes but that obviously gobbles up disk space.
tl;dr 264 = 👑
Shit, I like HEVC in theory for the compression especially but it’s copyrighted bullshit or whatever.
Isn't the same true for AVC/h264, at least in principle? https://en.wikipedia.org/wiki/Advanced_Video_Coding#LicensingMight be less of an issue in practice though, idk.
x264 with my home video media server i like knowing i can access all my content within any web browser anywhere. I'm also not worried about the extra bandwidth and hdd's are cheap, if bandwidth is a concern then x265 is the way to go.
x265 is awesome, although some of the older devices like firesticks from a few years ago struggle with buffering. Not sure if it is older codecs or processor doesn't have enough cores in the device.
720p x264 - good quality, good space, good compatibility
H264 then encode to h265 manually
Unless you're specifically grabbing those high bitrate archival copies you really shouldn't be re-encoding from one lossy codec to another lossy codec.
transcoding is certianly not ideal, but some releases have obscenely high bitrates and if you're more concerned about archival than max fidelity reducing size by a factor of 5-10x (h264->av1) is worth it for me.
It's hard to get to know if encode is good encode :)