well, it's like i said. which is why i'm confused...
Code:
[2019-05-19][02:16:40] avs [error]: failed to load avisynth
[2019-05-19][02:16:40] x264 [error]: could not open input file `C:\Temp\8E5_python.vpy'
[2019-05-19][02:16:40]
[2019-05-19][02:16:40] PROCESS EXITED WITH ERROR CODE: -1
i'll update with the latest version of the x264 gui tho just in case, and report back whether this changes anything.
--
further updates:
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
--
#update 2:
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?
thanks!