Welcome to Doom9's Forum, THE in-place to be for everyone interested in DVD conversion. Before you start posting please read the forum rules. By posting to this forum you agree to abide by the rules. |
5th July 2019, 14:30 | #6882 | Link |
Registered User
Join Date: Feb 2007
Location: Sweden
Posts: 483
|
x265 v3.1+4-4f6dde51a5db (32 & 64-bit 8/10/12bit Multilib Windows Binaries) (GCC 9.1.0)
Code:
https://bitbucket.org/multicoreware/x265/commits/branch/default |
10th July 2019, 02:34 | #6884 | Link |
結城有紀
Join Date: Dec 2003
Location: NJ; OR; Shanghai
Posts: 894
|
Code:
From 9612a000cb26748e62833dcd9e47d890af0e3dec Mon Sep 17 00:00:00 2001 From: Xinyue Lu <i@7086.in> Date: Tue, 9 Jul 2019 21:30:15 -0400 Subject: [PATCH] icc: fix compiling and linking issue under ICC --- source/common/x86/asm-primitives.cpp | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/source/common/x86/asm-primitives.cpp b/source/common/x86/asm-primitives.cpp index 3948c4b97..abd3665f8 100644 --- a/source/common/x86/asm-primitives.cpp +++ b/source/common/x86/asm-primitives.cpp @@ -5429,7 +5429,7 @@ void setupAssemblyPrimitives(EncoderPrimitives &p, int cpuMask) // Main } // namespace X265_NS extern "C" { -#ifdef __INTEL_COMPILER +#if defined(__INTEL_COMPILER) && EXPORT_C_API /* Agner's patch to Intel's CPU dispatcher from pages 131-132 of * http://agner.org/optimize/optimizing_cpp.pdf (2011-01-30) @@ -5440,7 +5440,7 @@ int __intel_cpu_indicator = 0; // CPU dispatcher function void PFX(intel_cpu_indicator_init)(void) { - uint32_t cpu = x265::cpu_detect(false); + uint32_t cpu = X265_NS::cpu_detect(false); if (cpu & X265_CPU_AVX) __intel_cpu_indicator = 0x20000; @@ -5467,7 +5467,7 @@ void PFX(intel_cpu_indicator_init)(void) * that backs up all the registers. */ void __intel_cpu_indicator_init(void) { - x265_safe_intel_cpu_indicator_init(); + PFX(intel_cpu_indicator_init)(); } #else // ifdef __INTEL_COMPILER -- 2.19.1.windows.1 |
10th July 2019, 07:25 | #6885 | Link | |
Registered User
Join Date: Mar 2002
Posts: 20
|
Quote:
|
|
11th July 2019, 13:51 | #6886 | Link |
Registered User
Join Date: Dec 2002
Location: Region 0
Posts: 1,436
|
What happened to x265 from 2.9 to 3.x? The bitrate dropped (and the QP increased) and the visual output quality has suffered at the same crf with the same command line. I read the release notes here: https://x265.readthedocs.io/en/defau...easenotes.html but they don't shed a ton of light. I know they made the old veryslow = new slower and effectively made a new preset between placebo and the old veryslow, but I've been using placebo so that doesn't explain it.
My typical 1080p command line switches for 8 bit 4:2:0 input. Code:
--crf 16.0 -p placebo --no-sao --aq-strength 1.15 --vbv-maxrate 25000 --vbv-bufsize 25000 --level 5.0 --keyint 120 --open-gop -D 10 --colorprim "bt709" --transfer "bt709" --colormatrix "bt709" --sar 1:1 |
11th July 2019, 15:05 | #6887 | Link |
German doom9/Gleitz SuMo
Join Date: Oct 2001
Location: Germany, rural Altmark
Posts: 6,782
|
Preset "placebo" as your "typical" 1080p parameter ... seriously?! I hope you use solar power to operate your PC.
The meaning of the placebo preset didn't change in the last years. So it must be a change in the general default behaviour. I can hardly imagine anyone actually seeing an obvious loss of quality in a CRF 16 result played at normal speed. I hope you don't compare single frames with a magnifier to produce this claim. Are you able to provide clips to compare? |
11th July 2019, 15:15 | #6888 | Link |
Helenium(Easter)
Join Date: Aug 2017
Location: Hsinchu, Taiwan
Posts: 99
|
The default AQ mode has been changed to auto-variance (aq-mode 2) in version 3.0.
Try setting --aq-mode 1 (the old default) in your command line.
__________________
Monochrome Anomaly |
11th July 2019, 15:26 | #6889 | Link | |
Registered User
Join Date: Dec 2002
Location: Region 0
Posts: 1,436
|
Quote:
Okay, thanks I will try this. |
|
11th July 2019, 17:59 | #6890 | Link |
Registered User
Join Date: Feb 2007
Location: Sweden
Posts: 483
|
x265 v3.1+7-147fb92c5ed5 (32 & 64-bit 8/10/12bit Multilib Windows Binaries) (GCC 9.1.0)
Code:
https://bitbucket.org/multicoreware/x265/commits/branch/default |
11th July 2019, 20:23 | #6892 | Link | ||
Noob
Join Date: Mar 2017
Posts: 221
|
Quote:
Quote:
|
||
11th July 2019, 21:37 | #6893 | Link |
Registered User
Join Date: Feb 2007
Location: Sweden
Posts: 483
|
V3.1+7 is from the Default channel and includes what the v3.1.1 have and some more
Skickat från min SM-G975F via Tapatalk
__________________
Do NOT re-post any of my Mediafire links. Download & re-host the content(s) if you want to share it somewhere else. |
12th July 2019, 00:38 | #6895 | Link |
Registered User
Join Date: Jun 2002
Location: On thin ice
Posts: 6,837
|
__________________
https://github.com/stax76/software-list https://www.youtube.com/@stax76/playlists |
12th July 2019, 01:24 | #6896 | Link |
Registered User
Join Date: Dec 2002
Location: Region 0
Posts: 1,436
|
Is there some trick to making x265-Yuuki work with avisynth+?
Code:
C:\HDTV Tools\x265_Yuuki>x265-gcc-multilib-full.exe -f 1500 --crf 16.0 -p placebo --no-sao --aq-strength 1.15 --vbv-maxrate 25000 --vbv-bufsize 25000 --level 5.0 --keyint 120 --open-gop -D 10 --colorprim "bt709" --transfer "bt709" --colormatrix "bt709" --sar 1:1 -o HZLIP_p_1.15_16.0_nosao_D10_dith_p1_t_10in.265 "E:\TempBD\HZLIP\HZLIP_comb_1.avs" [avs2 @ 00000000037d8300] Format avs2 detected only with low score of 1, misdetection possible! [avs2 @ 00000000037d8300] Could not find codec parameters for stream 0 (Video: avs2, none): unspecified size Consider increasing the value for the 'analyzeduration' and 'probesize' options [NULL @ 0000000004e14700] No codec provided to avcodec_open2() [NULL @ 0000000004e14700] No codec provided to avcodec_open2() lavf [error]: could not find decoder for video stream x265 [error]: unable to open input file <E:\TempBD\HZLIP\HZLIP_comb_1.avs> Last edited by Stereodude; 12th July 2019 at 02:02. |
12th July 2019, 03:46 | #6897 | Link |
...?
Join Date: Nov 2005
Location: Florida
Posts: 1,420
|
Yuuki is the patchset/branch (the patch itself is just generic LAVF input); whether the particular build was linked against a libavformat that itself was built with --enable-avisynth is up to the one building it. 'avs2' is not AviSynth (it's the Chinese AVS2 format), and the only reason libavformat would jump to that when given an AviSynth script is that FFmpeg hadn't been built with --enable-avisynth.
|
12th July 2019, 11:43 | #6898 | Link |
Registered User
Join Date: Dec 2002
Location: Region 0
Posts: 1,436
|
So why doesn't the Wolfberry build of x265 honor affinity restrictions? Using
Code:
START "Enc #1" /NORMAL /NODE 0 /AFFINITY 00FF |
13th July 2019, 01:20 | #6899 | Link |
Registered User
Join Date: Dec 2002
Location: Region 0
Posts: 1,436
|
--seek doesn't work correctly with the Wolfberry build with an avisynth+ input either.
Code:
x265.exe" --pools 4 -F 1 --crf 16.0 -p veryslow --no-sao --aq-mode 1 --aq-strength 1.15 --vbv-maxrate 40000 --vbv-bufsize 40000 --level 5.1 --keyint 120 --open-gop -D 10 --colorprim "bt709" --transfer "bt709" --colormatrix "bt709" --sar 1:1 --seek 16609 --frames 16678 -o out_2.265 "source.avs" Code:
lavf [info]: Format : avisynth Codec : rawvideo ( raw video ) PixFmt : yuv420p10le Framerate : 24/1 Timebase : 1/24 Duration : 2:18:31 lavf [info]: 1920x1080 fps 24/1 i420p10 sar 1:1 frames 16609 - 33286 of 199487 raw [info]: output file: out_2.265 x265 [info]: HEVC encoder version 3.1.1+1-04b37fdfd2dc x265 [info]: build info [Windows][GCC 9.1.1][64 bit] 10bit x265 [info]: using cpu capabilities: MMX2 SSE2Fast SSSE3 SSE4.2 AVX x265 [info]: Main 10 profile, Level-5.1 (Main tier) x265 [info]: Thread pool created using 4 threads x265 [info]: Slices : 1 x265 [info]: frame threads / pool features : 1 / wpp(17 rows) x265 [info]: Coding QT: max CU size, min CU size : 64 / 8 x265 [info]: Residual QT: max TU size, max depth : 32 / 3 inter / 3 intra x265 [info]: ME / range / subpel / merge : star / 57 / 4 / 5 x265 [info]: Keyframe min / max / scenecut / bias: 12 / 120 / 40 / 5.00 x265 [info]: Lookahead / bframes / badapt : 40 / 8 / 2 x265 [info]: b-pyramid / weightp / weightb : 1 / 1 / 1 x265 [info]: References / ref-limit cu / depth : 5 / off / off x265 [info]: AQ: mode / str / qg-size / cu-tree : 1 / 1.1 / 32 / 1 x265 [info]: Rate Control / qCompress : CRF-16.0 / 0.60 x265 [info]: VBV/HRD buffer / max-rate / init : 40000 / 40000 / 0.900 x265 [info]: tools: rect amp rd=6 psy-rd=2.00 rdoq=2 psy-rdoq=1.00 rskip x265 [info]: tools: signhide tmvp b-intra strong-intra-smoothing deblock [0.3%] 54/16678 frames, 0.16 fps, 6617.67 kb/s, 1.77 MB, eta 29:46:47, est.size 548.21 MB |
13th July 2019, 01:56 | #6900 | Link |
結城有紀
Join Date: Dec 2003
Location: NJ; OR; Shanghai
Posts: 894
|
AviSynth support came from LAVF input filter.
LAVF input filter was ported from x264. x264 didn't support seeking. So this input filter never had seeking feature. As a side note, LAVF was never designed to take AVS script (and that's exactly the reason I did not include AVS support in my build). I'd hope one day someone can add a proper AVS native input. But on the other hand my scripts are on 32-bit so I have no choice but to use piper anyway. |
|
|