Re: [x265] Fwd: NASM 2.15.03 (MYS2/MinGW) throws a huge amount of macro warnings

Am 24.05.23 um 10:04 schrieb Sam: On Wed, May 24, 2023 at 12:55 PM Mario *LigH* Rohkrämer wrote: Yes, it looks a lot more tidy. Just a few warnings left. chen schrieb am 24.05.2023 um 06:13: > Hello, > > Could you please try my local patch? > > Regards, > Min

Re: [x265] ARM patches

Hi, same here, I'm seeing the same error as below if I try to build x265 (latest master) for macOS arm64 on macOS Ventura (Xcode 14.1). Am 04.11.22 um 08:39 schrieb Damiano Galassi: Hi, I’m getting the following error when trying to build on macOS arm64 since these patches: Undefined

[x265] [PATCH] correct "macOS" to the current spelling v2

From 144c9dd6e8438e346b2ba3a7a494321f9a24dc76 Mon Sep 17 00:00:00 2001 From: Nomis101 Date: Fri, 19 Aug 2022 08:01:14 +0200 Subject: [x265] [PATCH] correct macOS to the current spelling Signed-off-by: Nomis101 --- source/common/version.cpp | 2 +- 1 file changed, 1 insertion(+), 1 deletion

[x265] [PATCH] correctly define 64-bit for aarch64 v2

From c1e8994dc888ccf0f37ebe2a0c8af1753224c886 Mon Sep 17 00:00:00 2001 From: Nomis101 Date: Fri, 19 Aug 2022 07:58:18 +0200 Subject: [x265] [PATCH] correctly define 64-bit for aarch64 Signed-off-by: Nomis101 --- source/common/version.cpp | 2 +- 1 file changed, 1 insertion(+), 1 deletion

[x265] [PATCH] correct "macOS" to the current spelling

From 7bafd9b975bd98c458ef96040b70ee08b30f410d Mon Sep 17 00:00:00 2001 From: Nomis101 Date: Sat, 11 Jun 2022 08:12:48 +0200 Subject: [x265] [PATCH] correct "macOS" to the current spelling Signed-off-by: Nomis101 --- source/common/version.cpp | 2 +- 1 file changed, 1 insertion(+),

Re: [x265] [PATCH] correctly define 64-bit for aarch64

Am 10.06.22 um 23:19 schrieb Nomis101: > From 1a8e353e4e4d0120c85df6c3505738d0f1ba03cd Mon Sep 17 00:00:00 2001 > From: Nomis101 > Date: Fri, 10 Jun 2022 23:11:25 +0200 > Subject: [x265] [PATCH] correctly define 64-bit for aarch64 > > Signed-off-by: Nomis101 > --- > s

[x265] [PATCH] correctly define 64-bit for aarch64

From 1a8e353e4e4d0120c85df6c3505738d0f1ba03cd Mon Sep 17 00:00:00 2001 From: Nomis101 Date: Fri, 10 Jun 2022 23:11:25 +0200 Subject: [x265] [PATCH] correctly define 64-bit for aarch64 Signed-off-by: Nomis101 --- source/common/version.cpp | 2 +- 1 file changed, 1 insertion(+), 1 deletion

Re: [x265] Wrong version info?

Am 22.03.22 um 04:44 schrieb Roger Pack: > On Fri, Mar 11, 2022 at 6:35 AM Mario *LigH* Rohkrämer > wrote: >> It would be wrong, though, if Roger compiled for 64 bit but this binary >> reports "[32 bit][noasm]" when running. Is this the case? > Yes. I believe the binary is actually 64 bit. The

Re: [x265] Releases

Am 03.09.21 um 09:46 schrieb Alexandru Băluț: > In http://hg.videolan.org/x265/file/tip/x265Version.txt > I see "releasetag: > 3.5" but 3.5 is not > available for download at https://get.videolan.org/x265/ > .

Re: [x265] [PATCH][MASTER] Support for Decoding-Energy-Rate-Distortion Optimization (DERDO)

Am 22.10.20 um 15:07 schrieb Christian Herglotz: ___ x265-devel mailing list x265-devel@videolan.org https://mailman.videolan.org/listinfo/x265-devel I've tried to build x265 with this patches applied, but I've discovered some issues. It applied

Re: [x265] [PATCH][MASTER] Support for Decoding-Energy-Rate-Distortion Optimization (DERDO)

