VEGAS Pro 16 Update 2 (build 307) - General Discussion

Comments

joost-berk wrote on 11/13/2018, 12:47 PM

NO NO NO! Do this right. Stop complaining, and take action. Open a support ticket, and read the FAQ and troubleshooting guides.

yeah that would a 1000 tickets.... got a blue screen yesterday.... this software at the price should not have these issues, started using pro 15 again just to get by for now... at least it works without issues...

If you experience BSOD on your machine, please check if your system is healthy. Because this often is related to a hardware issue. It will never happen that Vegas triggers a crash of Windows.

You probably experience the same problems with an other NLE, so don't blame it all on Vegas please.

Vegas Pro user since version 1.2

OS: Windows 10 Pro 1809

CPU: Intel Core i7-7820X

RAM: 32GB

GPU: Nvidia GeForce GTX 1080 8GB GDDR

Monitoring: Black Magic Design DeckLink SDI 4K

Audio: M-Audio M-Track Eight ASIO

Controller: Behringer X-Touch

joost-berk wrote on 11/13/2018, 12:50 PM

So far so good. The File > Render As = HANG bug appears to be fixed! I've opened, worked on and exported five projects since updating without a hiccup... SWEET!

This is great news! It was one of my most annoying bugs with Vegas! I will test this my self later, hope it is time to open the champagne! :-)

Vegas Pro user since version 1.2

OS: Windows 10 Pro 1809

CPU: Intel Core i7-7820X

RAM: 32GB

GPU: Nvidia GeForce GTX 1080 8GB GDDR

Monitoring: Black Magic Design DeckLink SDI 4K

Audio: M-Audio M-Track Eight ASIO

Controller: Behringer X-Touch

SoundVisions wrote on 11/15/2018, 6:45 AM

Just bought my license for Pro 16 307 trial (support made an audio guy feel very welcome) & from my green horn view point it's stable and quite easy to get a handle on. Thanks to all in the forums for encouraging energy & excellent content, that's all for now folks.

Last changed by SoundVisions on 11/15/2018, 6:46 AM, changed a total of 1 times.

Windows Pro 10 64x; i7 Intel xCore 8th gen 8700K 4.2Ghz; Asus X299 Prime-A; Corsair Vengeance LPX 64 GB RAM; NH-D15 Cooler; EV3A Supernova 650 G3; Samsung 960 EVO SSD. 5TB; Seagate 4TB HDD; WD 2 TB USB; Startech VIA Firewire; GeForce GTX1050Ti; Waves - WSG Server One; Midex-8; Cubase Pro 9.5/10.0.5; Vegas Pro 16 - 307; Ableton 10; MOTIF XF; TD-30 VDrums; Akai S5000; XR1, Focusrite ClarettPre8; Focusrite Voice Master; Yamaha SPX 900; Allen & Heath Mix Wiz 16; POD X3Pro; Samsung 27" , 22" Samsung, 20" Acer (by kit) monitor... (Waves Platinum /API /Abbeyroad /SSL 4000/ Sig Series Vocals/ VSeries /Scheps Omni Channel / H-Series /PRS SuperModels /Gtr3 /CLA CC / L3 16/ CLA Collection / Maserati /Video Sound Suite /JPP Analog Legends / Kramer Tape Transistors & Transistors / Grand Masters / Renaissance Maxx / Softtube / NuGen/ Bias/ Flux/ Addictive Keys, Inspire Virtual Keyboards)...

timothy-f wrote on 11/15/2018, 8:48 AM

I am also having crashing issues as well, especially with rendering. How do I get a support ticket? I use an Intel i7-8700k, Windows 10 Professional, EVGA Geforce GTX 1060 video card, and have 32 GB of RAM.

Tony-Rockliff wrote on 11/15/2018, 8:56 PM

I had thought that the black screen freezes when pressing the spacebar, and the other random crashes that happen every session were due to my system configuration, NVidia GeForce 1080TI etc., but I now have Vegas 16 build 307 on a completely different 2nd system with an Intel HD 630 card, and I get exactly the same crashes, plus a new one where the whole screen becomes frosted white and I can only close Vegas by going to another monitor so I can access the Task Manager.

With most of the freezes there is no error message so I can't tell if a plugin is causing it or not. I used to love the stability in earlier versions of Vegas but unfortunately can't go back because not even Version 15 will open Version 16 projects. On one booting crash on the NVidia system there was an error message that said that HitFilm Pro was the problem so I had to uninstall that before I could get into Vegas. I don't remember the black screen freeze before V15.

Seeing so many others having crashing problems in more recent versions of Vegas with new features makes me wish that the developers would put a lot more attention on getting Vegas stable before adding even more unstable features to the mix (Stabilizer, Hitfilm Pro, Storyboard). Reminds me a lot of Magix's Sampltude development which for many years followed a similar track of new features over stability. Thankfully the latest Samp version seems rock-solid stable, at least for me, on both systems.

karma17 wrote on 11/16/2018, 3:52 PM

The crazy thing is once Vegas 16 survives this trial by fire, we will be enamored with it, but then time to move to 17.

