VEGAS Pro 16 Update 1 (build 261) - General Discussion

Back to post

Comments

Former user wrote on 9/10/2018, 10:31 PM
  • Go into Options – Preferences and
    • General Tab: Disable “Allow legacy GPU rendering”
    • Video Tab: Disable GPU acceleration
    • Set other options like I had in Vegas 15
    • Note: VST Effects… turn off Izotope/ACID/Samplitude effects you’ll never use in Vegas
    • Click APPLY and OK
  • Exit and restart Vegas 16… starts ok

After the install/fix were you able to turn on the GPU again & use successfully?

Having a Nvidia Titan X & not being able to use it sure seems like a waste.

robert-falconer-taylor wrote on 9/10/2018, 11:55 PM

 

@richardbushell

BTW: if developers are listening, they need to test load their products on systems like long term customers have, with all the applications I mentioned previously and with all Vegas 15 Suite components.

Interesting point. I've got 12, 14, 15 and now 16 on the same computer. I still have all the Fx that came with all these versions! Interesting how VP has changed in size over time!

Following Richard's comment I have just uninstalled all the fx I never use and probs would not work with the newer versions anyway. Robert

NickHope wrote on 9/11/2018, 12:32 AM

...

  • Remove the Hitfilm Ignite Pro that got installed with the Suite
  • Right click the Vegas 16 icon, Hold SHIFT and select open from the pop up menu, this invokes Vegas SAFE Startup

...

@donde Is this "Vegas SAFE Startup" a Vegas-specific thing or something that can be done with any application? If I do this on my system (Windows 10 version 1511), Vegas Pro 16 opens as normal. Or did you mean "Hold CTRL+SHIFT" as in the procedure to reset Vegas to default settings?

richardbushell wrote on 9/11/2018, 2:21 AM

@donde Thanks, I have 16 Pro rather than 16 Suite. I still cannot get Vegas to start, even in Safe Startup (your step 4). I have uninstalled every FX or plug-in I can think of or find. I am sure it's a legacy issue carrying over from one of my previous Vegas versions or plug-ins, but I just cannot think of or find any others to remove to solve my problem. Very frustrating that I cannot get past this and get Vegas 16 to start...

vkmast wrote on 9/11/2018, 6:43 AM

Similarly with VP 16 on my system (Windows 10 version 1803).

donde wrote on 9/11/2018, 7:43 AM

@Nick Hope … You are right Nick. It was CTRL+SHIFT. I edited my post on Pg4 to reflect this change. Thanks for pointing this out.

- Don

donde wrote on 9/11/2018, 8:10 AM

@Former user Yes I have a Titan X. But its been my experience since v13 that Vegas will freeze without warning if "GPU acceleration of video processing" is enabled... and it simply doesn't if its off.

Interestingly with Vegas 15 and 16 I noticed I can use the NV Encoder instead of the MainConcept AVC which is more than twice as fast. The NV Encoder still works even though GPU acceleration is off.

I still prefer the MainConcept encoder for final renders because it appears sharper and the Two Pass option reduces file size.

- Don

jozef-pavlik wrote on 9/11/2018, 9:06 AM

VEGAS Pro 16 Update 1 (build 261) has been released. Please give us your feedback in this thread.

If you already have build 261 or earlier installed, there is no need to uninstall it. The build 261 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 261) installer

I don't know what Im doing wrong in V16 when I try open vegas crashed. But my V13 V14 works fine ,please any ideas I did update my W and my GTX670 driver and no luck

 

zaheer-abbas wrote on 9/11/2018, 9:08 AM

Does any one else find that the gap removal feature is dreadfully inconsistent, It seems it works some times then for no reason will not work at other times. Is this a buy or am i using it wrong???

zaheer-abbas wrote on 9/12/2018, 12:51 PM

Also not seeing any improvement in the storyboard function. At this point it basically does not work.

Anyone confirm this problem?

confirmed

JesusSheep-1965 wrote on 9/12/2018, 4:26 PM

I Just Activated My Vegas Pro 16 Vegas Crashed With The BCC Mocha Pixel Choser.

Edward-Givens wrote on 9/12/2018, 9:24 PM

My feedback? I JUST upgraded in June. 😡😡😡😡

michael-cookson wrote on 9/13/2018, 12:51 PM

