VEGAS Pro 18 Update 2 (Build 373) - General Discussion

Comments

MarcB wrote on 12/24/2020, 3:08 AM

Still same issues like all other versions...
GPU renderinger getting stuck at 78%. Whats up with this issue anyway? Only solutions that seems to work is to use CPU renderinger instead, but to create a proect and rendering it on 15 mins instead of 1h30min isnt what I really wanna do.

@MarcB If you want help, you should start your own thread with details about your project instead of commenting the same thing on other threads. You can disable GPU preview acceleration (and set dynamic ram preview to 0 if need-be) and still use NVENC or VCE acceleration.

I thought it was a general discussion about this very version? And I'm telling you this issue still remains in this very update. Workaround aint fixes. However, thanks for your input.

MarcB wrote on 12/24/2020, 3:10 AM

@MarcB please follow the advice given by @RogerS regarding threads. "Cross posting, i.e. spreading around the same entry in multiple categories, should be avoided." (Community rule #3)

I'm new here and I'll try to keep that in mind.
Thanks.

RogerS wrote on 12/24/2020, 3:32 AM

@MarcB If you want help, you should start your own thread with details about your project instead of commenting the same thing on other threads. You can disable GPU preview acceleration (and set dynamic ram preview to 0 if need-be) and still use NVENC or VCE acceleration.

I thought it was a general discussion about this very version? And I'm telling you this issue still remains in this very update. Workaround aint fixes. However, thanks for your input.

Here's the issue, in order to fix a problem you have to figure out the cause. Your render error isn't the same as someone else's, so if you want to solve your problem and potentially help Magix troubleshoot a fix, you need to start a thread. Generally it's a media issue, but who knows as we have zero info about your system, GPU and drivers or project/media.

MarcB wrote on 12/24/2020, 3:54 AM

@MarcB If you want help, you should start your own thread with details about your project instead of commenting the same thing on other threads. You can disable GPU preview acceleration (and set dynamic ram preview to 0 if need-be) and still use NVENC or VCE acceleration.

I thought it was a general discussion about this very version? And I'm telling you this issue still remains in this very update. Workaround aint fixes. However, thanks for your input.

Here's the issue, in order to fix a problem you have to figure out the cause. Your render error isn't the same as someone else's, so if you want to solve your problem and potentially help Magix troubleshoot a fix, you need to start a thread. Generally it's a media issue, but who knows as we have zero info about your system, GPU and drivers or project/media.

I'll understand. Going for that so I can get ride of this once and for all.

Thank you and have a great Christmas!

ngjb wrote on 12/26/2020, 11:58 AM

Adding titles to videos causes a memory leak and rendering to crash in Vegas 18 (all builds)

- Test system - AMD 8 core processor - Windows 10 - 16GB memory - Radeon  RX9 380 GPU, 4K Samsung monitor, Vegas 18 Build 373

-  The problem also occurs on my laptop - Intel I7 - NVIDIA GTX 1650  GPU, 16 GB memory, Windows 10

- This problem did not occur in Vegas version 14

- Files are 4K30P  10 bit 4:2:2 recorded in a flat profile

This problem is fairly easy to reproduce as shown in the attached video recording.  I just placed 4 clips on the timeline, performed some minor color correction and rendered the video without titles and the rendering completed without any issues.  The task manager performance monitor indicated that the memory usage as stable during the render.  I then added another video track and added some simple titles and attempted to render the files.  As shown in the attached video, the memory utilization start incrementing after each title is rendered until Vegas hangs up.  I had this problem with the first Version 18 build and still have this problem.  This is definitely a bug.  I can reproduce the problem on my laptop using the same build but on an Intel processor with NVIDIA GPU.

Update: Just to clarify... It also fails with 4K30P 8 bit 4:2:0 media. It works fine if I title over a solid color or if I use 1080P 8 bit media.

 

Last changed by ngjb on 12/26/2020, 4:44 PM, changed a total of 1 times.

Desktop system:


OMEN 30L GT13-1094
Operating system: Windows 10 Home
Processor: AMD Ryzen™ 7 5800X Processor
Memory: HyperX® 32GB DDR4-3200 XMP RGB SDRAM memory(97) (4x8 GB)
Internal Storage: 1 TB PCIe® NVMe™ M.2 SSD (Application storage, Windows OS)
500GB SDD (working drive)
4 TB HDD (Media Storage)
Graphics: EVGA NVIDIA® GeForce RTX™ 3060 XC graphics card with 12 GB GDDR6 dedicated memory
Display:
Samsung U28E590, Displayport,
UHD Monitor 3820x 2160


Laptop:


Acer Nitro 5 Gamer Laptop
Windows 10 (64 Bit)
System Memory 32 GB
500 GB SSD
1TB HDD

FHD Display
CPU Intel I-5 9300H
Graphics NVIDA GTX 1050

frmax wrote on 12/26/2020, 1:22 PM

I´ve tried now the same, but no errors/crash occur (I9900K,32GB,RTX20280). Maybe the crash is caused by your media ?

ngjb wrote on 12/26/2020, 4:41 PM

I'm 100% certain it has something to do with the media and the new titling function. It also fails with 4K30 8Bit 4:2:0 video. If title over a solid color, there are no issues. If I use 1080P MP4 media, there are no issues. Version 14 does not have this problem with 4K media. I use a Lumix G9 and the 4K30P 10 bit or 8 bit media would be the same as those produced by a Lumix GH5, S1, S1H, or S5. I upgraded to version 18 so that I could edit 4K 10 bit media without transcoding. As far as I'm concerned this is a pretty serious bug.

Last changed by ngjb on 12/26/2020, 4:41 PM, changed a total of 1 times.

Desktop system:


OMEN 30L GT13-1094
Operating system: Windows 10 Home
Processor: AMD Ryzen™ 7 5800X Processor
Memory: HyperX® 32GB DDR4-3200 XMP RGB SDRAM memory(97) (4x8 GB)
Internal Storage: 1 TB PCIe® NVMe™ M.2 SSD (Application storage, Windows OS)
500GB SDD (working drive)
4 TB HDD (Media Storage)
Graphics: EVGA NVIDIA® GeForce RTX™ 3060 XC graphics card with 12 GB GDDR6 dedicated memory
Display:
Samsung U28E590, Displayport,
UHD Monitor 3820x 2160


Laptop:


Acer Nitro 5 Gamer Laptop
Windows 10 (64 Bit)
System Memory 32 GB
500 GB SSD
1TB HDD

FHD Display
CPU Intel I-5 9300H
Graphics NVIDA GTX 1050

James-Eastwood wrote on 12/27/2020, 7:39 AM

I find Vegas Pro 18 unusable for 4k clips on my PC (core i7 32GB memory) because the trimmer keeps freezing or blacking out. I have no trouble with version 17 or 14 on the same PC and the same clips. I also get problems with frame dropping on some of the 4k rendering. Is this just software bloat making Vegas Pro 18 require more powerful computers, or is it bugs?

In the meantime, does anyone have suggestions for porting Pro 18 projects to Pro 17? So far I have only found cut and paste of the timeline, but this is less than perfect.

RogerS wrote on 12/27/2020, 9:46 AM

Vegas doesn't have software bloat. Is your GPU supported? Are you on the latest NVIDIA Studio or AMD Enterprise drivers?

Next would be to see what's under File I/O. Try resetting to default. Then try a different GPU for decoding or disable it all together.

ngjb wrote on 12/27/2020, 1:52 PM

I just wonder how much testing was done on version 18 with 4K media. I have no plans to revert back to shooting 1080P so I hope Magix fixes this problem. The problem I documented may explain why others are having problems with the rendering function hanging up with version 18. As I stated previously, the same rendering problem occurs on both AMD /Radeon and Intel/NVIDIA and is caused by the new titling function.

Desktop system:


OMEN 30L GT13-1094
Operating system: Windows 10 Home
Processor: AMD Ryzen™ 7 5800X Processor
Memory: HyperX® 32GB DDR4-3200 XMP RGB SDRAM memory(97) (4x8 GB)
Internal Storage: 1 TB PCIe® NVMe™ M.2 SSD (Application storage, Windows OS)
500GB SDD (working drive)
4 TB HDD (Media Storage)
Graphics: EVGA NVIDIA® GeForce RTX™ 3060 XC graphics card with 12 GB GDDR6 dedicated memory
Display:
Samsung U28E590, Displayport,
UHD Monitor 3820x 2160


Laptop:


Acer Nitro 5 Gamer Laptop
Windows 10 (64 Bit)
System Memory 32 GB
500 GB SSD
1TB HDD

FHD Display
CPU Intel I-5 9300H
Graphics NVIDA GTX 1050

j-v wrote on 12/27/2020, 3:14 PM

@ngjb
I propose you start your own pronblem under the normal POSTS because it is not a problem so common that is has to be made in this general Update post.
There I shall try to help you because I don't have any problems with this build on laptop from signature with 4 K editting with whatever Titler old or new. Here i'm not going further.

met vriendelijke groet
Marten

Camera : Pan X900, GoPro Hero7 Hero Black, DJI Osmo Pocket, Samsung Galaxy A8
Desktop :MB Gigabyte Z390M, W11 home version 21H2, i7 9700 4.7Ghz,16 DDR4 GB RAM, Gef. GTX 1660 Ti, Intel HD graphics 630
Laptop  :Asus EVO37T, W11 home version 21H2, CPU i7-10875H, 16 GB RAM, Intel UHD Graphics + NVIDIA GeForce RTX 2070. VP 19 and VMS PL 17 are installed, all latest builds, Nvidia GPU driver version 512.96 Studiodriver and Intel GPU
driver 30.0.101.1994
TV      :LG 4K 55EG960V

My slogan is: BE OR BECOME A STEML DONOR !!!

Older Dutch tutorials of 3POINT and me: https://vimeo.com/vegasvideoforum

brenda-oBB wrote on 12/28/2020, 8:43 AM

I rely on Vegas for money. Since Vegas 15...hell. All the way to Vegas 18 Build 363. It appears the hell is over. By turning off opencl/ to FALSE...rendering and time line crashes have ceased. Including a complicated render from an external SSD.

 

You turned off gpu processing which ofcourse fixes vegas GPU problems, but in 2020 you should be able to benefit by having GPU processing on an NLE and not having to turn it off. But if you don't even realise what you've done and Vegas performance is good enough for you, then maybe you dont' need a GPU


GPU processing is as normal. Not sure what you're talking about. But, the crashing has returned.

brenda-oBB wrote on 12/28/2020, 8:47 AM

Vegas doesn't have software bloat. Is your GPU supported? Are you on the latest NVIDIA Studio or AMD Enterprise drivers?

Next would be to see what's under File I/O. Try resetting to default. Then try a different GPU for decoding or disable it all together.


I've done everything and more. This is an ongoing three year old problem. I have an AMD laptop I am waiting to collect. I cannot recall a single crash under Sony. There must have been - but I cant recall one. Vegas 12 - then I went to Magix 15 and it has been a nightmare ever since. Two laptops, one desktop (AMD 3700) and the same problems. Just had a month of almost perfect use...and it crashes on render with a "BEEP" and "test pattern" 1 second track. Repeatedly. Never has it done this before. Ever. I sometimes wonder if it's hacking - I've worked in Iran and Lebanon and have annoyed many powerful people including Netanyahu.

walter-i. wrote on 12/28/2020, 2:01 PM

I sometimes wonder if it's hacking - I've worked in Iran and Lebanon and have annoyed many powerful people including Netanyahu.

@brenda-oBB
Before we are surrounded by the secret service here, in my opinion it makes more sense if you open your own thread and describe your problems there in a structured manner.

Follow this structure in your own thread - start at B and C:

https://www.vegascreativesoftware.info/de/forum/important-information-required-to-help-you--110457/

 

Edit:
I just saw that you've tried quite a lot in a long thread.
Excuse me.

 

ngjb wrote on 12/28/2020, 2:42 PM

@ngjb
I propose you start your own pronblem under the normal POSTS because it is not a problem so common that is has to be made in this general Update post.
There I shall try to help you because I don't have any problems with this build on laptop from signature with 4 K editting with whatever Titler old or new. Here i'm not going further.

Okay I posted it under the normal posts with all the other complaints. Hopefully it will get attention from Magix software personnel so they can address this issue in the next update.

Desktop system:


OMEN 30L GT13-1094
Operating system: Windows 10 Home
Processor: AMD Ryzen™ 7 5800X Processor
Memory: HyperX® 32GB DDR4-3200 XMP RGB SDRAM memory(97) (4x8 GB)
Internal Storage: 1 TB PCIe® NVMe™ M.2 SSD (Application storage, Windows OS)
500GB SDD (working drive)
4 TB HDD (Media Storage)
Graphics: EVGA NVIDIA® GeForce RTX™ 3060 XC graphics card with 12 GB GDDR6 dedicated memory
Display:
Samsung U28E590, Displayport,
UHD Monitor 3820x 2160


Laptop:


Acer Nitro 5 Gamer Laptop
Windows 10 (64 Bit)
System Memory 32 GB
500 GB SSD
1TB HDD

FHD Display
CPU Intel I-5 9300H
Graphics NVIDA GTX 1050

yoo-changyun wrote on 12/30/2020, 12:15 AM

The more you stack, the more errors you will get in Vegas 18. vegas 18 build 373 is the worst. When will a suitable build be released? Like the previous subversion, the 373 is full of errors.

walter-i. wrote on 12/30/2020, 1:57 AM

@yoo-changyun

It is no help to come in here and complain without giving any specific facts.

This is a user forum where volunteers try to help other users deal with problems in their free time. Your behavior is only suitable to demotivate these helpers.

If you need help, please open your own thread - and state exactly what your PC, media file and software is having problems with.

dennis-greenlaw wrote on 1/8/2021, 2:06 PM

Earlier I wrote:

So far, Vegas Pro 18 has been full of surprises and not necessarily good ones. I'll keep playing with it but I can't quite commit to it for real work yet. Hopefully, Magix can work out these issues before too long.

Just a quick follow up: earlier this week, I reset my Vegas Pro 18 settings and this seemed to fix a lot of the weird problems I had been seeing (not recognizing valid files, randomly losing files, poor playback performance.) My guess is that all the crashing that occurred during the early 18 releases probably corrupted my preference files.

Now, Vegas Pro 18 seems pretty stable on my computer. So far this week, I used it successfully on three short projects with no mishaps. I'm feeling more confident about using this release for a bigger project.

I wish I thought to try this earlier. In case anybody is wondering how to reset Vegas' settings files, just hold Ctrl+Shift while Vegas is launching until a 'reset' window pops up, then follow the directions.

RogerS wrote on 1/8/2021, 8:15 PM

My guess is that it was settings inherited from previous versions of Vegas that didn't play nicely with 18. Glad you got it fixed and resetting has helped a lot of people here.

vkmast wrote on 1/9/2021, 9:20 AM

In case anybody is wondering why the reset may not be successful, here are the full resetting instructions. There are numerous comments on the forum of failed resets because (e.g.) the cached application data was not deleted in the process.

Hektor-Leka wrote on 1/12/2021, 9:24 AM

Hi, I upgraded from Vegas 16 to 18 and I have an issue (that I've never had with Vegas 16).

At the moment I have the latest build 373. The issue is that the text of Video FX, Media Generator and Transitions look very small and it's hard to read. I already tried to deselect/select Preferences>Display>Use high DPI scaling (where available). I also ran the compatibility mode but nothing changed. Can anyone help me? I'll appreciate that, thanks!

I'll leave a screenshot showing the problem.

https://snipboard.io/PuHKE8.jpg

j-v wrote on 1/12/2021, 9:48 AM

Go to your Windows settings and choose another scale of your screen

met vriendelijke groet
Marten

Camera : Pan X900, GoPro Hero7 Hero Black, DJI Osmo Pocket, Samsung Galaxy A8
Desktop :MB Gigabyte Z390M, W11 home version 21H2, i7 9700 4.7Ghz,16 DDR4 GB RAM, Gef. GTX 1660 Ti, Intel HD graphics 630
Laptop  :Asus EVO37T, W11 home version 21H2, CPU i7-10875H, 16 GB RAM, Intel UHD Graphics + NVIDIA GeForce RTX 2070. VP 19 and VMS PL 17 are installed, all latest builds, Nvidia GPU driver version 512.96 Studiodriver and Intel GPU
driver 30.0.101.1994
TV      :LG 4K 55EG960V

My slogan is: BE OR BECOME A STEML DONOR !!!

Older Dutch tutorials of 3POINT and me: https://vimeo.com/vegasvideoforum

james-ollick wrote on 1/12/2021, 12:05 PM

Just installed the update. As for the previous update, I still cannot see my media generator tab and I cannot enable it from the Window menu. I was able to see it only in the first release of VP18.

Same issue here, I cannot see the Media Generator tab. Tried uninstalling VP18, running as Admin, etc.

 

Can I get a resolution to this issue with the Media Generators tab not showing. Running VP18 Build 373. I cannot get the check to take on VIEW, WINDOW, MEDIA GENERATORS and Alt +9 does not get the tab to show on my screen.

Home built PC - Corsair case, ASUS ROG Maximus XI Code motherboard, i9 9900k, 64GB Corsair Vengeance RGB DDR4 DRAM 3200MHz,  Sapphire Nitro+ Radeon RX 580 graphics card, Corsair 1000 watt power supply. Windows 11.

VP 19, BCC 2022 Continuum Complete, Titler Pro v7.

set wrote on 1/13/2021, 6:40 AM

Alternatively use Plug-in Manager to show Media Generator.

So far I found there is one incompatible OFX Media Generator, and temporarily moved it away from OFX folder fix the problem