ghostInTheSSH
Re:3M reaches $10.3B settlement over PFAS contamination of water systems
on Thursday July 13, 2023 @12:34PM (#36711957)
Yeah I don't get why people think holding LLC's and top ranking execs liable is problematic. If you work for an LLC and hold any sort of professional license you are held liable, but the executives who make all the policy decisions around you are not, even if the issue you are held liable for is really their fault.
Re:VPNs on iOS are a scam
on Sunday August 21, 2022 @02:01AM (#32537777)
Serious q, do other implementations exist that I can use on an iOS device?
Re:An update on the campaign to defend serious math education in Calif...
on Tuesday April 26, 2022 @11:09PM (#31175883)
Blank slatists?
Re:H.264 is Magic (2016)
on Monday March 21, 2022 @10:42AM (#30754676)
AFAICT AV1 is just a significantly more complex byte stream to create vs h264, especially if you want that byte stream to be meaningfully more compact than h265 created with x265 @ slow. x265 @ slow was already pretty time consuming[1][2]. And x265 itself had a hard time against x264 for years too[3]. So it may not be that the AV1 initiative is neglecting the public encoders and more that the math and algorithms for computing an AV1 byte stream really are that difficult.
[1] https://mattgadient.com/x264-vs-x265-vs-vp8-vs-vp9-examples/ (this is x265 medium, but it has a nice gui)
[2] I ran a test 1080P encodes using x264 and x265 slow both CRF 20 via handbrake on my m1 MacBook Air and got ~20FPS, and ~4.4FPS for x264 and x265 slow respectively. On my i7-1165G7 NUC I ran the same test but directly invoked FFmpeg and got ~16FPS and ~4FPS for x264 and x265 slow respectively.
[3] This is just a short debate on reddit as an example https://www.reddit.com/r/DataHoarder/comments/lx41cx/x264_vs...