I thought I would try the trail version first before committing, I see the FX update to the preview window still does not update until you exit out of the FX, this should have been fixed for goodness sake ...

j-v wrote on 9/13/2018, 1:21 PM

I thought I would try the trail version first before committing, I see the FX update to the preview window still does not update until you exit out of the FX, this should have been fixed for goodness sake ...

This is not a Vegas Problem but your own installation and/or use of the program.
Install older drivers for your Nvidia videocard or let it not start your Vegas program if you have more than 1 GPU active.

met vriendelijke groet
Marten

Camera : Pan X900, GoPro Hero7 Hero Black, DJI Osmo Pocket, Samsung Galaxy A8
Desktop :MB Gigabyte Z390M, W11 home version 24H2, i7 9700 4.7Ghz,16 DDR4 GB RAM, Gef. GTX 1660 Ti with driver 566.14 Studiodriver and Intel HD graphics 630 with driver 31.0.101.2130
Laptop  :Asus ROG Str G712L, W11 home version 23H2, CPU i7-10875H, 16 GB RAM, NVIDIA GeForce RTX 2070 with Studiodriver 576.02 and Intel UHD Graphics 630 with driver 31.0.101.2130
Vegas software: VP 10 to 22 and VMS(pl) 10,12 to 17.
TV      :LG 4K 55EG960V

My slogan is: BE OR BECOME A STEM CELL DONOR!!! (because it saved my life in 2016)

 

vkmast wrote on 9/13/2018, 1:45 PM

For more on the issue user j-v (who was probably the first one to suggest a solution to it on this forum) comments above, read this comment, Nick's comment (and the FAQ link therein), and the related comments below.

michael-cookson wrote on 9/13/2018, 6:08 PM

I have tried all the suggestions on the posts and still it does not work in FX preview, but I have just noticed that Color Curves does work and updates the preview window, but HSl and Saturation do nothing, its like one is working but not the any of the others I have tried.

RogerS wrote on 9/13/2018, 9:10 PM

Did you try the Graphics Settings fix too? It worked for me.

It is a Vegas x Windows x Nvidia problem and I hope Magix can improve GPU compatibility with the latest versions of all.

michael-cookson wrote on 9/14/2018, 4:01 AM

Yes RogerS I did all of that, If I look at the icon in my taskbar, it tells me that Vegas is using the Nvidia Card, so that part is working.

garygiles63 wrote on 9/15/2018, 2:45 AM

When will Vegas feature a proper VST 3.0 64 bit support? I can't use my Waves and Isotope plugins without stuttering! It is a big issue that is going on since the first 64-bit Vegas version. And how come that when I try to render a project (even without any plugins) the performance of my CPU, GPU and RAM are not running higher than say 30% load in the Windows Task Manager? Can this be fixed, I bought high spec hardware just for Vegas Pro.

I want to second this. Its a huge disappointment to me that VST 3.0 64bit support has not been updated at all. I will not be upgrading to 16 until the audio and VST support has been fixed. If not fixed soon I will have to move over to Reaper, as this all works fine with my plugin's.

Please, please fix.

G.

 

bitman wrote on 9/15/2018, 10:00 AM

Storyboard issue which is not mentioned in Nick's or Vegas official issues:

  • Problem1:

deleting placeholder events from the storyboard does not always remove of them from the timeline.

Easy to reproduce: add 2 video events to the timeline, go to the media bin with the storyboard, use alt and mouse to drag the first video event a few spaces after the second clip. This will add placeholder events. Delete the placeholder events in the storyboard. The timeline is not updated in the same way as the storyboard.

  • Problem 2:

There is also a weird thing, if you move the first video event over a lot of empty spaces in the storyboard, but finally drop the event after the second video event, a lot of placeholder events are created (where there should be none). There can also be many duplicates of the moved video event be created on the timeline.

Storyboard is unusable in the state it is in now.