Am 22.10.20 um 22:00 schrieb Alex Giladi: Dear Christian, Is there a paper describing the approach? Best, Alex. In the web I found some literature articles. https://www.lms.tf.fau.de/forschung/downloads/decoding-energy-rate-distortion-optimization-derdo-for-hevc-video-coding/

Re: [x265] NASM 2.15.03 (MYS2/MinGW) throws a huge amount of macro warnings

and inline, the other part have similar issue. btw: the latest macro parameters included all of parameter left after that. For example %macro test 1-3+ %3 will be included %4 and after Regards, Min Chen At 2020-09-03 23:56:13, "Nomis101" wrote: Am 03.09.20 um 15:28 sch

Re: [x265] [PATCH] fix warnings when assembling with NASM 2.15

Am 15.07.20 um 20:37 schrieb Nomis101: From e955f07a0596d5e3911dc02e845a2363da44bde4 Mon Sep 17 00:00:00 2001 From: Nomis101 Date: Wed, 15 Jul 2020 20:22:41 +0200 Subject: [PATCH] fix warnings when assembling with NASM 2.15 Adjust code to silence some new warnings added in NASM 2.15. Fixes

Re: [x265] NASM 2.15.03 (MYS2/MinGW) throws a huge amount of macro warnings

Am 03.09.20 um 15:28 schrieb Mario *LigH* Rohkrämer: In the meantime, MSYS2 provides NASM 2.15.04; same output. I had a patch for this in this list. Maybe you could try if this patch will fix the issue for you. https://mailman.videolan.org/pipermail/x265-devel/2020-July/013062.html

[x265] [PATCH] fix warnings when assembling with NASM 2.15

From e955f07a0596d5e3911dc02e845a2363da44bde4 Mon Sep 17 00:00:00 2001 From: Nomis101 Date: Wed, 15 Jul 2020 20:22:41 +0200 Subject: [PATCH] fix warnings when assembling with NASM 2.15 Adjust code to silence some new warnings added in NASM 2.15. Fixes Issue #559. Signed-off-by: Nomis101

[x265] Issue #555: x265 fails to build with nasm 2.15.01 (multicoreware/x265)

New issue 555: x265 fails to build with nasm 2.15.01 https://bitbucket.org/multicoreware/x265/issues/555/x265-fails-to-build-with-nasm-21501 Nomis101: x265 does not build with latest nahm version 2.15.01. I’ve tried to build on macOS and it fails after a few seconds. The Buildlog

Re: [x265] [PATCH]Add: Auto AQ Mode

I would like to have a question to this. I've played around a bit with this patch and encoded some files with --auto-aq. Is there a way to log/determine/find out, which AQ mode the algorithm has decided to use for each frame? Thanks. Am 27.02.20 um 09:59 schrieb Niranjan Bala: > # HG

Re: [x265] [PATCH]Add: Auto AQ Mode

What did happen with this auto-aq idea? Is it planned to pursue this idea further? I quite liked this idea and it gives me a nice reduction in file size. Thanks and regards. Am 27.02.20 um 09:59 schrieb Niranjan Bala: > # HG changeset patch > # User Niranjan

Re: [x265] Issue #534: Warning in x265 code (multicoreware/x265)

Am 22.02.20 um 23:05 schrieb 0brad0: > New issue 534: Warning in x265 code > https://bitbucket.org/multicoreware/x265/issues/534/warning-in-x265-code > > Brad Smith: > > There is one and only one warning throughout the build but it repeats many > times. > > ```c > In file included from >

[x265] Will there be a 3.2.1?

Will there be a 3.2.1 with all those fixes which are now in the Release_3.2 branch, at some point of time? Best Simon ___ x265-devel mailing list x265-devel@videolan.org

[x265] Issue #511: warning: declaration shadows a variable in namespace 'x265' [-Wshadow] (multicoreware/x265)

New issue 511: warning: declaration shadows a variable in namespace 'x265' [-Wshadow] https://bitbucket.org/multicoreware/x265/issues/511/warning-declaration-shadows-a-variable-in Nomis101: While building x265 inside HandBrake, I see some of the following warnings: ‌ ```c /HandBrake/build

Re: [x265] Use cases for aq-mode=4

e-cases > for this mode will be videos with high edge contents. (Ex: Ducks take off, > Crowd run, Raindrops etc). Please write to us if > you have more questions. :)  > > On Thu, Aug 8, 2019 at 3:25 AM Nomis101  <mailto:nomis...@web.de>> wrote: > > I know, al

