Trying to track down plug-in error in old VEG file

ddm wrote on 3/25/2019, 3:47 PM

I've been asked to resurrect an old project from 2008 and I've worked out many of the missing files etc issues, but I have one error left that I haven't been able to track down. It's the "an error occurred when loading a plug in,,," error. I had several plugins and I've installed all the old ones that I remember using but I must be still missing something. It's a long project (1 hour 22 minutes) with tons of tracks and edits so I haven't been able to see anything out of the ordinary as I've scrubbed the timeline. I've checked the "edit details" screen and I have the "Project Inspector" extension from Excalibur. Nothing seems to list what I might be missing. The plug in error is quite arcane (a76d1881-c7f7-46e1-87b5-213f980cdf91) and Google shows nothing, didn't really expect it would. Any insight would be most welcome. Thanks.

Comments

j-v wrote on 3/25/2019, 4:55 PM

Very difficult to help you while we know nothing about your Vegas version , build number a.s.o.

Maybe dealing here on a cloudservice your projectfile without any content can be of help for other users to seek something you don't know yourself.

ddm wrote on 3/25/2019, 7:49 PM

Pretty sure this isn't an issue with my version of vegas, more of a "can vegas do this, or is there a plug in that can", but here you go. I am presently using Vegas 16 v.361. Gigabyte MB, 16 gb ram, AMD R9 390 Video card, Windows 10 pro. Project was originally started in Vegas 8, moved to 9 and finished and delivered there. Thanks.

xberk wrote on 3/25/2019, 11:32 PM

Long shot. Open the .veg file in Notepad. You may be able to see what FX were used. I tried one example with a file from VP12. I could see that the Black and White FX was in the .veg. There must exist better debuggers to use with a .veg file than notepad but the information on what FX were used in the project should be in the .veg if you can debug it.

ddm wrote on 3/26/2019, 12:48 AM

Cool. Thanks. I'll check that out.

jetdv wrote on 3/26/2019, 2:16 PM

If you still have access to the machine this was created on, you could also search for a76d1881-c7f7-46e1-87b5-213f980cdf91 in the registry and it will tell you what plugin that is referring to. Whatever it is hasn't been installed on my current machine.

xberk wrote on 3/26/2019, 3:09 PM

Fooled around with this a bit today ... found out that Notepad++ (free download) will allow you to search the .veg file ..

ddm wrote on 3/26/2019, 7:16 PM

Thanks, Jetdv and xberk. I do have an old system drive, XP and W7, I'll have to take a look at the registry. I was able to load a veg in a text editor and search on the error message. No luck. But I did see that there was a font that was missing and that fixed an issue that I had missed, the whole Closing Credits sequence had defaulted to Helvetica. That might have been the problem, once I saved the VEG after installing the correct font, I stopped getting the plugin error, but that doesn't ring true. Again... thanks.