![]() Really strange things happening here in render land!Ģ) The output produce by VFAPI Reader isn't readable by any of the programs on my PC i.e. After test rendering with Vegas 64 and going back to Vegas 32, the renders with FrameServer and Video for Windows (AVI) work okay for a while. Vegas 64 bit renders no problems using any option. I guess because it's still selected in the Render window before trying to change to video for windows format. When I ran proxyon.reg, I got the same prompt saying all parameters couldn't be set.ī) Now, Vegas won't render to "Video for Windows" if FrameServer was tried previously. I tried the proxyon.reg in VD to see if it helps, but now FrameServer only works intermittently without crashing Vegas. When I ran proxyoff.reg, the PC complained that not all parameters could be set because they were in use by something else. I tried this because VFAPIConv wasn't giving me the option to open up an. ![]() I don't know if running proxyoff.reg, which comes with VirtualDub, as prescribed on Doom9 caused the problem or what. I had no problems with FrameServer before installing VFAPI Reader Codec. Looks like error crash points to modules vegas100.exe and ntdll.dll. I'm having problems getting your slo-mo workflow to work on Vegas Pro 10a 32 bit:Ī) DebugMode Frameserver 2.7 is causing Vegas to crash whenever I hit the save button in "Render As" window. ![]() I found that in order to have VirtualDub and Avisynth scripts to be recognized by VFAPIconv, you have to copy ReadAVS.dll and ReadAVS.reg to the VFAPIconv dir.į/threads/37390-How-to-frameserve-%28dvd2avi-VirtualDub-Avisynth-VFAPI%29 I'm having a few issues and apologize for the long post. Thanks so much John for sharing this wonderful techinique and opening our eyes to a better way! ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |