anyone ever test QSV from latest intel cpu vs NVIDIA preview ? which one does better?

I tried to install & failed, as well. Then I attempted to direct download and that failed too. Let me know when you guys make an install program that works, please.

It works for the rest of us... try to do a clean install. Completely uninstall Vegas (use a program like Revo Uninstall to make sure all traces of it are removed from the registry as well), and then try to install the latest version.

Thanks - but I was talking about the FX Panel Window´s size and position (it means the GUI Element) - so it must be a bug in the windows layout functionality.

Don't know if you can call it a bug.
The reason is a Windows DPI i.c.w. the Vegas Display High DPI scaling setting.
In my Dutch version that Windows setting looks like this.
Is it chequed you can see your "bug", uncheque it stays as you changed the window of Pan/Crop, FX , a.s.o.

 

check or uncheck does not have any effect on my system. But anyway this strange behaviour was introduced with Update 3 - with the first version and update 1 and 2 there was no issue. So I guess something broke it.

Vegas White Balance FX: Amount of Correction is zero after using eyedropper to select white point. It doesn't matter what color I click on. There is no amount of correction. I have to move the Amount of Correction slider myself while watching RGB amounts of point in a third party utility.

@Karsten-Semmer have you sent bug report to Magix?

UPDATE: Reported on 22/02 (Ticket#2020022117006294) and got reply today (25/02):

I was able to reproduce the issue given the steps provided.  This issue is now escalated to development and QA to be resolved in a future application update

BUG REPORT

The Position and Size of the "Video Event FX" Panel WINDOW is not stored properly.

 

Possible workaround is setup your FX window the way you want it and save as a layout. I have a layout assigned just for compositing and FX application. Open your FX in that layout and it will go to a screen location and size as it was saved. Very handy.

-- tom

Crash after too quickly use "ctrl+z / undo" still exists.

Possible workaround is setup your FX window the way you want it and save as a layout.

@monoparadox This does not work for me: as soon as I save layout, the pan/crop windows size reset to default.

NVENC Render broken. FX window size resets on startup. And what on Earth are you doing with that white balance plugin ???

David & Nick,

But in that case there is a bug because it sometimes works. The last time was just after I had written that story I tried it one more time and it worked. That was itt, never again, Any idea for a working workaround besides renaming the file? I'll try deleting it and rewriting on the spot and see how that goes. But thanks for the replies; it shows that you guys care.

This is just a guess based on my own test; the first time I did it, it appeared to work but I realised my default audio rendering template was set to use .wav and the source was .mp3 and even though I selected the existing filename when rendering, Vegas added the .wav as part of the name so it came out as “test.mp3.wav” which was not the same as the original file “test.mp3”. Thus it appeared to have worked but in fact had created a new file. Is there any chance that’s what you were seeing when it seemed to work?

Thanks to the developers for fixing the bug not saving the track audio plugins when archiving a project. At last I can archive safely and happily! Much appreciated.

Currently on the road for another 2 months but I pulled this update down (install now option) on my Intel Hades Canyon NUC and went w/o incident and is stable. Tried out the new AMD decoding (the NUC has a mini 4gb/hbm2 version of the AMD Vega) and it seems slightly lower in performance compared to the Intel HD630 also onboard. When I get over my Home Again Blues, I'll give it a spin on my full-sized 9900k/Radeon VII system. Anyone know if Vegas17 is supporting h.265 decoding of Canon XF705 or Panasonic EVA1 footage yet?

Update to 421 just simply...fails. OK, fired up the direct download link. Wasn't really paying attention; after all, this is SOP right? Message requesting activation popped up. OK, must be the update triggering the usual. Activated just fine. Load up V17. Lo! Still at build 387 and wanting to update! Any further attempt ( and I made many ranging from another direct download to let the program do it) results in the message: "Vegas Pro 17 is already installed. If you want to reinstall the program, please uninstall the existing version before reinstalling." Not a fan of doing that as I assume I will crawl my way back to build whatever. Any suggestions greatly appreciated.

Uninstall the previous build (you can always download it again if needed), re-install using the download link provided in the update thread OP. That's what I usually have to do when Windows programs won't install/update properly.

Off topic: This has not been linked to Vegas issues, but it's worth noting, if you've updated Windows recently, might want to see if you need to uninstall that update as well.

https://betanews.com/2020/02/15/windows-10-kb4524244-recall/

Thanks for the response - I didn't realize the update was basically a full install. Uninstalling and using the download link didn't solve the problem unfortunately. It is interesting to note that the expanded view of uninstall shows 17.0.421 while the about screen shows 387 which the program seems to agree with as it wants to update. Looking through the fix list, I can't find anything non-trivial to see if 421 might be lurking under the surface. Thanks for the Windows pointer. I'm a bit past the KB referenced which is therefore installed. Uninstalling that KB looks dicey as they want a PC Reset. Looks like 387 for the duration.

@Film_Digital, Often times install problems of this sort are the result of lack of disk drive space. May not be the problem here, but something to look at.

Just tried for the second time to update from VP 17 387. Started VP17, it said there was an update, I said go for it. Took it 10+ minutes to download. I said install immediately, VP17 window disappeared, security window appears (allow VP install...) I clicked yes, and then I get an error - Installer unable to update while VP is running!...

Ok, I tried it again - UGHHH it started the download again from the beginning. and I get the exact same error message - cannot install with VP running. It's not running - the install shut it down and the window disappeared before the security window opened!!!

Trying the direct download and install now!

The Install Immediately feature seems to be broken, exact the same behaviour here. The direct download worked, hopefully for you too :)

Christian

PS: In my case, the ldisk space was surely not a problem...

@VEGASDerek Thanks for that suggesting that possibility; I did a check and there should be enough disk space. @john-rappl, @Christian de Godzinsky. Taking a cue of john-rappl (and finally realizing what direct download really meant from Christian's post also, i.e. not the link posted in the announcement), I went to the Magix site and direct downloaded using their Vegas 17 Pro link. Voila! 421 is now installed. Thanks to all who took valuable time to offer help.

Hello. I'm looking for the direct link to down latest build .exe installation file. (Not the online installer.)
If it's already been posted, sorry, I missed it. Thank you.

Found it in here, tahnks: https://www.vegascreativesoftware.info/us/forum/vegas-pro-17-update-4-build-421--118954/

It is the worst ever....it crash all the time for not specific reason....it is so bug out I'm unable to finish projects I started.....I wish I did never install the update....and total lack of support from tech support create it total nightmare