Thanks so much for your interest, Edward. You have been a great advocate for me over these many years and trust that you may have a way to resolve this. Here is all of the current correspondence I have had with Magix Tech Support, in descending order starting with the June 25, 2022 email near the bottom (long):

Subject:

Re: [Ticket#2022062517005286] "HandlePIChanges" Requester Box, VP 19 ALL BUILDS AFTER 458--UPDATE!!

From:

Video Impressions <richkvideoimpressions@gmail.com>

Date:

7/12/2022, 1:14 PM

To:

MAGIX Pro Support <prosupport@magix.net>

I am most upset with your lack of customer service and that you are not looking at this with a different perspective. While I do accept that HandlePIChanges is a message that is not coming from your VEGAS software, I do NOT agree with your statement and attitude that "This means that it has to be coming from another source (most likely one of your third party products) which means there really isn't much else that we can do in regards to this message."

Please look at this again. As stated, all of my third party products work with Build 458; Magix updated to higher builds, each of which causes the HandlePIChanges error; therefore, even if a third party triggers "HandlePIChanges" it is in response to the code you changed in subsequent builds. Do you not agree that this is a solid line of logic, that your changes are causing something in my system to trigger the error? If so, what code is triggering the error? And asking for the umpeenth time, what exactly is the HandlePIChanges (as I have asked you in the computer programming business to check out, as I am not a programmer and have no access to one or I would gladly check this out myself).

I also am quite saddened that I am at the end of my Vegas Pro usage, for I can go no further on future builds until I know what is causing the problem AND I cannot work without my plug-ins.

It is a real shame that you are not willing to go any further in helping to resolve this issue when I know that really you can. The change causing the error was unilaterally triggered by your actions, not mine, and proof that Build 458 works for me indicates that with this build no third-party software causes ANY problems.

So please take another look at this with the hope that you will see things from this perspective and will be willing to continue to work with me.

Thank you in advance.

Rich

Richard W. Kutnick, President

427 Dunbar Ln

Highland Hts, OH 44143-3670

Home Office: 440-771-4117
Cell: 216-534-1246

richkvideoimpressions@gmail.com

www.videoimpressions.net

On 7/12/2022 12:51 PM, MAGIX Pro Support wrote:

Dear Richard,

This HandlePIChanges is a message that is not coming from our VEGAS software. This means that it has to be coming from another source (most likely one of your third party products) which means there really isn't much else that we can do in regards to this message.

--
Best regards,

MAGIX Software GmbH
Neal Siddell
Supportmanager
Berliner Str. 13
01067 Dresden - Germany

http://www.magix.com
 
Geschäftsführer | Managing Directors: Denis Burger, Jan Gackenholz, Klaus Schmidt
Amtsgericht | Commercial Register: Berlin Charlottenburg, HRB 127205 B
 Please make sure to include your original correspondence when replying and leave the subject line unaltered. Changing the subject line may cause your mail to be improperly assigned and result in a delayed response.

07/08/2022 22:28 - Video Impressions wrote:

I use ALL of these products in my editing, and greatly rely upon them. So if I remove them, I have nothing to replace them with. How will I be able to properly edit, then, when these applets are a necessary part of my workflow?

Furthermore, since Build 458 works just fine, what is my incentive to remove the majority of my editing tools? There is no guarantee that these plug-ins are the problem with subsequent builds, either, so it appears that you might be guessing that external add-ons are the culprit without first defining the HandlePIChanges error.

Finally, you have yet to address the root cause--what the hell is a HandlePIChanges error anyway? Or are you trying to create an Adobe Premier convert of me? I really love Vegas Pro and would hate to switch at this point in the game!!

Will you not pursue the HandlePIChanges error? Someone has coded it into the software somewhere!! Is it proprietary to Windows? SOMEONE had to code it so someone knows what it means, and it's not me!! I am a user, not a programmer, so I am at your and the entire industry's mercy!!

So won't you please search for the root cause, which I HIGHLY doubt is my third party applets, AS AGAIN BUILD 458 WORKS JUST FINE!! SO THIS MEANS THAT WHATEVER CHANGES YOU MADE IN LATER BUILDS IS CAUSING THE ERROR!! SINCE BUILD 458 WORKS FOR ME, IT ONLY CAN BE YOUR CODING CHANGES THAT IS BRINGING ON THE ERRORS!!   

Please consider an intelligent approach to this by not blaming add-ons but rather pinning down the HandlePIChanges--what it is, what causes it and how to eliminate it.

I hope and trust that you will be willing to do so.

Rich

Richard W. Kutnick, President
427 Dunbar Ln

Highland Hts, OH 44143-3670 Home Office: 440-771-4117
Cell: 216-534-1246

 
richkvideoimpressions@gmail.com
www.videoimpressions.net
 
 
 
 
 

On 7/8/2022 3:59 PM, MAGIX Pro Support wrote:

Dear Richard,

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.

Finally, since it looks like the sfvstserver is crashing a lot on your system...remove all 3rd party audio plugins.

--
Best regards,

MAGIX Software GmbH
Neal Siddell
Supportmanager
Berliner Str. 13
01067 Dresden - Germany

http://www.magix.com
 
Geschäftsführer | Managing Directors: Denis Burger, Jan Gackenholz, Klaus Schmidt
Amtsgericht | Commercial Register: Berlin Charlottenburg, HRB 127205 B
 Please make sure to include your original correspondence when replying and leave the subject line unaltered. Changing the subject line may cause your mail to be improperly assigned and result in a delayed response.

07/08/2022 21:10 - Video Impressions wrote:With respect to any third party scripts specifically, none are run automatically on start-up nor manually run for the message to appear, and the error occurs initially when something is placed on the timeline. The only third party script that I use is one written by Ed Troxel (Excalibur author), and this is a simple script that merely puts a 1 sec black clip either on the selected or top track. However, this script has NOT been run prior to the HandlePIChanges message.

May I ask if your dev is familiar with this message, what it means, what causes it and how to eliminate it, or did the dev just state that they never have seen this error before. Is there someone in your organization that DOES know what this message even means? If not, can someone find out from a programmer friend or colleague, as this will be the ONLY way to resolve the issue!!

Besides scripts, I use Magix, Sony, Boris, Izotope, D16 Group Adudio Software, Plug Alliance, Waves, Exponential Audio, Sapphire and New Blue efx and plug-ins (audio--VST and video), but again, NONE of these are loaded nor run when the HandlePIChanges message comes on screen. Finally, be aware that since your Build 458 works just fine, IT HAS TO BE CHANGES IN CODING AFTER THAT BUILD THAT ARE CAUSING THIS MESSAGE/ERROR!

Thank you in advance for hopefully continuing to look into this and eventually resolving it, for if not I am at the end of the line with Vegas Pro (as every Build past 458 has this problem).
 

Rich

Richard W. Kutnick, President
427 Dunbar Ln

Highland Hts, OH 44143-3670 Home Office: 440-771-4117
Cell: 216-534-1246

 
richkvideoimpressions@gmail.com
www.videoimpressions.net
 
 
 
 
 

On 7/8/2022 2:44 PM, MAGIX Pro Support wrote:

Dear Richard,

Thank you for the system information. I brought this up with one of our devs and they state that we have no message like the HandlePIChanges one you're getting within our code. Are you running any kind of third party script in the VEGAS Pro 19 software?

--
Best regards,

MAGIX Software GmbH
Neal Siddell
Supportmanager
Berliner Str. 13
01067 Dresden - Germany

http://www.magix.com
 
Geschäftsführer | Managing Directors: Denis Burger, Jan Gackenholz, Klaus Schmidt
Amtsgericht | Commercial Register: Berlin Charlottenburg, HRB 127205 B
 Please make sure to include your original correspondence when replying and leave the subject line unaltered. Changing the subject line may cause your mail to be improperly assigned and result in a delayed response.

06/30/2022 23:48 - Video Impressions wrote: 

Rich

Richard W. Kutnick, President
427 Dunbar Ln

Highland Hts, OH 44143-3670 Home Office: 440-771-4117
Cell: 216-534-1246

 
richkvideoimpressions@gmail.com
www.videoimpressions.net
 
 
 
 
 

On 6/30/2022 2:11 PM, MAGIX Pro Support wrote:

Dear Richard,

Thank you for your message. 

Please provide us with your system information to help us further research your issue. The instructions below show you how to do so.

1. On your system, press the Windows Key + R on your keyboard. This opens a Run dialog.

2. Type "msinfo32" then click OK. A System Information utility will open.

3. Go to File > Export, then name the file "SI" and save it to your Desktop. Please attach that text file to this incident.

Please attach that text file to this incident. The file must be a text file or we will be unable to open it, so ensure that step 3 was followed correctly.

--
Best regards,

MAGIX Software GmbH
Neal Siddell
Supportmanager
Berliner Str. 13
01067 Dresden - Germany

http://www.magix.com
 
Geschäftsführer | Managing Directors: Denis Burger, Jan Gackenholz, Klaus Schmidt
Amtsgericht | Commercial Register: Berlin Charlottenburg, HRB 127205 B
 Please make sure to include your original correspondence when replying and leave the subject line unaltered. Changing the subject line may cause your mail to be improperly assigned and result in a delayed response.

06/29/2022 21:02 - Video Impressions wrote:After I sent the below message to you about 20 minutes ago, I started working on customizing Build 643...

Guess what? After working on customizing the toolbar at the top of the screen,  the "HandlePIChanges" requester box re-appeared!!!

So I am back at sdquare one!!

All that I can say is HELP!!!!!

Looking forward to the next step, if there is one!!??


Rich

Richard W. Kutnick, President
427 Dunbar Ln

Highland Hts, OH 44143-3670 Home Office: 440-771-4117
Cell: 216-534-1246

 
richkvideoimpressions@gmail.com
www.videoimpressions.net

-------- Forwarded Message --------

Subject:Re: [Ticket#2022062517005286] "HandlePIChanges" Requester Box, VP 19 ALL BUILDS AFTER 458

Date:Wed, 29 Jun 2022 14:39:15 -0400

From:Video Impressions <richkvideoimpressions@gmail.com>

To:MAGIX Pro Support <prosupport@magix.net>

I followed your instructions. I now am running Build 643.

I loaded a test file and played back a few sections--no problem found. I did NOT change ANY parameters in the app, FYI. When I closed the file, VP19 crashed. I ran VP19 again, and the same crash occurred (I did NOT send the crash report to you). The third time I opened VP19 and tried the same steps, I closed the file and exited VP19 without incident.

HOWEVER, the next time I opened VP19 I DID change two parameters. I loaded a previous window layout and imported a saved preferences file. Importing the saved preference file appeared to have no negative affect, but after loading a previous window layout, as soon as the action was completed when I did anything else on the timeline, the  "HandlePIChanges" requester box reappeared. Testing shows that with 5 saved window layouts (two in 2021, three in 2022), if I select either of the 2021 window layouts there is no problem BUT if I instead select any of the 2022 saved window layouts the dreaded "HandlePIChanges" requester box appears.

I cannot test every iteration possible, so this is as far as I can take it on my end.

Your advice now? It takes quite some time to reset the layout, and thus the reason there now is the ability within the app to save these types of preferences. If I start from scratch with my preferred window layout in this build, how will I know if I save it that the same thing won't occur in the future? Do you have any clue what is going on, as Build 458 works just fine!!

I hope that all of this helps, and will await your response.

Thank you in advance.

Rich

Richard W. Kutnick, President
427 Dunbar Ln

Highland Hts, OH 44143-3670 Home Office: 440-771-4117
Cell: 216-534-1246

 
richkvideoimpressions@gmail.com
www.videoimpressions.net
 
 
 
 
 

On 6/28/2022 2:56 PM, MAGIX Pro Support wrote:

Dear Richard,
 

In that case, for our first troubleshooting step, I would like you to reset your software. To reset your software, you simply need to double click the program's icon while holding down Ctrl+Shift. This will bring up a window asking if you would like to delete the cache. Check the box then click okay and your program should start.

--
Best regards,

MAGIX Software GmbH
Neal Siddell
Supportmanager
Berliner Str. 13
01067 Dresden - Germany

http://www.magix.com
 
Geschäftsführer | Managing Directors: Denis Burger, Jan Gackenholz, Klaus Schmidt
Amtsgericht | Commercial Register: Berlin Charlottenburg, HRB 127205 B
 Please make sure to include your original correspondence when replying and leave the subject line unaltered. Changing the subject line may cause your mail to be improperly assigned and result in a delayed response.

06/28/2022 16:54 - MAGIX Pro Support wrote:Dear Richard,

Thank you for your message. Since it would appear that this message is occurring when trying to use this FASST App plug-in we would suggest contacting VASST support to confirm if the said plug-in is supported on more recent VEGAS Pro 19 builds. You can find VASST's contact info here: http://vasstsoftware.com/contact/

--
Best regards,

MAGIX Software GmbH
Neal Siddell
Supportmanager
Berliner Str. 13
01067 Dresden - Germany

http://www.magix.com
 
Geschäftsführer | Managing Directors: Denis Burger, Jan Gackenholz, Klaus Schmidt
Amtsgericht | Commercial Register: Berlin Charlottenburg, HRB 127205 B
 Please make sure to include your original correspondence when replying and leave the subject line unaltered. Changing the subject line may cause your mail to be improperly assigned and result in a delayed response.

06/25/2022 23:20 - richk@videoimpressions.net wrote:

[METADATA_START]
Product version:
- Vegas Pro 19 Any Build After 458
Processor:
- AMD Ryzen 9 3900X 12-Core Processor@3.79 GHz
Operating system:
- Windows 10 Pro 64-Bit
Memory:
- 32GB
Sound Card:
- Built-In
Graphics Card:
- NVIDIA RTX 2060 SUPER
Browser:
- Chrome 102.0.0

[METADATA_END]

"HandlePIChanges" Requester Box, VP 19 ALL BUILDS AFTER 458

See Attachment...This "HandlePIChanges" pops up in EVERY Build AFTER Build 458,
which is the ONLY one of the current crop of builds that is rock steady for me. I
tried Builds 550, 636 and 643, and ALL of them are affected by this anomaly.

Since I have a business to attend to, I was forced to revert back to Build 458,
which works without incident.

Have you ANY idea what could cause this requester box to pop up? I am using Win 10
Pro 64-Bit, 32GB RAM, AMD Ryzen 9 3900X 12-Core Processor@3.79 GHz and an NVIDIA
RTX 2060 SUPER graphics card with the latest Studio drivers. Let me know if you
need any additional info about my setup.

I cannot justify any more upgrades or purchases of Magix Vegas Pro until this is
resolved, nor can I update past Build 458, as the app becomes unusable due to this
nasty pop-up that I have to continually x-out in order to work!!

I trust that you will take the time to investigate this anomaly with the hope that
a solution will become available in the near future. If not, I am stuck in time
with your product.

I thank you in advance and look forward to your response.

I believe Magix is correct in this and there is not anything THEY can do to fix the issue as it would be coming from a 3rd party plugin. However, I still need to see a screenshot showing that message and still need to know exactly what extensions you have installed.

Odds are the message is coming from an extension you have installed. For example, my "Project Inspector" custom command has this routine:

        public void HandlePIChanges(object sender, EventArgs e)
        {
            if (autoUpdate && appActive)
            {
                CheckProject(false);
            }
        }

And it is called when things happen in VEGAS. Some examples:

            myVegas.TrackStateChanged += myform.HandlePIChanges;
            myVegas.TrackEventStateChanged += myform.HandlePIChanges;
            myVegas.TrackCountChanged += myform.HandlePIChanges;
            myVegas.TrackEventCountChanged += myform.HandlePIChanges;

When the track state changes, the track event state changes, the track count changes, or the track event count changes in the above example, it will call the "HandlePIChanges" routine.

When looking at example scripts, "HandlePIChanges" is a common name used for this routine. And, sometimes, in testing, a programmer may add something like:

MessageBox.Show("In HandlePIChanges");

to see if it's getting inside that routine properly which would pop up a message which sounds similar to what you may be seeing. My thought is that perhaps you've installed an extension that accidentally has something like that left in it.

@Videoimpressions0622 I am the person who has been working with our support to try to figure out the problem you are having. Unfortunately, the message you are seeing is not coming specifically from VEGAS Pro and we have no way of knowing what of the various scripts and plugins is actually throwing this error. Your unwillingness to try uninstalling the various third party plugins to help us determine which one is actually causing the problem makes it quite difficult for us to try to understand what specifically on your system is causing this malfunction. I wish we could help you more. We simply know that you have an error that is causing this dialog, which is unknown to the VEGAS team, to appear and that you have a number of other third party scripts and application extensions hooked into your VEGAS installation.

Thank you, Edward, for being the first person to acknowledge the existence of HandlePIChanges and how it is used in programming. I will follow-through with the VP 19 error screenshot and the additional info you requested tomorrow. 2 quick questions: Do you need to know EACH INDIVIDUAL PLUG-IN on my system (there a quite a few!!), or just the group of plug-ins (e.g., New Blue Active Camera, New Blue Auto Pan, etc. vs. just listing New Blue Elements, of which these two noted effects are in that group)? Also, is there a best-practices way to troubleshoot and drill down to the culprit plug-in(s)? Much appreciated!!

It would first be most helpful to know every Extension you have installed.

As for things like NewBlue, I really doubt they would be the issue. I lean more towards an extension than an effect or transition. But for things like NewBlue, the individual packages installed would be enough - not the individual effects/transitions.

Personally I'd uninstall everything that's not stock and add them back one package at a time. If Vegas stops working correctly that's your answer. Maybe even just reinstalling them will fix the problem, too.

@RogerS, spot on. Messages going back and forth looking for a quick solution to what doesn't seem to have one, it would be the only way to to get to the bottom of this.

Thanks to all of you for your comments/suggestions/etc. (and ESPECIALLY to Edward Troxel for his step-by-step advice!)!! In order to avoid spending hours and hours attempting to troubleshoot by removing EVERY third-party module, through careful observations I noted exactly when the HandlePIChanges kicked in and then did the following:

1) Uninstalled SeMW Extensions from Build 458. I no longer need this since the VP 19 render box now works just fine (had a problem awhile back with it).

2) I placed an MP4 on the timeline, saved it, closed VP19 and reopened this new .VEG file in VP 19.

