VEGAS Pro 14.0 (Build 161) Released

NickHope wrote on 9/20/2016, 2:36 AM

http://www.vegascreativesoftware.com/us/vegas-pro/

Abbreviated Release Notes:

New features in version 14.0

Added Smart Zoom, Smart Scale, and Smart adaptive deinterlacing to allow you to upscale clips for Ultra HD delivery (requires a supported NVIDIA, AMD/ATI, or Intel GPU).
Added a Vignette video effect.
Added support for working with high-frame-rate (HFR) clips.
Added hover scrub to the Trimmer for fast scrubbing.
Updated support for current BlackMagic Design hardware:
- DeckLink 4K Extreme 12G, 4K Pro, 4K Extreme, Studio 4K, SDI 4K, HD Extreme, Extreme 3D, Mini Monitor, and Mini Recorder.
- Intensity Shuttle, Pro 4K, and Pro.
- UltraStudio 4K Extreme, 4K, Pro, SDI, Express, Mini Monitor, and Mini Recorder.
Improved support for clips from RED ONE, EPIC, SCARLET, and WEAPON cameras.
- Added Post lift, Post gamma, Post gain, and Dragon enhanced blacks controls to the R3D Decode Properties dialog.
- Fixed an issue that caused certain clips to fail to load on upgraded RED WEAPON cameras with older firmware.
- Fixed a crash that could occur when loading certain old RED ONE clips.
- Fixed a color cast that could occur in clips shot with RED Motion Mount on the latest camera firmware.
Updated support for current AJA hardware.
Added a Resample mode drop-down list to the Video tab in the Project Properties dialog. You can use this control to set the default resample mode for your project video. To override the project resample mode, you can use the Force resample and Disable resample event switches.
Improved playback and editing performance when using a Dynamic RAM Preview cache size greater than 200 MB.
Improved gamma calculations for still-image sequence renders for 32-bit floating point projects. Now levels for 32-bit floating point (video levels) and 32-bit floating point (full range) with nonlinear gamma are more consistent with 8-bit levels.
Added a Group Video and Audio Events script (Tools > Scripting) to allow you to easily group audio and video events from an imported EDL.
Increased the top-end of the range of event Velocity envelopes to 1,000% to increase the maximum possible overall velocity of video on the timeline to 40 times normal speed (in conjunction with the Playback rate event property).
New artwork and icons for buttons and other interface elements give the application an updated, more modern look and feel.
Support for reading and writing HEVC/H265 files.
Native support for reading ProRes 422 files without the need for QuickTime.

Bug Fixes

Fixed a bug that caused a disabled Beziér mask to become enabled when the mask is moved
Fixed a bug that caused some Video Capture Help links to be non functional
Fixed a bug that caused the Sharpen FX to exhibit different results when set to 0.000 depending upon whether the GPU was engaged or not
Fixed a but that caused the arrow keys and J/K/L shortcuts to lose the ability to move the play head after undoing a framerate change in Project Properties
Fixed a bug that prevented users from choosing their language during the installation process
Fixed a bug that prevented video files from some cell phone devices from being recognized
Fixed a bug in the scripting API that could cause an OverflowException in scripting extensions
Fixed a bug that could cause VEGAS Pro to hang if the Escape key is pressed to dismiss the Render As dialog box
Improved support for HiDPI displays. WIndows 8.1 or Windows 10 is recommended when using a HiDPI display.
Fixed a bug that could cause Vegas to crash when clicking in the header of the Vegas Explorer in Details view.
Fixed a bug that could cause Vegas to crash when renaming an in-use file in the Vegas Explorer.
Fixed a bug that could cause Vegas to crash during startup when running with multiple GPUs.
Fixed a bug that could cause Vegas to crash during startup when running with many network adapters.
Fixed a bug that could cause Vegas to become unresponsive when loading projects that contained unavailable plug-ins.
Fixed a bug that could cause rendered files to be truncated when rendering from FLAC source audio.
Fixed a bug that could cause inconsistent audio and video stream lengths when working with some MP4 clips.
Fixed an issue that could cause one frame to appear black when using Side by side (full) stereoscopic 3D mode with GPU acceleration enabled.
Fixed an issue that could cause incorrect output when using Track Motion to offset horizontally only with GPU acceleration enabled.
Fixed an issue that could cause incorrect output when using Track Motion when the 2D Glow check box was selected with GPU acceleration enabled.
Fixed an issue that could cause incorrect display when using FX Bypass mode in a split-screen configuration with GPU acceleration enabled.
Fixed an error that incorrectly listed the Studio RGB range in the Broadcast Colors plug-in as 16-135. The correct range -- 16-235 -- is now displayed.
Fixed drawing and scaling issues that could occur when running Vegas Pro with a HiDPI display on Windows 8/8.1 or Windows 10.
Fixed drawing issues that could occur when scaling the keyframe timeline for OpenFX plug-ins.
Improved performance when using 64-bit VST plug-ins.
Fixed a bug that could result in inconsistent behavior after pasting video event attributes.
Fixed a bug that could prevent Vegas Pro from correctly reading the Field Order value in some MOV files.
Fixed a bug that prevented the Titles & Text plug-in from working correctly.
Fixed a bug that could cause the application to become unresponsive in projects that contain a large number of bins in the Project Media window.
Fixed a bug that prevented smart bins from preserving their Condition setting.
Pressing A in the Trimmer now adds the current selection to the timeline as an event. If there is no selection in the Trimmer, the entire clip is used.

