VEGAS Pro 17 Update 2 (Build 353) - General Discussion

Bri-Hageman wrote on 11/11/2019, 11:29 AM

We have just released our second update for VEGAS Pro 17 (build 353). Please give us your feedback in this thread.

If you already have an earlier build of VEGAS Pro 17, there is no need to uninstall it. Build 353 will overwrite your installation and retain your settings. Keep in mind that your computer will need to be online for activation after the update

For more information, check out the official announcement with patch notes, here.

Have a great week everyone!
 

Comments

pierre-k wrote on 11/11/2019, 11:55 AM

Backwards tracking for Bézier Mask video effect is the Best of!

fr0sty wrote on 11/11/2019, 11:57 AM

Thanks! Hoping it helps with this Render As crash I've been having... let's see.

Systems:

Desktop

AMD Ryzen 7 1800x 8 core 16 thread at stock speed

64GB 3000mhz DDR4

Radeon VII

Windows 10

Laptop:

ASUS Zenbook Pro Duo 32GB (9980HK CPU, RTX 2060 GPU, dual 4K touch screens, main one OLED HDR)

KaraUSA wrote on 11/11/2019, 1:12 PM

Really disappointed, not news codecs videos for the exportation, nothing new... bad. Sorry it's my opinion

fr0sty wrote on 11/11/2019, 1:14 PM

Updates like this focus on bugfixes and improvements to existing features. Don't expect things like new formats being supported until the next version update.

pioneer109 wrote on 11/11/2019, 1:23 PM

Thank you for the update and the teams hard work. Although not mentioned in what has been included in the update, sadly build 353 there is still no video (Audio only) with screen capture for me sadly.

Sungmin-Kang wrote on 11/11/2019, 2:24 PM

thank you for the update but

auto preview in project media must be fixed!!

it's very uncomfortable while click n hold mouse button for preview my files

fr0sty wrote on 11/11/2019, 2:30 PM

Render As guaranteed crash on first try bug fixed. Thanks!

VEGASPascal wrote on 11/11/2019, 2:38 PM

Really disappointed, not news codecs videos for the exportation, nothing new... bad. Sorry it's my opinion

In the past everybody was disappointed that we did not improve the features, performance and stability... but thanks for your feedback.

fifonik wrote on 11/11/2019, 2:59 PM

It is always like this. Whatever you do -- some people will be disappointed :)

P.S. Thanks for the new build.

Camcorder: Panasonic X920

Desktop: MB: MSI B450M MORTAR TITANIUM, CPU: AMD Ryzen 3700X (not OC), RAM: G'Skill 16 GB DDR4@3200 (not OC), Graphics card: MSI RX580 8GB (factory OC), SSD: Samsung 970 Evo+ NVMe 500MB (OS), HDDs: Seagate & Toshiba 2TB, OS: Windows 10 Pro 1909

NLE: Vegas Pro [Edit] 11, 12, 13, 15, 17

fr0sty wrote on 11/11/2019, 3:11 PM

I spoke too soon, render as crash for complex projects is still there. First time I tried from a fresh open, the render as dialog appeared as it should have. Upon loading the project again, doing some editing, then clicking render as, it crashed.

pioneer109 wrote on 11/11/2019, 3:13 PM

Thank you for the update and the teams hard work. Although not mentioned in what has been included in the update, sadly build 353 there is still no video (Audio only) with screen capture for me sadly.

Maybe you are now convinced to use the needed Windows 10?😄


I am not sure if this comment was directed at my post. Why would there be an assumption I am not on Win10?

j-v wrote on 11/11/2019, 3:36 PM

Sorry @pioneer109  my mistake.
I accidentally exchanged you with another user.
I'll delete that comment.

met vriendelijke groet
Marten

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

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

Nerd-Sidekick wrote on 11/11/2019, 7:28 PM

I can't render even a two minute clip without the program crashing. I haven't had render problems in years (been a user for about 10 years). Now, with this update, I can't get anything out. I'm rendering two minute clips of 1080 video with nothing but a fade in and fade out--no other effects.

Version 17 crashes ALL THE TIME but at least I was able to render. Now with the 353 update, I can't even do that. I'm almost ready to jump ship. I have wasted so much time and I'm just about done.

Grazie wrote on 11/11/2019, 11:07 PM

I can't render even a two minute clip without the program crashing. .....

Now with the 353 update, I can't even do that. . . .

I'm almost ready to jump ship. I have wasted so much time and I'm just about done.

@Nerd-Sidekick - I'm rendering stuff all the time. As this is a primary function of any NLE, maybe it's your setup or your workflow that needs overhaulin'?

