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

Comments

john-rappl wrote on 9/26/2019, 9:12 AM

Just installed 321 and it is still not loading hitfilms movie essentials. I also tried uninstalling and reinstalling Movie Essentials after the VP17 321 update but it is still not being loaded!

I did contact FXhome about this issue at the beginning of Sep (before the VP update) and received the following response. Where is the fix is this update????

A new response has been posted to your ticket:

Hello,


Thank you for contacting FXhome. That compatibility requires an update to VEGAS Pro 17, and I believe Magix plans to include it in the next update to that software.

 

Regards,

Axel Wilkinson
HitFilm Support

 

Alexandre wrote on 9/26/2019, 9:35 AM

How do I go back to the Vegas Pro version 17.0 Build 284? The new version is not functioning properly.

LongIslanderrr wrote on 9/26/2019, 3:12 PM

Seems Stabler.. but still had a crash when editing (feels thumbnail related) waiting on update. No issues on V16 for me.

set wrote on 9/27/2019, 10:18 AM

https://www.vegascreativesoftware.info/us/forum/faq-where-can-i-download-vegas-pro-and-other-vegas-software--104782/

If you need to go back to previous build, look at no 5

Paul-Fierlinger wrote on 9/27/2019, 1:13 PM

Usage of High DPI scaling in Display settings.

Can someone explain this experimental feature for me? I have experimented with the DPI selection turned off and on and it appears to give me better graphics definition when turned on. For instance when I have a built in pan across a lengthy background which I animated in 12fps within my animation software TVP and then export to Vegas as 24fps I see less stuttering (or actually NO stuttering!). The differences are subtle because I know when I can get away with this and when not.

For instance, If the drawing of a street depicts a downhill slant I can get away with this 12 versus 24 fps discrepancy because the human eye can be better fooled when vertical lines repeat themselves twice but each second instance is a fraction of a milometer lower lower lower than the first.

But when I have the Vegas DPI scaling turned on it seems to me that the stuttering completely disappears making for a wonderful hidden cheat. Can I be right or is this just wishful thinking on my part which fools itself into believing there is indeed "improvement" when the feature has nothing to do with what I am expecting of it.

Len Kaufman wrote on 9/27/2019, 3:25 PM

I received this message from Magix today and something different from NewBlue, blaming Magix:

"Hello

Thank you for your message.

VEGAS Pro 17 had a change to its video plugin host id. The third party plugins which are missing will require an update since they are host locked with the old VEGAS id. You will need to get the update from the third party plug in provider.
--
Thank you for contacting Magix Support.

Best regards,
XXXXXXXXXXX
MAGIX Software GmbH
XXXXXXXXXXX
XXXXXXXXXXXXXXX
XXXXXXXXXXX
XXXXXXXXX

MagixD....(can I use your ID?). Thank you for removing the name of the person who sent the above. Sorry. My bad!

joseph-desaavedra wrote on 9/27/2019, 3:49 PM

No AMD decode, thought that was the priority?


I'm glad I took my AMD card back after all

 CPU Name
