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 |
29th July 2009, 16:04 | #2061 | Link | |
Registered User
Join Date: Sep 2007
Posts: 12
|
Quote:
Unfortunately, 13 doesn't apply cleanly to latest git (x264.c changes) and my work schedule will leave me only an hour or so each day to check it out. I did notice that if I don't specify --fps (with version 15 of the patch) I don't get the assertion failure. But it assumes 25fps, which is incorrect, and seems to encode at about 1/4th the rate that I was previously getting with x264+hrd version 9 from several months ago. |
|
29th July 2009, 17:21 | #2063 | Link |
Wewkiee
Join Date: Feb 2002
Location: kashyyyk
Posts: 2,269
|
@mopurist
http://forum.doom9.org/showthread.ph...66#post1306166 <-the 13 in this post. it was modified by one of the other builders to patch post preset era x264.
__________________
...yeah...but...why on earth would I compare apples with apples? |
29th July 2009, 18:30 | #2064 | Link |
もこたんインしたお!
Join Date: Jan 2008
Location: Finland / Japan
Posts: 512
|
x264 r1195 64bit unpatched:
download ; hash
x264 r1195 32bit download ; release notes
x264 r1195 64bit download ; release notes
patched with:
__________________
[I'm human, no debug]
|
29th July 2009, 21:31 | #2065 | Link |
Registered User
Join Date: Jul 2005
Posts: 438
|
I'm using Techouse's build r1195 and I'm still getting the same error "This application has requested the Runtime to terminate in an unusual way. Please contact the application's support team for more information." using subme 10. Something is seriously wrong... The last working revision for me was r1187 (I think).
|
29th July 2009, 21:32 | #2066 | Link | |
x264 developer
Join Date: Sep 2005
Posts: 8,666
|
Quote:
|
|
29th July 2009, 21:51 | #2068 | Link |
Compiling Encoder
Join Date: Jan 2007
Posts: 1,348
|
x264 w/ debug symbols
you can use this with mingw's gdb and provide a backtrace upon the crash (if it does still crash) |
29th July 2009, 22:06 | #2071 | Link | |
x264 developer
Join Date: Sep 2005
Posts: 8,666
|
Quote:
... <it crashes> bt |
|
29th July 2009, 22:06 | #2072 | Link |
Software Developer
Join Date: Jun 2005
Location: Last House on Slunk Street
Posts: 13,248
|
Maybe a problem with "SJLJ" -vs- "Dwarf-2" Unwinding?
__________________
Go to https://standforukraine.com/ to find legitimate Ukrainian Charities 🇺🇦✊ |
29th July 2009, 22:09 | #2074 | Link | |
Software Developer
Join Date: Jun 2005
Location: Last House on Slunk Street
Posts: 13,248
|
Quote:
http://forum.doom9.org/showpost.php?...postcount=2071 BTW: You may need to type "run" or "c" to make the program start/resume until it crashes...
__________________
Go to https://standforukraine.com/ to find legitimate Ukrainian Charities 🇺🇦✊ Last edited by LoRd_MuldeR; 29th July 2009 at 22:15. |
|
29th July 2009, 22:11 | #2075 | Link | |
Registered User
Join Date: Jul 2005
Posts: 438
|
Quote:
I'll report back when results have arrived. Edit: Sorry, it's strange... Now gdb says, "gdb: unrecognized option --threads" Edit2: Oh, @DarkShikari: --args was meant literally... now it works, but I get massive output in the console. Does it terminate and show the error, when there is an abnormal termination? kemuri-_9's debug build does not include the --nal-hrd patch, so the situation is not identical to my crash situation. Edit3: I got to go to bed, exam tomorrow, but I'll post the results in about 8 hours. Encoding is slow, duplicating the encoding situation (1 fps...), but it'll probably have crashed by tomorrow morning (if it crashes). Last edited by moviefan; 29th July 2009 at 22:43. |
|
29th July 2009, 22:53 | #2076 | Link | |
Software Developer
Join Date: Jun 2005
Location: Last House on Slunk Street
Posts: 13,248
|
Quote:
But if x264 crashes, gdb will interrupt, show an error message and return to the propmpt. Then you can type "bt" to get a stacktrace, so we see where exactly it crashed. If that doesn't happen, the crash simply doesn't occur with kemuri's debug build. Good luck !!!
__________________
Go to https://standforukraine.com/ to find legitimate Ukrainian Charities 🇺🇦✊ |
|
30th July 2009, 08:10 | #2077 | Link |
Registered User
Join Date: Jul 2005
Posts: 438
|
x264 crashed.
"Program received signal SIGSEGV, Segmentation fault. [Switchting to thread 2268.0x20c] 0x6fb775f6 in libavcodec!dspuitl_init () from ...\DGAVCDec\libavcodec.dll" Hm, it seems, that x264 is OK and DGAVCDec is the problem, right? Strange, since I had done encodes with exactly the same .dga-file and exactly this DGAVCDec version. Thanks, I hope it'll be good. Stochastic processes... Last edited by moviefan; 30th July 2009 at 18:44. |
30th July 2009, 09:42 | #2078 | Link |
Software Developer
Join Date: Jun 2005
Location: Last House on Slunk Street
Posts: 13,248
|
When the "Segmentation fault" happens, type bt to get a Stacktrace and post the result back here...
__________________
Go to https://standforukraine.com/ to find legitimate Ukrainian Charities 🇺🇦✊ |
30th July 2009, 18:44 | #2079 | Link |
Registered User
Join Date: Jul 2005
Posts: 438
|
Hm, I did type bt at that point, but it didn't reveal any new information. There were some thread messages (or whatever they are) and the message about libavcodec. What should have been written there? In case, I missed something, I will repeat the backtrace.
|
Tags |
h.264, x264, x264 builds, x264 patches, x264 unofficial builds |
Thread Tools | Search this Thread |
Display Modes | |
|
|