[x265] [PATCH] Allow different Csp for picture

2016-05-30 Thread santhoshini
# HG changeset patch # User Santhoshini Sekar # Date 1464152658 -19800 # Wed May 25 10:34:18 2016 +0530 # Node ID 028ccaa6486047ffafef38d78f9b00880908c0c3 # Parent 6d3849d648f0be5a8e334f1d75a2f7cf93c86cb3 Allow different Csp for picture diff -r 6d3849d648f0

Re: [x265] [PATCH] threadpool: fix warning: ‘int popCount(uint64_t)’ defined but not used [-Wunused-function]

2016-05-30 Thread Deepthi Nandakumar
Thanks for the patch, Praveen. Mateusz' earlier patch provides a more complete fix and has been pushed. On Mon, May 30, 2016 at 6:48 PM, Praveen Tiwari < prav...@multicorewareinc.com> wrote: > I remember some numa functionality requires minimum window 7, they are not > supported on previous

Re: [x265] [PATCH] threadpool: fix warning: ‘int popCount(uint64_t)’ defined but not used [-Wunused-function]

2016-05-30 Thread Praveen Tiwari
I remember some numa functionality requires minimum window 7, they are not supported on previous version of window OS. Regards, Praveen On Mon, May 30, 2016 at 6:43 PM, Mateusz wrote: > There is a serious bug in threadpool code that prevent working in Windows >

Re: [x265] [PATCH] threadpool: fix warning: ‘int popCount(uint64_t)’ defined but not used [-Wunused-function]

2016-05-30 Thread Mateusz
There is a serious bug in threadpool code that prevent working in Windows XP/Vista. VS 2015 error when compiling for 32-bit Windows XP: (ClCompile target) -> I:\vs\x265\source\common\threadpool.cpp(590): error C3861: 'GetNumaNodeProcessorMaskEx': identifier not found [I:\vs\x265\ma\

[x265] [PATCH] threadpool: fix warning: ‘int popCount(uint64_t)’ defined but not used [-Wunused-function]

2016-05-30 Thread praveen
# HG changeset patch # User Praveen Tiwari # Date 1464585837 -19800 # Mon May 30 10:53:57 2016 +0530 # Node ID b8dbe8d7c09e7fc0b7cce236569fc5df2eb70b1e # Parent aeade2e8d8688ebffb8455b8948d89d6a72e2c38 threadpool: fix warning: ‘int popCount(uint64_t)’ defined

Re: [x265] [PATCH] [OUTPUT CHANGED]SAO: convert sao rdo cost calculation from float to int

2016-05-30 Thread Ashok Kumar Mishra
Fixed the crash for --cu-lossless command. The crash was due to divide by zero issue. Successfully ran smoke test on it. On Mon, May 30, 2016 at 1:54 PM, wrote: > # HG changeset patch > # User Ashok Kumar Mishra > # Date 1464596647 -19800

[x265] [PATCH] [OUTPUT CHANGED]SAO: convert sao rdo cost calculation from float to int

2016-05-30 Thread ashok
# HG changeset patch # User Ashok Kumar Mishra # Date 1464596647 -19800 # Mon May 30 13:54:07 2016 +0530 # Node ID 21c9f83bcdac2d2c5beca9c7349e397460dd94d5 # Parent aeade2e8d8688ebffb8455b8948d89d6a72e2c38 [OUTPUT CHANGED]SAO: convert sao rdo cost calculation from

Re: [x265] api: change name of 32-bit dll from libx265.dll to libx265-32.dll

2016-05-30 Thread Mateusz
W dniu 2016-05-30 o 08:26, Mario *LigH* Rohkrämer pisze: > Am 29.05.2016, 08:51 Uhr, schrieb Mateusz : > >> api: change name of 32-bit dll from libx265.dll to libx265-32.dll > > So in fact, if one builds separate DLLs depending on the internal bitdepth, > they will now

Re: [x265] api: change name of 32-bit dll from libx265.dll to libx265-32.dll

2016-05-30 Thread Mario *LigH* Rohkrämer
Am 29.05.2016, 08:51 Uhr, schrieb Mateusz : api: change name of 32-bit dll from libx265.dll to libx265-32.dll So in fact, if one builds separate DLLs depending on the internal bitdepth, they will now be named libx265-32_main[10|12].dll for Win32 target? -- Fun