@Nerd-Sidekick - Also, this is your very first Post under this name - yes? You only joined last month. Is there ANYTHING we can do to help you?

However, your comments and those of others here have pursaded me to hold-back installing VP17 Update 2 (Build 353) until I'vegot my latest creation through to FINAL render.

Last changed by Grazie on 11/11/2019, 11:08 PM, changed a total of 1 times.

Grazie

PC 10 64-bit 64gb * Intel® Core™i9 - 3.3GHz * 40Gb NVIDIA  GeForce RTX 2070

Cameras: Canon XF300 + PowerShot SX60HS Bridge

Nerd-Sidekick wrote on 11/11/2019, 11:20 PM

@Grazie I've been rendering without any problem on the previous version 17 build. Something changed today after installing 353.

I'm running on a newly built Ryzen 9 system with 64GB RAM and a RTX 2080 video card with NVMe drives. So this computer smokes.

I upgraded from Vegas 13 to 17 at the same time I built the computer, so that's when I setup my account here. I also had an account on the old Sony forum.

Not sure if there's anything anyone can do to help unless there's a fix for the constant crashes for unknown/unpredictable reasons, and now the new rendering problem. Perhaps someone has suggestions for specific settings based on my hardware configuration. I'm all ears. I'd rather not have to learn another NLE, but I'm already testing Resolve.

GerY wrote on 11/11/2019, 11:25 PM

Hello nice that there is another update but the automatic update does not work and always breaks down. Is there also a link to download it? Keeps on telling that the programma must by closed, but it's not running!

fr0sty wrote on 11/11/2019, 11:29 PM

@Grazie I've been rendering without any problem on the previous version 17 build. Something changed today after installing 353.

I'm running on a newly built Ryzen 9 system with 64GB RAM and a RTX 2080 video card with NVMe drives. So this computer smokes.

I upgraded from Vegas 13 to 17 at the same time I built the computer, so that's when I setup my account here. I also had an account on the old Sony forum.

Not sure if there's anything anyone can do to help unless there's a fix for the constant crashes for unknown/unpredictable reasons, and now the new rendering problem. Perhaps someone has suggestions for specific settings based on my hardware configuration. I'm all ears. I'd rather not have to learn another NLE, but I'm already testing Resolve.

Make a thread about your issue, or it'll get buried under unrelated posts here, but the first thing I'd try is updating your GPU drivers (use nvidia studio drivers, many users have said it helped their issues). If that doesn't help, we'll continue helping in your new thread once you make it.

Last changed by fr0sty on 11/11/2019, 11:29 PM, changed a total of 1 times.

Systems:

Desktop

AMD Ryzen 7 1800x 8 core 16 thread at stock speed

64GB 3000mhz DDR4

Radeon VII

Windows 10

Laptop:

ASUS Zenbook Pro Duo 32GB (9980HK CPU, RTX 2060 GPU, dual 4K touch screens, main one OLED HDR)

ngjb wrote on 11/12/2019, 1:03 AM

How stable is version 17? I have seen some of the troubling posts on this thread already indicating to me that Magix software quality is as poor as ever. I am still running Version 14 and it is stable and I am able to edit my 4K videos without any grief. I upgraded to Version 16 this time last year and it was constantly crashing and locking up my computer and required me to reset power. This in itself was troubling. The best thing I can say about installing Version 16 was that it didn't delete my Version 14 installation. I uninstalled Version 16 the same day and requested and got a refund. Before I go through that exercise again, can someone comment on the stability of version 17?

bitman wrote on 11/12/2019, 1:32 AM

@ngjb stable enough I would assume looking at the (rather few) items they fixed in this second patch, and the fact that this second patch took a while to release, but not unplanned I assume. Just saying, if stability was a drama, and blocking, quick fixes would have come sooner I guess.

