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

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. 👍

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

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?

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.

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'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.

@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.
 

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.

@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 :-)

@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

Thanks for the update.

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

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).

@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.

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

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

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

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.

@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.

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

@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.

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