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.

 

Go Back   Doom9's Forum > Video Encoding > MPEG-4 AVC / H.264

Reply
 
Thread Tools Search this Thread Display Modes
Old 29th July 2009, 16:04   #2061  |  Link
mopurist
Registered User
 
Join Date: Sep 2007
Posts: 12
Quote:
Originally Posted by Trahald View Post
@mopurist
Hmm... i couldnt duplicate the issue, but i'll keep trying.

Except for wasting a few bits.. rev 13 of the patch is fine to use.
Thanks for taking a look.

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.
mopurist is offline   Reply With Quote
Old 29th July 2009, 16:10   #2062  |  Link
imk
|ン、)
 
imk's Avatar
 
Join Date: Feb 2008
Posts: 77
x264-r1195M-imk-win.7z
win_build_info.txt
imk is offline   Reply With Quote
Old 29th July 2009, 17:21   #2063  |  Link
Trahald
Wewkiee
 
Trahald's Avatar
 
Join Date: Feb 2002
Location: kashyyyk
Posts: 2,270
@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?
Trahald is offline   Reply With Quote
Old 29th July 2009, 18:30   #2064  |  Link
JEEB
もこたんインしたお!
 
JEEB's Avatar
 
Join Date: Jan 2008
Location: Finland / Japan
Posts: 514
x264 r1195 64bit unpatched:
download ; hash
  • built on Jul 29 2009, gcc: 4.3.4 20090220 (prerelease) (x64.generic.Komisar)
  • fprofiled, otherwise defaults
________________________________________________________________________________

x264 r1195 32bit
download ; release notes
  • built on Jul 29 2009, gcc: 4.3.4 20090220 (prerelease) (x32.generic.Komisar)
  • fprofiled, -march=i686

x264 r1195 64bit
download ; release notes
  • built on Jul 29 2009, gcc: 4.3.4 20090220 (prerelease) (x64.generic.Komisar)
  • fprofiled, -march=core2

patched with:
  • x264_win_zone_parse_fix_05.diff
  • x264_hrd_pulldown.15_interlace.diff
__________________
[I'm human, no debug]
JEEB is offline   Reply With Quote
Old 29th July 2009, 21:31   #2065  |  Link
moviefan
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).
moviefan is offline   Reply With Quote
Old 29th July 2009, 21:32   #2066  |  Link
Dark Shikari
x264 developer
 
Dark Shikari's Avatar
 
Join Date: Sep 2005
Posts: 8,688
Quote:
Originally Posted by moviefan View Post
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).
I can't do anything without a gdb backtrace, sorry.
Dark Shikari is offline   Reply With Quote
Old 29th July 2009, 21:40   #2067  |  Link
moviefan
Registered User
 
Join Date: Jul 2005
Posts: 438
Do I need to compile x264 for performing the backtrace with gdb? I have never done this before... Or is it too difficult do it right away for the first time?
moviefan is offline   Reply With Quote
Old 29th July 2009, 21:51   #2068  |  Link
kemuri-_9
Compiling Encoder
 
kemuri-_9's Avatar
 
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)
__________________
custom x264 builds & patches | F@H | My Specs
kemuri-_9 is offline   Reply With Quote
Old 29th July 2009, 21:59   #2069  |  Link
moviefan
Registered User
 
Join Date: Jul 2005
Posts: 438
OK, what's this? ".../gdb/dwarf2read.c:985: gdb-internal-error: read_comp_unit_head: dwarf from non elf file" "An internal GDB error was detected. This may make further debugging unreliable."
moviefan is offline   Reply With Quote
Old 29th July 2009, 22:03   #2070  |  Link
kemuri-_9
Compiling Encoder
 
kemuri-_9's Avatar
 
Join Date: Jan 2007
Posts: 1,348
A. if you aren't already, be sure to be using mingw gdb 6.8-3
B. if you are, then post a sample that you can consistently crash with and the command line you're using to cause the crash.
__________________
custom x264 builds & patches | F@H | My Specs
kemuri-_9 is offline   Reply With Quote
Old 29th July 2009, 22:06   #2071  |  Link
Dark Shikari
x264 developer
 
Dark Shikari's Avatar
 
Join Date: Sep 2005
Posts: 8,688
Quote:
Originally Posted by moviefan View Post
Do I need to compile x264 for performing the backtrace with gdb? I have never done this before... Or is it too difficult do it right away for the first time?
gdb --args ./x264_debug_build --all --your --normal --options

...

<it crashes>