Current system: VP 17 (build 421), VP16 (suite) build 424, (uninstalled VP 13,14,15), Vegasaur, Magix Video Pro X (VPX11), Corel VS ultimate 2019, a lot of NEWBLUE plugins, Titler Pro 6, Mercalli 4.0, Respeedr, Vasco Da Gamma 12, VASST stuff, Production Assistent pro3, Boris Continuum 2020, Davinci Resolve Studio 16,...

  • OS: Windows 10 Pro 64, version 1909
  • CPU: i9900K stepping R0 (since October 2019), previously, der8auer i7-8700K (advanced edition), default speed (no overclock), Cooler: Noctua NH-D15s
  • RAM: G.Skill Trident Z 3200C14 DDR4 64GB, XMP set to profile 1 in BIOS
  • Videocard: NVIDEA RTX 2080Ti (Founders edition), NVIDEA studio drivers
  • Monitor: LG 38 inch ultra-wide (21x9) - Resolution: 3840x1600
  • C-drive (games & APPS): Samsung NVMe SSD 2TB 960 pro

  • Current Video source work drive: Samsung NVMe SSD 2T 970 EVO plus

  • Mass Data storage & Backup: WD gold 6TB + WD Yellow 4TB

  • MOBO: Gigabyte Z370 Aorus Gaming 7, BIOS F14
  • PS: Corsair HX1200i, Case: Silverstone fortress 2,
  • Misc: Logitech G910, Evoluent Vertical Mouse, shuttlePROv2

 

bitman wrote on 11/12/2019, 1:37 AM

Something else and maybe a stupid question to the devs, I have Vegas post (albeit I was never able to use it due to the Boris conflict), is this update 2 version compatible with Vegas 17 Post version of Vegas 17?

I assume it does, but before installing I may well ask...

Current system: VP 17 (build 421), VP16 (suite) build 424, (uninstalled VP 13,14,15), Vegasaur, Magix Video Pro X (VPX11), Corel VS ultimate 2019, a lot of NEWBLUE plugins, Titler Pro 6, Mercalli 4.0, Respeedr, Vasco Da Gamma 12, VASST stuff, Production Assistent pro3, Boris Continuum 2020, Davinci Resolve Studio 16,...

  • OS: Windows 10 Pro 64, version 1909
  • CPU: i9900K stepping R0 (since October 2019), previously, der8auer i7-8700K (advanced edition), default speed (no overclock), Cooler: Noctua NH-D15s
  • RAM: G.Skill Trident Z 3200C14 DDR4 64GB, XMP set to profile 1 in BIOS
  • Videocard: NVIDEA RTX 2080Ti (Founders edition), NVIDEA studio drivers
  • Monitor: LG 38 inch ultra-wide (21x9) - Resolution: 3840x1600
  • C-drive (games & APPS): Samsung NVMe SSD 2TB 960 pro

  • Current Video source work drive: Samsung NVMe SSD 2T 970 EVO plus

  • Mass Data storage & Backup: WD gold 6TB + WD Yellow 4TB

  • MOBO: Gigabyte Z370 Aorus Gaming 7, BIOS F14
  • PS: Corsair HX1200i, Case: Silverstone fortress 2,
  • Misc: Logitech G910, Evoluent Vertical Mouse, shuttlePROv2

 

RogerS wrote on 11/12/2019, 1:45 AM

Really happy to see multilingual releases so those of us in Japan don't have to wait for the SourceNext version.

joost-berk wrote on 11/12/2019, 3:52 AM

I spoke too soon, render as crash for complex projects is still there. First time I tried from a fresh open, the render as dialog appeared as it should have. Upon loading the project again, doing some editing, then clicking render as, it crashed.

Hey @fr0sty Try deinstalling all magix software, then reboot en run Ccleaner (cleaner + reg-cleaner), reboot en install the latest version of Vegas. After that, the Render As.. crash disapears. At least, this did it for me!

Cheers!

Vegas Pro user since version 1.2

OS: Windows 10 Pro (Latest version)

CPU: AMD Ryzen 7 3800X

RAM: 32GB DDR4 3200MHz

GPU: Nvidia GeForce RTX 2080 Super 8GB GDDR (Latest Studio Driver)

Monitoring: Black Magic Design DeckLink SDI 4K (or Nvidia HDMI for 4K HDR)

Audio: M-Audio M-Track Eight ASIO

Controller: Behringer X-Touch

j-v wrote on 11/12/2019, 4:34 AM

Hello nice that there is another update but the automatic update does not work and always breaks down. Is there also a link to download it? Keeps on telling that the programma must by closed, but it's not running!

Hallo Ger,
here no problem to do the automatic update on laptop and desktop.
Look how it goes on my laptop

There is always a link for downloading the new build on your Magix account.

Last changed by j-v on 11/12/2019, 4:37 AM, changed a total of 1 times.

met vriendelijke groet
Marten

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

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

John-Richardson wrote on 11/12/2019, 5:35 AM

No render crashes in previous version. I upgraded in the middle of a project and now can’t render without an instant crash.

 

Updated to latest NVIDIA Studio Drivers and problem fixed.

 

12/3 render crash has become "render hang." It gets to 82% of render on a multicamera 5 minute 4K clip and hangs showing 0:00 left. Have to use Task Manager to force quit.