Each time i try to start up Vegas pro 17, it freezes when i get to this point "creating video plugin factory". Does someone know how to fix it?
im using windows 10 with the latest update install.
Vegas Pro 17 version 17 (build 421)
I found the problem, thanks to another post :)
What was the problem? I have the same issue and cant find an answer
What was the problem? I have the same issue and cant find an answer
j-v wrote on 3/17/2020, 5:55 PM
Welcome to this forum.
it is probably due to a not good OFX plugin installed on your hardware.
You can try before to start VPro 17 to rename the File "C:\Program Files\VEGAS\VEGAS Pro 17.0\OFX Video Plug-Ins" to "C:\Program Files\VEGAS\VEGAS Pro 17.0\OldOFX Video Plug-Ins" an try to start again. When it goes now good, change it back to the old name and try the plugins being allowed one by one untill you find the guilty one.
What was the problem? I have the same issue and cant find an answer
j-v wrote on 3/17/2020, 5:55 PM
Welcome to this forum.
it is probably due to a not good OFX plugin installed on your hardware.
You can try before to start VPro 17 to rename the File "C:\Program Files\VEGAS\VEGAS Pro 17.0\OFX Video Plug-Ins" to "C:\Program Files\VEGAS\VEGAS Pro 17.0\OldOFX Video Plug-Ins" an try to start again. When it goes now good, change it back to the old name and try the plugins being allowed one by one untill you find the guilty one.
This trick does not work. It crashes the software once its has started, especially when opening older projects.
@ToonDoctor
It is better to stay at your own message for your problem that is not the same as on which you react here.
I have the exact same bug described above.
My Vegas17 started crashing on the video plug-in factory after working well at first. After much testing, uninstalling things, and re-installing, I found the c:\Windows\System32\OpenCL.dll file had been updated on 5/7/2020. When I pulled an older copy and replaced it (which took some doing), Vegas17 (as well as several other programs) started working fine.
I found out some companies include a custom OpenCL.dll file and install it over the standard one from Microsoft. The one I have now is dated 1/30/2020, but Catalyst Browse from Sony complains about it needing updating...still works, but doesn't do some GPU rendering...which I don't need in Catalyst Browse anyway.
@jhinnant58 if you delete your cache files, put the new dll back, can you load ok?
Make sure your cache folder is clean by deleting everything in C:\Users\<user name>\AppData\Local\VEGAS Pro\<version #> (delete everything with VP closed and use task manager to make sure it's really gone from memory). The initial startup will be kind of long after this cleaning but once it's up, restart VP again. Use task manager to make sure VP is completely gone from memory before starting it back up.
I just did a search for OpenCL.dll on my system and found all these:
C:\>dir /s /b opencl.dll C:\Program Files\BorisFX\ContinuumHitFilmOFX\12\lib\OpenCL.dll C:\Program Files\BorisFX\ContinuumOFX\11\lib\OpenCL.dll C:\Program Files\FXHOME\HitFilm Express\OpenCL.dll C:\Program Files\VEGAS\Movie Studio Platinum 16.0\FileIO Plug-Ins\mxhevcplug\opencl.dll C:\Program Files\VEGAS\Movie Studio Platinum 16.0\FileIO Plug-Ins\so4compoundplug\opencl.dll C:\Program Files\VEGAS\Movie Studio Platinum 17.0\FileIO Plug-Ins\mxhevcplug\opencl.dll C:\Program Files\VEGAS\Movie Studio Platinum 17.0\FileIO Plug-Ins\so4compoundplug\opencl.dll C:\Program Files\VEGAS\VEGAS Pro 17.0\FileIO Plug-Ins\mxhevcplug\opencl.dll C:\Program Files\VEGAS\VEGAS Pro 17.0\FileIO Plug-Ins\so4compoundplug\opencl.dll C:\Windows\System32\OpenCL.dll C:\Windows\System32\DriverStore\FileRepository\rdvgwddmdx11.inf_amd64_4d3a1b424a257b28\opencl.dll C:\Windows\SysWOW64\OpenCL.dll C:\Windows\WinSxS\amd64_dual_rdvgwddmdx11.inf_31bf3856ad364e35_10.0.18362.1_none_d782513d0562d02b\opencl.dll C:\Windows\WinSxS\wow64_microsoft-windows-r..xwddmdriver-wow64-c_31bf3856ad364e35_10.0.18362.1_none_8385dcee297257d1\opencl.dll
The one in C:\Windows\System32 is huge compared to most of the others.
@jhinnant58 if you delete your cache files, put the new dll back, can you load ok?
Make sure your cache folder is clean by deleting everything in C:\Users\<user name>\AppData\Local\VEGAS Pro\<version #> (delete everything with VP closed and use task manager to make sure it's really gone from memory). The initial startup will be kind of long after this cleaning but once it's up, restart VP again. Use task manager to make sure VP is completely gone from memory before starting it back up.
That's basically what I did. Changing out the OpenCL.dll is what did it as I had cleared everything before hoping that alone would fix it, but it didn't. I think it's still a good idea to try anyway.