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. |
1st March 2018, 20:04 | #43 | Link |
Registered User
Join Date: Jul 2004
Posts: 213
|
Thanks, I'll have a look, but when reading your warning it's like reading chinese, I understand that something seems to be broken and you had to take some actions to handle it (I don't know if staying with ffmpeg 2.8.x has any undesirable side effect), but I don't know if I should take any further precautions.
I've also see that by default your build uses weightp=2 that had some time back problems with some buggy AVC decoder chipsets, so I've always used weightp=1 that was also improved with near weightp=2 results. Do you really recommend 2 or is 1 just fine? |
1st March 2018, 20:25 | #44 | Link |
Registered User
Join Date: Oct 2002
Location: France
Posts: 2,316
|
It's not that something is broken, it's that the huge update blending the 8 and 10 bits code introduce so much changes, that a lot of patches need a LOT of rework to be implemented again, so, i've skipped it, but still implement the critical changes. So, my releases are not anymore directly from the master branch. At one point i've created my own branch, and to this branch implement the commits i think necessary.
My personnal point of view is that i absolutely don't care of ***#### buggy chipset because, they are buggy. Their responsability they should assume, not force things on me. Still, personnal point of view and subject which piss me off... So, nothing realy i can recommend.
__________________
My github. |
11th March 2018, 09:12 | #46 | Link |
変身!
Join Date: Dec 2008
Location: Brazil
Posts: 38
|
that means you won't provide new builds anytime soon, @jpsdr?
I've always used your builds, they process the encodes faster than the others, I have no idea why... Guess I'll rely on this website then for x264 builds. For x265 I'm using from LigH in HEVC's dedicated topic. |
11th March 2018, 11:54 | #47 | Link |
Registered User
Join Date: Oct 2002
Location: France
Posts: 2,316
|
If you read, i'll still provide builds, but they'll not be anymore from the master branch.They'll just include what i think is realy necessary, because now i have to add the commits "at hands".
Still, it's not impossible that at one point, i'll not be able to provide builds anymore, but it's not the case yet.
__________________
My github. |
16th March 2018, 19:25 | #48 | Link |
Registered User
Join Date: Feb 2014
Posts: 355
|
Happy Friday! and I hope komisar is well . I've been using the kmod build for several years as I find it noticeably faster than the standard build. Please, does anyone know of another modded build similar to komisar's? Thanks in advance for any help.
|
16th March 2018, 22:38 | #49 | Link | |
Software Developer
Join Date: Jun 2005
Location: Last House on Slunk Street
Posts: 13,248
|
Quote:
To make a long story short: If you came to the conclusion that "kmod" build is any faster than others, it is probably because you have been comparing different revisions of x264 and/or you have been comparing different encoding settings - which is comparing apples and oranges. I suggest that you look at the specific patches included in "kmod" build and understand what they really do. Unless you really need the "feature" enabled by these specific patches, there is absolutely no reason to use "kmod" instead of a "vanilla" build. For me it was much more important to find an up-to-date x264 build that has FFMS input and MP4 output enabled - which no build except Komisar's seems to have. Well, now Ligh's build has too!
__________________
Go to https://standforukraine.com/ to find legitimate Ukrainian Charities 🇺🇦✊ Last edited by LoRd_MuldeR; 16th March 2018 at 22:54. |
|
17th March 2018, 11:49 | #50 | Link |
Registered User
Join Date: Oct 2002
Location: France
Posts: 2,316
|
On my releases, i made several versions : Somes build with a posix gcc (the version you have in msys2 with "pacman") and everything is build with threading posix option, and somes build with a win32thread gcc (versison you can get here for exemple) and everything is build win32 threading option.
For each version, i have a "standard" build, and an AVX2/Broadwell build (compiler settings option). Personnaly, never made tests, but someone who used my versions one day made a test : using the different builds on the same video with the same settings, on a Win7x64 system. Result : win32thread was faster than posix, AVX2/Broadwell build was faster than "standard". But... differences were very slight, no more than 5% between the slowest and the fatest. So, you can have differences according "how best" the compiler optimize, because even if a lot of things are wonderfully well optimized in ASM, there still also a lot of things in pure C code, which leave rooms for optimization. Nevertheless, you'll will never hit more than a small few %.
__________________
My github. |
17th March 2018, 14:49 | #51 | Link |
German doom9/Gleitz SuMo
Join Date: Oct 2001
Location: Germany, rural Altmark
Posts: 6,782
|
Well ... "LigH's build" just came out of the media-autobuild_suite. No further patches. I have no experience in optimizing the building process or even adding patches.
|
17th March 2018, 22:58 | #52 | Link | |
Registered User
Join Date: Feb 2014
Posts: 355
|
Quote:
|
|
26th March 2018, 09:22 | #53 | Link |
Registered User
Join Date: Oct 2014
Posts: 476
|
They should add a note on videolan, since I was wondering why 10 bit looked to be two revisions behind 8.
Is this why the executable doubled in size? (and out of curiosity, why was x264-r2744-b97ae06.exe 1/5th the size of the ones before it?) Last edited by kuchikirukia; 26th March 2018 at 09:26. |
26th March 2018, 10:00 | #54 | Link |
German doom9/Gleitz SuMo
Join Date: Oct 2001
Location: Germany, rural Altmark
Posts: 6,782
|
If you have an executable which includes two quite substantially different encoders, then you have about twice the size of code in it, yes.
Earlier versions may also not include additional code to read compressed video formats directly from media files in different containers; small builds may only support raw source formats and AviSynth. |
5th April 2018, 01:59 | #56 | Link |
Registered User
Join Date: Oct 2014
Posts: 476
|
Is anyone else having a problem where encoding x264 lags their computer? It's running in low process priority like it should but I'm having problems with MPC-HC taking 20 seconds to start a video and new tabs hang, and it gets worse the more threads I throw at x264.
Windows 10. Last edited by kuchikirukia; 5th April 2018 at 02:04. |
5th April 2018, 03:29 | #57 | Link |
Registered User
Join Date: Feb 2002
Location: San Jose, California
Posts: 4,407
|
Mine doesn't slow down that much! Are you low on memory? Are you encoding to or from your OS drive? SSD or spinning disk?
__________________
madVR options explained |
5th April 2018, 09:28 | #59 | Link |
Registered User
Join Date: Oct 2014
Posts: 476
|
No other bottlenecks. --threads 4 I'm fine. --threads 8 I'm fine. -threads 12 it chokes other things, though the encode runs fine.
i7 4790 If it's pegged at 100% util my computer acts like it's 100% util at a higher priority. Last edited by kuchikirukia; 5th April 2018 at 09:35. |
8th April 2018, 08:02 | #60 | Link |
Registered User
Join Date: Oct 2001
Location: Germany
Posts: 7,277
|
Anyone got a link to a current, statically linked, x264 version with libav in it that's for MacOS X ?
Latest build over at http://download.videolan.org/x264/bi...macosx-x86-64/ is from 25-Dec-2017. Cu Selur |
|
|