VEGAS Pro 17 Update 1 (build 321) - General Discussion

Comments

AlesCZ wrote on 10/9/2019, 1:43 PM

I found it not good to turn on NVIDIA NVDEC for me


Very many artifacts, flickering (disable/enable/disable/enable...) effects, black or red video preview ...etc.
This happened if I opened a project shot with a YI camera.
This work for me:

fr0sty wrote on 10/9/2019, 8:57 PM

Make sure you have the latest version the nvidia studio driver installed. Then try nvdec again if not.

Happy wrote on 10/10/2019, 5:18 AM

Thought I'd give VP17 a try...

Load time for a large XAVC project: 13 minutes vs. VP16: under 3 minutes....

Raises the question does my 2014 machine no longer meet the VP17  system requirements?...

(Windows 10 64-bit; Processor Intel Core i7-4700MQ with Intel Turbo Boost Technology, 2.40 / 3.40 Turbo GHz; RAM 16 GB; Graphics NVIDIA GeForce GTX 770M with CUDA Technology and NVIDIA Optimus Technology)

j-v wrote on 10/10/2019, 5:48 AM

Raises the question does my 2014 machine no longer meet the VP17  system requirements?

Look after the needed specifications, your processor is on or below the lowest border and your GPU cannot help by anything.

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 !!!

Dexcon wrote on 10/10/2019, 6:21 AM

Load time for a large XAVC project: 13 minutes vs. VP16: under 3 minutes....

The original release build of VP17 had issues with building thumbnails which drew many comments on the forum after VP17's release. My 135 mins project created in VP16, mostly consisting of XAVC video, took ages to load in VP17 and had virtually no timeline playability - it stuttered and stalled and was unusable. So I am currently finishing the project back in VP16. OTH, a similar 80 mins project created in VP16, also using XAVC video from the same camera with the same settings, and using similar FX etc, works well in VP17.

I'm also using a 2014 computer but with 32GB RAM and a couple of years old AMD graphics card.

Perhaps try starting a completely new project in VP17 to test how that goes before concluding the problem lies with your computer, though that of course may well be the case. But it's one way of knowing with more certainty.

bob-h wrote on 10/10/2019, 7:19 AM

Thought I'd give VP17 a try...

Load time for a large XAVC project: 13 minutes vs. VP16: under 3 minutes....

Raises the question does my 2014 machine no longer meet the VP17  system requirements?...

(Windows 10 64-bit; Processor Intel Core i7-4700MQ with Intel Turbo Boost Technology, 2.40 / 3.40 Turbo GHz; RAM 16 GB; Graphics NVIDIA GeForce GTX 770M

Prob a bug or some setting you can change as a workaround. Boost should work ok with timeline editing, your gpu would do openCL much better than onboard graphics in current Ryzen APU's & your GPU does hardware decoding of h.264 making it suitable for the major graphics upgrade of v17 & should perform better than v16 with timeline editing and render with compatible codec actually bringing new life into your slower cpu

AlesCZ wrote on 10/10/2019, 12:20 PM

Make sure you have the latest version the nvidia studio driver installed. Then try nvdec again if not.

I uses latest version nVidia studio drivers

j-v wrote on 10/10/2019, 1:09 PM

On my new desktop I cannot install that latest Studio driver anymore.
During my install-try I get this message while the Nvidia program controles my system comptability.
Installing those DHC drivers works fine ( untill now)


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 !!!

Happy wrote on 10/10/2019, 2:29 PM

Thought I'd give VP17 a try...

Load time for a large XAVC project: 13 minutes vs. VP16: under 3 minutes....

Raises the question does my 2014 machine no longer meet the VP17  system requirements?...

(Windows 10 64-bit; Processor Intel Core i7-4700MQ with Intel Turbo Boost Technology, 2.40 / 3.40 Turbo GHz; RAM 16 GB; Graphics NVIDIA GeForce GTX 770M

Prob a bug or some setting you can change as a workaround. Boost should work ok with timeline editing, your gpu would do openCL much better than onboard graphics in current Ryzen APU's & your GPU does hardware decoding of h.264 making it suitable for the major graphics upgrade of v17 & should perform better than v16 with timeline editing and render with compatible codec actually bringing new life into your slower cpu

Come to think of it, the minimum system requirements for VP17 were upscaled, so I can imagine demanding tasks like rendering could pose a challenge for my PC, but loading a project requiring a processor load of 10% and a memory load of 30%, doesn't make much sense...

Happy wrote on 10/10/2019, 3:17 PM

On my new desktop I cannot install that latest Studio driver anymore.
During my install-try I get this message while the Nvidia program controles my system comptability.
Installing those DHC drivers works fine ( untill now)


To keep your drivers up to date, you might want to use this link for NVIDIA Automatic Driver Updates software:

https://www.nvidia.com/en-us/geforce/geforce-experience/

or manually:

https://www.nvidia.com/Download/index.aspx?lang=en-us

zdogg wrote on 10/10/2019, 3:21 PM

On my new desktop I cannot install that latest Studio driver anymore.

Do you have Win 10, only works with Win 10.

j-v wrote on 10/10/2019, 3:50 PM

Do you have Win 10, only works with Win 10.

Windows 10 home, version 1903, buildnr. 18362.239

 

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 !!!

bob-h wrote on 10/10/2019, 5:41 PM

 

Come to think of it, the minimum system requirements for VP17 were upscaled, so I can imagine demanding tasks like rendering could pose a challenge for my PC, but loading a project requiring a processor load of 10% and a memory load of 30%, doesn't make much sense...

Rendering has always been worse case situation, no boost stuck at 2.5ghz, and as it sounds like you're using a laptop will surely throttle to keep cool. I have had the slow project load with vp15, I believed it to be related to 3rd party plugins as reinstalling vegas did not fix, I uninstalled all plugins and deleted all directories.

I was hoping these varying reports of slowness in editing & rendering were just bugs to be fixed

Dexcon wrote on 10/10/2019, 6:32 PM

@Happy .... if you have a lot of subfolders in your project, especially more than 20, it may be a problem affecting VP17 but not VP16. Have a look at this recent post:

https://www.vegascreativesoftware.info/us/forum/vegas-crashes-on-startup-if-there-s-over-20-sub-folders--117373/

The latest comment was from MAGIX who acknowledge that it is now a known problem and they'll be working on a fix in a future update.

Happy wrote on 10/10/2019, 6:59 PM

@Happy .... if you have a lot of subfolders in your project, especially more than 20, it may be a problem affecting VP17 but not VP16. Have a look at this recent post:

https://www.vegascreativesoftware.info/us/forum/vegas-crashes-on-startup-if-there-s-over-20-sub-folders--117373/

The latest comment was from MAGIX who acknowledge that it is now a known problem and they'll be working on a fix in a future update.

Thanks, no subfolders, only XAVC files (no thumbs loaded), but the low processor load of 10% and memory load of 30% during loading is questionable...