Expect an official announcement here later today when the U.S. office in Madison WI wakes up.

I still dont see render dialog upon rendering

Looking good so far. Colorization fx now shows where before did not work. Also looks like the crash has been fixed if you try and open new file while Vegas is opening an existing project. well done Vegas team. Thanks.

All good for me from what I have looked at so far. Keeping fingers crossed that they have got the whole nest of bugs.

Loading Sony A7SIII HEVC 4:2:0 10bit still crashes Vegas. Sources said Magix were going to fix that even if 4:2:2 was never going to happen anytime soon.

Looks like a problem with building proxies using NVENC. it keeps building the proxy over and over, also it's very slow at encoding, only encoding for 50% of the time, also it's encoding at 1080P, if vegas has to playback a proxy file of 1080P60fps many slower computers will have problems. I think anything above 30fps resolution of proxy should drop to 720P automatically and should be an option to choose 720P or 1080P as default option for proxy

in the I / O tab I cannot activate GTX970 in a new update.
In the Video tab I have the GTX970 active.
Game drivers 456.38

in the I / O tab I cannot activate GTX970 in a new update.

It is possible by activating legacy AVC decodingg and after restart the other possibilities become possible.
When I did it, I became all kind of renderproblems and -faults.
The best setting for me is to use the default settings the program finds at the new start for Video and I/O File.

in the I / O tab I cannot activate GTX970 in a new update.
In the Video tab I have the GTX970 active.
Game drivers 456.38

Same for me with 1080Ti card

in the I / O tab I cannot activate GTX970 in a new update.
In the Video tab I have the GTX970 active.
Game drivers 456.38

Mine doesnt display since day 1. RTX2060, seems VP18 cant find my GPU.

only VP17 can detect my RTX2060

I can confirm GPU video decode does not work for Nvidia or INTEL. This is a shameful embarrassment. You need to cancel whoever is beta testing for you, Send a kill signal on this version to disable, and never admit to ever releasing it. I am returning to previous version

@andyrpsmith and @alifftudm95

Which cards does the program find at Help/check for driver updates?

Just tried a render using Magix AVC and looking at task manager it is showing the GPU as using both video encode and encode during the render. (j-v using driver update it finds my 1080Ti just fine and has in in the video tab). Looks like the Auto (off) is still using the GPU as both timeline is good as before and render seems to work as before.

Is there a direct link to the update somewhere?

I tried 3 times now without success. "Cannot perform update while program is running" even if I shut it down.

I would expect there will be an "official" announcement in Forum's News / Patches later today.

Meanwhile try https://www.magix.com/int/support/my-service-center/product-downloads/

Looks like the Auto (off) is still using the GPU as both timeline is good as before and render seems to work as before.

No it's not. I returned to previous version of vegas18, and found to my horror that it also no longer could use gpu for decode, set to auto(off). I chose the reset to default option, restarted vegas original release vp18, and got both intel and nvidia decoding options back. I then reinstalled latest vp18 and this time the video decoder settings stuck. Try choosing default decoder settings for FILE IO and restarting. it is possible it will work fine

I can confirm GPU video decode does not work for Nvidia or INTEL. This is a shameful embarrassment. You need to cancel whoever is beta testing for you, Send a kill signal on this version to disable, and never admit to ever releasing it. I am returning to previous version

No issues here on my 1080ti.

Although, I should note that I did install the Studio Driver they released a couple of days ago.

Also QSV rendering is functioning appropriately.

So far, so good.

Yes, all their testing may have been done with latest studio drivers, and it all worked, and if you already have those installed, maybe everything works without problem. If not, while in file IO, click "DEFAULT ALL , and restart, it should bring back Nvidia/Intel decoder options

I should also note I did install studio drivers after problem with no gpu decode, and before resetting decoder settings, but It asked me to reset computer, so I took that to mean those drivers are not active yet, but if people reset and still have no decode settings then it means the new drivers did take effect and they need to install new drivers

For those having issues with Hardware Decoding in the latest update, here are some more details of what has changed:

- One of the major sources of crashes in the earlier versions of VEGAS was related to hardware decoding, more specifically, crashes in the drivers. This would occur when the user would actually try to use the hardware decoder (either showing thumbnails, or adding files to timeline). Besides this issue, the user needed to manually set the hardware decoder to use anything other than Intel QSV - it was up to them to set the right decoder.

- In VP18, we decided to detect all hardware decoding solutions available on the system, and try and instantiate them ahead of time (at application startup), to help us automate the process, and make a better choice for the user. However, this caused application crashes/freezes on certain systems with out-of-date drivers. So for Update 1, we move the detection to a separate process which is run when VEGAS starts up. If this independent process crashes or freezes up, VEGAS will simply disable the hardware decoding feature, instead of itself crashing. The detection code is the same as what was available in VP18 original release, just the process it executes in has been moved, so we would not expect users who had this working in VP18 to see problems. We did test this extensively (both internally, and through the beta process), but it is hard to cover all possible cases of OS/Driver configurations, so we will work with those of you who see issues to try and help you resolve it.

