![]() |
avsInfo.exe has stopped working - Printable Version +- Selur's Little Message Board (https://forum.selur.net) +-- Forum: Hybrid - Support (https://forum.selur.net/forum-1.html) +--- Forum: Problems & Questions (https://forum.selur.net/forum-3.html) +--- Thread: avsInfo.exe has stopped working (/thread-1530.html) |
avsInfo.exe has stopped working - lordsmurf - 13.09.2020 Continuing this conversation from July... Every time I drop a .avs into the Open File, this appears. I'm still using the 64+32 build from July, _dev_2020.07.28-212013.exe I just have to close the error, and that's that. Nothing bad seems to happen, just annoying. What else do you need to trace this, make it stop? ![]() Quote:Problem signature: RE: avsInfo.exe has stopped working - Selur - 13.09.2020 Quote:What else do you need to trace this, make it stop?a debug output to start off ![]() RE: avsInfo.exe has stopped working - lordsmurf - 13.09.2020 (13.09.2020, 05:29)Selur Wrote:Quote:What else do you need to trace this, make it stop?a debug output to start off Where is it? (Forgot again. ![]() RE: avsInfo.exe has stopped working - Selur - 13.09.2020 read sticky: https://forum.selur.net/showthread.php?tid=3 RE: avsInfo.exe has stopped working - lordsmurf - 13.09.2020 Debug attached. RE: avsInfo.exe has stopped working - Selur - 13.09.2020 Okay, not surprised that Hybrid might not like your script: AVISource("N:\DC final new\DC 03.avi") b. your script does not include the scripts and load the files it relies on. Strange thing is that avsInfo (64bit) version properly reports: Color: YUY2, Resolution: 640x480, Frame rate: 60000/1001 fps, Length: 260114 frames, TFF -> I'll compile a current dev version for Windows and send you a link via PM. atm. my guess is that this is either some problem with the old version or this is a problem with AviSource not liking the fast open and release of the source file. Cu Selur RE: avsInfo.exe has stopped working - lordsmurf - 22.09.2020 No effect, still the same ... sort of. The error is now instant. There used to be a lag of 2-3 seconds, between dragging AVS to input, and the pop-up error. Using the 9/18 dev. This issue aside, I see some other nice changes and additions in that new dev. Need time to play. ![]() Note that I write my scripts in AvsPmod, and generally test encode a trim() piece as AVI before commit to Hybrid encode. Not running into any Avisynth errors there. RE: avsInfo.exe has stopped working - Selur - 22.09.2020 Did you 'fix' the problems I mentioned, like: a. loading the dependencies b. adding 'return last' to the end of your script ? Have you tried using FFVideoSource instead of AviSource. Problem with AviSource is that it uses VFW and thus I can't easily reproduce the problem here. ![]() Using: ClearAutoloadDirs() My guess is that the problem is due to a mix of Avisynth dlls or script versions being loaded between Hybrid and your auto-load Avisynth folder. (or an issue with AviSource or the vfw decoder) Which is why Hybrids Avisynth scripts always start with 'ClearAutoloadDirs()' to avoid auto-loading. --- Quote:Note that I write my scripts in AvsPmod, and generally test encode a trim() piece as AVI before commit to Hybrid encode. Not running into any Avisynth errors there.Your AvsPmod is probably setup to use the system wide files in the Avisynth auto-load folder which whatever Avisynth version is installed in your system. When loading it in Hybrid, Hybrid does not auto-load stuff. Cu Selur |