gaythor | 108 points
This is my own hevc encode. let me know what you think.
Source is the uncensored amazon webrip.
https://xxxx.nz/#!Nf5F2IrJ!QBK8QJnFwXb0lri4EKwOR2svJys_zPTaWM2O-3tluZg
Rick.and.Morty.S03E02.HDTV.x264-BATV | Megalinks MegaDB Rick.and.Morty.S03E02.HDTV.x264-BATV -1 CD- Download SubtitleRick.and.Morty.S03E02.720p.HDTV.x264-BATV | Megalinks MegaDB Rick.and.Morty.S03E02.720p.HDTV.x264-BATV -1 CD- Download SubtitleRick.and.Morty.S03E02.Rickmancing.the.Stone.720p.Amazon.WEB-DL.DD+5.1.H.264-QOQ | Megalinks MegaDB Rick.and.Morty.S03E02.Rickmancing.the.Stone.720p.Amazon.WEB-DL.DD+5.1.H.264-QOQ -1 CD- Download Subtitle
^This ^list ^of ^subtitles ^are ^taken ^from ^opensubtitles.org ^| ^For ^feedback ^or ^suggestions ^contact ^/u/indigo6alpha
[-] JulianCatablancas | 2 points
I can't access it :(
[-] Rowan-Paul | 1 points
Thanks!
[-] [deleted] | 1 points
[-] VERY_SAD_RICHARD | 1 points
Looks fantastic! Thanks!
[-] Blazingbee98 | 1 points
Is there a way to rip straight from Amazon nowadays or is it still HDMI capture?
[-] may_be_indecisive | 1 points
[-] C_McButterpants | 8 points | Jul 31 2017 20:56:14
Not sure how beefy your processor is... but you'd certainly benefit from slowing down the encode.
Comparison with PSA's release (177MB) — your textures are less muddy, but the motion edge detail is really suffering.
permalink
[-] gaythor | 3 points | Jul 31 2017 21:00:42
Yeah I could slow it down. This was done on fast. And everything else was just none, I didn't put any filters because I honestly don't know much about them. So I put it on off or auto.
permalink
[-] C_McButterpants | 1 points | Jul 31 2017 21:08:38
Ah right. I never go above Slow/Slower — sometimes only get ~4 fps with my lowly Haswell i5-4570 @3.2GHz.
permalink
[-] gaythor | 2 points | Jul 31 2017 21:04:59
it's hard to balance the size and quality like, I don't understand how ppl get it so small.
permalink
[-] C_McButterpants | 2 points | Jul 31 2017 21:14:24
22:37 runtime = 1357sec = 32,535 images
With a good i7 that can rip through in a reasonable time on VerySlow/Placebo speed you're producing 32 thousand images with less artifacts — cleaner image means more useful compression.
permalink
[-] gaythor | 1 points | Jul 31 2017 22:00:59
I have an i5 too so i get about the same. i did slow and it's still 288mb, how do you get the size down? do you use any filters?
permalink
[-] doober187 | 1 points | Aug 01 2017 01:03:43
Can either of you link me to whatever app you're talking about? I use Avidemux with just a little bit of know how.
what app has "slow/slower / veryslow/placebo" encode speed options?
permalink
[-] MaskedT | 1 points | Aug 01 2017 01:57:14
Most likely handbrake
permalink
[-] doober187 | 1 points | Aug 01 2017 02:46:58
that's what i'm thinking. i'll just as soon stick with avidemux if that's the case.
permalink
[-] gaythor | 1 points | Aug 06 2017 16:56:25
yeah it's just handbrake. but im gonna try out what you mentioned it's the first time I heard of it.
permalink
[-] doober187 | 1 points | Aug 07 2017 01:10:56
a LOT more control over settings and encoding
...to a ridiculous degree
permalink
[-] douchebanner | 1 points | Aug 01 2017 07:35:12
2pass average bitrate?
permalink
[-] gaythor | 1 points | Aug 06 2017 16:48:09
No just 1 pass. And it was on constant 24 I think?
permalink
[-] douchebanner | 1 points | Aug 06 2017 18:46:08
if you want to get the highest quality to size ratio you should consider using 2pass, with x264 it takes roughly 50% longer but i dont know how much longer it takes with x265.
animation also benefits from high frametype lookahead and high maximum frame reference and b-frames, so if you set those high on your encode it should improve quality but at the cost of some speed.
permalink
[-] is_it_fun | 1 points | Aug 01 2017 23:21:36
TWSS.
permalink