VEGAS Pro 16 Update 4 (build 361) - General Discussion

VEGAS_CommunityManager wrote on 1/16/2019, 8:46 AM

We have just released VEGAS Pro 16 Update 4 (build 361). Please give us your feedback in this thread.

If you already have build 361 or earlier installed, there is no need to uninstall it. The build 361 will overwrite your installation and retain your settings. Your computer will need to be online for activation after the update.

If you are installing VEGAS Pro 16 for the first time, it is generally better to install using a VEGAS Pro download manager. See here for details & links.

Official announcement with Patch Notes

VEGAS Pro 16 (build 361) installer

Comments

Chris-Harwood wrote on 1/16/2019, 8:51 AM

problems installing. Keep getting message, "installer can't update with program running" . Tried various routes, same message

ivan-f wrote on 1/16/2019, 9:02 AM

Hello, I too have a problem, when we can take mxf videos on Vegas? Because I try to carry this type of video file, but his refuses. It will be nice at the next update, that Vegas can take away MXF

Thank you

Former users wrote on 1/16/2019, 9:11 AM

I had no problem with it installing, I chose to install after close program.

Pity they didn’t see fit to fix the blue ray image creation bug, you have to use say vp15, its still broken, or maybe it doesn’t come under the heading of a bug?

Fix by Oldsmoke here … https://www.vegascreativesoftware.info/us/forum/problem-making-blue-ray-iso-in-vp15--108589/

Dimitrios wrote on 1/16/2019, 9:30 AM

Does anyone know if they are still blacklisting plugins in this version?

SphinxRa40 wrote on 1/16/2019, 11:03 AM

What the heck is MAGIX doing to Vegas, (auto) preview only black in the preview window, frames you can see running/counting, then crashes after selecting several files, all video formats and picture formats the only thing it preview right are audio files...

Antti wrote on 1/16/2019, 1:08 PM

Still crashes on startup when Ignite Pro is installed 😒. I haven't found a working solution from the other threads to fix the issue with Vegas Pro and e.g. Natron starts up just fine and it can use Ignite Pro effects. I tried with both the bundled Ignite Pro 2.2.7729 as well as the fairly recent Ignite Pro 3.2.8328 straight from FXhome. I've sent the full report from the Problem Report tool.

Problem Description
   Application Name:    VEGAS Pro
   Application Version: Version 16.0 (Build 361)
   Problem:             Unmanaged Exception (0xc0000005)
   Fault Module:        C:\Program Files\VEGAS\VEGAS Pro 16.0\vegas160.exe
   Fault Address:       0x0000000219930522
   Fault Offset:        0x0000000219930522

Fault Process Details
   Process Path:        C:\Program Files\VEGAS\VEGAS Pro 16.0\vegas160.exe
   Process Version:     Version 16.0 (Build 361)
   Process Description: VEGAS Pro
   Process Image Date:  2019-01-07 (Mon Jan 07) 16:54:52

Kinvermark wrote on 1/16/2019, 1:11 PM

@SphinxRa40

FYI, preview working fine here. Probably best to open a support ticket and / or post your system details.

zdogg wrote on 1/16/2019, 2:35 PM

Thanks Mathias and Magix.

Folks, this is a terrific company, (I have been a Samplitude customer since about the year 2001) for many years, in a tough business, and they are going to bring Vegas into relevance again, they have the tenacity and the brain trust and German know-how.

This is the program (Samplitude/Sequoia) that was used to record/edit the Vienna Symphonic Orchestra (top grade sample orchestra). Also a go to staple in mastering studios. Extremely high end audio.

For many years Magix has had its eyes on the multi media world. As did the original Sonic Foundry Vegas -- they came from the audio-first perspective -- and Vegas is a good fit, and obviously it still needs some improvement, but that is what Magix is all about, now that they have a serious video editing/compositing program in their portfolio to go with their consumer grade offerings.

Thanks for getting to serious stability issues, mostly related to the ever changing GPU/hardware landscape. Let's not dismiss that idea.

Visit Magix AG in Berlin, circa 2012





(Forgive the Cal/Texan rep Dolbear saying "sample-tude" instead of Samp-LI-tude. Drives me nuts).

zdogg wrote on 1/16/2019, 2:37 PM

Part 2. Magix AG Berlin, 2012

Josh-J wrote on 1/17/2019, 12:33 AM

We have just released VEGAS Pro 16 Update 4 (build 361). Please give us your feedback in this thread.

If you already have build 361 or earlier installed, there is no need to uninstall it. The build 361 will overwrite your installation and retain your settings. Your computer will need to be online for activation after the update.

If you are installing VEGAS Pro 16 for the first time, it is generally better to install using a VEGAS Pro download manager. See here for details & links.

Official announcement with Patch Notes

VEGAS Pro 16 (build 361) installer

I hope The Full-Screen preview was fixed in this update since that's what I was having the most amount of trouble with.

SphinxRa40 wrote on 1/17/2019, 6:26 AM

@SphinxRa40

FYI, preview working fine here. Probably best to open a support ticket and / or post your system details.

