[x264-devel] Bug Report/Help?

[Kevin P. Jacobson]

Mathieu, thanks for your reply.  I am willing to go through the different variables to try and find the issue.  I didn't intend to say the problem was only with x264 - it is just that is the only application that I've run that has had this result.  But I digress, maybe it is the avisynth filter, I'm not sure that I've run this script on this quad core system before, but I have used it on a dual core without a problem (this is why I thought the quad core was more of the issue at hand).

Here is the script...basically an AutoGK generated one actually, but I made some changes.  Something that stands out is maybe the RemoveGrainSSE3 filter.  Perhaps I should try a run with that filter disabled.  Does that sound like a worth while idea?

Thanks!

LoadPlugin("D:\EncodingTools\Filters\DGDecode.dll")
LoadPlugin("D:\EncodingTools\Filters\autocrop.dll")
LoadPlugin("D:\EncodingTools\Filters\vsfilter.dll")
LoadPlugin("D:\EncodingTools\Filters\ColorMatrix.dll")
LoadPlugin("D:\EncodingTools\Filters\RemoveGrainSSE3.dll")
movie = mpeg2source("D:/1.d2v")
ConvertFPS(movie,23.976)
cropclip = autocrop(movie,mode=0,wmultof=4,hmultof=4,samples=10,aspect=0,threshold=34,samplestartframe=0,leftadd=0,rightadd=0,topadd=0,bottomadd=0)
fixed_aspect = 1.18518518518519
c_width = width(cropclip)
c_height = round(height(cropclip) / fixed_aspect)
input_par = float(c_width)/float(c_height)
input_par = (input_par > 1.4) || (input_par < 1.25) ? input_par : (4.0/3.0)
out_width = 640
out_height = round(float(out_width) / input_par)
hmod = out_height - (floor(out_height / 16 ) * 16)
out_height = (hmod > 4) ? (out_height + (16 - hmod)) : (out_height - hmod)
new_aspect = (float(out_width) / float(out_height)) / fixed_aspect
autocrop(movie,mode=0,wmultof=4,hmultof=4,samples=10,aspect=new_aspect,threshold=34,samplestartframe=0,leftadd=0,rightadd=0,topadd=0,bottomadd=0)
LanczosResize(out_width,out_height)
RemoveGrain(mode=2)
ColorMatrix("Rec.709->Rec.601",opt=0,hints=false)
### Watermark ###
TextSub("D:\1.ssa")


________________________________________
From: x264-devel-bounces at videolan.org [x264-devel-bounces at videolan.org] On Behalf Of Mathieu Monnier [manao at melix.net]
Sent: Tuesday, August 14, 2007 9:42 AM
To: Mailing list for x264 developers
Subject: Re: [x264-devel] Bug Report/Help?

First of all, random crashes tends more often than not to be due to
hardware failure. And even memtests & co don't always manage to test
exhaustively CPU/Ram ( I know that for a fact, since I got into the same
trouble as you, with XviD at that time. Ram passed every possible tests,
but it kept randomly crashing on me, and only with XviD. Changing the
ram fixed definitely the issue ).

Secondly, you using an avisynth script. Care to past that script here ?
I would tend to trust x264 far more than some avisynth filters...

Thirdly, what happens if you use --threads 1 ( and 2, 3, 4 ? ). What
about --thread-input ?

Finally, you're the first one to experience crashes with x264 &
multicore ( even quadcore ), that's why everyone here tends to think
something other than x264 is guilty.

Regards,

Mathieu

_______________________________________________
x264-devel mailing list
x264-devel at videolan.org
http://mailman.videolan.org/listinfo/x264-devel
_______________________________________________
x264-devel mailing list
x264-devel at videolan.org
http://mailman.videolan.org/listinfo/x264-devel