Comments

diverG wrote on 10/24/2016, 7:33 AM

Just clean installed W10 Pro (1607).  Have my origonal VP14 install suite but reluctanct to reinstall.

origonal install was OK but NBT screwed earlier working VP12.

How does one obtain version 178?  There seems to be nothing on Magix site other than download a trial, which hopefully would accept my licence

Sys 1 Gig Z370-HD3, i7 8086K @ 5.0 Ghz 16gb ram, 250gb SSD, 2x2Tb hd,  GTX 1060 6Gb Vegas 14 & 16 plus Edius 8WG Win 10 (1809) BMIP4k video out. (PS 650W)

Sys 2 Gig Z170-HD3, i7 6700K @ 3.8Ghz 16gb ram, 250gb SSD, 2x2Tb, hdd GTX 750ti,  Vegas 14 & 16 plus Edius 8WG Win 10 (1809) BMIP4k video out. (PS 650W)

Sys 3 Laptop 'Clevo' i7 6700K @ 3.0ghz, 16gb ram, 250gb SSd + 2Tb hdd,   nvidia 940 M graphics. VP14 & 15 via humble bundle. Plus Edius 8WG

 

set wrote on 10/24/2016, 8:01 AM

Go to your MAGIX.com account. First log in, then click MyProduct, and re-download the installer for the software on that page.

https://www.magix.com/us/support/my-service-center/

paul-marshall wrote on 10/24/2016, 9:40 AM

No need to download the installer again if you have it already, it fetches the latest version.

Still getting this error in 178 on saving the project. However it only seems to happen after making a change in NewBlue Tiler, but the changes are saved and the title does work.

Warning: An error occurred while saving one or more files. An exception has occurred.

C:\Users\Paul\AppData\Local\Temp\scr0.cs(3) : The type or namespace name 'Sony' could not be found (are you missing a using directive or an assembly reference?)
C:\Users\Paul\AppData\Local\Temp\scr0.cs(8) : The type or namespace name 'Vegas' could not be found (are you missing a using directive or an assembly reference?)
C:\Users\Paul\AppData\Local\Temp\scr0.cs(20) : The type or namespace name 'Vegas' could not be found (are you missing a using directive or an assembly reference?)
C:\Users\Paul\AppData\Local\Temp\scr0.cs(3) : The type or namespace name 'Sony' could not be found (are you missing a using directive or an assembly reference?)
C:\Users\Paul\AppData\Local\Temp\scr0.cs(8) : The type or namespace name 'Vegas' could not be found (are you missing a using directive or an assembly reference?)
C:\Users\Paul\AppData\Local\Temp\scr0.cs(20) : The type or namespace name 'Vegas' could not be found (are you missing a using directive or an assembly reference?)

Quitter wrote on 10/24/2016, 10:42 AM

The script error is that what they are working on.
On the contrary to MAGIX you get from NewBlue info that they work on it, and not only the demand for respect and patience

Last changed by Quitter on 10/24/2016, 10:48 AM, changed a total of 1 times.

Camcorder: Sony CX 520 VE
Hardware:   Acer NG-A717-72G-71YD, Win 10 Home 1903, i7-8750 H, 16GB, GTX 1060 6GB, 250GB SSD, 1TB HDD
NLE:  Sony Vegas Pro 13.0 Build 453
           Vegas Pro 14.0 Build 270

Nick Hope wrote on 10/24/2016, 12:13 PM

The VEGAS Pro 14.0 build 178 update contains only 2 fixes. One is for the memory issues that were mainly discussed in this post. The other is for keyboard shortcuts to scripts being removed on exit.

This release still exhibits the bug whereby the resample mode is reset to "Smart resample" in new projects, and the problem with reading some long HDV files.

The release notes have not been updated between builds 161 and 178.

I understand an announcement about a further update will be made by MAGIX in the near future.

glovercover wrote on 10/24/2016, 12:24 PM

Where i can see the changelog for V14 build 178?

Kit-As-Was wrote on 10/24/2016, 5:40 PM

