VEGAS Pro 14 Update 6 (build 252)

VEGAS_CommunityManager wrote on 4/11/2017, 10:14 AM

Dear community,

The previous update provided several important bug fixes, but inadvertently exposed a bug that prevented certain custom render templates from working properly. This new update (build 252) fixes that bug as well as a transparency bug in the Film Effects plug-in.

You can download build 252 now: http://rdir.magix.net/?page=YX5CXRX3NIYR

Here are the patch notes for this update:

Bug fixes

Custom HEVC, MainConcept AVC/AAC, and ProRes render templates now work properly again
The Film Effects plug-in was found to expose unwanted transparency in 8-bit Pixel format mode. The plug-in now works properly and no longer introduces inadvertent transparency

As always, thank you for your valuable feedback, enthusiasm, and support for helping VEGAS Pro to continually improve!

Best regards,
Mathias

Back to post

Comments

hughdemand wrote on 4/15/2017, 7:33 AM

I did not receive notifications about any new builds. I just checked and I am using 161.

Should I download 252 ? What are the steps ?

Just follow the link on the first post.

Completed, simple enough. Thank you

Whit

cadudesun wrote on 4/15/2017, 12:55 PM

I had build 211 working properly just now.

Then updated to build 252 and Vegas started crashing during the initial loading screen , when "creating video plug-in factory", as showed in this snapshot: http://i.imgur.com/kcbB11c.png

I have BCC 10 OFX installed. Then I reinstall BCC and Vegas 252 again. Even after that the same crash still happening.

Is there a "security" mode in Vegas that bypass plug-in factory?

I would like to try isolating if the problem is plug-in indeed...

Thanks

Actually, the plugins crashing Vegas 252 were the NewBlue ones bundled with Vegas 14.

Then I deleted the NewBlueFX folder under "C:\Program Files\Common Files\OFX\Plugins\" and Vegas 252 just started working.

Does someone else have experienced any conflict between Vegas 14 and NewBlue plugins bundled with Vegas, be it in the last build 252, or any other build?

Thanks!

set wrote on 4/15/2017, 5:59 PM

I have NewBlueFX Titler Pro 5 Ultimate (V 5.0.170103) installed here and so far working fine.

Grazie wrote on 4/15/2017, 8:47 PM

Set? Which build of VP14 have installed?

set wrote on 4/15/2017, 8:55 PM

Latest 252. And I never install the bundled Titler Express as it seems affecting Titler Pro

Grazie wrote on 4/15/2017, 9:11 PM

Thanks Set. Are you getting any of the other issues listed? Docking Panes?

set wrote on 4/15/2017, 9:14 PM

I haven't checked any detail issue on build 252. A bit busy with other activities...

oliverSpain wrote on 4/17/2017, 8:14 AM

Thanks. Downloaded.

alexander-nNevis wrote on 4/18/2017, 9:33 AM

Does someone else have experienced any conflict between Vegas 14 and NewBlue plugins bundled with Vegas, be it in the last build 252, or any other build?
Thanks!

With the release of version 252, "Vegas 14 Pro" no longer crashes while the project saving. But continues falling during rendering "NewBlue" titles as it was in previous versions.

But I noticed if I start an empty project and add "NewBlue" title as the first video track without adding other tracks, "Vegas14 Pro" not crashing during rendering "NewBlue" title.

I'm using "NewBlue Titler Pro build 3.0.161119" instead of bundled, Win7 64bit Ultimate, GTX1080 (latest driver), MS Framework 4.6.2

rik wrote on 4/20/2017, 4:11 AM

I did receive a news popup-message within Vegas, a minute ago about a "new version available"....But the update is already installed acouple of days a go"build 252". Is this news "too late" or is there maybe another update coming which is not mentioned in the newssection here?

Paul-Fierlinger wrote on 4/20/2017, 6:03 AM

Same happened here; same question. What's going on?