Back to post

Comments

Quitter wrote on 9/27/2016, 12:25 AM

something else?
reboot your PC an try again

megabit wrote on 9/27/2016, 12:34 AM

Just did that, and this time a bunch of errors about not being able to extract registry keys....

Quitter wrote on 9/27/2016, 12:42 AM

Antivirussoftware or similar running?

R0cky wrote on 9/27/2016, 10:24 AM

Where are the download files stored? All you get from magix is a downloader/installer. I haven't been able to find where it puts the install files.

Thanks jkerry, but that isn't correct. A bunch of log files from the install, but not the install files.

Quitter wrote on 9/27/2016, 10:55 AM

Again, the install files are stored in Documents\ Magix Downloads

James Moore wrote on 9/27/2016, 2:04 PM

Ok, I went a bit the bullet and upgraded. So far things have gone pretty well as I've gotten VP14 to load the Sony Izotope VST's which was important to me.

The one item I haven't been able to get working is PluralEyes which works as an extension. Does anyone have a suggestion to how I might get it working in VP14?

I tried to load a Pro Res 4444 clip but no joy.

Grazie wrote on 9/27/2016, 2:12 PM

Plural? Nothing yet.

MemoriesFX wrote on 9/27/2016, 2:46 PM

Ok, I went a bit the bullet and upgraded. So far things have gone pretty well as I've gotten VP14 to load the Sony Izotope VST's which was important to me.

The one item I haven't been able to get working is PluralEyes which works as an extension. Does anyone have a suggestion to how I might get it working in VP14?

I tried to load a Pro Res 4444 clip but no joy.

I have PluralEyes, Singular and the VASST series and none show up as extensions. This really anoys me as I use Plurel Eyes and the VASST tools often. So I still need to use Vegas 13 if I want to use these tools, which I do of course. I emailed support last Friday and no answer yet. If I cannot get support on this I will request a refund

jkerry wrote on 9/27/2016, 3:11 PM

I was advised by VASST that they are working updates so the programs will work with Vegas Pro 14. Just that it will take a little time to get them all working.

James Moore wrote on 9/27/2016, 3:23 PM

I've contacted Red Giant asking about how to get PluralEyes to work with VP14. We shall see what they say.

Is there a place to post bugs? I'll try starting a new thread but I think I've got a bug going on with a Pro Res file.

MemoriesFX wrote on 9/27/2016, 4:01 PM

I was advised by VASST that they are working updates so the programs will work with Vegas Pro 14. Just that it will take a little time to get them all working.

How come VASST can answer right away but Magix does not respond to new support tickets? Not good Magix

ushere wrote on 9/27/2016, 7:02 PM

one of the problems with 'organisations' is the bigger they get the less well they can respond to their customers' concerns. this is especially evident with software, where small startups actively seek immediate feedback but as they grow the ability to implement changes rapidly becomes bogged down in inter-dept communications and marketing driven forces for more sales and rapid releases.

magix is a large organisation selling multiple overlapping products and needs to generate sales to continue expanding - vegas is simply another product that probably has to prove it's value before they invest too much in it.

george-sealy wrote on 9/28/2016, 10:35 PM

I am having severe problems with rendering. VP14 is shutting down after about 4 minutes. The program is unusable in its current form. VP13 does not shut down.

James Moore wrote on 9/29/2016, 5:36 AM

Is it all renders or a particular project?