When did this build come out? What`s the point of having an important posts section if announcements of new builds don't show up in it? The old Sony system of linking to the downloads page with an annoucement was much more user friendly. I've yet to try V14 because of the issues with breaking scripting. But I do have a serious problem with V13 bluescreening when going online.

gary-rebholz wrote on 10/25/2016, 2:36 PM

Hello everyone. Yes, the first update is available, however we discovered a problem with the update mechanism so we've held off officially announcing it. While we will have a fix for that problem shortly, you can install the new update now. In most cases, the update will work without problem. If you do run into this bug (or if you just want to make sure you avoid it), uninstall your previous build of VEGAS Pro first, and then install the update.

To download the update, log onto your MAGIX.com account. Then, click MyProduct and click the Installation program link. After the installation is complete, you will have build 178.

This build 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 continue 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 coming weeks.

Thank you for all of your feedback on VEGAS Pro 14--it was this community that alerted us to the problem this update fixes.

fr0sty wrote on 10/25/2016, 3:01 PM

Thank you for listening. I was getting concerned about that memory issue as it was holding up progress on some projects, glad you addressed it quickly. Can't wait to see what you have in store in the coming weeks. 

Kit-As-Was wrote on 10/25/2016, 4:25 PM

I had to try three times before the system would offere me a download and then it was only around 4 mb in size - is that the right file? Thanks

Quitter wrote on 10/25/2016, 4:37 PM

Yes, this is the downloader for VP14
Klick and run it

Camcorder: Sony CX 520 VE
Hardware:   Acer NG-A717-72G-71YD, Win 10 Home 1903, i7-8750 H, 16GB, GTX 1060 6GB, 250GB SSD, 1TB HDD
NLE:  Sony Vegas Pro 13.0 Build 453
           Vegas Pro 14.0 Build 270

Kit-As-Was wrote on 10/25/2016, 4:50 PM

Why so many hoops? Why not give us the file directly as Sony used to? Will the downloader give me a file or try to force an install directly? I really dislike installing software while being online. Cheers.

Nick Hope wrote on 10/25/2016, 9:05 PM

Will the downloader give me a file or try to force an install directly?

After the installation I have been left with a 416MB file at D:\Documents\MAGIX Downloads\Installationsmanager\VEGAS_Pro_14.0.0.178_Trial_14_0_0_178.exe  I believe that file could be run independently of the initial small installer.

Quitter wrote on 10/25/2016, 10:02 PM

Yes, that's how it works:
Run the downloader until 100% of VP 14,
abort the downloader and install VP14 from D:\Documents\MAGIX Downloads\Installationsmanager

Camcorder: Sony CX 520 VE
Hardware:   Acer NG-A717-72G-71YD, Win 10 Home 1903, i7-8750 H, 16GB, GTX 1060 6GB, 250GB SSD, 1TB HDD
NLE:  Sony Vegas Pro 13.0 Build 453
           Vegas Pro 14.0 Build 270

Wolfgang S. wrote on 10/26/2016, 5:28 AM

I always save the downloaded files from the directory Installationsmanager to an independend directory, since that allows to run the installation again and again, without downloading the files again and again. Works fine.

Quitter wrote on 10/26/2016, 5:41 AM

Not really necessary, because each installation file has an individual name, and old versions are not automatically deleted

Camcorder: Sony CX 520 VE
Hardware:   Acer NG-A717-72G-71YD, Win 10 Home 1903, i7-8750 H, 16GB, GTX 1060 6GB, 250GB SSD, 1TB HDD
NLE:  Sony Vegas Pro 13.0 Build 453
           Vegas Pro 14.0 Build 270

Wolfgang S. wrote on 10/26/2016, 6:08 AM

And since I know that I save the files into other directorys with name of the major version and date. And delete the download directory manually.

Seems to be some work but is not work at all, since that is how I manage files since years, for different machines and different software realeases.

Aiki wrote on 10/27/2016, 3:04 PM

''This build 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 continue 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 coming weeks.''

I opened an AVCHD file 15 G (1h 18m 43 sec Sony HVR-Z7U) with 12 and 13 V PR in seconds but with version 14 is much longer, I 2minutes 20 seconds after the messages (not responding) and I wait, I wait, (I give it a chance, as they say) to 2m 20 s., Ta Lam.

Ordinateur I7, 12G de Ram

Quitter wrote on 10/27/2016, 3:28 PM

Yes, same as i noticed, the loading time in VP14 is 3 to 5 times longer
It takes, but finally it is loaded

Last changed by Quitter on 10/27/2016, 3:29 PM, changed a total of 1 times.

Camcorder: Sony CX 520 VE
Hardware:   Acer NG-A717-72G-71YD, Win 10 Home 1903, i7-8750 H, 16GB, GTX 1060 6GB, 250GB SSD, 1TB HDD
NLE:  Sony Vegas Pro 13.0 Build 453
           Vegas Pro 14.0 Build 270

gary-rebholz wrote on 10/27/2016, 3:54 PM

Yes, same as i noticed, the loading time in VP14 is 3 to 5 times longer
It takes, but finally it is loaded

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.

Quitter wrote on 10/27/2016, 4:09 PM

Thanx,
i think this is what the crowd is needing.
to know that you hear us and that someone is working on the problems.

SphinxRa40 wrote on 10/28/2016, 3:44 AM

Thanx,
i think this is what the crowd is needing.
to know that you hear us and that someone is working on the problems.

Agreed

Hulk wrote on 10/28/2016, 9:59 AM

This update improved stability a lot for me with large projects.  Thank you.

Aiki wrote on 10/28/2016, 11:31 AM

We look forward to this new version. Do not let go !

Nous attendons avec impatience cette nouvelle mouture.

Lâché pas !