I normally use BDRB for most stuff, but lately the x264.exe that it uses for some odd reason is crashing while encoding and I get this error message:
[Attachment 48075 - Click to enlarge]
So, I tried using the CMD line using the x264.exe that JD uses in his subfolder. Same thing. Weird... never happened before. So, I thought I'd try DLing the newest version of x264 for Windows 64 and use the CMD line. Well, it LOOKS like it is running just fine, BUT... in this case, the CMD window is NOT showing the rather important parameters that the older version did show. Mainly, showing the percentage of the file done (which is important because that gives me some idea as to the resulting file size) and also the estimated time left is not showing. So, I have NO bloody idea how large the file size is going to be or how long the encode is going to take.
So, if anyone can kindly help me to understand both why running the version x264 that I've ALWAYS used in BDRB or in the CMD line causes this prompt, or at least WHY the newest version of x264 does not show these important parameters in the CMD window (or perhaps what I may need to add to the instructions TO show it) that would be great!
This is the version I'm using: x264-r2935-545de2f
+ Reply to Thread
Results 1 to 6 of 6
Does DBRB use x264 for directly opening e.g. an avs script? The crash could be a problem with AviSynth/its plugins/the source, not the core x264 library. (Then again, I think it should show the percentage in that case. Percentage usually isn't shown if you pipe or use lavf input and aren't using --frames argument.)
Upload DBRB log.
avs4x26x.exe -L x264-64bit.exe --crf 18 --output out.264 input_32bit_avisynth.avs
Yes, thanks to all of you very much! I actually did figure out from another thread, as Sneaker mentions above, that I do need to add --frames [number of frames] in the CMD line and then it DOES indeed show the percentage done and time remaining, so that's nice.
However, strangely, even with the latest 264.exe above my system gave the same error during encoding. I'm thinking that maybe this is some kind of heat issue...??? This is going to be a real drag if I cannot encode with x264 anymore...
Thanks though for all your help!