Started by xyzzy, October 06, 2020, 02:05:39 AM
x265 [info]: Main profile, Level-3.1 (Main tier) Stream #0:0: Video: hevc (Main), yuv420p(tv), 1280x720, SAR 1:1 DAR 16:9, 59.94 fps, 59.94 tbr, 1k tbn, 59.94 tbc (default)
x265 [info]: Main 10 profile, Level-4 (Main tier) Stream #0:0: Video: hevc (Main 10), yuv420p10le(tv), 1920x1080, 30 fps, 30 tbr, 1200k tbn, 30 tbc
Quote from: xyzzy on October 06, 2020, 02:05:39 AMI'm using a recent git version, 2.7.6-203-g5869b5f30, on Linux.
Quote from: eumagga0x2a on October 06, 2020, 04:35:54 PMthe internal image format in Avidemux is YV12 which is 8-bit, so there is no gain from using a higher bit depth.
Quote from: eumagga0x2a on October 06, 2020, 04:35:54 PMThis git revision doesn't match any commit in the repository, so I'm somewhat puzzled. 2.7.6 cannot be recent anyway, a lot of development happend already after the version was incremented to 2.7.7.
commit 5869b5f30c1f259c77867f10dc27c1df9e73dde7Author: eumagga0x2a <email@example.com>Date: Fri Oct 2 00:11:14 2020 +0200 [build/createDeb] Add libtwolame-dev as build dependency, remove libfaad-dev and libdca-dev as we prefer libavcodec, regroup packages for clarity
Quote from: xyzzy on October 06, 2020, 05:35:52 PMIn order to support 10 bit encodes one either needs to link with the 10 bit library, which is limited to 10 bit only, or use the x265_api_get() interface to have the appropriate library dlopened. But if one does the latter, then all access to libx265 needs to be through the api pointer and avidemux doesn't use that.
Quote from: xyzzy on October 09, 2020, 06:15:32 AMOne could allow profile in advanced mode. Just call `x265_param_apply_profile()` after putting in all the params. But then it could be that a setting is turned on in the UI, but disabled anyway because of the profile, which would be confusing.