View Single Post
Old 19th May 2019, 10:34   #1800  |  Link
LoRd_MuldeR
Software Developer
 
LoRd_MuldeR's Avatar
 
Join Date: Jun 2005
Location: Last House on Slunk Street
Posts: 13,248
Quote:
Originally Posted by aldix View Post
um. latest simple x264/x265 gui. using latest this (https://github.com/jpsdr/x264/releases) for my encoding, always have been, swapping it out in the
C:\Program Files (x86)\MuldeR\Simple x264 Launcher v2\toolset\x64 folder. does this mean i cannot use tmod anymore? that would be very unfortunate...

Code:
[2019-05-19][02:45:34] 
[2019-05-19][02:45:36] vpyp [info]: Error: fwrite() call failed when writing frame: 0, plane: 0, errno: 22
[2019-05-19][02:45:36] vpyp [info]: Output 9 frames in 1.82 seconds (4.95 fps)
[2019-05-19][02:45:36] 
[2019-05-19][02:45:36] WARNING: Input process exited with error (code: 1), your encode might be *incomplete* !!!
[2019-05-19][02:45:36] 
[2019-05-19][02:45:36] FATAL ERROR: The encoder process has *crashed* -> your encode probably is *incomplete* !!!
[2019-05-19][02:45:36] Note that this indicates a bug in the current encoder, *not* in Simple x264/x265 Launcher.
[2019-05-19][02:45:36] 
[2019-05-19][02:45:36] PROCESS EXITED WITH ERROR CODE: -1073741795
Quote:
Originally Posted by aldix View Post
that sucks. tmod indeed doesn't work at all. whereas regular x264 does. with regular avisynth script it has always worked though. is it something inherent to tmod and there's no hope or what?
As we can see from your log, the encoder process (i.e. x264.exe) has crashed!

From the exit code -1073741795, which is equivalent to STATUS_ILLEGAL_INSTRUCTION (0xC000001D), we can conclude that x264 crashed because it tried to execute an instruction that is not supported by your CPU. If you get that error with "tmod" build, whereas the vanilla build that ships with Simple x264/x265 Launcher is working, then this indicates that the person who compiled "tmod" build used different compiler settings – settings not compatible with your CPU.

Anything else concerning "tmod" build would have to be discussed with the person who provides those builds. I don't provide or use "tmod" build.

BTW: You can ignore the warning about the input process (VapourSynth) in this case, because when the encoder processes crashes and thus breaks the pipe, then the input process won't be able to write to the pipe anymore, obviously.
__________________
Go to https://standforukraine.com/ to find legitimate Ukrainian Charities 🇺🇦✊

Last edited by LoRd_MuldeR; 19th May 2019 at 17:31.
LoRd_MuldeR is offline   Reply With Quote