EDIT: There was a strange anomaly associated with this occurrence. My computer, which I never turn off, was depowered this morning but there had not been any OS updates or power outages. It was quiet strange...could this have been caused by the equally strange appearance of the no-news MAGIX news of the availability of a 252 update?

DDDyson wrote on 4/20/2017, 3:19 PM

I did receive a news popup-message within Vegas, a minute ago about a "new version available"....But the update is already installed acouple of days a go"build 252".

I have the same problem. Every time I launch Vegas Pro, I get an announcement that there's an update, and it downloads the build 252, which I already have installed.

Quitter wrote on 4/21/2017, 1:31 AM

I have the same problem. Every time I launch Vegas Pro, I get an announcement that there's an update

check: Do not show this message again

DDDyson wrote on 4/21/2017, 2:11 AM

check: Do not show this message again

It should not make that notification if I already have the build 252 installed. So it seems like a bug.

If I check that checkbox, will it mean that I won't be notified of later updates either? :/

Quitter wrote on 4/21/2017, 3:06 AM

If I check that checkbox, will it mean that I won't be notified of later updates either? :/

The "News Feed" function is not deactivated

VEGASDerek wrote on 4/21/2017, 8:19 AM

The check box on the news feed popup window only dismisses the current message so that the same message will not appear the next time you start the application. When new news is published, the window will popup again with the new message. To turn off the feature all together, there is a check box in the preferences dialog.

As far a notifications for updates, we are continuing to enhance our update/notification mechanisms and integrating in with the Magix system, but we need to balance those needs with the work we are doing adding features and fixing bugs as well.

LindaSunshine wrote on 4/21/2017, 2:42 PM

Bug: after i updated from build 244 to build 252 it was just crashing and vegas did not start. I deleted folder c:\users\Linda\appdata\local\VEGAS Pro and vegas started, recreated the folder and tadaaa running without any problems. I tried it few time uninstall vegas 14 completely, but as i noticed it did not delete folder from appdata\local\VEGAS Pro\ after installation same problem even the old version. BCC10 + others plugins i bought works without any problem.

LindaSunshine wrote on 4/21/2017, 3:33 PM

