# HG changeset patch
# User Andrey Semashev <andrey.semas...@gmail.com>
# Date 1475709624 -10800
# Thu Oct 06 02:20:24 2016 +0300
# Branch atomic_bit_ops
# Node ID 539c83edceb540e7785719876a161a48382b4c09
# Parent af3678bc1dff6eb3df5879ac49fdb532ce8bd6ac
Use atomic bit test and set
On 07/21/17 09:29, ar...@multicorewareinc.com wrote:
# HG changeset patch
# User Aruna Matheswaran
# Date 1500457328 -19800
# Wed Jul 19 15:12:08 2017 +0530
# Branch stable
# Node ID fd354d5ec1328a000c24e1551804a1ce569ec3b0
# Parent
Hi,
While compiling 2.4 I'm seeind lots of warnings like this:
.../source/common/ipfilter.cpp: In instantiation of ‘void
{anonymous}::interp_horiz_ps_c(const pixel*, intptr_t, int16_t*,
intptr_t, int, int) [with int N = 8; int width = 4; int height = 4;
pixel = unsigned char; intptr_t = long
On 11/21/17 15:25, Sean McGovern wrote:
Hi,
Is this really necessary?
Ubuntu 16.04 Xenial Xerus only ships with nasm 2.11.08.
yasm does not support AVX-512 and has very low activity recently[1].
nasm supports AVX-512 since 2.13[2]. Even if x265 does not use AVX-512
currently, this is the
On Thu, May 3, 2018 at 7:37 PM, Pradeep Ramachandran
wrote:
>
> On Thu, May 3, 2018 at 2:23 PM, wrote:
>>
>> # HG changeset patch
>> # User Praveen Tiwari
>> # Date 1525328839 -19800
>> # Thu May 03
On 01/10/18 11:52, Pradeep Ramachandran wrote:
On Mon, Jan 1, 2018 at 6:05 PM, Andrey Semashev
<andrey.semas...@gmail.com <mailto:andrey.semas...@gmail.com>> wrote:
# HG changeset patch
# User Andrey Semashev <andrey.semas...@gmail.com
<mailto:andrey.
This is a minor update from the previous patch. The changes are:
- Incremented X265_BUILD version.
- Moved set_log in x265_api above the delimiter comment to add extensions below
it.
- Added a second patch to remove logging from a signal handler.
___
# HG changeset patch
# User Andrey Semashev <andrey.semas...@gmail.com>
# Date 1515597241 -10800
# Wed Jan 10 18:14:01 2018 +0300
# Branch add_custom_logging
# Node ID fbd3aa7b346e337bc5fefb4f2e51fb74c2ded597
# Parent a5ad2f32cd45697897fdf6b643c69291861520c7
Do not use logging in a
# HG changeset patch
# User Andrey Semashev <andrey.semas...@gmail.com>
# Date 1515596947 -10800
# Wed Jan 10 18:09:07 2018 +0300
# Branch add_custom_logging
# Node ID a5ad2f32cd45697897fdf6b643c69291861520c7
# Parent 2f3c4158cf3553030920708271bc43cdc79932a3
Add support for custo
Any feedback on this one?
I've been using it for quite some time locally. It does seem to work
slightly faster on my Sandy Bridge machine (it should be a few percents
of gain in fps, although I didn't save the benchmark numbers).
On 01/01/18 15:28, Andrey Semashev wrote:
# HG changeset
On 01/10/18 21:03, chen wrote:
At 2018-01-11 00:06:29, "Andrey Semashev" <andrey.semas...@gmail.com> wrote:
On 01/10/18 18:53, chen wrote:
the "lock" prefix will lock the CPU bus, it will be greater penalty on
the multi-core system.
Just for the record, the lock
replaces "lock; cmpxchg" loops that are normally generated for the
atomic AND and OR operations with a single instruction.
At 2018-01-10 23:30:06, "Andrey Semashev" <andrey.semas...@gmail.com
<mailto:andrey.semas...@gmail.com>> wrote:
Any feedback on this on
On 02/05/18 02:31, John Comeau wrote:
https://bitbucket.org/multicoreware/x265/issues/139 was solved over a
year ago by rmous...@us.ibm.com when he wrote
source/common/ppc/pixel_altivec.cpp.
the issue should be closed and the bounty awarded as appropriate.
I've done some testing to prove that
# HG changeset patch
# User Andrey Semashev <andrey.semas...@gmail.com>
# Date 1514810081 -10800
# Mon Jan 01 15:34:41 2018 +0300
# Branch add_custom_logging
# Node ID 248f862033e9fb01ee54d3e466dc284eeeb30365
# Parent ff02513b92c000c3bb3dcc51deb79af57f5358d5
Add support for custo
# HG changeset patch
# User Andrey Semashev <andrey.semas...@gmail.com>
# Date 1514810404 -10800
# Mon Jan 01 15:40:04 2018 +0300
# Branch fix_docs_invalid_utf8_chars
# Node ID 3bf4f11669b20669cf2d64f7405774c41ad24b98
# Parent ff02513b92c000c3bb3dcc51deb79af57f5358d5
Fix invalid
# HG changeset patch
# User Andrey Semashev <andrey.semas...@gmail.com>
# Date 1514809583 -10800
# Mon Jan 01 15:26:23 2018 +0300
# Branch atomic_bit_opsv2
# Node ID 81529b6bd6adc8eb31162daeee44399dc1f95999
# Parent ff02513b92c000c3bb3dcc51deb79af57f5358d5
Use atomic bit test and set
On 03/01/18 14:50, Ashok Kumar Mishra wrote:
Hi all,
x265 version 2.7 is now out! The key new improvements include support
for RADL pictures, moving from YASM to NASM assembler and reduced x265
build time by more than 50%. The tarball of this release can be
downloaded fromhere
# HG changeset patch
# User Andrey Semashev <andrey.semas...@gmail.com>
# Date 1515596947 -10800
# Wed Jan 10 18:09:07 2018 +0300
# Branch add_custom_logging_v3
# Node ID 3ebefb64a1eb1487389db4ff7a808490b3005c39
# Parent d7c26df32fae052b7e895fee9bda1c22b24cc44b
Add support for custo
This is the same as v2 with the only change being X265_BUILD version conflict
resolved.
___
x265-devel mailing list
x265-devel@videolan.org
https://mailman.videolan.org/listinfo/x265-devel
# HG changeset patch
# User Andrey Semashev <andrey.semas...@gmail.com>
# Date 1515597241 -10800
# Wed Jan 10 18:14:01 2018 +0300
# Branch add_custom_logging_v3
# Node ID c53408bbc3021696f9b949858799639311eb44ee
# Parent 3ebefb64a1eb1487389db4ff7a808490b3005c39
Do not use logging in a
On 03/18/18 20:04, Derek Buitenhuis wrote:
On 3/16/2018 3:28 PM, Andrey Semashev wrote:
+/* x265_set_log:
+ * Sets a custom logger function */
+void x265_set_log(x265_log_t log);
I would like to voice my distaste for this implementation.
This is a global callback, and will introduce
On 03/05/18 13:09, Ashok Kumar Mishra wrote:
On Mon, Mar 5, 2018 at 3:26 PM, Andrey Semashev
<andrey.semas...@gmail.com <mailto:andrey.semas...@gmail.com>> wrote:
On 01/10/18 18:20, Andrey Semashev wrote:
This is a minor update from the previous patch.
On 01/10/18 18:20, Andrey Semashev wrote:
This is a minor update from the previous patch. The changes are:
- Incremented X265_BUILD version.
- Moved set_log in x265_api above the delimiter comment to add extensions below
it.
- Added a second patch to remove logging from a signal handler
On 10/31/18 2:33 PM, prav...@multicorewareinc.com wrote:
# HG changeset patch
# User Praveen Tiwari
# Date 1540983948 -19800
# Wed Oct 31 16:35:48 2018 +0530
# Node ID 1c878790edea64186edabcd40fb3df121f536311
# Parent fd517ae68f93dbfdd1bff45a9dd8e626523542b6
fix Issue #442: linking issue
Here's a patch I'm using.
On 7/13/19 6:21 PM, Mario Rohkrämer wrote:
Forgot to mention: This was v3.1.1+1
Am 13.07.2019, 16:41 Uhr, schrieb Mario *LigH* Rohkrämer :
Ubuntu 18.04 LTS + GCC 9.0
/home/ligh/x265/source/encoder/ratecontrol.cpp: In member function
‘int
I see no 3.4 tag in git.
On 2020-05-29 21:15, Aruna Matheswaran wrote:
Hi all,
x265 version 3.4 is out with cool new features and encoder enhancements
in terms of encoding efficiency as well as speed.
Please download v3.4 from our downloads page
On 11/24/20 12:08 PM, Michael Lackner wrote:
Hello,
I'm not sure whether this is a slightly stupid question (I'm no dev, so
not used to git much), but since I'm interested in obtaining and
building release versions as well, I'll just ask:
How do I get a specific x265 release version from git?
On 11/24/20 1:33 AM, ebals...@pm.me wrote:
I’d like to update MacPorts x265 to enable the 10-bit variant. As I
started reading the docs and source code, I am confused about where is
the best place to obtain source code. Currently MacPorts is using
Hi,
When libx265 3.5 (as checked out from git tag 3.5) is compiled, it
reports version 3.4+31-6722fce1f. Probably because x265Version.txt file
contents are incorrect.
___
x265-devel mailing list
x265-devel@videolan.org
29 matches
Mail list logo