VEGAS Pro 14 Update 2 (build 189)

MathiasH wrote on 10/31/2016, 12:01 PM

Hello everyone,

The problem with the update mechanism of our first update is resolved.

This update (build 189) replaces the originally released build 161 and the first update build 178. In addition to the fixes included in build 178, this build fixes the updating bug that prevented some from updating to 178.

The build 178 is essentially a hotfix for a memory leak that could result in a crash when using multiple AVCHD and HDV files in a project. This is the only noteworthy fix contained in this update. We are continuing to work on a more robust update that addresses some long-standing issues as well as improvements to new features. That update will be available in the upcoming weeks.


We are sorry for the inconvenience the updating bug has caused and thank every one for their patience.

Download build 189 now with the help of the following link: http://rdir.magix.net/?page=3WYQO6PGVP3Q

Best regards,
Mathias

Comments

SphinxRa40 wrote on 10/31/2016, 12:58 PM

ūüĎć I am excited about the robust update in the upcoming¬†weeks, maybe..just maybe i will go for VP14 after all thenūüėĆ

Keep up the good workūüĎä

Tiber wrote on 10/31/2016, 1:35 PM

It is still very slow. Much slower and more cumbersome than the previous Sony 13 version. I really do not understand why you had to spoil instead of further development.

gary-rebholz wrote on 10/31/2016, 2:22 PM

It is still very slow. Much slower and more cumbersome than the previous Sony 13 version. I really do not understand why you had to spoil instead of further development.

The slowness issue has been discussed here: https://www.vegascreativesoftware.info/us/forum/vegas-14-build-178-whats-new--104227/#ca644357. 

In that post I said:

We are also aware of this problem. It is part of the same issue we released the new update to fix, but the aspect we fixed was so urgent that we didn't want to make you wait until this aspect was also fixed. We plan to have a fix for this additional issue in place in Update Two which we're planning to release in the coming weeks. We appreciate your patience on the long load time, and hope that at least you can now move ahead with your projects in the meantime.

james-ollick wrote on 10/31/2016, 6:19 PM

Thank's for the quick update!

Home built PC - Corsair case, ASUS ROG Maximus XI Code motherboard, i9 9900k, 32 gigs Corsair Vengeance RGB 32GB DDR4 DRAM 3200MHz,  Sapphire Nitro+ Radeon RX 580 graphics card, Corsair 1000 watt power supply.

Cielspacing wrote on 10/31/2016, 10:54 PM

And specially thanks for the transparency in disclosing what happens and what the developers' team is up too. Put these together with your alignment with our requests as customers and we have the main bases of an excellent future together. Wellcome indeed.

Nick Hope wrote on 11/1/2016, 12:56 AM

Thank you for this release, which installed and activated smoothly on my machine over the top of build 178.

I would very much like to see the release notes updated, even for these minor releases. This will help support and troubleshooting in the future by allowing us to see exactly what was changed or fixed with each release. I would also like to see release notes/changelog published on your website, along with a repository for old versions in case someone needs to roll back for an unforeseen reason.

Kit-As-Was wrote on 11/1/2016, 3:45 AM

Thanks, I think I'll have a go at installing this version.

vkmast wrote on 11/1/2016, 11:44 AM

I would very much like to see the release notes updated, even for these minor releases. This will help support and troubleshooting in the future by allowing us to see exactly what was changed or fixed with each release. I would also like to see release notes/changelog published on your website, along with a repository for old versions in case someone needs to roll back for an unforeseen reason.

+1. Sorely needed essential info.

teaktart wrote on 11/1/2016, 11:45 AM

I just did a clean install of build 189 and zero improvement.  Tried to open a V12 .veg project and computer totally froze up...along with no 'cancel' button or 'opening project' % along the bottom left corner.   Only way to kill it is via Task Mgr.  Next, I tried to open a previous project via "File" menu....totally froze up and could not 'cancel' .
Tried dragging HDV files and it got to 13% and froze up hard once again.
I'm so disappointed I can not use this V14 at all ......

Wolfgang S. wrote on 11/1/2016, 12:38 PM

Tried dragging HDV files and it got to 13% and froze up hard once again.

I have here an older HDV project with 7 hours HDV files. I have tried to open this project in the new build and it lasts about something near to 30-40 minutes. It opens but it takes very long. I understand that you may think that Vegas has crashed - but check it during this time in the task manager. You will see that the memory allocation to the application is going up very slow, but it goes up.

I have sent this project to the development team yesterday on an SSD since it has 90GB and cannot be transfered in an easy way.

Gary wrote that they are aware of that problem too.

We are also aware of this problem. It is part of the same issue we released the new update to fix, but the aspect we fixed was so urgent that we didn't want to make you wait until this aspect was also fixed.

JJKizak wrote on 11/2/2016, 5:00 PM

I just installed build 189 and it worked just fine on the overwrite.

JJK

wslagter1 wrote on 11/4/2016, 3:33 AM

The NewBlue express plugin is very limited with 25 templates only instead of the 60 as per Vegas Pro 14  ad. 

NewBlue said sometime ago that they would update so we could use the complete ver.4 but no date was given. 

george-sealy wrote on 11/4/2016, 9:43 PM

VP14-189 quits working on the render just as the previous version did.  This program is worthless if it cannot render. I never, ever had this problem with VP-13.  I am fed up.  I will call customer service next week and talk to them about getting my money back.  

VormVorna wrote on 11/5/2016, 3:40 PM

Hello

I'am Pierre from France.

With VP 12, i was automatically by the software. But, with VP14 this  functionality doesn't exist or i don't find it.

By chance i find this forum. How can I be automatically informed of VP14' updates.

Thanks

 

andyd wrote on 11/7/2016, 2:13 PM

I am not sure how to upgrade to the latest-  I bought Version 13 in may about a week before the annoucenment that Magix was taking over Sony's software suite. I had heard there was a free upgrade for those users who bought it late as I did for Vegas 14. How can I find out if I am eligible for the free update?

 

set wrote on 11/7/2016, 4:13 PM

 I had heard there was a free upgrade for those users who bought it late as I did for Vegas 14. How can I find out if I am eligible for the free update?

The promo was last July and no longer available, and the alternate offer is upgrade price as posted here:

https://www.vegascreativesoftware.info/us/forum/upgrade-offer-until-18-11-2016-nov-18th-2016--103831/

andyd wrote on 11/8/2016, 8:50 PM

Ok well since that is the case maybe I will wait another 5 years to update the software. No point in upgrading for useless features.

 

andyd wrote on 11/8/2016, 8:55 PM

I don't really need any of the new features and since there is no new sound forge included, then, what is the point of upgrading the entire suite?  

 

VidMus wrote on 11/15/2016, 3:02 AM

Out of curiousity, I clicked on the link for the latest update and got the following warning page:

 

The site ahead contains harmful programs

Attackers on d104.magix.net might attempt to trick you into installing programs that

harm your browsing experience (for example, by changing your homepage or showing

extra ads on sites you visit).

--------------------------

Now this might be a false warning or whatever, but I think it should be addressed. Maybe there is something about Magix that Google Chrome does not like? I do not know but I will not download from any site when I see something like this.

My curiosity was to read the release notes for all of the updates. I can afford the upgrade in December but I will stay away if this is going to be the case.

I have a screen capture if you want to see it.

 

Radomir wrote on 11/17/2016, 5:17 AM

I'm getting this same warning.

m2016 wrote on 11/17/2016, 12:27 PM

We already opened an investigation ticket there to remove this warning - the file is fine. Local installed antivirus software will confirm that.