- For those of you who see issues with the hardware decoding not showing up, and who have otherwise up to date GPU drivers (which can be verified using the Help -> Check for Driver Updates feature), please post the contents of the files in the following folder "C:\Users\<USERNAME>\AppData\Local\MAGIX\FileIO\1.0" (replace <USERNAME> with your actual Windows user account name). In case of normal detection, there will be a file called "So4HardwareDetectionOutput.xml", otherwise there will be a file called "So4HardwareDetectionError.log". Please post the contents of the latter file if you run into issues, or contact me directly via a PM.

In my case, things now appear to work provided I disable my Intel driver (even though latest driver installed) before running VP18 and leaving just the Nvidea drivers. No need for me to rename So4Reader.dll any more.

@Video_flaneur: Do you also have your Windows 10 machine up to date? We have found that sometimes the latest drivers will not work correctly with older versions of Windows. For the situation you face otherwise, we do plan to enhance this detection process going forward, so that if we run into problems with a particular driver, we only disable that, instead of disabling everything - in your case, that would allow you to continue to use your NVIDIA decoder, and not have to manually disable the Intel device. As this has been such a troubling aspect of the VEGAS experience, we decided to go for the conservative approach first.

For those having issues with Hardware Decoding in the latest update, here are some more details of what has changed:

- One of the major sources of crashes in the earlier versions of VEGAS was related to hardware decoding, more specifically, crashes in the drivers. This would occur when the user would actually try to use the hardware decoder (either showing thumbnails, or adding files to timeline). Besides this issue, the user needed to manually set the hardware decoder to use anything other than Intel QSV - it was up to them to set the right decoder.

- In VP18, we decided to detect all hardware decoding solutions available on the system, and try and instantiate them ahead of time (at application startup), to help us automate the process, and make a better choice for the user. However, this caused application crashes/freezes on certain systems with out-of-date drivers. So for Update 1, we move the detection to a separate process which is run when VEGAS starts up. If this independent process crashes or freezes up, VEGAS will simply disable the hardware decoding feature, instead of itself crashing. The detection code is the same as what was available in VP18 original release, just the process it executes in has been moved, so we would not expect users who had this working in VP18 to see problems. We did test this extensively (both internally, and through the beta process), but it is hard to cover all possible cases of OS/Driver configurations, so we will work with those of you who see issues to try and help you resolve it.

- For those of you who see issues with the hardware decoding not showing up, and who have otherwise up to date GPU drivers (which can be verified using the Help -> Check for Driver Updates feature), please post the contents of the files in the following folder "C:\Users\<USERNAME>\AppData\Local\MAGIX\FileIO\1.0" (replace <USERNAME> with your actual Windows user account name). In case of normal detection, there will be a file called "So4HardwareDetectionOutput.xml", otherwise there will be a file called "So4HardwareDectectionError.log". Please post the contents of the latter file if you run into issues, or contact me directly via a PM.

in my case there is no file present at all in fileio\1.0

For those having issues with Hardware Decoding in the latest update, here are some more details of what has changed:

- One of the major sources of crashes in the earlier versions of VEGAS was related to hardware decoding, more specifically, crashes in the drivers. This would occur when the user would actually try to use the hardware decoder (either showing thumbnails, or adding files to timeline). Besides this issue, the user needed to manually set the hardware decoder to use anything other than Intel QSV - it was up to them to set the right decoder.

- In VP18, we decided to detect all hardware decoding solutions available on the system, and try and instantiate them ahead of time (at application startup), to help us automate the process, and make a better choice for the user. However, this caused application crashes/freezes on certain systems with out-of-date drivers. So for Update 1, we move the detection to a separate process which is run when VEGAS starts up. If this independent process crashes or freezes up, VEGAS will simply disable the hardware decoding feature, instead of itself crashing. The detection code is the same as what was available in VP18 original release, just the process it executes in has been moved, so we would not expect users who had this working in VP18 to see problems. We did test this extensively (both internally, and through the beta process), but it is hard to cover all possible cases of OS/Driver configurations, so we will work with those of you who see issues to try and help you resolve it.

- For those of you who see issues with the hardware decoding not showing up, and who have otherwise up to date GPU drivers (which can be verified using the Help -> Check for Driver Updates feature), please post the contents of the files in the following folder "C:\Users\<USERNAME>\AppData\Local\MAGIX\FileIO\1.0" (replace <USERNAME> with your actual Windows user account name). In case of normal detection, there will be a file called "So4HardwareDetectionOutput.xml", otherwise there will be a file called "So4HardwareDectectionError.log". Please post the contents of the latter file if you run into issues, or contact me directly via a PM.

Theres no file in my file i/o too