Skip to content

vtenc: Fix checking for certain CPU variants when running in VMs

Piotr Brzeziński requested to merge thewildtree/gstreamer:vtenc-argb-m1-v2 into main

Checks introduced in !3912 (merged) currently set the CPU name string length to 15, which was enough under normal testing, but didn't take into account that it changes when running in a VM. For example - Apple M1 Pro becomes Apple M1 Pro (Virtual), making it too long for the current buffer, thus failing the sysctlbyname call and exposing the broken ARGB/RGBA formats when it shouldn't.

Increasing the buffer size should be enough. I also added a GST_WARNING to notify when (and why) we're disabling the broken formats.

Merge request reports