VP17 Update 5 & VEGAS Image/Effects Update 3 - General Discussion

Bri-Hageman wrote on 5/27/2020, 11:04 AM

Dear Community,

The fifth update for VEGAS Pro 17/VEGAS POST (build 452) and the third update for VEGAS Image (version 1.2) and VEGAS Effects (version 1.3) have all just been released. Please give us your feedback in this thread.

If you already have an earlier build, there is no need to uninstall it. The latest build 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, please refer to our official announcement with patch notes.

I hope you all are staying safe and healthy. Have a great rest of your week.

Sincerely,

Bri

Comments

LongIslander wrote on 5/27/2020, 11:24 AM

Thank You Vegas Team!!!! 😁My memory usage is finally comparable if not better than vegas 16 now.

"Handling of HEVC media has been improved" Additionally large imports are MUCH smoother now!

 

alifftudm95 wrote on 5/27/2020, 11:29 AM

HEVC media still laggy playing at 7FPS in timeline. Its a 10bit media in 8 bit project. I also disable so4 compound for stability.

LAPTOP

Dell Inspiron 15 7577 4K 8Bit Screen

CPU: Intel i7 7700HQ

GPU: GTX 1060 6GB Max-Q

RAM: 16GB RAM

Storage: 128GB SSD & 1TB HDD

 

PC DEKSTOP

CPU: Ryzen 5 3600 X

GPU: RTX2060 6GB

RAM: 16GB 2666MHZ

Storage: 480GB SSD & 1TB HDD

 

LongIslander wrote on 5/27/2020, 12:25 PM

I render proxies on all my media; so a smooth preview window is a non issue for me. HEVC media did have a huge memory issue that has clearly been fixed. 👍

michael-harrison wrote on 5/27/2020, 3:29 PM

It would appear that the saving of window positions has been fixed though that's not in the release notes

System 1:

Processor        Intel(R) Core(TM) i7-8700 CPU @ 3.20GHz, 3192 Mhz, 6 Core(s), 12 Logical Processor(s)

BaseBoard Product        ROG STRIX Z390-E GAMING

Installed Physical Memory (RAM)        32.0 GB

Adapter Description        NVIDIA GeForce GTX 1660

Driver Version        Studio <the latest stable>

Resolution        1920 x 1080 x 60 hertz

Video Memory 6G GDDR5

 

System 2:

Lenovo Yoga 720

Core i7-7700 2.8Ghz quad core, 8 logical

16G ram

Intel HD 630 gpu

Nvidia GTX 1050 gpu

michael-harrison wrote on 5/27/2020, 3:31 PM

Can we get more information on these updates?

  • Fixed problem where white balance did not work
    • What version can we compare it to and is there a reference project we can compare with? I saw a difference in WB behavior going from 15 to 17, is that the "problem?"
  • Improved the preferences for hardware decoding to help simplify the user experience
    • Where?

System 1:

Processor        Intel(R) Core(TM) i7-8700 CPU @ 3.20GHz, 3192 Mhz, 6 Core(s), 12 Logical Processor(s)

BaseBoard Product        ROG STRIX Z390-E GAMING

Installed Physical Memory (RAM)        32.0 GB

Adapter Description        NVIDIA GeForce GTX 1660

Driver Version        Studio <the latest stable>

Resolution        1920 x 1080 x 60 hertz

Video Memory 6G GDDR5

 

System 2:

Lenovo Yoga 720

Core i7-7700 2.8Ghz quad core, 8 logical

16G ram

Intel HD 630 gpu

Nvidia GTX 1050 gpu

3d87c4 wrote on 5/27/2020, 3:36 PM

I'm afraid I haven't been following/understanding all the new Vegas packages... How do I know whether the Vegas Image or Vegas Effects updates are relevant to me?

I'm assuming that if I have to ask, they aren't...but just in case, figured I'd ask.

NickHope wrote on 5/27/2020, 3:46 PM

It would appear that the saving of window positions has been fixed though that's not in the release notes

@michael-harrison Do you mean this issue? That one is not fixed for me.

NickHope wrote on 5/27/2020, 3:48 PM

I'm afraid I haven't been following/understanding all the new Vegas packages... How do I know whether the Vegas Image or Vegas Effects updates are relevant to me?

I'm assuming that if I have to ask, they aren't...but just in case, figured I'd ask.

@3d87c4 If you bought or subscribe to VEGAS POST then they're relevant to you. Otherwise not.

michael-harrison wrote on 5/27/2020, 3:52 PM

@NickHope

I *think* it's working for me. So far, VP is consistently bringing up the various windows where I had them on exit. Even an even fx window came up where it belonged even though it wasn't visible on startup.
 

System 1:

Processor        Intel(R) Core(TM) i7-8700 CPU @ 3.20GHz, 3192 Mhz, 6 Core(s), 12 Logical Processor(s)

BaseBoard Product        ROG STRIX Z390-E GAMING

Installed Physical Memory (RAM)        32.0 GB

Adapter Description        NVIDIA GeForce GTX 1660

Driver Version        Studio <the latest stable>