3) Updated in app from VP 19 Build 458 to Build 643.

4) Observed that there are no extensions listed in Edit-Extensions drop down menu; view-extensions drop down menu lists Excalibur, Project Inspector and 9 VASST extensions—NO ERRORS AT THIS POINT IN TIME!

5) Imported preferences that were saved 06/2022 in Build 458; HandlePIChanges ERROR pops up in a requester box in the middle of the screen!

6) Restored PC via System Restore so that I was back to VP 19 Build 458

7) Once again Re-updated in app from Build 458 to Build 643

8) This time I manually set up my preferences for VP 19 Build 643 (using an existing VP 18 screen as a visual guide)

9)  As a test, I exported my VP 19 Build 643 preferences and saved the current screen's windows layout

10) I imported the newly-saved preferences and clicked on the current windows layout. I realize that I was not changing a thing, but tried this just in case it might cause the HandlePIChanges to kick in.

11) I closed the current file and then closed VP 19 Build 643. Reopened the same file with no errors whatsoever!!

12) I then loaded a project from an external HD that I produced last month, and no anomalies were observed in this file, either!!

13) Observationally, I can conclude that there must be something in the first saved preferences file that I loaded right after updating from Build 458 to Build 643 which caused HandlPIChange to pop up, but this merely is an unscientific observation at a minimum.

14) All of that being said and done, YOUR thoughts on this process and if you have a clue what caused HandlPIChanges? I believe that I resolved the problem, but...!!??

Could you give us more information on #5?

1. Exactly what did you do and exactly when did the error message pop up? Perhaps a short video showing what you are doing through when the error message pops up?

2. Can we get a screenshot of that error message?

3. The actual file imported in #5?

Re: #5--I selected Options-Import Preferences. From there I clicked on a file to load that contained my preferences which were saved last month under Build 458. This file is named "VEGASPreferences V19 as of 06-2022.vegprefs". Once this file loaded, HandlePIChanges popped up in the requester box. Screenshot of my VP 19 screen showing this requester box is attached.

Ok, I suspect this *may* be coming from "Project Inspector". Exit VEGAS, Go to:

[My Documents]\Vegas Application Extensions

Rename "ProjectInspectorVP.dll" to something like "ProjectInspectorVP.dllSAVE"

Then see if you get the same result in step #5.

My Vegas Pro 13 version did have a message box that said that at one time. I'm not seeing one in VEGAS Pro 14 and newer but, who knows, maybe one slipped through.

I DID NOT rename the Project Inspector DLL file on a hunch. INSTEAD, I DID import "VEGASPreferences V19 as of 06-2022.vegprefs" and no error occurred. I closed the open .VEG file and the app, THEN AGAIN loaded VP 19 Build 643 and the same .veg file, and AGAIN imported "VEGASPreferences V19 as of 06-2022.vegprefs". I am happy to report that not only did HandlePIChanges not pop up, but there were no errors of ANY other kind! So your educated guess at this point, Edward? I even opened Project Inspector to see if it would create the error, but it had absolutely no effect on anything!!

Thank you for your message. Since it would appear that this message is occurring when trying to use this FASST App plug-in we would suggest contacting VASST support to confirm if the said plug-in is supported on more recent VEGAS Pro 19 builds. You can find VASST's contact info here: http://vasstsoftware.com/contact/
Best regards,
MAGIX Software GmbH
Neal Siddell
Supportmanager
Berliner Str. 13
01067 Dresden - Germany

It appears that FASST APPS as it appears in your screenshot is not being actively developed, at least not in the last 36 months, and that it is not specifically certified by its developer for use with Vegas Pro 19.

This fact alone validates the guidance you received, whether or not you choose to pursue it with your peer users on this forum.

You can take comfort in knowing that this regularly happens when Vegas updates hit the streets; as an example, the venerable Happy Otter Scripts broke in recent updates, and its developer, who is a longtime friend of the team, neither received pre-release versions for testing, nor did Vegas test their builds for compatibility with his extensions and scripts before committing them.

Compatibility with Vegas updates is always the responsibility of third party developers, and almost always comes after the fact, the exception being officially partnered plugins and utilities.

Who knows what fixed it as we don't know what was in the preferences that were saved, but as the error said PI the "Project Inspector" guess seems reasonable.

Did you really save time with these strings of emails, installs and reinstalls vs removing and reinstalling plugins and manually restoring preferences? If you have the source files it should go quickly and preferences for plugins should remain between reinstalls.

Seems like guesswork to do it in this self-admittedly "unscientific" way, but I hope it is resolved.

(also VASST has plugins that are certified to VP 18 or 19 depending on which one: http://vasstsoftware.com/download/current/ and all FASST apps are certified to VP 19)

Thanks you for your comments, Neal and Roger. May I respond?

Here are the hard facts:

1) Regardless of what caused the problem, it appears that the steps I took remediated it and HandlePIChanges requester boxes no longer appear.

2) It appears, Neal, that Roger has information noting that VASST IS certified for VP 19. In addition, the extensions seem to work just fine on my system!!

3) Roger, since Edward Troxel has not chimed back in as of late, we cannot be so sure that Project Inspector caused the problem. Not only have I used Edward's Excalibur and Project Inspector extensions (plug-ins?) going back around 10 VP versions (starting with VP 8 or 9) without any lingering problems (I recall once or twice he had to tweak something over the years), but I did NOT touch Project Inspector during all of these other changes--so it appears PI has nothing to do with the problem (unless I am missing some key fact or point, which may be possible).

3) Finally, Roger, YES, my methodology was streamlined and specific, and probably took no more that an hour or two to complete the whole process, including posts herein. My uninstalls/installs went quickly, as well, as I used Windows System Restore when I ran into a problem to get me back to Build 458 quickly. Furthermore, I didn't want to rely on the assumption that preferences would remain on cold installs. I probably have way too many extensions and plug-ins installed, and it would have taken a full workday to start again from scratch.

Bottom Line: Everything appears to work as advertised. Fact: the HandlePIChanges requester box ONLY appeared right after I imported preferences using Build 643 saved a month earlier in Build 458. So until proven otherwise, my initial contention remains that it is something in VP 19 (after Build 458) that caused it, as this saved preferences capability is a function of VP 19. If anyone can definitively point to another culprit, I would be quite interested in learning about it.

I do not know if ANYONE else ever will run in to this problem, but if they do I have shown how to correct it (at least in my case).

Thank you again to all that have participated and have offered their comments in helping to find a solution.

Yup, reproed and my “remedies”:

1 - I’ve removed all of VASST sw. No good.

2 - I’ve imported VP19 Prefs in VP20. No good.

3 - I’m now doing a system restore from five days prior to today’s error. Waiting for Sys Res to finish….

WARNING: If this isn’t my system, then don’t touch Project Inspector, for me it throws up these irritating handling errors. It’s a menace.

Update: System Restore got me back working without those “HandlePIChanges” Errors.

@Grazie 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

This version has a couple changes related to quantize to frames and also removes the test message that could pop up a "HandlePIChanges" message.

@jetdv - THis DLL?

ProjectInspectorVP.dll

@jetdv - You TOTAL Star! Thank you 🙏. All back to working as it should.

@jetdv - THis DLL?

ProjectInspectorVP.dll

Yes. The only one in that file!

Grazie, did YOU also suffer from the dreaded HandlePIChanges pop-up? Did you read (above) how I resolved it? To be safe, I also replaced the DLL per Edward. Everything still appears to work just fine. Misery loves company! At least I'm not the only one in the world who was afflicted!!