APPS: VIDEO: VP 365 suite (VP 22 build 194) VP 21 build 315, VP 365 20, VP 19 post (latest build -651), (uninstalled VP 12,13,14,15,16 Suite,17, VP18 post), Vegasaur, a lot of NEWBLUE plugins, Mercalli 6.0, Respeedr, Vasco Da Gamma 17 HDpro XXL, Boris Continuum 2025, Davinci Resolve Studio 18, SOUND: RX 10 advanced Audio Editor, Sound Forge Pro 18, Spectral Layers Pro 10, Audacity, FOTO: Zoner studio X, DXO photolab (8), Luminar, Topaz...

  • OS: Windows 11 Pro 64, version 24H2 (since October 2024)
  • CPU: i9-13900K (upgraded my former CPU i9-12900K),
  • Air Cooler: Noctua NH-D15 G2 HBC (September 2024 upgrade from Noctua NH-D15s)
  • RAM: DDR5 Corsair 64GB (5600-40 Vengeance)
  • Graphics card: ASUS GeForce RTX 3090 TUF OC GAMING (24GB) 
  • Monitor: LG 38 inch ultra-wide (21x9) - Resolution: 3840x1600
  • C-drive: Corsair MP600 PRO XT NVMe SSD 4TB (PCIe Gen. 4)
  • Video drives: Samsung NVMe SSD 2TB (980 pro and 970 EVO plus) each 2TB
  • Mass Data storage & Backup: WD gold 6TB + WD Yellow 4TB
  • MOBO: Gigabyte Z690 AORUS MASTER
  • PSU: Corsair HX1500i, Case: Fractal Design Define 7 (PCGH edition)
  • Misc.: Logitech G915, Evoluent Vertical Mouse, shuttlePROv2

 

 

NickHope wrote on 9/16/2018, 1:21 AM

Storyboard issue which is not mentioned in Nick's or Vegas official issues....

As there seem to be a number of issues with the new storyboard feature, I'm guessing there will be some fixes in the next update. So I'm waiting for that and will attempt to clarify and add any remaining issues to the Known Issues thereafter.

Former user wrote on 9/18/2018, 3:50 PM

VEGAS Pro 16 is worse in stability than previously version. Putting some 4K 60p vids XAVC-S and some Pixel 2 XL movies make it crash very often. There are two situations:

  • VERSION 1 of crashing:

VEGAS stops and displaying windows that it stopped working.

  • VERSION 2 of crashing:

VEGAS just turns off itself without displaying error or something.

  • Storyboard works excellent, but displacement videos on the timeline is very lagged 💻

 

I'm using laptop which has i7-7500U and Intel HD620 graphics working under Windows 10 Home edition.

Martin L wrote on 9/19/2018, 12:49 AM

I can join the ranks of those who have VP16 crashing at startup. I have the update 2 installed and it runs very nicely for 30-60 minutes, then it crashes. When it does there is no way to get it started again. Each attempt to start it up ends at "Creating windows" where it freezes and never wakes up. Actually the entire computer then stops and even Task Manager doesn't work. The only thing I can do then is to force a restart. After doing that VP16 is unusable, always freezes at "Creating windows".

The only work-around I found is to unistall VP16 and install it again. Then it works for 30-60 minutes after which the same things happen again.

Also, when Vp16 does work, timeline events are slow to be dragged using ripple, as someone else has mentioned.

Also, since I've been installing and uninstalling it a number of times now I think the registry is a litte messed up. Don't know how to make a total cleaning of it. NewBlue Titler Pro 5 is hardly working now.

I hope next update will address this crash problem.

Sadly I am forced to use VP15 for now but I can't wait to see a fixed and stable VP16.

Fiola wrote on 9/19/2018, 6:25 AM

Ok. Today, I will let speak my video instead of my wall of text. I want to showcase you VEGAS 16 experience - first 3 minutes in simple project with some layers + music - all MP4 UHD 16:9 files. With HW acceleration on. On i9 Intel rig with NVIDIA GTX 1080 Ti and 64 GB RAM. It is real use-case scenario. This project I opened it's regular video production work. On top of that I also included small replication of similar case for Adobe Premiere for you to see, there are no problems on the same rig as in VEGAS.

Especially @gary, please, look on the video!

Problem video:

Final rendered video:

(Final video I am giving you here to see, that we are still able to finish project somehow, but hey... you know, the time spent on crashing and re-opening project every few minutes is really annoying).

Guys, you need to really step it up this time. Address stability and this problem I am showing right away, it's replicable on all of our computers AMD/INTEL doesn't matter! There is no way you can't replicate this in your office. If so, I am still waiting for your RIG recommended configuration - I want to build PC specifically from your provided specs - to see, if I can replicate that or not. (Yes, I am that crazy person, that I will invest blindly in that rig).