INFO 13:30:08 = End Hardware Decoders Auto-detection = INFO 13:30:08 Hardware Decoders detected (in order of preference): INFO 13:30:08 Total Hardware Decoders detected = 1 INFO 13:30:08 = Start Hardware Decoders Auto-detection = Hardware Detection Process crashedĪnd So4HardwareDetectionOutput.xml file contains : There is a So4HardwareDetectionError.log file that contains : (I purged the folder and reset Vegas 18, then launched Vegas 18). VP18 Update 334 released (), I looked to the hardware detection logs. If you find the solution, please make sure to post a reply back here !!! If that does not fix your problem, I recommend you post your problem on the official Vegas Pro Forums here: Now do another full program reset for Vegas Pro. ![]() Location of Intel tbb.dll files are here:Ĭ:\Program Files (x86)\Intel\OpenCL SDK\3.0\bin\圆4\tbbĬ:\Program Files (x86)\Intel\OpenCL SDK\3.0\bin\x86\tbbĭelete Intel tbb.dll versions and replace with Vegas Pro version. Location of Vegas Pro 18 version is here. The solution is to replace the Intel versions with the Vegas Pro 18 version. If you are both using Intel CPUs, there is something you can try to fix the bug, before the next new build is released. We believe the problem is being caused by new code that was added to the latest Vegas Pro 18 update #373. I remembered something important today, that may be the cause of your problem.Īnother user on the forum before Christmas was having problems with Batch rendering not working in Vegas Pro 18. I do have a suggestion that BOTH OF YOU to try, if you're using Intel CPUs. Uninstall Vegas Pro and re-install if you have been doing that. ![]() If you have been changing source code, it can have other effects which cause other problems. If any of you have been mucking around file FileIO components, I recommend you do not do that. ![]() I've tried replacing that mp4 dll with one of the same name from other video programs, including MSP, but that didn't work. But then I don't have ability to render MainConcept MP4s! All other output formats work, even the Sony Xcam MP4 (though that generates huge files.) I could accept this and find a work-around (e.g., export the Xcam MP4s and shrink them in another program like Handbrake) but that's not an appealing workflow. VP Pro seems to work perfectly if that one dll file is removed from the File IO plug-ins folder. Through much trial and error, I've concluded that the problem lies in the folder "mxavcaacplug" and specifically the file "mc_mux_mp4.dll." This apparently is something needed to make MainConcept MP4s. That got me thinking maybe one of these plug-ins is causing the problem. If I disable the program's FileIO Plug-Ins folder (by temporariily renaming it), I can choose "render as" in VP18 and the render window opens. I saw a reference elsewhere to the FileIO Plug-Ins, specifically saying to remove any 3rd party plug-ins.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |