Hello. Vegas works very well when it can draw Files from a SSD. Chrashes not so often. A fast HDD is also fine, but Chrashes Happen much more often when you work fast and want to pull data with a slow disk. Maybe this Information can help sometimes
after update when i turn on vegas and have serial activate window. but when i click on activate button a have error window "an online connection could not be established...."
I have internet all the time...i turn off fire wire, i open vegas as administrator...a reinstalled Vegas and still have the same problem....if this not change i want my money back from magix....
I have exactly the same problem. After upgrading to version 550. Windows 11 operating system. The VAGAS recording module does not seem to connect to the internet. Disabling the firewall does not change anything.
Finally got the new build to download via the direct link. After that the updates for Effects and Image downloaded and installed correctly. The Speech to Text works really well. I am going through all of my YouTube videos and turning the audio track into transcripts. This works better than any other method I have tried and best of all, it is included in the price of the program. A couple of things though, would it be possible to have the Speech to Text window remember what language you last used. The auto-detect works fine but it seems a little faster if I tell it what language the recording is in. Also, can it also remember your last size setting and, if you are saving the file as a .txt or other type, the last save location?
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?
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 am sorry, but I cannot offer a screenshot due to the fact that I no longer have the problem using Build 458. Trust me, the error is no more than a rectangular requestor box that pops up in the mid center of the screen, black lettering on a white background enclosed in a black rectangle and the text is HandlePIChanges (caps and small letter-specific). I had to click "OK" or X it out numerous times before it would vanish. The box came back when I either pressed a transport button, imported something to the timeline or clicked anywhere in the timeline. Very strange...but I am very grateful that rolling back got me back in business!! In any event, I would think that any Windows programmer (or other computer programmer) who reads this would know what the term means. It appears to be a command or call from a specific computer language, don't you think?
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.
I've never heard of it, the VEGAS dev team has never heard of it, and doing a google search of it turns up nothing, so I'm stumped as to what it could be... very likely from something outside of VEGAS, interfering with VEGAS operations somehow... as if it was a VEGAS error, the team would know what it is, they programmed those error messages in themselves.