X264 terminate unexpected

[GZZ]

I get the following error in X264 encoder:

"F:\GZZ\!Tools\x264\x264.exe" "c:\GZZ\Chicken\job1.AVS" --bitrate
7096 --level 4.1 --sar 1:1 --aud --vbv-bufsize 14745 --vbv-maxrate 17500 --filt
er 0,0 --bframes 3 --direct auto --keyint 24 --min-keyint 1 --subme 2 --b-pyrami
d --b-adapt 1 --aq-mode 2 --me dia --partitions none --threads auto --thread-inp
ut --progress --no-psnr --no-ssim --stats "c:\GZZ\Chicken\job1.log" --pass 1 --o
utput NUL
avis [info]: 1920x1080 @ 23.98 fps (116401 frames)
x264 [info]: using SAR=1/1
x264 [info]: using cpu capabilities: MMX2 SSE2Fast SSSE3 Cache64
x264 [info]: profile Main, level 4.1
[95.7%] 111400/116401 frames, 10.38 fps, 7011.80 kb/s, eta 0:08:01
This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information.

I'am using the following AVS Script:
LoadPlugin("F:\GZZ\!Tools\dgAVCDec\DGAVCDecode.dll")
AVCSource("c:\GZZ\Chicken\Video.dga")

X264 encoder is rev. r1029 - I have downloaded the newest version r1046 from x264.nl to see if its any better.

I can insert a Trim script like Trim(111000, 116401) and encode the last part without any problems, so I dont think it has anything to do with the source. I have tried reencode it twice and it stops at the exact same location.. So is this a bug in X264 encoder ?

[neuron2]

It's probably libavcodec barfing on a stream error.

[LoRd_MuldeR]

Before you suspect x264 to crash: If you open that Avisynth script in VirtualDub, can you play it all the way to the end?
And what happens when you seek to the position where the crash has occurred?

[GZZ]

I will try virtualdub. But like I say I'm frameserving using DGAvcDec in a AVS script and DGavcDec didnt report any errors when creating the dga file. I can also reencode the last bit using the trim function and its working fine.

[poisondeathray]

Does it crash @ the same point using the same script if you use XviD, for example ? If not, that would suggest something amiss with x264 or at least that x264 build

[Dark Shikari]

Does it crash @ the same point using the same script if you use XviD, for example ? If not, that would suggest something amiss with x264 or at least that x264 buildNo, it would only suggest something amiss if x264 crashed in the same place every time and something else didn't.

This is what we have backtraces for folks.

[poisondeathray]

No, it would only suggest something amiss if x264 crashed in the same place every time and something else didn't.


Isn't that what I said? or am I misunderstanding your line of thinking ? :confused:

The OP said he tried it twice and it crashed at the same spot... and I said if XviD didn't it might suggest something is up with that x264 build...


I have tried reencode it twice and it stops at the exact same location.

[Dark Shikari]

Isn't that what I said? or am I misunderstanding your line of thinking ? :confused:No, I'm just blind.

[GZZ]

you where all right. I got like a few bad frames on my bluray rip. If I browse the frames with DGAvcDec it turn gray with pixel errors in a few frames, before it becomes normal again, like the decryption wasnt succesfully for a short amount of time. I will try rerip the disk. Sorry the 'fast' response on this... Maybe x264 should say something about bad source input or something.. Just an idea.

/GZZ

[LoRd_MuldeR]

you where all right. I got like a few bad frames on my bluray rip. If I browse the frames with DGAvcDec it turn gray with pixel errors in a few frames, before it becomes normal again, like the decryption wasnt succesfully for a short amount of time. I will try rerip the disk. Sorry the 'fast' response on this... Maybe x264 should say something about bad source input or something.. Just an idea.

/GZZ

If the Source filter in Avisynth encounters a crash, then x264 doesn't have a chance to do anything :p

Instead AVCSource() shouldn't crash, even with totally borked frames. But most likely the problem isn't in AVCSource() itself, but in libavcodec...