[Rich Kutnick]

To bring up this subject again, apparently Vegas Pro 23 does NOT use “eDefEnvVideoASRType” nor “eDefEnvAudioASRType” in it’s “Preferences>Internal ” settings. At least I can’t find it! So any ideas how to set new default crossfade settings types? I know that Edward Troxel posted a short video suggeting the use of a script, but is there an easier way to do this similar to that which we were able to accomplish in the internal settings in the past?

[Rich Kutnick]

My needs are for “Speech-to-Text”. However, I just read that for the most part the Microsoft Azure outage problem was rectified within a day or so of its first occurrence and that Microsoft has halted any changes to that platform that would create additional/recurring problems. So is Magix STILL affected by this, causing terrible problems accessing/using Vegas Hub, or do they have other issues causing the Vegas Hub access situation??!! I put in a trouble ticket the other day and Magix support replied that they are aware of the problem and will deal with it in a future software update–but WHEN??!!

[Rich Kutnick]

I found out the answer in an email reply by Magix Support just a few minutes ago:

““Thank you for your message.

​This is a known issue which will be resolved in a future application update. Thank you for reporting this issue.”

Furthermore, the Forum on https://www.vegascreativesoftware.info/ has posts that drill down to the exact problem (I believe). It is noted that (Magix) Hub Services are currently unreliable. They are investigating whether this is related to the outages on Microsoft’s side or whether Magix’s backend is experiencing problems.

vegascreativesoftware.info

VEGAS Community | vegascreativesoftware.info

Discuss the most important challenges and trends in video editing with other VEGAS users within the VEGAS Community.

[Rich Kutnick]

I purchased the update! Now working in VP 21 and looking forward to VP 22!! The AI voice-to-text editing is really cool! Still having ocassional hiccups with “An error occurred during while processing the undo buffer. You should save your work immediately using a new project filename and restart Vegas Pro. The reason for the error could not be determined”. I believe this is caused by New Blue Titler Pro (currently using V 7). Anyone else experience this in any version of VP?

[Rich Kutnick]

Thanks SO MUCH, Hector, not only for the quick reply but also providing the answer for which I was hoping!!!

[Rich Kutnick]

A REAL shame about the demise of Pluraleyes, although it does continue to work great in VP 18! Are you aware of any other such synchronization apps out there that compare??

Unfortunately, Vegas Pro IS NOT backwards compatible–so what I saved in VP 19 had to be cut and pasted into VP 18. I just have to be careful NOT to open VP 19 again!!

I’m NOT going to abandon ship, looking instead to upgrade to the latest VP if and when it becomes available this year. In my use of VP 19, though, it appeared that it was doomed from the start–always had a small-to-medium issue with it one way or another, which gradually developed into LARGE problems, but what I am experiencing now does not allow me to work at all in VP 19. So thank goodness for my VP 18!!

[Rich Kutnick]

Thanks for the response, Hector. Before reading the Reddit blog to which you refer, I coincidentally did try importing my audio tracks directly from the VP 19 Pro timeline into Sound Forge Pro 14. I then was able to use VEA along with any other VST 3 plug-ins or any other Sound Forge tools to sweeten my audio and seemlessly import it back onto the VP 19 Pro timeline. BTW, VEA works very well, using AI to automatically sweeten the audio to the limits of its capabilities. It does not work well on ALL audio clips, but the ones it does help show a marked improvement.

[Rich Kutnick]

FINALLY, AN APPARENT RESOLUTION!!! WE HAVE BEEN BARKING UP THE WRONG TREE AND HAVE LED OURSELVES ON A WILD GOOSE CHASE!!!

For some reason, the New Blue Color Fixer Pro plugin has caused all of the anomalies that I reported experiencing when used in ANY version of Magix Vegas Pro in which I tried it (VP 18, VP 19 and VP 20). Having stumbled upon this as a possible source of the problem, I substituted a similar Boris Effects Plugin in the place of Color Fixer Pro and have not experienced any problems whatsoever! Eliminating Color Fixer Pro apparently has resolved the issue!

I have regained FULL use of my graphics card and set the RAM Preview at 50% of my installed RAM. No problems editing or rendering (at full speed) during the past half dozen or so editing sessions!! Knock on wood (LOL)!

Thanks again to everyone who chimed in to try to help, and I’m sorry that you all wracked your brains out. So the moral of the story is ALSO to check out if plugins may be the culprit when such anomalies arise BEFORE jumping through all of the hoops that I had to go through! What an educational and learning experience, though!!

Thanks again!!!!

[Rich Kutnick]

I have made no changes since my last successful editing session a few months ago. So before I do a full reset it was suggested that I manually delete all of the cached files, but I do not know where they reside for VP 18 and VP 19. Does anyone here know where I can find the cached files for both of these versions?

[Rich Kutnick]

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>