[x265] Use cases for aq-mode=4

I know, all the command line options are may give an improvement for one situation and others where they don't give an improvement or even hurt quality. So, I've learned aq-mode=3 is best for dark scenes (in SDR). But, I was wondering about the (best) intended use cases for the new aq-mode=4?

Re: [x265] [PATCH] Fix for Issue #373

This is cherry-picked from "Update json11 to v1.0.0 release" and just fixes Issue #373. I checked that it builds on macOS Mojave with hdr10plus enabled. Find patch attached. # HG changeset patch # User Nomis101 # Date 1564692921 -7200 # Do Aug 01 22:55:21 2019 +0200

Re: [x265] [PATCH] Update json11 to v1.0.0 release

Am 25.07.19 um 23:58 schrieb Nomis101 : > Am 25.07.19 um 06:48 schrieb Aruna Matheswaran: >> >> >> On Wed, Jul 24, 2019 at 9:59 PM Nomis101  > <mailto:nomis...@web.de>> wrote: >> >> Hi Aruna, >> >> could you specifiy what kind of

Re: [x265] [PATCH] Update json11 to v1.0.0 release

Am 25.07.19 um 06:48 schrieb Aruna Matheswaran: > > > On Wed, Jul 24, 2019 at 9:59 PM Nomis101  <mailto:nomis...@web.de>> wrote: > > Hi Aruna, > > could you specifiy what kind of errors and warnings you see on Windows? I > don't have Windows, so I can no

Re: [x265] [PATCH] Update json11 to v1.0.0 release

Hi Aruna, could you specifiy what kind of errors and warnings you see on Windows? I don't have Windows, so I can not test or reproduce. Am 24.07.19 um 16:11 schrieb Aruna Matheswaran: > The patch applies on default and builds successfully in Mac and Linux, but > gives build warnings and

[x265] [PATCH] Fix two typos in the documentation of hevc-aq

This looks not nice on the homepage, without the dot and the typo: https://x265.readthedocs.io/en/default/cli.html#cmdoption-hevc-aq Patch is attached. # HG changeset patch # User Nomis101 # Date 1562860011 -7200 # Do Jul 11 17:46:51 2019 +0200 # Node ID

Re: [x265] [PATCH] Update json11 to v1.0.0 release

This is the patch to update json11 to v1.0.0 release against latest master. I also included the fix for json11 issue #131. Find patch attached. # HG changeset patch # User Nomis101 # Date 1555165564 -7200 # Sat Apr 13 16:26:04 2019 +0200 # Node ID c63e02ef363527e1321142403083ad82a33845eb

[x265] Fix Issue #470

This should fix Issue #470. Patch is attached. # HG changeset patch # User Nomis101 # Date 1555164185 -7200 # Sat Apr 13 16:03:05 2019 +0200 # Node ID b89d065b20751f3f20d542faa2a75dba74bb9982 # Parent 768ab38fd5fd104a8d58f42b646d6117d63b2c0a Fix for Issue #470 diff -r 768ab38fd5fd -r

Re: [x265] [PATCH] Update json11 to v1.0.0 release

Is there something wrong with my patch? If there is still something that hinders to accept the patch from Feb 15, please tell me. Am 15.02.19 um 17:21 schrieb Nomis101 : # HG changeset patch # User Nomis101 # Date 1550247153 -3600 # Fri Feb 15 17:12:33 2019 +0100 # Node ID

Re: [x265] [PATCH] Update json11 to v1.0.0 release

# HG changeset patch # User Nomis101 # Date 1550247153 -3600 # Fri Feb 15 17:12:33 2019 +0100 # Node ID f5e1822cce4cc43d9cfd1c7fcb4204ce34f0a2cf # Parent dcbec33bfb0f1cabdb1ff9eaadba5305ba23e6fa Update json11 to v1.0.0 release diff -r dcbec33bfb0f -r f5e1822cce4c source/dynamicHDR10/json11

[x265] [PATCH] Update json11 to v1.0.0 release

# HG changeset patch # User Nomis101 # Date 1548440484 -3600 # Fri Jan 25 19:21:24 2019 +0100 # Node ID 0ed9b73b07b21ffdd0d5c12ab7c2ac782ce4c3c9 # Parent ae085e5cd8a2cdb161eb5bf54ba9019c3d873506 Update json11 to v1.0.0 release This will fix Issue #373 (and maybe some other issues too