Well...after an hour last night to try several standard things in Vegas (GPU Acc.- comp - ram etc) I came with a ridiculous idea myself, I closed a few times the preview window and turned back on, worked^^

Well..guess I have to that every freaking time I start Vegas, just started Vegas and have to do the same, guess its gonna be a ticket and get copy/paste answers again 😡

Lukasz wrote on 1/17/2019, 7:44 AM

Hello, this update has fixed the cooperation of the vegas 16 with GPU GTX1050Ti and works properly. Good job :)

 

j-v wrote on 1/17/2019, 8:43 AM

This update solved also my problem here.
Probably now Vegas is using its memory different now.
Thanks.

met vriendelijke groet
Jan

Camera : Pan X900, GoPro Hero7 Hero Black, Samsung Galaxy A8
Desktop :MB Gigabyte Z390M, W10, i7 9700 4.7Ghz,16 DDR4 GB RAM, Gef. GTX 1660 Ti.
Laptop  :Asus ROG GL753VD, W10 home, version 1903 build 18.362,295 CPU i7 7700HQ, 16 GB RAM, GeF. GTX 1050 (2 GB) + Int. HD Graphics 630(2GB).VP 16,17 and VMS PL 16 are installed
Both Nvidia GPU's have driver version 431.86 Studio Driver, desktop the Studio DHC driver
TV      :LG 4K 55EG960V

Dutch video tutorials for beginners

My slogan is: BE OR BECOME A STEMCELL DONOR !!!

musko wrote on 1/17/2019, 10:18 AM

But this build is not fixed this problem with restore backupup files.
I'm disappointed.

D7K wrote on 1/17/2019, 1:22 PM

Just loaded a project that is representative of what I do, the patient lives:) Tks for the update.

Reyfox wrote on 1/17/2019, 1:48 PM

Saw the update prompt when I started VP16. I exited the program and came here to download and then install.

So far, all is well!

Former users wrote on 1/17/2019, 6:54 PM

At the moment, I prefer bug fixes than new features. I believe this is the right path. Thank you!

peck1234 wrote on 1/18/2019, 4:26 PM

Update feels good and snappy. Settings in project properties are still not being retained however. (Start all new projects with these settings)

3d87c4 wrote on 1/18/2019, 9:50 PM

The only 360 fx I'm seing is tiny planet, the rest (re-orient, dual lens stitch, 360 stabilization) are still missing.

Antonio-Franco wrote on 1/19/2019, 5:50 AM

I update to this latest version, but I see the program extremely unstable.

It hangs up many times. And it does it in simply actions, like moving my videos in the time lane. I've imported some simple presets that were working in v14.0 and they are not longer working with this version

The hangups frequency is notable high. It makes the program almost unusable. Sorry, I can follow a logical path to discover when and why it crushed..

Using a Dell Computer, Windows 10 Home fully updated (Jan 2019), GEFORCE gtx 960M, and 32Gb RAM

Fiola wrote on 1/20/2019, 11:06 AM

So with newest build I am seeing still my problems... but it gets better! :) I recognize less and less crashes of the software ... but still problems with 4K persists, but we are just trying to roll with it in our studio and just kill Vegas.exe everytime it get hang and boot it up again.

So thank you Magix for your hard work. No sarcasm intented. Really thank you.

Oh, except one more thing: I can't use MAGIX GPU render codec now with this version. After installing last version of VEGAS via automatic software updater, I am getting "System is low on memory" error during render. Great thing, so I need to render everything without GPU acceleration with this build of Vegas, which seems that I will roll back to prev version rather.

Just for keeping clear, my rig is: i9 7900X, 64 GB DDR4 RAM, NVIDIA RTX2080 Ti with newest drivers and Windows 10 Pro instalation.

Edit: So it seems that my problem with "System is low on memory" is related to settings in Options / Video - where I had 512 MB for video render cache I believe. I set it to zero - and the render seems to work without problem. Wow. Interesting.

Kinvermark wrote on 1/20/2019, 11:21 AM

Latest build of Vegas 16 is very stable for me.

pierre-k wrote on 1/20/2019, 11:57 AM

Still a permanent problem with Dynamic Ram and GPU on Rendering.

I have to do each time before rendering:

1. Complete the project and close Vegas.
2. Open Vegas and loading the latest project. I can not change anything in the project, otherwise it will contain random errors.
3. Dynamic Ram to Zero MB
4. Start rendering.
5. Check for any errors caused by Dynamic Ram.

This method is most effective, but terrible! The rendering time is very long.

Errors appear most when the project contains graphics such as JPG, PSD, and others.
Fix it definitely.

https://www.vegascreativesoftware.info/us/forum/v16-permanent-problem-with-dynamic-ram-in-rendering--113885/

ALEJANDRO-BELTRAN wrote on 1/21/2019, 5:59 PM

Problems in Dual Fish Eye Stitching 360 Plug in, this plug in , dont save custom presets. show the new preset name saved, but with default settigs.

Is Fundamental for workflow with other 360 cameras , that are not in the presets..

Thanks!