Resolution        1920 x 1080 x 60 hertz

Video Memory 6G GDDR5

 

System 2:

Lenovo Yoga 720

Core i7-7700 2.8Ghz quad core, 8 logical

16G ram

Intel HD 630 gpu

Nvidia GTX 1050 gpu

VEGASDerek wrote on 5/27/2020, 3:53 PM

It would appear that the saving of window positions has been fixed though that's not in the release notes

@michael-harrison Do you mean this issue? That one is not fixed for me.

I can confirm the item the Nick is referring to is not fixed in this update. Michael must be referring to something different.

michael-harrison wrote on 5/27/2020, 4:00 PM

@VEGASDerek

@NickHope

I'm definitely seeing failure of that bug. :-) In other words, it's working like it's supposed to, for me.

event/video fx window placement and size is being restored on restart. Sounds like it's intermittent (someone forget to init a variable?) or a dev snuck a fix in.

I can post a video if you like :-)

System 1:

Processor        Intel(R) Core(TM) i7-8700 CPU @ 3.20GHz, 3192 Mhz, 6 Core(s), 12 Logical Processor(s)

BaseBoard Product        ROG STRIX Z390-E GAMING

Installed Physical Memory (RAM)        32.0 GB

Adapter Description        NVIDIA GeForce GTX 1660

Driver Version        Studio <the latest stable>

Resolution        1920 x 1080 x 60 hertz

Video Memory 6G GDDR5

 

System 2:

Lenovo Yoga 720

Core i7-7700 2.8Ghz quad core, 8 logical

16G ram

Intel HD 630 gpu

Nvidia GTX 1050 gpu

michael-harrison wrote on 5/27/2020, 4:24 PM

@NickHope @VEGASDerek

ok, more info. Looks like the fx position survives a restart of VP but doesn't survive a reboot of the machine.

I restarted vp three times and the fx window always came back where I left it.

I rebooted my machine and it came back in the default position and size

System 1:

Processor        Intel(R) Core(TM) i7-8700 CPU @ 3.20GHz, 3192 Mhz, 6 Core(s), 12 Logical Processor(s)

BaseBoard Product        ROG STRIX Z390-E GAMING

Installed Physical Memory (RAM)        32.0 GB

Adapter Description        NVIDIA GeForce GTX 1660

Driver Version        Studio <the latest stable>

Resolution        1920 x 1080 x 60 hertz

Video Memory 6G GDDR5

 

System 2:

Lenovo Yoga 720

Core i7-7700 2.8Ghz quad core, 8 logical

16G ram

Intel HD 630 gpu

Nvidia GTX 1050 gpu

set wrote on 5/27/2020, 6:49 PM

Thanks for the update.

Just been updated without issues. Prefer to install from downloaded 'offline installer'.

fifonik wrote on 5/27/2020, 7:01 PM

Thanks for the update.

For me the Pan/Crop window size/position issue is not fixed as well. This is sad.

@michael-harrison You could check if VP is actually disappearing from Task Manager when closed. This might prevent the windows position from resetting. Also, it was discussed that the window position resets only if the window closed (and not docked).

Last changed by fifonik on 5/27/2020, 7:02 PM, changed a total of 1 times.

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

Ivey-League-Films wrote on 5/27/2020, 7:05 PM

@VEGASDerek, it appears that no one fixed the 4096 x 2160 issue that has been reported more than once. There is still no option to render at that resolution and it will not let me do a custom template to create it, either. I was really banking on this being fixed. I know there is a work around with using the 8K settings, but we should not have to do that.

set wrote on 5/28/2020, 12:31 AM

General quick advice:

after update, recommended to restart your system, even though you probably not requested by the system.