build 252 do not support rendering using AMD open CL i changed it to render Open CL and it every time it switch to render using CPU only. Whats wrong with CPU i will not achieve rendering time like before :-( Allow legacy GPU rendering using AVC mainconcept profile and it doesn't work in build 244 it was working

set wrote on 4/21/2017, 7:35 PM

build 252 do not support rendering using AMD open CL i changed it to render Open CL and it every time it switch to render using CPU only. Whats wrong with CPU i will not achieve rendering time like before :-( Allow legacy GPU rendering using AVC mainconcept profile and it doesn't work in build 244 it was working

What AMD model do you use?

I'm curious and do quick testing, and found AMD RX470 works for me without any issues (Sony AVC render):

Lower CPU usage rather than Mainconcept rendering (unable to use GPU on my system)

LindaSunshine wrote on 4/21/2017, 8:31 PM

RX 480 8GB waiting for RX Vega Sony main concept do not support 4 K 29.97 or 59.97 even with main concept AVC the max CPU usage is 74%. But open CL in new version not working at all I was checking the internal settings no option. It is telling me that Open CL is supported in main concept AVC, but not let me allow rendering using Open CL every time it switch to CPU rendering. Not using full HD 1080p that mean Sony AVC is worthless because I cannot change resolution for 4096x2160 or 3840x2160 :-( even with the frame server using external encoder I tried GTX 1080Ti I own and no GPU Cuda no Open CL RX480 works due to Vegas rendering export stream :-( I expected this to be fixed, but new and new builds fixing minor bugs and rejected totally open CL support or GPU rendering :-(

set wrote on 4/21/2017, 8:50 PM

Ah, yes.. for a higher than 1080 resolution, then there's no choice but Mainconcept. And yes, I also cannot utilize the GPU.

NickHope wrote on 4/22/2017, 2:04 AM

Allow legacy GPU rendering using AVC mainconcept profile and it doesn't work in build 244 it was working

Check Preferences > General > Allow legacy GPU rendering. That might have become un-checked during your troublesome update from build 244 to 252.

But OpenCL rendering in the MainConcept AVC encoder is not supported for any card since the AMD Radeon HD 6970, in any build of Vegas. If you have the above preference checked, and you have a GPU that supports OpenCL, then you can select "Render using OpenCL if available", but the render time in my experience (my laptop with modern AMD graphics) is actually slower than if you select "Render using CPU only".

With the Sony AVC encoder there may be a modest speed up or slow down if you select "Render using GPU if available". I wouldn't bother.

LindaSunshine wrote on 4/22/2017, 1:17 PM

I tried it once again and it didn't work Preferences > General > Allow legacy GPU rendering v244 uncheck, upgrade for 252 crash. It start working after i deleted c:\users\Linda\appdata\local\VEGAS Pro folder and let the new update recreate that directory. I run couple of tests, open CL was 10s faster than CPU rendering v244. Cuda no difference. Rendering using 6950x 10c 20t cpu using Boris Fx filters slower by 0.4fps comparing Ryzen 1800X. I tested multiple memories from 2400-3600 Mhz the best were G.Skills 2400Mhz 32G CL 15. Benchmark looks the best 3600, but not with Maya or Vegas everything over 2400 Mhz just degrade the rendering performance. It looks everything over 16 threads is waste of money for rendering is the best GPU Open CL. RX 480 Saphire + Nitro 8GB is nothing special but to run BCC i need open CL to see the preview in Vegas, GTX 1080ti doesn't support open CL and not working with BCC. Waiting for Vega Firepro 24-32GB that can do better rendering speeds if the Magix will implement Open CL support. I can render 4K 1.2fps with BCC running 3 vegs at the same time that means 3.6fps. Under windows 7 it was much worst. For example 6950X 32GB m.2 rendering 1hr 4K video using BCC = 26hr 15minutes 12second. Ryzen 1800X 32GB 2400 Mhz same filters = 19hr 05minutes 56seconds. I'm not sure if i can use Vegas 14 on my notebook and PC at the same time due to license and notebook will probably render 4K 1h maybe a years lol. With BCC i need every time deactivate BCC if I'm switching systems.

lowly-pawn wrote on 4/22/2017, 1:49 PM

I just finished my new AMD Ryzen build but the render times were horrible compared to my old rig so I updated Vegas Pro to build 252 and it didn't help at all. I need some advice. My new computer is a Ryzen 7 1800X, ASRock X370 killer SLI/ac, 32 GB of Gskill trident memory. Radeon RX 480 GPU, not overclocked, all newest bios,chipset windows ETC updates. Apparently Vegas Pro is not using my graphic card open CL in this new system. My old system (Phenom II 1090T with a Radeon HD 6800) really used the graphic card well while rendering out using MainConcept AVC/AAC, it would render in almost real time. Meaning a 10 minute video would render in about the same time (10 min) which is awesome for an old computer. But my new system takes more then twice as long to render! Meaning a 10 minute video takes just over 20 minutes! I've been trying every setting I can find under the sun but nothing seems to speed it up. Highly disappointed is understatement to say the least. Looking at AMD-system-monitor I can see my graphic card is barely doing anything during rendering so my CPU is doing most if not all of the work. Sony AVC is a little faster but the bit-rate maxes out at 25,999,360. Which is probably more than fine when uploading to youtube but I just like MainConcept options better. Also there is one more annoying bug with this build is when I switch between trimmer and timeline it won't always put my video fullscreen on my 3rd monitor. So I have to constantly un-check and check "Video Preview on external monitor" and the "trimmer on External monitor" to get them working again. That's annoying. Anyway, any advice on how to speed up my render times and for my Ryzen system would be great and maybe you guys can look into that external monitor bug, hopefully I'm not the only one experiencing this. Thanks.

1 2 3 4 … 5

of 5