README.txt
File Size | 2.776 KB (2,843 bytes) |
---|---|
Download | ClickNUpload | Go4Up▼ | Jheberg▼ | MultiUp▼ | OpenLoad | Sendspace | SolidFiles | ZippyShare |
Hashes | CRC32: 185E1846, MD5: 23879BAB74E9C44A074ED6D8D14E5BB4, SHA1: E2E7BA0C5AD8F6FD3C07EBC8064EF7DE9B54158A, SHA256: 80E90F1CEE3C9160738E9BEFADE277BDF27865D00A6FFFF416997E014524D037, ED2K: B50723A94BB718BC1BBC8FE4ACC1A2B6 |
Additional Info | Video: Source: https://nyaa.si/view/1036108 Encode: 851 kb/s, libaom 1.0.0-969-gfe996504f 10bit, 1080p Audio: Source (Jap): https://nyaa.si/view/1036108 Source (Eng): https://nyaa.si/view/1096360 Encode: 292 kb/s (Jap), 282 kb/s (Eng), libopus 1.3, 5.1 Subs: Signs & Songs: CherryBlossomsDream from https://nyaa.si/view/1096360 Full Subtitles: CherryBlossomsDream from https://nyaa.si/view/1096360 Chapters included WARNING: This is to be considered a tech demo for the new codecs. The objective of this release is threefold: 1) examine implications of using new codecs, in particular AV1/libaom, in an encoding workflow 2) examine the potential gains deriving from doing so 3) fine-tune encoding parameters to use for future encodes Point 1 has been achieved on my end by structuring a personal workflow and gathering encoding times Point 2 asseses how much we have saved using this codec, based on subjective quality evaluations; in short, evaluate the net positives Point 3 is similar to point 2, but this time around we avaluate the net negatives: which scenes look bad? Starting from point 3 some test cases can be isolated and used to tweak encoding parameters and evaluate costs and benefits of doing so. There's going to be a writeup or something on https://reddit.com/r/AV1 where I'd also like to hear the opinion of anybody who doesn't want to comment here on Nyaa for whatever reason. And now a word about decoding performance: AV1 is a new codec. Therefore, the decoders are still getting stuff in working order and playback performance is going up by the day. I asked to somebody who understands hardware far better than I do to draft up some minimum requirements for fast motion, hard-to-decode scenes with the software available right now. Thanks to Nintendo Maniac 64 for his effort and time! Software: MPC-HC 1.8.3 w/ LAVFilters 0.73.1 ________CPUs that are just too slow________ Any Core 2 Duo (even 45nm Wolfdale would need ~6.5GHz) Any CPU lacking SSE 4.1 (most notably Phenom II, Athlon II, 65nm Conroe-based Core 2 Duo/Quad) Low-power architectures (Intel Atom, AMD Jaguar/Puma, any VIA CPU ________CPUs that likely require overclocking________ [45nm Wolfdale] Core 2 Quad; overclocked @ ~4.2GHz [Westmere 2c/2t] Pentium; overclocked @ ~4.4GHz [Westmere 2c/4t] (1st gen) Core i3 / i5; overclocked @ ~3.8GHz [Nehalem 4c/4t] (1st gen) Core i5; overclocked @ ~3.0GHz ________CPUs that should be fine as-is at stock clockrates________ (1st gen) Core i7 870 / 940 / Xeon X3470 (4c/8t Nehalem @ 2.93GHz) Pentium G3250 (2c/2t Haswell @ 3.2GHz) (4th gen) Core i3 4340TE (2c/4t Haswell @ 2.6GHz) (4th gen) Core i5 4670T (4c/4t Haswell @ 2.3GHz) (4th gen) Core i7 4702HQ (4c/8t Haswell @ 2.2GHz) Anything based on AMD Zen (mobile and desktop Ryzen, Athlon 200GE, etc) |
Other Files in this Torrent |
---|
README.txt |