I had little weird here when opening a previous project, but after restart, the project going back to normal. Not sure if MP4 issue (reported on other post) is also solved by restarting (problem is I didn't experience that issue!)

Howard-Vigorita wrote on 5/28/2020, 1:17 AM

Seeing an inability to render to 4k running the Sample Project benchmark with build 452 using the Magix avc Nvidia encoder on my Dell laptop when decoder is also set to Nvidia. Build 421 exhibited the same problem but only when rendering to NVenc. 452 bombs out rendering to MC and QSV too. I suspect it's a limitation of the gtx1050ti gpu being overwhelmed my the media generator in that test project. Everything else I threw at it rendered just fine. Also tested 452 on my Radeon VII system and it seems the the top quality hevc play is significantly better under 452... I was able to play a test hevc file at Good-Full with no drop in frame rate with the Radeon VII under 17.421. Build 452 can now play it at Best-Full. Put all the numbers I got so far online here. Got to do some license shuffling before I can bench my other systems.

EDIT: build 452, not 451

Last changed by Howard-Vigorita on 5/28/2020, 9:46 PM, changed a total of 3 times.

Cameras: Z-Cam E2 classic, Canon XF305, JVC GV-LS2, Canon 6D w/L-glass line.
Laptop: Dell XPS15-9570; i7-8750h 32gb (integrated Intel UHD-630 & Nvidia GTX-1050Ti)
Road: Intel NUC i7 8809g 32gb (integrated AMD VegaM 4gb graphics and Intel HD630)
Workstation: i9 9900k 32 gb (Sapphire AMD Radeon VII 16gb graphics and integrated Intel UHD630)
Workstation2: e5 1650v4 128 gb (Sapphire Nitro+ RX5700xt Navi 8gb graphics)
Workstation3: i7-980X 24gb (Sapphire Nitro+ Vega64 8gb graphics)
currently Vegas 17.452 (testing Vegas 18.284)

NickHope wrote on 5/28/2020, 1:28 AM

@Howard-Vigorita Do you mean build 451? The latest build is 452.

RogerS wrote on 5/28/2020, 4:32 AM

Can we get more information on these updates?

  • Fixed problem where white balance did not work
    • What version can we compare it to and is there a reference project we can compare with? I saw a difference in WB behavior going from 15 to 17, is that the "problem?"
  • Improved the preferences for hardware decoding to help simplify the user experience
    • Where?

@michael-harrison The White Balance Fx is now back to normal. It had a few bugs in 17, from forgetting the setting upon closing the project (!) to in the last build having the amount of correction stuck at 0, making it unusable.

The hardware decoding is under File I/O- I think they just made the choices clearer (Intel QSV vs NVIDIA NVENC vs AMD something) and removed the "preferred decoder" language.

michael-harrison wrote on 5/28/2020, 7:38 AM

@RogerS

@michael-harrison The White Balance Fx is now back to normal. It had a few bugs in 17, from forgetting the setting upon closing the project (!) to in the last build having the amount of correction stuck at 0, making it unusable.

The hardware decoding is under File I/O- I think they just made the choices clearer (Intel QSV vs NVIDIA NVENC vs AMD something) and removed the "preferred decoder" language.

IMO they made the HW decoding more confusing. They've now got a checkbox for Intel as well as it appearing in the dropdown at the bottom of that same screen.

Last changed by michael-harrison on 5/28/2020, 7:38 AM, changed a total of 1 times.

System 1:

Processor        Intel(R) Core(TM) i7-8700 CPU @ 3.20GHz, 3192 Mhz, 6 Core(s), 12 Logical Processor(s)

BaseBoard Product        ROG STRIX Z390-E GAMING

Installed Physical Memory (RAM)        32.0 GB

Adapter Description        NVIDIA GeForce GTX 1660

Driver Version        Studio <the latest stable>

Resolution        1920 x 1080 x 60 hertz

Video Memory 6G GDDR5

 

System 2:

Lenovo Yoga 720

Core i7-7700 2.8Ghz quad core, 8 logical

16G ram

Intel HD 630 gpu

Nvidia GTX 1050 gpu

RogerS wrote on 5/28/2020, 7:42 AM

You mean legacy decoding via Intel for HEVC? That's safe to ignore (and wasn't that there before?)

michael-harrison wrote on 5/28/2020, 7:57 AM

@RogerS the dropdown was there before, which makes still having a checkbox confusing.

For example, what happens if I check "Enable legacy HEVC decoding via Intel QSV" AND choose "Hardware Decoder To Use: Nvidia NVDEC"

Which one is it going to use?

As a developer I think these changes were hacked in and not well thought out. It looks like they're doing the minimum they can get away with in order to work around problems in either their or third-party software. I'm all for them doing what they can when they can, but this arrangement is not simplifying anything.

System 1:

Processor        Intel(R) Core(TM) i7-8700 CPU @ 3.20GHz, 3192 Mhz, 6 Core(s), 12 Logical Processor(s)

BaseBoard Product        ROG STRIX Z390-E GAMING

Installed Physical Memory (RAM)        32.0 GB

Adapter Description        NVIDIA GeForce GTX 1660

Driver Version        Studio <the latest stable>

Resolution        1920 x 1080 x 60 hertz

Video Memory 6G GDDR5

 

System 2:

Lenovo Yoga 720

Core i7-7700 2.8Ghz quad core, 8 logical

16G ram

Intel HD 630 gpu

Nvidia GTX 1050 gpu

michael-harrison wrote on 5/28/2020, 7:58 AM

@VEGASDerek @NickHope Here's a video of the window position and size being restored as expected.

System 1:

Processor        Intel(R) Core(TM) i7-8700 CPU @ 3.20GHz, 3192 Mhz, 6 Core(s), 12 Logical Processor(s)

BaseBoard Product        ROG STRIX Z390-E GAMING

Installed Physical Memory (RAM)        32.0 GB

Adapter Description        NVIDIA GeForce GTX 1660

Driver Version        Studio <the latest stable>

Resolution        1920 x 1080 x 60 hertz

Video Memory 6G GDDR5

 

System 2:

Lenovo Yoga 720

Core i7-7700 2.8Ghz quad core, 8 logical

16G ram

Intel HD 630 gpu

Nvidia GTX 1050 gpu

VEGASDerek wrote on 5/28/2020, 8:01 AM

I was able to make a fix for the resizing problem last week, however this was too late to get into the update.