AMD Ryzen Threadripper 1950X 16-Core Processor
Threading
1 CPU - 16 Core - 32 Threads
Frequency
3466.73 MHz (34.75 * 99.76 MHz) - Uncore: 1596.2 MHz
Multiplier
Current: 34.75
Architecture
Threadripper / Stepping: ZP-B1 / Technology: 14 nm
CPUID / Ext.
F.1.1 / 17.1
IA Extensions
MMX(+), SSE, SSE2, SSE3, SSSE3, SSE4.1, SSE4.2, SSE4A, x86-64, AMD-V, AES, AVX, AVX2, FMA3, SHA
Caches
L1D : 32 KB / L2 : 512 KB / L3 : 8192 KB
Caches Assoc.
L1D : 8-way / L2 : 8-way / L3 : 16-way
Microcode
Rev. 0x8001137
TDP / Vcore
180 Watts / 1.212 Volts
Temperature
63.5 °C / 146 °F
Type
Retail
Cores Frequencies
#00: 3466.73 MHz #01: 3491.67 MHz #02: 3466.73 MHz #03: 3466.73 MHz
#04: 3491.67 MHz #05: 3491.67 MHz #06: 3466.73 MHz #07: 3466.73 MHz
#08: 3491.67 MHz #09: 3441.79 MHz #10: 3491.67 MHz #11: 3466.73 MHz
#12: 3466.73 MHz #13: 3491.67 MHz #14: 3466.73 MHz #15: 3466.73 MHz
Motherboard
Model
Gigabyte X399 AORUS XTREME-CF
Socket
Socket SP3r2 (4094)
North Bridge
AMD Ryzen SOC rev 00
South Bridge
AMD X399 rev 51
BIOS
American Megatrends Inc. F5i (05/08/2019)
AMD AGESA
SummitPI-SP3r2-1.1.0.2
Memory (RAM)
Total Size
32768 MB
Type
Quad Channel (256 bit) DDR4-SDRAM
Frequency
1596.2 MHz (DDR4-3192) - Ratio 1:16
Timings
16-18-18-38-56-1 (tCAS-tRC-tRP-tRAS-tCS-tCR)
Slot #1 Module
G.Skill 8192 MB (DDR4-2137) - XMP 2.0 - P/N: F4-3200C16-8GTZR
Slot #2 Module
G.Skill 8192 MB (DDR4-2137) - XMP 2.0 - P/N: F4-3200C16-8GTZR
Slot #3 Module
G.Skill 8192 MB (DDR4-2137) - XMP 2.0 - P/N: F4-3200C16-8GTZR
Slot #4 Module
G.Skill 8192 MB (DDR4-2137) - XMP 2.0 - P/N: F4-3200C16-8GTZR
Graphic Card (GPU)
GPU Type
NVIDIA GeForce RTX 2080 Ti (TU102-300) @ 300 MHz
GPU Brand
EVGA Corp.
GPU Specs
TU102-300 / Process: 12nm / Transistors: 18600M / Die Size: 754 mm² / TDP: 260W
GPU Units
Shader Units: 4352 / Texture Units (TMU): 272 / Render Units (ROP): 88
GPU VRAM
11264 MB GDDR6 352 bit @ 405 MHz (Samsung)
GPU APIs
DirectX 12.0 (12_1) / OpenGL 4.5 / OpenCL 1.2 / Vulkan 1.0
Storage (HDD/SSD)
Model #1 Name
Seagate ST8000VN0022-2EL112 (FW: SC61)
Model #1 Capacity
7452.0 GiB (~8010 GB)
Model #1 Type
Fixed - Bus: SATA (11)
Model #2 Name
Samsung SSD 970 PRO 512GB
Model #2 Capacity
476.9 GiB (~510 GB)
Model #2 Type
Fixed, SSD - Bus: NVMe (17)
Model #3 Name
Samsung SSD 960 PRO 1TB
Model #3 Capacity
953.9 GiB (~1020 GB)
Model #3 Type
Fixed, SSD - Bus: NVMe (17)
Model #4 Name
Samsung SSD 970 PRO 512GB
Model #4 Capacity
476.9 GiB (~510 GB)
Model #4 Type
Fixed, SSD - Bus: NVMe (17)
Model #5 Name
Samsung SSD 970 PRO 512GB
Model #5 Capacity
476.9 GiB (~510 GB)
Model #5 Type
Fixed, SSD - Bus: NVMe (17)
Display
Screen #1
Dell Computer DELL P4317Q (DELD084)
Screen #1 Spec
42.5 inches (108 cm) / 3840 x 2160 pixels @ 23-80 Hz
Miscellaneous
Windows Version
Microsoft Windows 10 (10.0) Professional 64-bit
Windows Subver.
Build 18362
CPU-Z Version
1.90.0 (64 bit)

