-
HandlePIChanges
Not having fired up Vegas Pro 19 for awhile, when I loaded it today I was greeted with a requestor box stating, “HandlePIChanges”. I am up-to-date with VP 19 Build 550 and loaded the latest NVIDIA drivers for my video card. This box keeps popping up and prevents me from doing anything until I clear it. As soon as I clear it, it pops up again ad nauseum!! VP 18 Build 527 appears to work just fine, so what’s going on with VP19?
-
5 Replies
-
Hey Rich — wish I knew the answer… (I don’t)
You may want to cross-post on the VegasCreativeSoftware forums if you don’t get an answer here.
-
Since I posted here last evening I have had the opportunity to revert to an earlier Vegas Pro 19 build. I found that not only Build 550 presents me with the HandlePIChanges requestor box anomaly, but Build 532 does so as well. Thankfully, when I reverted back to Build 458 everything now appears to work just fine (and I tested it for about a half hour, as well). While I have absolutely NO IDEA what programming jargon HandlePIChanges does or means, apparently my fix works. I probably will not update to any more VP 19 builds, since I do not know what in their programming code caused this problem for me. Evidently, it is a rare occurence, as I only found one other VP user who encountered it back in 2017 in an earlier version of VP. So the bottom line is if anyone else encounters this just try to revert back to Build 458.
-
I have asked Magix Support a number of times to investigate just exactly what HandlePIChanges means. Someone out there in computer programming land created this verbiage and it has to means something, but they have bided the question. Going back and forth with them over the past week or so, they asked for a system information report. Their first response was to blame third party scripts and add-ons (mini-apps, plug-ins, etc.), but I told them that I have not run any of them when the error occurs, and besides, if Build 458 works for me then it is SOME change THEY made in coding subsequent builds that is causing the error. Their answer: “we have no message like the
HandlePIChanges one you’re getting within our code…and In regards to those third party products the dev had this to add: Uninstall the VASST tools as well as the Excalibur installed too. Please also uninstall all of your NewBlue plug-ins as well. <font face=”inherit”>Finally, since it looks like the sfvstserver is crashing a lot on your system…remove all 3rd party audio plugins.” So are they saying I should just use Vegas Pro 19 out of the box WITHOUT ANY ADD-ONS? Sorry, but I NEED those add-ons, and besides, if Build 458 works and the add-ons work just fine with Build 458, it is not my add-ons that are causing the problem but the coding changes. Am I not correct in my line of thinking? Well I am not about to uninstall just about every third-party applet and am at my wit’s end with them, given that it appears they are the ones who made unilateral changes that apparently causes the </font>subsequent<font face=”inherit”> problem. So I am stuck on Build 458 ad nauseum and cannot move forward with Vegas Pro unless they stop blaming everyone else and turn to look inwards into what they have done.</font> -
I can tell you that I’ve used Excalibur and NewBlue in all versions of 19 including the current build 643 without seeing an error message. Could you please post a screenshot of that error message as well and any details that might be available?
-
It is possible that Project Inspector installed with Excalibur can cause this message to pop up. If you have Project Inspector installed, this will remove that message as well as add a Quantize to Frames check.
Please replace the DLL file in [My Documents]\Vegas Application Extensions
With the DLL in this zip file:
http://www.jetdv.com/scripts/ProjectInspectorVP220611.zip
Reply to this Discussion! Login or Sign Up