bt
Dark Shikari is offline   Reply With Quote
Old 29th July 2009, 22:06   #2072  |  Link
LoRd_MuldeR
Software Developer
 
LoRd_MuldeR's Avatar
 
Join Date: Jun 2005
Location: Last House on Slunk Street
Posts: 13,196
Quote:
Originally Posted by moviefan View Post
OK, what's this? ".../gdb/dwarf2read.c:985: gdb-internal-error: read_comp_unit_head: dwarf from non elf file" "An internal GDB error was detected. This may make further debugging unreliable."
Maybe a problem with "SJLJ" -vs- "Dwarf-2" Unwinding?
__________________
There was of course no way of knowing whether you were being watched at any given moment.
How often, or on what system, the Thought Police plugged in on any individual wire was guesswork.


LoRd_MuldeR is offline   Reply With Quote
Old 29th July 2009, 22:08   #2073  |  Link
moviefan
Registered User
 
Join Date: Jul 2005
Posts: 438
A. is the problem. I used the current gdb version of DevCpp which is old. Do I have to run x264 in the gdb environment with my current x264 settings? So is this like a normal encode only under supervision of gdb?
moviefan is offline   Reply With Quote
Old 29th July 2009, 22:09   #2074  |  Link
LoRd_MuldeR
Software Developer
 
LoRd_MuldeR's Avatar
 
Join Date: Jun 2005
Location: Last House on Slunk Street
Posts: 13,196
Quote:
Originally Posted by moviefan View Post
A. is the problem. I used the current gdb version of DevCpp which is old. Do I have to run x264 in the gdb environment with my current x264 settings? So is this like a normal encode only under supervision of gdb?
Do it like proposed here:
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...
__________________
There was of course no way of knowing whether you were being watched at any given moment.
How often, or on what system, the Thought Police plugged in on any individual wire was guesswork.



Last edited by LoRd_MuldeR; 29th July 2009 at 22:15.
LoRd_MuldeR is offline   Reply With Quote
Old 29th July 2009, 22:11   #2075  |  Link
moviefan
Registered User
 
Join Date: Jul 2005
Posts: 438
Quote:
Originally Posted by LoRd_MuldeR View Post
Sorry, parallel posting

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.
moviefan is offline   Reply With Quote
Old 29th July 2009, 22:53   #2076  |  Link
LoRd_MuldeR
Software Developer
 
LoRd_MuldeR's Avatar
 
Join Date: Jun 2005
Location: Last House on Slunk Street
Posts: 13,196
Quote:
Originally Posted by moviefan View Post
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.
Yes, Avisynth spams the gdb console with debugging messages

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.

Quote:
Originally Posted by moviefan View Post
Edit3: I got to go to bed, exam tomorrow, but I'll post the results in about 8 hours.
Good luck !!!
__________________
There was of course no way of knowing whether you were being watched at any given moment.
How often, or on what system, the Thought Police plugged in on any individual wire was guesswork.


LoRd_MuldeR is offline   Reply With Quote
Old 30th July 2009, 08:10   #2077  |  Link
moviefan
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.

Quote:
Originally Posted by LoRd_MuldeR View Post
Good luck !!!
Thanks, I hope it'll be good. Stochastic processes...

Last edited by moviefan; 30th July 2009 at 18:44.
moviefan is offline   Reply With Quote
Old 30th July 2009, 09:42   #2078  |  Link
LoRd_MuldeR
Software Developer
 
LoRd_MuldeR's Avatar
 
Join Date: Jun 2005
Location: Last House on Slunk Street
Posts: 13,196
When the "Segmentation fault" happens, type bt to get a Stacktrace and post the result back here...
__________________
There was of course no way of knowing whether you were being watched at any given moment.
How often, or on what system, the Thought Police plugged in on any individual wire was guesswork.


LoRd_MuldeR is offline   Reply With Quote
Old 30th July 2009, 18:44   #2079  |  Link
moviefan
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.
moviefan is offline   Reply With Quote
Old 30th July 2009, 18:56   #2080  |  Link
Dark Shikari
x264 developer
 
Dark Shikari's Avatar
 
Join Date: Sep 2005
Posts: 8,688
Quote:
Originally Posted by moviefan View Post
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.
You were able to backtrace but you can't paste the results here so we can read them?
Dark Shikari is offline   Reply With Quote
Reply

Tags
h.264, x264, x264 builds, x264 patches, x264 unofficial builds

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


All times are GMT +1. The time now is 17:04.


Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2021, vBulletin Solutions Inc.