AOM_Management wrote on 9/27/2019, 10:40 PM

I'm using Vegas Post and although I was having a few issue learning how to use the new features and separate programs in Post, I could still access them to learn, BUT, after the 321 build update, the rendering slowed extremely 28 hours to render 1 hour and 40 minutes, and the new features and programs will still open, but nothing works when I try to use them. The buttons/sliders in color grading are now greyed out and can't be used, Vegas Effects, none of the effects work when added. All drivers are up to date. Is there a way to go back to the previous build?

karma17 wrote on 9/28/2019, 3:05 AM

I think V17 will end up being one of the most historic versions of Vegas. Nice to see the kinks getting worked out. I was looking through an old box of stuff the other day and the installation disc for V11 fell out. It is amazing to see how far Vegas has come since then, and yet, someone using V11 wouldn't have a hard time transitioning to V17.

Christopher-Frank wrote on 9/28/2019, 4:07 AM

I did a clean install of Windows because ACID PRO 9 was messing up and crashing so much, I just gave up. So brand new, clean install of windows 10 and guess what??????

1st program I go to install is vegas, and it won't even install... so I went to install my previous version (saved on an external) and it won't install with same error.

 

FOR THE LOVE OF GOD!!! Stop putting out new product to try and get more money in your pockets and FIX THE HUGE NUMBER OF ISSUES!!!!! I'm thinking I'm starting to like Sony a whole lot more... they did nothing with the software for years... probably why it worked PERFECTLY for years. Magix, quite honestly, have no common sense or understanding of what makes a good product. Probably why No one in the industry thinks about their products anymore.

adis-a3097 wrote on 9/28/2019, 5:03 AM

I did a clean install of Windows because ACID PRO 9 was messing up and crashing so much, I just gave up. So brand new, clean install of windows 10 and guess what??????

1st program I go to install is vegas, and it won't even install... so I went to install my previous version (saved on an external) and it won't install with same error.

 

FOR THE LOVE OF GOD!!! Stop putting out new product to try and get more money in your pockets and FIX THE HUGE NUMBER OF ISSUES!!!!! I'm thinking I'm starting to like Sony a whole lot more... they did nothing with the software for years... probably why it worked PERFECTLY for years. Magix, quite honestly, have no common sense or understanding of what makes a good product. Probably why No one in the industry thinks about their products anymore.

Um, did you try installing as administrator?

MagixPascal wrote on 9/28/2019, 9:25 AM

I did a clean install of Windows because ACID PRO 9 was messing up and crashing so much, I just gave up. So brand new, clean install of windows 10 and guess what??????

1st program I go to install is vegas, and it won't even install... so I went to install my previous version (saved on an external) and it won't install with same error.

 

FOR THE LOVE OF GOD!!! Stop putting out new product to try and get more money in your pockets and FIX THE HUGE NUMBER OF ISSUES!!!!! I'm thinking I'm starting to like Sony a whole lot more... they did nothing with the software for years... probably why it worked PERFECTLY for years. Magix, quite honestly, have no common sense or understanding of what makes a good product. Probably why No one in the industry thinks about their products anymore.

@Christopher-Frank Please install https://www.microsoft.com/en-US/download/details.aspx?id=15336 ("Microsoft Visual C ++ 2008 (x64)") and https://www.microsoft.com/en-US/download/details.aspx?id=29 ("Microsoft Visual C ++ 2008 (x86)") before you install. It comes with an Windows update or some installer. Next time before flaming something try to search for a solution in this forum, ask the community or use the live chat with support.

Len Kaufman wrote on 9/28/2019, 10:51 AM

Len Kaufman wrote on 9/28/2019, 11:24 AM