george-sealy wrote on 9/29/2016, 12:03 PM

I have not tried other projects. Reading the above posts I see there are issues with ProRes files. This project has several of them on the timeline. VP14 does not crash during editing. But it sure does on the render. So, are they fixing the problems with ProRes?

george-sealy wrote on 9/29/2016, 12:07 PM

Also, I don't like how the fonts render in the application and the icons are goofy. I am using an Nvidia 980Ti card which is outputing to a 4K display. The font rendering in Sony VP13 is perfect. I don't understand why there are all these issues when VP13 worked fine. Didn't Sony sell them the source code? Why did some developer go in and screw with things?

James Moore wrote on 9/29/2016, 12:37 PM

I've done beta testing in the past for another companies editing software. I've rarely had a beta build that has given me as much trouble as VP14. I thought I would try doing a small job on it. Basically I've got to clean up some audio on a 3 min short film.

First I had troubles with the Pro Res file they supplied me. I've reported the info to Magix tech support. So far no reply. I rendered the Pro Res file to an MPG2 file in VP13 and used that as my reference video. I am having great difficulty simply opening projects. It often seizes up at 4% or 5% loading. When I go to close the program it tells me a background process is running. Sometimes I can stop it and get the program closed. Other times I have to use task manager to close it. Still it takes a few trys there as well.

Some projects open ok it seems (VP13 projects) I can then load the small project I am working on. I decided to test a render. I tried to render to MPG2 and it rendered but in play back the picture freezes at about the half way. Then it renders black. It's a mess. I tried to open the project again to try a different render and VP14 hung again.

Not good.

By the way, I heard back from Red Giant about getting PluralEyes running and they wrote:

"Unfortunately we haven't got any version of PluralEyes that's yet compatible with Vegas Pro 14. It's something our project team would love to tackle but I couldn't give a definitive timeframe as to when it'll get implemented. I'll append this ticket into the tally system to hopefully give it some weight in development, until then there's nothing that can be done to get those two programs to work together. Sorry this wasn't a more fruitful query, but let me know if there's any other way I can help."

Quitter wrote on 9/29/2016, 1:09 PM

I think the major problem is the renaming.
Why else named some folders with items of VP14 still Sony?
They renamed it from Sony Vegas to Vegas, it would be better they had done this to Magix Vegas in the whole software. So it would be easier for all to adapt everything.
Also for Magix.

vkmast wrote on 9/29/2016, 1:12 PM

The current renaming may help if there are further changes in ownership.

James Moore wrote on 9/29/2016, 1:14 PM

I did notice that the render pre-sets I created in VP13 appear in the VP14 list

Quitter wrote on 9/29/2016, 1:22 PM

The current renaming may help if there are further changes in ownership.

Yes, maybe, but I think it has not been fully carried out.

James Moore wrote on 9/29/2016, 3:02 PM

In my case the loading projects problem was because one file was on a network drive and there was a network problem so it just hung.

The render problem came from using a preset that I created in VP13 but which (I think mistakenly) is loaded in VP14 (because it is accessing the wrong directory for the presets?).

I shall continue working on this little project with VP14 for now.

set wrote on 9/29/2016, 6:48 PM

I think the major problem is the renaming.
Why else named some folders with items of VP14 still Sony?
They renamed it from Sony Vegas to Vegas, it would be better they had done this to Magix Vegas in the whole software. So it would be easier for all to adapt everything.
Also for Magix.

I had crashes on OFXs when trying Magix VP14 first time. In the middle of experiment, the crash window came out with report of each 3rd party OFX (in my case, I have NewBlueFX TotalFX3 and Red Giant Universe installed):

(Sorry, didn't copy-paste the details of report). Then closes down. Next time restart Magix VP14, I had no further issue.

BUT, if I'm running Sony VP13 again, in the middle of editing, I had similar crash like shown above, like happening in Magix VP14. Restart Sony VP13 - and no further issue. So, I guess I agree if renaming is totally confusing anyone.

(I have temporarily do system restore to previous condition before installing VP14 - so I currently have no VP14 for experiment - but probably return later)

MemoriesFX wrote on 9/29/2016, 10:11 PM

I keep getting an error message saying that autosave failed to save project.. Don't know how to turn this off. Also I chose to have files in media bin open in trimmer when double clicked but it does not stick, so then I get files getting applied on the timeline over my edits. So maybe they fixed old bugs but seem to have new ones. The best thing is that rendering times seem better.

1 … 6 7 8 9

of 9