maksa
17th March 2005, 15:14
Just discoverd interesting thing and decided to share with community.
We all know that on Avisynth.org is warning about Avisynth 2.5 chrashing encoders after first pass. They recommend stres test to check soundness of your hardware.
I have:
P IV, 3 GHz, HT, 512MB RAM, 400 MHz bus, 160 GB HD, 200 GB HD, 128 MB ATI Radeon 9200.
Installed: Avisynth 2.5.5
CCE SP 2.50 retail
Did one small PAL interlaced segment (500 frames) of scrached material with Fizick DeSpot & DePan configuration. Everything works fine in Mplayer, but when attempt to encode, CCE just closes the window after first pass. Fiddled around, used simpler script, it works fine. Tried stress test (Mesner primes - Prime95) for over an hour, everything fine.
Tried something exotic. Used Vdub as a frame server. Opened AVS script with it and served it to CCE through VDub. Eurecca...it passes everything! Any ideas why would usage of 2 frameservers stop CCE from chrashing?
Regards...
We all know that on Avisynth.org is warning about Avisynth 2.5 chrashing encoders after first pass. They recommend stres test to check soundness of your hardware.
I have:
P IV, 3 GHz, HT, 512MB RAM, 400 MHz bus, 160 GB HD, 200 GB HD, 128 MB ATI Radeon 9200.
Installed: Avisynth 2.5.5
CCE SP 2.50 retail
Did one small PAL interlaced segment (500 frames) of scrached material with Fizick DeSpot & DePan configuration. Everything works fine in Mplayer, but when attempt to encode, CCE just closes the window after first pass. Fiddled around, used simpler script, it works fine. Tried stress test (Mesner primes - Prime95) for over an hour, everything fine.
Tried something exotic. Used Vdub as a frame server. Opened AVS script with it and served it to CCE through VDub. Eurecca...it passes everything! Any ideas why would usage of 2 frameservers stop CCE from chrashing?
Regards...