jpsdr
16th May 2013, 18:46
I'm having a big issue with last x264 r2310.
I compile my own builds adding fade-compensate and Aq-Mode3&4 patches. Before i was also adding the "film grain optimisation", but it doesn't compile anymore with, so, i've removed it from my custom builds. I'm compiling (fprofiled) following doom10 tutorial, using komisar libpack & gcc (4.7.3), disabling opencl.
I'm doing this for months, no issues until now.
I've 5 files i try to encode targetting Blu-Ray.
First, i've try to use the DS x264-devel r2330.
After two days of encoding, i've checked the status. The file N°1 and N°2 were encoded and finished, and the second pass of file N°3 was running. When checked the log file, i've noticed a warning which should not be there, saying i was using 6 ref frames, not compliant with level. Strange, as there is --ref 4 in the command line. After checking the raw h264 files, media info tells me frame rate is 94fps... First line of log was properly showing 24000/1001... Played with DGIndexNV, file was at 60fps... Ok, my fault for using the devel version...
So, i've build the normal version. Make a little test, fps good.
So, i restarted the encoding. No luck, now x264 seems to crash rebooting the PC during the second pass of my file N°2. Reboot the PC, restart all encoded from clean boot... Same result. So, i've checked my partial h264 file, take a look at the scenes, nothing pops. I've created a little file of 1500 frames around the supposed crashing point, encode was fine. It's reproductible with the whole 100GB file 150000 frames, but not with a few frames... Wonderfull !!!
So, with devel version, no crash, but something very odd is happening (bad fps output and warning which should not be there), and with standard version, crash/reboot.
So... i don't know what to do... I can't provide 100GB of files, and except eventualy put on my github the version i'm using, i'm a little stuck...
Edit : Github here (https://github.com/jpsdr/x264/commits/Custom_Build2).
I compile my own builds adding fade-compensate and Aq-Mode3&4 patches. Before i was also adding the "film grain optimisation", but it doesn't compile anymore with, so, i've removed it from my custom builds. I'm compiling (fprofiled) following doom10 tutorial, using komisar libpack & gcc (4.7.3), disabling opencl.
I'm doing this for months, no issues until now.
I've 5 files i try to encode targetting Blu-Ray.
First, i've try to use the DS x264-devel r2330.
After two days of encoding, i've checked the status. The file N°1 and N°2 were encoded and finished, and the second pass of file N°3 was running. When checked the log file, i've noticed a warning which should not be there, saying i was using 6 ref frames, not compliant with level. Strange, as there is --ref 4 in the command line. After checking the raw h264 files, media info tells me frame rate is 94fps... First line of log was properly showing 24000/1001... Played with DGIndexNV, file was at 60fps... Ok, my fault for using the devel version...
So, i've build the normal version. Make a little test, fps good.
So, i restarted the encoding. No luck, now x264 seems to crash rebooting the PC during the second pass of my file N°2. Reboot the PC, restart all encoded from clean boot... Same result. So, i've checked my partial h264 file, take a look at the scenes, nothing pops. I've created a little file of 1500 frames around the supposed crashing point, encode was fine. It's reproductible with the whole 100GB file 150000 frames, but not with a few frames... Wonderfull !!!
So, with devel version, no crash, but something very odd is happening (bad fps output and warning which should not be there), and with standard version, crash/reboot.
So... i don't know what to do... I can't provide 100GB of files, and except eventualy put on my github the version i'm using, i'm a little stuck...
Edit : Github here (https://github.com/jpsdr/x264/commits/Custom_Build2).