Florian Zwoch

I would think the encoder select the proper ones depending on what features are being selected and used by the encoder? I haven't checked though.. Having features and profiles independently...

Ok, AVC and HEVC are a bit different here. In AVC you could for example select to have b-frames, which cannot exist in baseline/constraint-baseline for example. It is a bit...

> ah, so if the video stream obs creates is 10 bit, vah265enc would automatically choose a 10-bit output? I'd hope so. I think I verified that it is/was working...

yuv420p10 sounds like 10 bit to me.

I need to check some time whats happening here. I'm not even sure what Main 10 and yuv420p10 together means. Main 10 shoul dbe 8 bit only, so no idea...

A quick test: ``` $ gst-launch-1.0 videotestsrc ! vapostproc ! vah265enc ! video/x-h265,profile=main ! h265parse ! filesink location=x.265 $ mediainfo x.265 General Complete name : x.265 Format : HEVC Format/Info...

Perhaps.. not even sure what this exact syntax is trying to say, or where these values come from. Using x265enc I can get the Main 10 at the beginning too....

Closing for now. I don't think there is anything to do at the moment.

Common issue when binaries are compiled with a newer glibc. You can mark symbols to be linked to an older version explicitly. See https://github.com/wheybags/glibc_version_header for more info/helpful scripts.