Of course, objective metrics do not replace subjective testing, but this should still be okay to get some very rough estimates. I dusted off my own automated codec testing setup so I can track AV1-development. I only removed the "2004" text because I thought using "original" would be clearer to convey that the visual novel came before any think else Fate-related. dav1d.exe -framethreads 6 -tilethreads 2 -o /dev/null -muxer yuv4mpeg2 -i 2> /dev/null It'll be more interesting after ASM optimizations start trickling in.ĮDIT: after playing a bit with the numbers I've been able to push the times down a bit further and CPU util higher (50-53% range): Right now dav1d is implemented in pure C and of course it shows. # time aomdec.exe -threads=8 -o /dev/null dav1d.exe -framethreads 8 -o /dev/null -muxer yuv4mpeg2 -i 2> /dev/null Using my most CPU-intensive clip (PresageFlowerFight, 1080 encoded with as many tiles as possible) I have only been able to observe a 45% max utilization with -framethreads 8 (to clarify, the original visual novel only renders at 800圆00 while this "merge project" will have HD visuals and high-res text - that alone should make it a no-brainer)Īlso, the pre-edit "the original visual novel from 2004" was just fineI only removed the "2004" text because I thought using "original" would be clearer to convey that the visual novel came before any think else Fate-related. You gave me a reason to install FSN again :DJust as long as it's that upcoming "merge project" mentioned on the last couple of pages at the end of the linked thread, otherwise I'll never forgive you. I mean, if its too slow on an i7-8550U, then it'll be too slow for almost all laptops in existence except for maybe those 6core i9 laptops and those crazy gamer/professional laptops that have full-fat desktop CPUs like that Asus with a Ryzen 1700. please tell me I'm not being overly optimistic by saying that? The way I see it, a Xeon x3470 shouldn't be all too different from the likes of an i7-8550U seeing as the Xeon has a ~33% IPC deficit while the i7 has a ~33% clockrate deficit, so the end result should be pretty similar (not counting AVX anyway). Now the wait begins for dav1d to be implemented into LAVfilters and for my low multi-threaded utilization woes to be gone once and for all! I surely hope so.Īnd a small heads up, Video Dev Days () have officially begun, and today they're going to showoff dav1d, their very own decoder! settings benwaggoner suggested a few pages ago (), which in my limited testing came around at half aomenc's time a week or two ago.Īlso rav1e might become a real game changer for av1 encoding in the same timeframe. Maybe they'll get cpu-used=4 on par (speed wise) with x265's placebo-and-then-slowed-down-some-more, using the no-wpp etc. Now, of course these things don't really follow a linear time-optimization correlation, buuuuut I wonder where we'll be in another 4 months :) The 0.1.0-9348 () build is from April, so that's 146 days () between the first and the last tested build. I wonder how long is going to take for another 10 times improvement. (And for being on the first line in the works, thanks to y'all for what you do!)Īlso, the pre-edit "the original visual novel from 2004" was just fine, I didn't choose FSN just because the clips look good ) I'd have you fight me IRL for dissing anything ufotable, but that evened out after you gave me a reason to install FSN again :D (and that's not all all because I've had a hand with some of the media stuff in the latest and upcoming unofficial English PC versions of "Fate/stay night Realta Nua" (), nope no way what 'choo talkin' bout Willis you crazy)
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |