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. |
12th October 2010, 23:18 | #4 | Link |
Software Developer
Join Date: Jun 2005
Location: Last House on Slunk Street
Posts: 13,249
|
Just in case anybody is interested, here is my x264 r1745 build:
http://www.mediafire.com/file/9a6536...6-fprofiled.7z (You can ignore the 'libx264-106.dll' and simply use the EXE file as usual)
__________________
Go to https://standforukraine.com/ to find legitimate Ukrainian Charities 🇺🇦✊ |
12th October 2010, 23:50 | #7 | Link | ||
Software Developer
Join Date: Jun 2005
Location: Last House on Slunk Street
Posts: 13,249
|
Quote:
You can just replace the 'x264.exe' or 'x264_64.exe' with the desired build/revision and that's it... Quote:
The latest builds on x264.nl obviously were linked against the shared C++ run-time. This isn't necessarily a bad thing, only 'libstdc++-6.dll' will be needed at run-time. Anyway, I assume it happened by mistake and will be "fixed" soon. So simply be patient or use another build in the meantime...
__________________
Go to https://standforukraine.com/ to find legitimate Ukrainian Charities 🇺🇦✊ Last edited by LoRd_MuldeR; 12th October 2010 at 23:55. |
||
12th October 2010, 23:58 | #9 | Link |
Registered User
Join Date: Feb 2005
Posts: 149
|
I don't get it, I downloaded r1745 (32bit 8bit) from x264.nl, yesterday, the minute the site was updated from r1732... So I believe I got it before the OP of this thread.
I can run x264.exe without any problems... Is it possible that this .dll error happens only with some systems, and not with others? As I write, I am encoding with this r1745 from x264.nl, downloaded yesterday. 5 hours to finish. Will my encode be messed up? |
13th October 2010, 00:00 | #10 | Link | |
Software Developer
Join Date: Jun 2005
Location: Last House on Slunk Street
Posts: 13,249
|
Quote:
http://msdn.microsoft.com/en-us/libr...86(VS.85).aspx So you either are using a statically linked build of x264 -or- the required DLL is available on your system. For more information please use the Dependency Walker: http://www.dependencywalker.com/
__________________
Go to https://standforukraine.com/ to find legitimate Ukrainian Charities 🇺🇦✊ Last edited by LoRd_MuldeR; 13th October 2010 at 00:04. |
|
13th October 2010, 00:04 | #11 | Link | |
Registered User
Join Date: Feb 2005
Posts: 149
|
Quote:
So, what about this encoding I am doing here... 5 hours left, and it has been running for another 8 hours or so (and this is fisrt pass, I will need to do a 2nd pass too). Shoud I continue encoding, or should I cancel it now, and use your build? I don't wanna waste another 5 hours to discover my video is messed up because of x264 bad builds. What should I do? Last edited by simps; 13th October 2010 at 00:07. |
|
13th October 2010, 00:06 | #12 | Link | |
Software Developer
Join Date: Jun 2005
Location: Last House on Slunk Street
Posts: 13,249
|
Quote:
(BTW: x264 itself shouldn't need the C++ run-time at all, as it's pure C. So I guess it's GPAC or FFMS2 or libavcodec/libavformat that adds the dependency)
__________________
Go to https://standforukraine.com/ to find legitimate Ukrainian Charities 🇺🇦✊ |
|
13th October 2010, 00:11 | #13 | Link | |
Registered User
Join Date: Feb 2005
Posts: 149
|
Quote:
I won't cancel the encode. |
|
13th October 2010, 17:51 | #14 | Link |
Pain and suffering
Join Date: Jul 2002
Posts: 1,337
|
I figured i'd update gcc, because the past few years no real issues occured, until now:
gcc 4.5.1 now compiles dynamicly by default, which made you require the .dll file. I now compile gcc 4.5.1 this way: Code:
1. cd gcc-4.5.1/ 2. mkdir obj 3: cd obj 4: ../configure --enable-static --disable-shared 5: make CFLAGS='-O' LIBCFLAGS='-g -O2' LIBCXXFLAGS='-g -O2 -fno-implicit-templates' bootstrap 6: make install I also compiled gcc 4.4.5 as i always do (did, see above): Code:
1. cd gcc-4.4.5/ 2. mkdir obj 3: cd obj 4: ../configure 5: make CFLAGS='-O' LIBCFLAGS='-g -O2' LIBCXXFLAGS='-g -O2 -fno-implicit-templates' bootstrap 6: make install Code:
gcc -Wshadow -O3 -ffast-math -Wall -I. -march=i686 -mfpmath=sse -msse -std=gnu99 -IF:/msys/1.0/local/include o encoder/encoder.c encoder/encoder.c: In function 'x264_slice_write': encoder/encoder.c:1820: warning: 'bs_bak.p_start' may be used uninitialized in this function encoder/encoder.c:1820: warning: 'bs_bak.p' may be used uninitialized in this function encoder/encoder.c:1820: warning: 'bs_bak.p_end' may be used uninitialized in this function encoder/encoder.c:1820: warning: 'bs_bak.cur_bits' may be used uninitialized in this function encoder/encoder.c:1820: warning: 'bs_bak.i_left' may be used uninitialized in this function encoder/encoder.c:1820: warning: 'bs_bak.i_bits_encoded' may be used uninitialized in this function encoder/encoder.c: In function 'x264_encoder_encode': encoder/encoder.c:2282: internal compiler error: Segmentation fault Please submit a full bug report, with preprocessed source if appropriate. See <http://gcc.gnu.org/bugs.html> for instructions. make[1]: *** [encoder/encoder.o] Error 1 make[1]: Leaving directory `/home/xuser/x264_32bit_10bit_depth' make: *** [fprofiled] Error 2 Thanks for the report! Sorry for the trouble! Note to self: next time test x264.exe again before and after updating gcc! |
18th October 2010, 10:37 | #15 | Link | |
Registered User
Join Date: Oct 2009
Location: crow-land
Posts: 543
|
Quote:
Lots of advice http://forum.doom9.org/showthread.php?t=89979 http://forum.doom9.org/showthread.ph...89#post1432889 http://doom10.org/index.php?topic=3.0 but I don't know what an unpatched build is. Edit, looks like it's "more reliable" without experimental type patching. Last edited by hydra3333; 18th October 2010 at 10:42. |
|
|
|