Hooray! I fixed the problem of many of my NewBlue Plugins not working after I updated VP17. The solution was originally suggested by Seth at NewBlue: "clear the cache of the plugins in Vegas." I didn't even know there was a separate cache for the plugins. The path to finding the cache files that Seth suggested didn't work for me, and I was reluctant to restore VP17 to its original install, as I would have lost all the settings, etc. But I found this on a Sony Vegas UK site, and life is good again. The path shown in the second option (in bold) is what worked, but substituting 17 for 14. I'm even sufficiently optimistic to try upgrading my VP17 again! Here's what I found that worked! Addendum: I even did the update to version 321 and everything still seems to be working!

Clear Plug-in Cache
Vegas is notorious for getting its plug-in cache database screwed up. Not updated properly on effects install or uninstall. This affects items showing up in the various effects lists dialogs/panels.
In Vegas 12, 13, 14 this is easily cleaned up by deleting the cache files and Vegas will re-create them the next time it starts up. In the folder
C:\Users\<your user name>\AppData\Local\Sony\Vegas Pro\13.0   (if SV12 then > 12.0)
delete the files “plugin_manager_cache.bin” and “svfx_plugin_cache.bin” and then restart Vegas. Your effects list should be complete.
In 17 the folder is
C:\Users\<your user name>\AppData\Local\VEGAS Pro\17.0 (Substitute 17.0 here.)

ADDENDUM: After doing the above, everything worked fine, for awhile. Then the problem reared its ugly head again. This time, I replicated the steps listed above, but I took an additional step. As I had a previous version of Vegas Pro installed on my computer, I went back into those files and checked the 2 files that we were instructed to remove. Sure enough, even though I hadn't used the previous versions of Vegas lately, the plugin_manager_cache.bin file now had a current date! Somehow, it was connected to V17. I deleted that file, and everything is working again. Let's see how long that lasts!

diverG wrote on 9/28/2019, 2:14 PM

I did a clean install of Windows because ACID PRO 9 was messing up and crashing so much, I just gave up. So brand new, clean install of windows 10 and guess what??????

1st program I go to install is vegas, and it won't even install... so I went to install my previous version (saved on an external) and it won't install with same error.

 

FOR THE LOVE OF GOD!!! Stop putting out new product to try and get more money in your pockets and FIX THE HUGE NUMBER OF ISSUES!!!!! I'm thinking I'm starting to like Sony a whole lot more... they did nothing with the software for years... probably why it worked PERFECTLY for years. Magix, quite honestly, have no common sense or understanding of what makes a good product. Probably why No one in the industry thinks about their products anymore.

 

Sys 1 Gig Z370-HD3, i7 8086K @ 5.0 Ghz 16gb ram, 250gb SSD, 2x2Tb hd,  GTX 1060 6Gb Vegas 14 & 16 plus Edius 8WG Win 10 (1809) BMIP4k video out. (PS 650W)

Sys 2 Gig Z170-HD3, i7 6700K @ 3.8Ghz 16gb ram, 250gb SSD, 2x2Tb, hdd GTX 750ti,  Vegas 14 & 16 plus Edius 8WG Win 10 (1809) BMIP4k video out. (PS 650W)

Sys 3 Laptop 'Clevo' i7 6700K @ 3.0ghz, 16gb ram, 250gb SSd + 2Tb hdd,   nvidia 940 M graphics. VP14 & 15 via humble bundle. Plus Edius 8WG

 

diverG wrote on 9/28/2019, 2:24 PM

After reinstalling W10 allow a couple of days for Windows to update. Once you have good clean install complete with graphics drivers etc make a system image. A clean W10 install will the only take about 15 minutes. We'll worth the effort. Had problems after latest VP17 update so was glad I had a fallback image.

.

Sys 1 Gig Z370-HD3, i7 8086K @ 5.0 Ghz 16gb ram, 250gb SSD, 2x2Tb hd,  GTX 1060 6Gb Vegas 14 & 16 plus Edius 8WG Win 10 (1809) BMIP4k video out. (PS 650W)

