VEGAS Pro 18 Update 4 (Build 482) - General Discussion

Comments

James-Alburger wrote on 3/24/2021, 9:24 PM

3/30/21

Just reinstalled Vegas 18-482. There was a second Effects update that either wasn't there the first time or I missed it. After running both updates, the VST plugins have reappeared (see original post below). I did try a reset with the original issue, which did not fix the problem.

On another note - completely different issue - I ran into a problem where Vegas would not render to .wav or to .wav64. It would render audio only to all the other audio formats, but not .wav. This was a project built in Vegas 18-434. I was unable to isolate the cause of the problem but the solution was simple (once I found it). Resetting Vegas Pro to its default settings by holding down CTRL-SHIFT and double-clicking on the Vegas Pro icon and waiting for the prompt to reset - then clicking "yes", did the trick. Nothing in the project changed - all the track settings, levels and plug-in settings appeared to stay in place and Vegas worked as it should. I did need to import my preferences though, but that didn't cause any problem.

3/25/21 (original post)

Just ran the update for build 482 and all my VST plugins vanished. The VST scan shows the correct folders, but returns empty, so no VST plugins show in build 482. Attempted to roll back to build 434, but discovered that the download from Magix is actually build 482 (even though it's labeled 434). 434 was working just fine before the update. Build 373 restores my VST plugins. Reinstalled 482 and 373 several times to confirm the issue. Anyone else seeing this or have any ideas as to why the VST plugins would disappear? All legacy options are unchecked.

walter-i. wrote on 3/25/2021, 2:33 AM

@James-Alburger
Have you already tried a reset? I expect this to be more effective, because a new installation retains all the settings you have made - unlike a reset.

https://www.vegascreativesoftware.info/us/forum/faq-how-can-i-reset-vegas-pro-to-default-settings--104646/

Last changed by walter-i. on 3/25/2021, 2:34 AM, changed a total of 1 times.

CPU: Intel i9-9900KS 4GHz, (UHD Graphics 630, driver: 27.20.100.9126)
MB: ASUS TUF Z390-PLUS Gaming,
MEM.: 32 GB Ram, DDR4-3200
GPU: Nvidia GTX 1660 SUPER, (driver 460.89)
Storage: SSD 970 EVO Plus 500GB M.2, SSD 860 EVO Series 1TB, Toshiba 3TB SATA,
OS: WIN 10 Pro, 1909
Monitor: HP243i 1920x1200 / BenQ G2200W 1680x1050
NLE: Vegas Pro11-15+17,18 Heroglyph4, RespeedR
Camcorder: Pana HDC SD909, Sony FDR-AX53

Reyfox wrote on 3/25/2021, 5:56 AM

I just checked, all the VST plugins are there in Build 482 on my computer. I did nothing special when updating. I updated from within Vegas.

JE22222 wrote on 3/25/2021, 12:18 PM

What are you guys doing? I reported that the render dialog was annoying in the last build because it didn't respect that the video editor window was minimized and whenever you batch render a video file the render video re-appears once one segment is completed and the next starts up.

Now with the new patch it is literally doing exactly the same but now you have removed the minimize button from the render window so now you cannot even minimize it anymore without expanding the original editor window and then re-minimize it again.

Why do you change the render window to begin with? All the information there is useless anyway, old render window was better because you could minimize vegas to render a batch of 200 files and it would not popup everytime a new clip started to render, now it is really annoying because if you are for example writing a document while rendering and you type on the keyboard and the render window pops up while you render you may just be unlucky and cancel the render because the focus of the window is now the render window making the workflow of your program worse.

Robert-Wilson wrote on 3/25/2021, 4:00 PM

There's no switch in the software for that behavior? That's going to be something to not look forward to.

VEGASDerek wrote on 3/25/2021, 4:20 PM

What are you guys doing? I reported that the render dialog was annoying in the last build because it didn't respect that the video editor window was minimized and whenever you batch render a video file the render video re-appears once one segment is completed and the next starts up.

Now with the new patch it is literally doing exactly the same but now you have removed the minimize button from the render window so now you cannot even minimize it anymore without expanding the original editor window and then re-minimize it again.

Why do you change the render window to begin with? All the information there is useless anyway, old render window was better because you could minimize vegas to render a batch of 200 files and it would not popup everytime a new clip started to render, now it is really annoying because if you are for example writing a document while rendering and you type on the keyboard and the render window pops up while you render you may just be unlucky and cancel the render because the focus of the window is now the render window making the workflow of your program worse.

I have confirmed the behavior you are describing. I have added bug to our database. This most certainly is annoying for anyone using the batch rendering script. I cannot promise anything, but we will attempt to resolve this for the next update.

James-Alburger wrote on 3/25/2021, 4:55 PM

I updated from within Vegas, then launched with the recommended reset procedure. Vegas loads with default settings (verified this) but still does not load the VST plugins. No VST plugins show when first opened, and setting folders and refreshing the plugin scan still results in an empty VST list. Anyone have a link to build 434? The 434 download actually installs as 482.

set wrote on 3/25/2021, 5:11 PM

In case needed: https://www.vegascreativesoftware.info/us/forum/vegas-pro-18-update-3-build-434--126816/

JN- wrote on 3/28/2021, 11:53 AM

There's a visual display distortion in the Render output screen display, see screenshot below. This can also be a problem with the the inability to finder the "Render" box, it goes to black on black. Dragging the main render dialog box makes it re-appear. When attempting to select a render option items disappear also, black on black.

I have previously done a reset and reinstall to fix another problem, so no luck with this issue. This happens on my laptop and PC. I have the very latest Studio drivers installed.

This is the display output while rendering on my PC.

The "Current speed" FPS value cannot be made out, it's visibility comes and goes, maybe it shouldn't be updated so quickly. Somewhere between real time and the "Average FPS" readout?

I checked the 5 pages so far and haven't seen a mention of this issue. This has appeared in previous versions/builds, it comes and goes with different versions, but I thought it was gone.

Last changed by JN- on 3/28/2021, 12:03 PM, changed a total of 3 times.

---------------------------------------------

VFR2CFR, Variable frame rate to Constant frame rate link here.

Copies Video Converts Audio to AAC, link here.

Benchmarking thread

Codec Render Quality tables

---------------------------------------------

PC ... Corsair case, own build ...

CPU .. i9 9900K, iGpu UHD 630

Memory .. 32GB DDR4

Graphics card .. MSI RTX 2080 ti

Graphics driver .. latest studio

PSU .. Corsair 850i

Mboard .. Asus Z390 Code

 

Laptop ... (Acer Predator G9-793-77AC)

CPU .. i7-6700HQ Skylake-H

Memory ..32 GB DDR4, was previously 16 GB

Graphics card .. Nvidia GTX 1070

Graphics driver .. latest studio

Illusion wrote on 3/28/2021, 3:59 PM

There's a visual display distortion in the Render output screen display, see screenshot below. This can also be a problem with the the inability to finder the "Render" box, it goes to black on black. Dragging the main render dialog box makes it re-appear. When attempting to select a render option items disappear also, black on black.

I have previously done a reset and reinstall to fix another problem, so no luck with this issue. This happens on my laptop and PC. I have the very latest Studio drivers installed.

This is the display output while rendering on my PC.

The "Current speed" FPS value cannot be made out, it's visibility comes and goes, maybe it shouldn't be updated so quickly. Somewhere between real time and the "Average FPS" readout?

I checked the 5 pages so far and haven't seen a mention of this issue. This has appeared in previous versions/builds, it comes and goes with different versions, but I thought it was gone.

See if the solution here works for you: https://www.vegascreativesoftware.info/us/forum/vegas-18-visual-glitching-in-one-panel-after-last-update--126415/#ca786801

JN- wrote on 3/28/2021, 7:23 PM

@Illusion Thanks. I remember seeing those threads, comments. At the time I didn't have the issue. I will check out my PC with the fix tomorrow. At the laptop at the moment, and would you believe it it's ok for now! In VP18 when I search for GPU only the single item you mention comes up. So I'll check it out on the PC tomorrow, where it's really quite bad, thanks.

I checked up on my previous reset date time, comments. I now realise it was just before this new build. So I now first tried a reset on my PC and so far aok. If it comes back i’ll use your suggestions in the linked threads.

Appears to be that a reset solves a lot of problems with b482.

Last changed by JN- on 3/29/2021, 6:48 AM, changed a total of 3 times.

---------------------------------------------

VFR2CFR, Variable frame rate to Constant frame rate link here.

Copies Video Converts Audio to AAC, link here.

Benchmarking thread

Codec Render Quality tables

---------------------------------------------

PC ... Corsair case, own build ...

CPU .. i9 9900K, iGpu UHD 630

Memory .. 32GB DDR4

Graphics card .. MSI RTX 2080 ti

Graphics driver .. latest studio

PSU .. Corsair 850i

Mboard .. Asus Z390 Code

 

Laptop ... (Acer Predator G9-793-77AC)

CPU .. i7-6700HQ Skylake-H

Memory ..32 GB DDR4, was previously 16 GB

Graphics card .. Nvidia GTX 1070

Graphics driver .. latest studio

JN- wrote on 3/29/2021, 12:41 PM

@Illusion Ok, problem came back. So I changed the GPU value to FALSE in internals ...

"GPU Acceleration for Windows Presentation Foundation (WPF) Panels"

So far issue is gone away.

---------------------------------------------

VFR2CFR, Variable frame rate to Constant frame rate link here.

Copies Video Converts Audio to AAC, link here.

Benchmarking thread

Codec Render Quality tables

---------------------------------------------

PC ... Corsair case, own build ...

CPU .. i9 9900K, iGpu UHD 630

Memory .. 32GB DDR4

Graphics card .. MSI RTX 2080 ti

Graphics driver .. latest studio

PSU .. Corsair 850i

Mboard .. Asus Z390 Code

 

Laptop ... (Acer Predator G9-793-77AC)

CPU .. i7-6700HQ Skylake-H

Memory ..32 GB DDR4, was previously 16 GB

Graphics card .. Nvidia GTX 1070

Graphics driver .. latest studio

JN- wrote on 3/30/2021, 2:07 PM

Ok, I know there are a few threads with this issue, but this thread, hopefully is being monitored by Magix?

I had this problem with 4K media, Red Screen, Black screen.

Red screen indicates use of proxies. Black screen occurs when proxies are not used.

This is another similar media type to my previouslyy used 4K media. It's FHD with the same black screen issue. The issue can be resolved by ...

#1 enabling Legacy AVC decoding, or

#2 using VP16.

Using #1 means that Nvenc encoding is not available.

Enabling Legacy AVC decoding #1 means that compoundplug.dll is used instead of the SO4 ... dll.

It appears there is more work to do with the SO4 ... dll plugin.

Note that enabling the Deprecated item Quicktime doesn't fix the problem.

 

Last changed by JN- on 3/30/2021, 2:14 PM, changed a total of 1 times.

---------------------------------------------

VFR2CFR, Variable frame rate to Constant frame rate link here.

Copies Video Converts Audio to AAC, link here.

Benchmarking thread

Codec Render Quality tables

---------------------------------------------

PC ... Corsair case, own build ...

CPU .. i9 9900K, iGpu UHD 630

Memory .. 32GB DDR4

Graphics card .. MSI RTX 2080 ti

Graphics driver .. latest studio

PSU .. Corsair 850i

Mboard .. Asus Z390 Code

 

Laptop ... (Acer Predator G9-793-77AC)

CPU .. i7-6700HQ Skylake-H

Memory ..32 GB DDR4, was previously 16 GB

Graphics card .. Nvidia GTX 1070

Graphics driver .. latest studio

JN- wrote on 3/30/2021, 7:50 PM

I did notice that all of the files have one thing in common ALL-I. IPB files so far, don't have this issue. See this other thread ... here Forget that theory, I found a Panasonic ALL-I GH5 file that plays fine.

Last changed by JN- on 3/31/2021, 4:14 AM, changed a total of 2 times.

---------------------------------------------

VFR2CFR, Variable frame rate to Constant frame rate link here.

Copies Video Converts Audio to AAC, link here.

Benchmarking thread

Codec Render Quality tables

---------------------------------------------

PC ... Corsair case, own build ...

CPU .. i9 9900K, iGpu UHD 630

Memory .. 32GB DDR4

Graphics card .. MSI RTX 2080 ti

Graphics driver .. latest studio

PSU .. Corsair 850i

Mboard .. Asus Z390 Code

 

Laptop ... (Acer Predator G9-793-77AC)

CPU .. i7-6700HQ Skylake-H

Memory ..32 GB DDR4, was previously 16 GB

Graphics card .. Nvidia GTX 1070

Graphics driver .. latest studio

RogerS wrote on 3/30/2021, 8:15 PM

This is the thread referenced by JN- above: https://www.vegascreativesoftware.info/us/forum/canon-80d-video-won-t-play-in-vegas-18--128174/

David-Jodon wrote on 3/31/2021, 1:31 PM

After doing a few projects with Build 482, I must say it's the first version of Vegas which actually works my graphics card. Not just for timeline playback, but also for rendering. There is something different about rendering. If I want to make a DVD or Blu-Ray of a project I have done in Vegas, I must go to Options/Preferences/File I/O and check ENABLE LEGACY AVC decoding (otherwise Vegas will render some green frames and then crash). So yesterday I edited a project, rendered it 4k to an HEVC/NVENC mp4 file. It rendered very fast. Then, after some trial & error, I discovered the problem with rendering to older video codecs (mp2) and came up with what I have written above. Does anyone know of a better way to do this?

RogerS wrote on 3/31/2021, 8:36 PM

The older codecs don't have GPU-enabled encoding (VCE/NVENC) options, do they so you are talking about either GPU decoding or the decoder in use?

What about leaving legacy AVC unchecked but setting hardware decoding to off? I'm not clear if the issue is with GPU assisted decoding or the so4compound plugin. What media are you using?

Other workarounds are setting dynamic ram preview to 0 and disabling GPU preview acceleration before renders. These latter two are things I've done to fix render issues but I haven't rendered for DVDs in quite a while.

Erkki wrote on 4/3/2021, 7:59 AM

Generally works pretty good.

Noticed crashes with one small project where is one clip from mobile and created nested subproject to it. I will send crash reports as they come.

Reyfox wrote on 4/3/2021, 8:10 AM

@Erkki I would use MediaInfo to see what the frame rate of the cellphone video is. Editors usually like a constant frame rate video (like from video/DSLR/Mirroless cameras), while some editing software will balk at a video that has a frame rate all over the place. https://mediaarea.net/en/MediaInfo

If this is the case with the cellphone video, I would convert it to a constant frame rate with a free program like Handbrake. https://handbrake.fr/

Erkki wrote on 4/3/2021, 8:20 AM

@Erkki I would use MediaInfo to see what the frame rate of the cellphone video is. Editors usually like a constant frame rate video (like from video/DSLR/Mirroless cameras), while some editing software will balk at a video that has a frame rate all over the place. https://mediaarea.net/en/MediaInfo

If this is the case with the cellphone video, I would convert it to a constant frame rate with a free program like Handbrake. https://handbrake.fr/

Thanks for tip. Checked with Mediainfo and seems to be variable framerate (framerate mode: variable). When I downloaded latest Vegas build I have been editing only videocamera files (mxf) and did not notice any crashes before now. So this could explain crashes.

I will test Handbrake.

Reyfox wrote on 4/3/2021, 9:56 AM

@Erkki I knew it would be variable frame rate, but curious as to what the "highs and lows" are with the video. And what was the "selected" frame rate on the phone.

Erkki wrote on 4/5/2021, 8:18 AM

@Erkki I knew it would be variable frame rate, but curious as to what the "highs and lows" are with the video. And what was the "selected" frame rate on the phone.

If I understand correctly, minimum framerate was 23.083 FPS and max 42.878. About phone settings.. they were 16:6 FHD 1920x1080 (30 fps).

Reyfox wrote on 4/5/2021, 10:50 AM

I'd try 30fps constant frame rate in Handbrake.

adis-a3097 wrote on 4/5/2021, 3:41 PM

Is it possible to set Vegas so it prevents the Screen saver from going off?