vmaf VS coreboot

Netflix did VMAF for this: https://github.com/Netflix/vmaf

It checks a reference video against an encoded video and returns a score representing how close the encoded video appears to the original from a human perspective.

Not sure this is the right sub but I'm going to encode my entire BluRay collection in AV1 / NVEC. I'd like to optimize settings with VMAF but would like an ubuntu/debian based GUI to work with.

VMAF for anybody that doesn't know quantifies the quality difference between a source and modified video.

Netflix even has a method to measure perceivable quality difference. A little while ago I used this tool to calculate this.

Well you can use something like https://mediaarea.net/en/MediaInfo to look at the files and https://github.com/Netflix/vmaf to see if there is no loss.

Vmaf exists

You can try some tests https://github.com/Netflix/vmaf

You can try VMAF as well (which ffmpeg supports). It's normally recommended to make a lossless copy first as a baseline too

Why BIOS (did you mean UEFI?) when it runs the best boot loader, which is Coreboot¹. Many users would love to re-flash their bios/uefi for it, if it’s supported.

1: https://www.coreboot.org/

Coreboot is 0.6% C++.

NovaCustom ; some models come with Dasharo a coreboot distribution.

You can also use Mr. Chromebox Script to install Coreboot on your chromebook to get a UEFI BIOS on your Chromebook and then you can go an install either a linux distro or even Windows if you want. It's a pretty straightforward process and also reversable if you want to go back to just using ChromeOS.

Some models are available with Dasharo a [coreboot]https://www.coreboot.org/) distribution.

why no haswell_ult_dmi_registers for broadwell? in https://github.com/coreboot/coreboot/blob/master/util/inteltool/pcie.c

use croshfirmware.sh from https://github.com/coreboot/coreboot/tree/master/util/chromeos

There may be other protections to restrict SPI flash access for security reasons (so you might not be able to flash your custom firmware in the OS), but worst case you can use a HW flasher (or maybe USB flashback). Still, this doesn't address the elephant in the room - platform initialization code might be open-sourced, but that isn't everything. You'll still need to figure out the board-specific stuff (the Super I/O chip, chipset GPIOs, other peripherals, etc.). Using coreboot as an example, Intel provides the Firmware Support Package blob to handle platform initialization. I think AGESA is somewhat similar to this, though Intel publicly releases the binaries for use in coreboot/etc. Thanks to the FSP, coreboot has support for recent Intel chipsets. However, there is only support for two recent consumer boards: the MSI PRO Z690-A WiFi DDR4 and DDR5.

does anyone know what is https://github.com/coreboot/coreboot/blob/b12caef23bc1b29c2e658f2b728cc4beac1e62b9/src/northbridge/intel/haswell/vcu_mailbox.c

Download crosfirmware.sh and run it from command line: bash crosfirmware.sh droid