[SmilingWolf]

Originally Posted by Nintendo Maniac 64

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!

...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).

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.

I'm afraid we're not quite there yet. 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
My CPU is an i7-4770, with 4/8 cores

Some timings:

# time ./dav1d.exe --framethreads 8 -o /dev/null --muxer yuv4mpeg2 -i Fight.cq20.1080p.ivf 2> /dev/null

real    0m19,460s
user    0m0,000s
sys     0m0,000s

# time aomdec.exe --threads=8 -o /dev/null Fight.cq20.1080p.ivf

real    0m5,170s
user    0m0,000s
sys     0m0,000s

Right now dav1d is implemented in pure C and of course it shows. It'll be more interesting after ASM optimizations start trickling in.

EDIT: 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):

# time ./dav1d.exe --framethreads 6 --tilethreads 2 -o /dev/null --muxer yuv4mpeg2 -i Fight.cq20.1080p.ivf 2> /dev/null

real    0m17,800s
user    0m0,000s
sys     0m0,000s

Originally Posted by Nintendo Maniac 64

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.

I see, I see