donde wrote on 11/16/2018, 10:39 PM

I've had a crashing on startup issue from with both the original and 307 builds. Sometimes it would simply vanish after loading all the VSTs. Other times it would show the Problem Report window. At no time did it draw the User Interface.

I used the trouble shooting tips to one-by-one disable the VST folders (by renaming them). On my desktop, renaming Program Files/Steinberg to Steinberg.X got me going. On my laptop it was Program Files(x86)/vstplugins to vstplugins.X

Once Vegas started, I went to Options - Preferences - VST Effects. Both text fields were empty by default (and this may be the cause of the issue as there were a TON of effects in the VST list already including a bunch of MIDI things from ACID and Samplitude and even more stuff. Perhaps Vegas does some sort of exhaustive search when the fields are blank, and the MIDI dlls I had in both Steinberg and vstplugins folders seemed to cause the bomb out.

I simply put C:\Program Files\Steinberg\VstPlugins in the first field (Default VST search folder). Click APPLY, OK, then exit and restart Vegas. Worked! Rename the VST folders to their original names... and retry it STILL WORKS !! Lol.

I don't remember having this problem in Vegas Pro 15, so either the Default VST fields had default search folder text values after install, or the algorithm to find VSTs changed.

Took a lot of work and uninstall/reinstalls to figure this out. Hope it helps someone.

Don

Industrystandard wrote on 11/17/2018, 5:05 AM

I can add some information that may be helpful for the developers. I run Vegas Pro on Windows 10, 32GB, i5-4570, NVIDIA GTX 770 with latest drivers.

I also expericence rather random crashes with Build 307. But there seems to be a faint pattern. Crashes tend to happen more often when

- I edit and play back clips quickly on the timeline, with quick jumps from one point in time to another

- clips with speed changes on more than one layer are involved

- clips are 4K MP4 (H.264) from Panasonic GH-4

- preview display is enabled on a second monitor (using the Windows graphics card)

Crashes during rendering are quite rare, which is a good thing. They are also rare when I work more slowly just color correcting for example, from still point to still point with no quick changes between playback and stop.

To me this looks like the culprits may hide 1) in H.264 handling, 2) in file access (feels somewhat related to the old iosomething.dll problem prior to Vegas 12). This is just a guess, but it feels like several parallel threads are not safe and tend to kill each other.

Please don't stop to improve Vegas! The "scrub in thumbnails" feature is a great and much needed addition, in a hopefully future stable environment a great leap forward for Vegas.

Yes I’ve also picked up this “faint pattern”!

Roberto65 wrote on 11/18/2018, 9:19 PM

Hi,

not sure if I am the only one experiencing this, but if HItFilm Ignite Express 2017 (latest version available on HitFilm website) is installed, then when Vegas Pro 16 Edit is launched, it crashes when it is building the plug-in list.
Not sure about Ignite Pro (I am out for 2 weeks so I can´t try right now...).
Would be nice to have this fixed...

Cheers

Roberto

Former users wrote on 11/20/2018, 5:46 AM

Hi,

not sure if I am the only one experiencing this, but if HItFilm Ignite Express 2017 (latest version available on HitFilm website) is installed, then when Vegas Pro 16 Edit is launched, it crashes when it is building the plug-in list.
Not sure about Ignite Pro (I am out for 2 weeks so I can´t try right now...).
Would be nice to have this fixed...

Cheers

Roberto

Yes,

Here too happened.

1.Uninstall Ignit Pro

2.Start Vegas.

3.Close Vegas

4.Reinstall Ignit Pro.

5.Start Vegas once more and it will recognize Ignite Pro.

jorgeandresb3 wrote on 11/20/2018, 7:43 AM

it's a big change d vegas 15 to 16, but vegas pro16, does not use 100% of the microprocessor to export a video.

Premiere pro if you use 90% -100% of the microprocessor including the gpu.

After all, I really like the update.

jorgeandresb3 wrote on 11/20/2018, 9:36 AM

I have a problem, a project generated in vegas pro 15, if I open it in vegas pro 16 the timeline in reproduction is very slow. Does anyone know what the problem is ?

j-v wrote on 11/20/2018, 11:30 AM

Patience?

met vriendelijke groet
Jan

Camera : Pan X900, GoPro Hero7 Hero Black, Samsung Galaxy A8
Desktop :MB Gigabyte Z390M, W10, i7 7900 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 15,16,17 and VMS PL 15,16 are installed
Both Nvidia GPU's have driver version 431.86 Studio Drivers
TV      :LG 4K 55EG960V

Dutch video tutorials for beginners

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

Roberto65 wrote on 11/24/2018, 5:32 AM

Hi,

not sure if I am the only one experiencing this, but if HItFilm Ignite Express 2017 (latest version available on HitFilm website) is installed, then when Vegas Pro 16 Edit is launched, it crashes when it is building the plug-in list.
Not sure about Ignite Pro (I am out for 2 weeks so I can´t try right now...).
Would be nice to have this fixed...

Cheers

Roberto

Yes,

Here too happened.

1.Uninstall Ignit Pro

2.Start Vegas.

3.Close Vegas

