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?)
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
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.
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.
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.
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.
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.
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
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.
''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.
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.