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. |
23rd July 2016, 04:40 | #4021 | Link | |
Registered User
Join Date: Mar 2015
Location: New Zealand
Posts: 45
|
Quote:
|
|
23rd July 2016, 06:42 | #4022 | Link | |
German doom9/Gleitz SuMo
Join Date: Oct 2001
Location: Germany, rural Altmark
Posts: 6,753
|
Quote:
x265 2.0+9-2737c6ff5f80 was built with an older MSYS/MinGW package by XhmikosR. |
|
23rd July 2016, 08:05 | #4023 | Link | |
Registered User
Join Date: Feb 2015
Posts: 326
|
Quote:
If I add option '-mincoming-stack-boundary=2' to encoder/slicetype.cpp in 32-bit GCC 6.1, it works without '-march' option. I need some time to detailed analyze... By the way, if you add line in your build script: export CXXFLAGS="-march=pentium4 -mtune=generic" before part that build 32-bit x265, it will be much faster version of 32-bit x265. |
|
23rd July 2016, 09:00 | #4024 | Link |
Registered User
Join Date: Nov 2011
Posts: 66
|
@divxmaster: Using more than 6 B-frames indeed gives little benefit, in my experience only about 2-3% of B-frame "rows" contain 7 frames, for example. But, I also haven't noticed any significant speedup reducing B-frame count to 6, and that's the reason I kept it at 9 - for medium/low bitrate encoding any improvement counts.
I've tested many sharpening filters yesterday and discarded Adaptive Sharpen, as it smooths out less pronounced details slightly. The best combination I've come up is Sharpen (AviSynth built-in filter) at value 0.2, followed by Msharpen at threshold 10 and strength 20. For the time being, performance of AviSynth is not an issue as my new octo-core AMD FX CPU "Bulldozes" through data quite nicely. |
23rd July 2016, 11:50 | #4027 | Link |
Registered User
Join Date: Feb 2007
Posts: 128
|
Hey Selur,
I didn't try the VLC Nightly yet. Though neither MKV, MP4 nor using Handbrake instead of Staxrip seemed to make a real difference. The only thing that helped was deactivating OpenGOP... But I still got seek times of roundabout 5sec with a 1080p video on my Xeon 1241v3. |
23rd July 2016, 12:06 | #4028 | Link | |
ffx264/ffhevc author
Join Date: May 2007
Location: /dev/video0
Posts: 1,843
|
Quote:
|
|
23rd July 2016, 12:07 | #4029 | Link | ||
Registered User
Join Date: Oct 2001
Location: Germany
Posts: 7,259
|
Quote:
Quote:
|
||
23rd July 2016, 14:29 | #4032 | Link | |
Registered User
Join Date: Feb 2007
Posts: 128
|
Ahh... thx guys.
The VLC Nightly helped... as did the --keyint 150 parameter. Quote:
|
|
23rd July 2016, 15:04 | #4033 | Link |
SuperVirus
Join Date: Jun 2012
Location: Antarctic Japan
Posts: 1,351
|
To whom this may interest:
I've decided to share my new (MSYS2-based) MinGW_w64 toolchain. The directory includes CMake, Git and Mercurial. https://www.mediafire.com/?3ib29yauv5kdw NOTICE: when calling the .SH scripts, you (may) need to add a ./ to the command-line — for example, "./multi64.sh" instead of simply "multi64.sh". Last edited by filler56789; 23rd July 2016 at 15:11. Reason: clarification |
26th July 2016, 07:03 | #4035 | Link |
German doom9/Gleitz SuMo
Join Date: Oct 2001
Location: Germany, rural Altmark
Posts: 6,753
|
Hard to believe if >90% of the relevant code is in assembler, optimized for several different levels of supported instruction set extensions. Without details and numbers, "much faster" won't mean anything.
|
26th July 2016, 07:50 | #4036 | Link |
Registered User
Join Date: Dec 2014
Posts: 240
|
Command:
Code:
--crf 20 --output-depth 10 --level-idc 5.1 --cbqpoffs -3 --min-keyint 23 --keyint 240 --no-open-gop --colorprim bt709 --colormatrix bt709 --transfer bt709 --rskip --crqpoffs -3 --high-tier GCC 6.1.0 - 12.28fps average Movie - Batman v Superman. The rest is the same: StaxRip, DirectShowSource, LAV filters CPU decoding, Core i7-4790K CPU, 8GB RAM, Windows 7 x64. OK... taking back..... Now realised,that I haven't turned on --me star, like with GCC 5.3.0. Running new test. Last edited by jlpsvk; 26th July 2016 at 07:58. |
26th July 2016, 08:02 | #4038 | Link |
Registered User
Join Date: Dec 2014
Posts: 240
|
LigH, as i wrote...running new test with --me star, as wih GCC 5.3.0... So will report new speed then.
Code:
x265 [info]: using cpu capabilities: MMX2 SSE2Fast SSSE3 SSE4.2 AVX AVX2 FMA3 LZCNT BMI2 |
26th July 2016, 08:13 | #4039 | Link |
German doom9/Gleitz SuMo
Join Date: Oct 2001
Location: Germany, rural Altmark
Posts: 6,753
|
The search for motion vectors in different ME modes is more or less exhaustive; "star" will probably prefer vertical and horizontal directions, but won't search as far in diagonal directions, I believe. I never saw descriptive diagrams yet, though... But fewer directions means faster speed, obviously.
|
26th July 2016, 09:49 | #4040 | Link |
German doom9/Gleitz SuMo
Join Date: Oct 2001
Location: Germany, rural Altmark
Posts: 6,753
|
XhmikosR recently released an MSYS / MinGW / GCC 6.1.0 package (2016-07-08); so I built x265 binaries for you to cross-compare compilers and linking types of mostly the same generic options, just including the pentium4/generic flag pair Ma suggested for Win32 builds (at least I hope I did it right, please check).
x265 2.0+10-5a0e139e2938 (GCC 5.3.0) x265 2.0+10-5a0e139e2938 (GCC 6.1.0) |
Thread Tools | Search this Thread |
Display Modes | |
|
|