4.Reinstall Ignit Pro.

5.Start Vegas once more and it will recognize Ignite Pro.

Hi,

actually I have Ignite Express 2017 (free version).
I will try anyway what you suggest (when I am back, as currently out of home for some days) but I think I already tried to uninstall Ignite Express 2017, then start VP and see that it does not crash, then re-install Ignite Express 2017, start VP again and see that it crashes again.
I will anyway retry with the trial version of Ignite Pro in order to see whether it behaves differently.

Thanks

Roberto

 

arthur7 wrote on 11/24/2018, 1:14 PM

I have used GPU acceleration of my HD 530 internal graphics card (is more stable of crashing instead of my GTX 970M) since version 15 of Vegas. Something is changed with the newest intel drivers for their chipsets and ruined that. I tested to my oldest notebook with HD 4000 and goes the same. I cannot playback any MP4 or MTS file i have in normal speed ranged from (28Mbps to 52Mbps) and without crashing after a while!!! What has happened to that??? Every update to newer version is so stressful because of the anticipation everything goes same or better than before but not worst! Is any other experiencing that kind of problemwith its MP4/AVCHD files in any bitrate?? I use latest Intel drivers 25.20.100.6373 for Windows 10 64bit...

j-v wrote on 11/24/2018, 1:27 PM

Which FX ('s) are added to the events, what is the MediaInfo of your sourcefiles and what are your settings in Option/Preferences/Video for GPU acceleration of video processing?

met vriendelijke groet
Jan

Camera : Pan X900, GoPro Hero7 Hero Black, Samsung Galaxy A8
Desktop :MB Gigabyte Z390M, W10, i7 7900 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 15,16,17 and VMS PL 15,16 are installed
Both Nvidia GPU's have driver version 431.86 Studio Drivers
TV      :LG 4K 55EG960V

Dutch video tutorials for beginners

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

arthur7 wrote on 11/24/2018, 1:40 PM

Only a curve and a LUT but even if i disable them it is the same playback exactly. GPU acceleration is OFF. If i turn it ON is much much worse.. also it crashes a lot.

This is from a i7 6700HQ CPU laptop with 16GB of RAM and SSD...

arthur7 wrote on 11/24/2018, 1:50 PM

Now i disabled the sO4.... decoder internally, i restarted and goes almost perfect! What the heck is happening??? Maybe there should be an updated revision to the internal decoder after all!...

j-v wrote on 11/24/2018, 1:56 PM

I only heard from people with this build that they can use that decoder again.😟

met vriendelijke groet
Jan

Camera : Pan X900, GoPro Hero7 Hero Black, Samsung Galaxy A8
Desktop :MB Gigabyte Z390M, W10, i7 7900 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 15,16,17 and VMS PL 15,16 are installed
Both Nvidia GPU's have driver version 431.86 Studio Drivers
TV      :LG 4K 55EG960V

Dutch video tutorials for beginners

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

arthur7 wrote on 11/24/2018, 2:05 PM

The internal decoder IS NOT WORKING for my HD 530 or 4000 Intel GPU graphics card. It is a fact.. maybe the new drivers from intel did that but surely if MAGIX team search to reconnect the drivers with the decoder properly will be fixed.. sooo when will there be next build of Vegas hopefully fixing (and not adding features) driver support for full GPU accelleration??? 😥

fr0sty wrote on 11/27/2018, 11:45 PM

Or keep an eye out for another driver update, sometimes they break Vegas compatibility, then later fix it with a future release. I've seen that happen with Nviida.

OldSmoke wrote on 11/28/2018, 9:21 AM

I posted this in another thread for VP15 but it might affect VP16 too. In VP15, selectively prerendering with Magix AVC and VCE doesn’t work. The render complete but the preview is still of the timeline and there is no indicator on top marking the rendered section.

Last changed by OldSmoke on 11/28/2018, 2:20 PM, changed a total of 1 times.

Proud owner of Sony Vegas Pro 7, 8, 9, 10, 11, 12 & 13 and now Magix VP15&16.

System Spec.:
Motherboard: ASUS X299 Prime-A

Ram: G.Skill 4x8GB DDR4 2666 XMP

CPU: i7-9800x @ 4.6GHz (custom water cooling system)
GPU: 1x AMD Vega Pro Frontier Edition (water cooled)
Hard drives: System Samsung 970Pro NVME, AV-Projects 1TB (4x Intel P7600 512GB VROC), 4x 2.5" Hotswap bays, 1x 3.5" Hotswap Bay, 1x LG BluRay Burner

PSU: Corsair 1200W
Monitor: 2x Dell Ultrasharp U2713HM (2560x1440)

Widetrack wrote on 11/29/2018, 4:04 PM

I've been trying to learn the new features in V16, Bld307, but Vegas continues to lock up after ~ten minutes of work. I can close it with Task Manager, and re-open without re-startinig the machine. Usually I've had open just one video clip, a Text event and whatever effect I'm trying out. Just now it was the BCC Star Matte OBS, but it happens with even a plain old Vegas effect like Light Rays. Does anyone have any sugestions? Would it help if I went back to the previous build?