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. |
|
|
Thread Tools | Search this Thread | Display Modes |
6th September 2008, 05:19 | #944 | Link | |
Registered User
Join Date: Feb 2007
Posts: 176
|
Quote:
(Also, in case my EDIT2 was missed, both Ranguvar and my builds are affected, so beware for bugs in both.) |
|
6th September 2008, 05:24 | #945 | Link | |
Registered User
Join Date: Sep 2004
Location: Wales UK
Posts: 228
|
Quote:
Thanks for confirming skystrife Last edited by gav1577; 6th September 2008 at 05:38. |
|
6th September 2008, 05:37 | #946 | Link |
Registered User
Join Date: Feb 2007
Posts: 176
|
Vanilla r964 build has the issue here for me, so this is most likely not related to the patching. What setting exactly is fuxing the output though is beyond me, I'm slowly removing every setting and not getting anywhere.
Any ideas? |
6th September 2008, 06:15 | #948 | Link |
Compiling Encoder
Join Date: Jan 2007
Posts: 1,348
|
well i tried working at it and in different players, the frames were definitely miscolored, so maybe one of the new updates had a regression where the chroma gets corrupted.
tried on something else and got similar massive corruption. when reverting back to my r956 build, there were no problems. Last edited by kemuri-_9; 6th September 2008 at 06:20. |
6th September 2008, 06:15 | #949 | Link | |
Registered User
Join Date: Feb 2002
Location: OF/Germany
Posts: 111
|
Quote:
now with 964 i get the same nice green with my mpeg2source sample and crf settings?? 957 works fine. EDIT: coreavc in mpc decodes the broken scene, powerdvd in mpc just skipps over the broken scene... maybe this does say something to someone? EDIT2: 964 broken: http://www.mediafire.com/?i9h3tshdlcs 957 ok: http://www.mediafire.com/?1llhbmrsjdy Last edited by gigah72; 6th September 2008 at 06:35. |
|
6th September 2008, 06:37 | #950 | Link |
Compiling Encoder
Join Date: Jan 2007
Posts: 1,348
|
i went through git revisions one by one starting from r958 to find which one caused the problem...
revision 963 caused the problem, meaning from r962 to r963, the problematic code occurs. Last edited by kemuri-_9; 6th September 2008 at 06:48. Reason: typoz |
6th September 2008, 06:45 | #951 | Link | |
x264 developer
Join Date: Sep 2005
Posts: 8,666
|
Quote:
Anyways, this seems odd because I ran all of these patches through a huge slew of regression tests, and posted the patches in #x264 IRC, where another few people ran them through all of their own regression tests and confirmed that they worked flawlessly...
__________________
Follow x264 development progress | akupenguin quotes | x264 git status ffmpeg and x264-related consulting/coding contracts | Doom10 Last edited by Dark Shikari; 6th September 2008 at 06:48. |
|
6th September 2008, 07:17 | #954 | Link |
Registered User
Join Date: May 2007
Posts: 75
|
I can confirm that there's an issue in r963. Horrible blocking shows up in the encode, which I've run 3 times now. It's not there in the source, I'm 100% certain, and it's not an avs filter.
Actually, I guess I'm late since it's fixed now. |
6th September 2008, 08:13 | #955 | Link |
Registered User
Join Date: Feb 2007
Location: ::1
Posts: 1,236
|
rang_x264_r965
Home
Direct download, Mirrors Code:
x264 r965 from Git (patched, fprofiled). Compiled by Ranguvar on September 6th, 2008, with GCC 4.3.2. DON'T think that because I used march=athlon it restricts the CPUs you can use. It seems to improve performance (VERY slightly) for all CPUs. Open this archive with the free, multi-platform tools 7-Zip or p7zip. Compressed with LZMA. The src folder contains the patched source code. The bin folder contains a binary executable, and a DLL for those apps that use them (NOT for AviDemux - get those from LoRd_MuldeR). Git: git://git.videolan.org/x264.git Info, and source tarballs: http://www.videolan.org/developers/x264.html Changelog: http://git.videolan.org/gitweb.cgi?p=x264.git Vanilla builds: http://x264.nl/ Discussion: http://forum.doom9.org/forumdisplay.php?f=77 http://forum.doom9.org/showthread.php?t=130364 Applied patches (included, unchanged, in the patches folder): patch -p1 -i ../x264diffs/x264_dll_alignment_fix.01.diff patch -p1 -i ../x264diffs/x264_progress.indication_r957.diff patch -p1 -i ../x264diffs/x264_hrd_pulldown.09_interlace.diff patch -p1 -i ../x264diffs/x264_psy_rdo_0.6_r956.diff patch -p1 -i ../x264diffs/x264_new_bframe_decision_04.7.diff CLI used for build: ./configure --enable-shared --extra-cflags="-march=athlon -pipe" make fprofiled VIDS="../enctests/deadline_cif.y4m" Platform: X86 System: MINGW asm: yes avis input: yes mp4 output: yes pthread: yes gtk: no debug: no gprof: no PIC: no shared: yes visualize: no |
6th September 2008, 08:22 | #956 | Link | |
Registered User
Join Date: Dec 2007
Posts: 639
|
Quote:
Completely different source too, one anime and the other a 3D game D: I shouldn't have downloaded a new compile D: |
|
6th September 2008, 09:19 | #959 | Link |
Strictly Rhythm
Join Date: Jul 2007
Location: Ljubljana, Slovenia
Posts: 166
|
Ranguvar:
I guess you got GCC-4.3.2 from TDM's website and have overwritten all your old files with the new ones from TDM's zip/tar.gz packages. The problem is that the gcc-4.3.2-tdm-1-core.tar.gz package includes pthreadGC2.dll and pthreadGCE2.dll in its /bin folder, libpthreadGCE2.a, libpthreadGC2-static.a and libpthread.a in its /lib folder and pthread.h, sched.h and semaphore.h in its /include folder. You probably copied over those files to your MinGW /bin, your MinGW /include and your MinGW /lib folder folder. I suggest you remove all these files, get the latest pthread cvs (cvs -d server:anoncvs@sources.redhat.com:/cvs/pthreads-win32 checkout pthreads), compile (make clean GC-static) and install it (copy libpthreadGC2.a to your MinGW /lib folder and copy pthread.h, sched.h and semaphore.h to your MinGW /iclude folder). That way you will eliminate the need of x264.exe for an extra pthreadGC2.dll in C:\Windows\System32. Trust me on this one, I had the same problem. I also suggest you people update your GPAC libraries. Many have reported errors building it from CVS, however I have found a nasty trick that actually works: 1. download the old stable tarball from here http://downloads.sourceforge.net/gpa...4.4-rc2.tar.gz 2. once it is downloaded, extract it to your MSYS /home/username folder and cd into it (i.e. cd /home/username/gpac) 3. while inside the gpac folder get the latest GPAC CVS using the command cvs -z3 -dserver:anonymous@gpac.cvs.sourceforge.net:/cvsroot/gpac co -P gpac 4. run ./configure && make lib 5. copy /home/username/gpac/include/gpac to your MinGW /include folder P.S.: If this doesn't work for you try it in your /home folder (i.e. /home/gpac).
__________________
Last edited by techouse; 6th September 2008 at 09:50. |
6th September 2008, 09:20 | #960 | Link | |
Little red-cap
Join Date: Mar 2008
Location: wanna on moon
Posts: 42
|
Quote:
|
|
Tags |
h.264, x264, x264 builds, x264 patches, x264 unofficial builds |
Thread Tools | Search this Thread |
Display Modes | |
|
|