Sys 2 Gig Z170-HD3, i7 6700K @ 3.8Ghz 16gb ram, 250gb SSD, 2x2Tb, hdd GTX 750ti,  Vegas 14 & 16 plus Edius 8WG Win 10 (1809) BMIP4k video out. (PS 650W)

Sys 3 Laptop 'Clevo' i7 6700K @ 3.0ghz, 16gb ram, 250gb SSd + 2Tb hdd,   nvidia 940 M graphics. VP14 & 15 via humble bundle. Plus Edius 8WG

 

fr0sty wrote on 9/28/2019, 3:00 PM

The problem you are having is caused by the windows update, not by Vegas. I had that same thing happen to me after windows updated. It also broke all my previous installations. 2 things fixed it:

1. Microsoft makes an uninstall utility that uninstalls software that is being difficult. I had to use it to uninstall the 2015-2019 c++ redistributable package in windows, using the programs and features dialogue box. Then I re-installed it.

2. I had Vegas 17's launch version installed when the windows update ruined it. I had to install the latest version of Vegas 17 to get it working. After this, all my previous versions of Vegas started working again as well.

Edit: I see Pascal got to it first... however, FWIW, it wasn't the 2008 redist that I re-installed to fix it, it was the 2015-2019 redistributeable... though I also updated Vegas, which could have in turn installed the 2008 update and I didn't realize that fixed it, I'm not sure... just listing what I did to fix it.

Stephen-Longo wrote on 9/28/2019, 4:33 PM

I have Vegas Pro 17 Update 1 applied yet the rendering part hangs before completion. I've sent a report to tech team - no word. My laptop runs fine so it may be an isolated issue from my Dell Desktop.

Laci-Kobulsky wrote on 9/29/2019, 6:49 AM

Hey guys, I had this issue with color grading panel, but was waiting for the update to fix it but its still there. Basically the whole interface is messed up, buttons disappearing, sliders go wrong etc.I never seen anything like this in vegas or any of my program. Does anybody know of some fix?

fr0sty wrote on 9/29/2019, 7:58 AM

Can't say I've experienced anything like that. Make a thread for it so we can troubleshoot it and it not get buried under a bunch of unrelated posts.

NCARalph wrote on 9/29/2019, 1:12 PM

The bug in rendering where the "render options" button is grayed out for AC-3 Studio is still there. 😠

Sylk wrote on 9/30/2019, 12:14 AM

The bug in rendering where the "render options" button is grayed out for AC-3 Studio is still there.

Where? What encoder? What template?

[OS] : Windows 10 Ent. x64 v1903 (18362.356) // (18362.295 if posted before 9/24/19)
[NLE] : Vegas Pro 17.0 (Build 321) // (Build 284 if posted before 9/24/19)
[DRV] : Studio 431.86 (Display, PhysX, HD Audio) // (Game Ready 436.15 if posted before 9/24/19)

[GPU] : Gainward GeForce GTX 1080 Phoenix GLH
[CPU] : Intel Core i7-2600K @3.4GHz OC@4.5GHz (HyperThreaded) | AirCooling: Noctua NH-D14
[RAM] : 16GB (4x 4GB GSkill Ripjaws X DDR3 1600MHz 9-9-9-24) @1333MHz
[SSD] : Samsung 850 Pro 256GB
[MOB] : Asus P8P67 Deluxe (Rev.1), doesn't support iGPU
[PSU] : Corsair HX750

[DSP1] : 30" DELL UltraSharp U3011 @2560x1600
[DSP2] : 26" iiyama ProLite E2607WS @1920x1200

[UPS] : Eaton 5PX 2200i RT

[DEVICES] : GoPro Hero3 Black, Hero4 Black. Apple iPhone 6S.

set wrote on 9/30/2019, 2:08 AM

I think AC-3 Studio encoder cannot be modified... that's why 'Render Options' is grayed out.

vkmast wrote on 9/30/2019, 3:33 AM

@set some of the Render Options were still available in VPro 15.