Vegas pro 18 (also build 337) "no response" after about 30 minutes.

walter-i. wrote on 10/31/2020, 5:19 AM

After about 30 minutes of work, I get pretty regular "no response" from Vegas Pro 18 with UHD material.
Is now also the case with Build 373 (I was hoping for an improvement). I can then only exit Vegas with the Task Manager.

While working, I kept an eye on the Task Manager on the second screen - no unnatural spikes were noticeable before the freeze. CPU approx. 20%, memory approx. 10 GB (of 32), GPu approx. 40-50%

Graphics card driver is up-to-date.
After installing the update, I didn't make any changes to the settings.

Any Ideas?

Comments

andyrpsmith wrote on 10/31/2020, 9:33 AM

I have been running v18 373 for over an hour and no problem with freezing. Must be something with your setup.

(Intel 3rd gen i5@4.1GHz, 32GB RAM, SSD, 1080Ti GPU, Windows 10) Not now used with Vegas.

13th gen i913900K - water cooled, 96GB RAM, 4TB M2 drive, 4TB games SSD, 2TB video SSD, GPU RTX 4080 Super, Windows 11 pro

michael-harrison wrote on 10/31/2020, 11:14 AM

Post mediainfo for your source media.

Also you might try reducing your dynamic ram to 0

System 1:

Windows 10
i9-10850K 10 Core
128.0G RAM
Nvidia RTX 3060 Studio driver [most likely latest]
Resolution        3840 x 2160 x 60 hertz
Video Memory 12G GDDR5

 

System 2:

Lenovo Yoga 720
Core i7-7700 2.8Ghz quad core, 8 logical
16G ram
Intel HD 630 gpu 1G vram
Nvidia GTX 1050 gpu 2G vram

 

walter-i. wrote on 10/31/2020, 2:29 PM

Here is the media info
All files in the project were recorded with the Sony FDR-AX53 in the XAVCS 4K file format at 60Mbps.

I have now set the dynamic ram to "0" because I hardly use the dynamic ram preview anyway.
But as I said: Before the freeze, there was no noticeable increase in CPU, RAM, or GPU.
The video preview is good and smooth in Optimal full.

Allgemein
Vollständiger Name               : E:\Videobearbeitung\Ausflüge_Reisen\Virgen_2020\Footage\Teil2\C0003.MP4
Format                                   : XAVC
Codec-ID                                 : XAVC (XAVC/mp42/iso2)
Dateigröße                               : 187 MiB
Dauer                                    : 24s 960 ms
Modus der Gesamtbitrate                  : variabel
Gesamte Bitrate                          : 63,0 Mb/s
Kodierungs-Datum                         : UTC 2020-09-04 15:02:58
Tagging-Datum                            : UTC 2020-09-04 15:02:58

Video
ID                                       : 1
Format                                   : AVC
Format/Info                              : Advanced Video Codec
Format-Profil                            : High@L5.1
Format-Einstellungen                     : CABAC / 2 Ref Frames
Format-Einstellungen für CABAC           : Ja
Format-Einstellungen für RefFrames       : 2 frames
Codec-ID                                 : avc1
Codec-ID/Info                            : Advanced Video Coding
Dauer                                    : 24s 960 ms
Bitraten-Modus                           : variabel
Bitrate                                  : 61,2 Mb/s
maximale Bitrate                         : 60,0 Mb/s
Breite                                   : 3 840 Pixel
Höhe                                     : 2 160 Pixel
Bildseitenverhältnis                     : 16:9
Modus der Bildwiederholungsrate          : konstant
Bildwiederholungsrate                    : 25,000 FPS
ColorSpace                               : YUV
ChromaSubsampling/String                 : 4:2:0
BitDepth/String                          : 8 bits
Scantyp                                  : progressiv
Bits/(Pixel*Frame)                       : 0.295
Stream-Größe                             : 182 MiB (97%)
Kodierungs-Datum                         : UTC 2020-09-04 15:02:58
Tagging-Datum                            : UTC 2020-09-04 15:02:58
colour_range                             : Limited
colour_primaries                         : BT.709
transfer_characteristics                 : xvYCC
matrix_coefficients                      : BT.709
Codec configuration box                  : avcC

Audio
ID                                       : 2
Format                                   : PCM
Format-Einstellungen                     : Big / Signed
Codec-ID                                 : twos
Dauer                                    : 24s 960 ms
Bitraten-Modus                           : konstant
Bitrate                                  : 1 536 kb/s
Kanäle                                   : 2 Kanäle
Samplingrate                             : 48,0 kHz
BitDepth/String                          : 16 bits
Stream-Größe                             : 4,57 MiB (2%)
Kodierungs-Datum                         : UTC 2020-09-04 15:02:58
Tagging-Datum                            : UTC 2020-09-04 15:02:58

Andere
Type                                     : meta
Dauer                                    : 24s 960 ms

Shinra Bansho wrote on 10/31/2020, 3:14 PM

@walter-i., I ran into the same exact "no response" problem as you did after a couple of hours of editing since I had installed VEGAS Pro 18 this morning. After I changed the "Temporary files folder" to other drive (D: in my case) from the default folder on C:drive in the Preference, the problem seems to have gone away for me. I do not know if this would help you but might be worth a try.

PC 1: ASUS ROG Strix B-760i Gaming Wifi, 64GB RAM (DDR5), i5 14600K, 2TB M2.SSD, ASUS RTX-4070 (12GB), Windows 11 Pro Version 23H2

PC 2: ASUS Prime H570-PLUS MB, 32GB RAM, i7-10700K, 1TB SSD (M.2), 8TB HD, NVidia RTX3080 10GB, Windows 11 Home 23H2 (22631.3593)

Gears: Panasonic GH4/GH5, Sony FDR-AX100/A7C/A74/FX30

walter-i. wrote on 10/31/2020, 3:52 PM

After I changed the "Temporary files folder" to other drive (D: in my case) from the default folder on C:drive in the Preference, the problem seems to have gone away for me. I do not know if this would help you but might be worth a try.

@Shinra Bansho
Thanks for your suggestion, but I always save the temporary files on a drive other than C.

walter-i. wrote on 10/31/2020, 5:09 PM

Also you might try reducing your dynamic ram to 0

Unfortunately, reducing dynamic ram to 0 does not work - I know that this helps in many cases, but it produces freezes every minute for me.
It is also astonishing that - if I have to end the task with the Task Manager after the freeze - dynamic ram is back to the standard setting 200 MB, and my "extended memory settings" are deleted.

I would also like to say that this is by no means a big project, it contains about 20 minutes of raw material, and I'm currently only doing the rough cut - so no transitions, no FX, no color correction.

Shinra Bansho wrote on 10/31/2020, 5:22 PM

@walter-i., How about disabling so4compoundplug.dll? Would that help? This was relevant, tho' in VEGAS Pro 17/16, when I had a similar problem.

PC 1: ASUS ROG Strix B-760i Gaming Wifi, 64GB RAM (DDR5), i5 14600K, 2TB M2.SSD, ASUS RTX-4070 (12GB), Windows 11 Pro Version 23H2

PC 2: ASUS Prime H570-PLUS MB, 32GB RAM, i7-10700K, 1TB SSD (M.2), 8TB HD, NVidia RTX3080 10GB, Windows 11 Home 23H2 (22631.3593)

Gears: Panasonic GH4/GH5, Sony FDR-AX100/A7C/A74/FX30

walter-i. wrote on 10/31/2020, 5:28 PM

@walter-i., How about disabling so4compoundplug.dll? Would that help? This was relevant, tho' in VEGAS Pro 17/16, when I had a similar problem.


Thanks for the tip, I'll try tomorrow - I'll go to sleep now .......

walter-i. wrote on 11/1/2020, 10:53 AM

So4 Audio Reader deactivated, unfortunately no improvement either - freeze after 15 minutes.
(With VP17 I have the So4 Reader active, and never had problems with it - with VP17 I only cut 1920x1080 material from the same camera (Sony FDR-AX53).)

Dynamic Ram set to "0" again - freeze after 3 minutes.

Edit:
I have now copied the content of the timeline to Vegas Pro 17 - but after about 10 minutes of rough cut that too is frozen.
Note: Every time after the freeze I restarted the PC.

Does anyone else have an idea?
If not, I'll probably have to use the support.

j-v wrote on 11/1/2020, 11:52 AM

@walter-i.
On desktop I have almost the same hardware as you, I don't see what you write here. No problem there.
After the upgrade to VPro 18 I had to change a lot of the settings that were needed for me in VPro 17, resulting for the two settings you showed I use only what the install of the program does.
In my case I made for 1 a litle bit else ( never use dyn preview) than default and at 2 that are my default settings. My normal GPU use editting your kind of files is only 6.3 GB

met vriendelijke groet
Marten

Camera : Pan X900, GoPro Hero7 Hero Black, DJI Osmo Pocket, Samsung Galaxy A8
Desktop :MB Gigabyte Z390M, W11 home version 24H2, i7 9700 4.7Ghz,16 DDR4 GB RAM, Gef. GTX 1660 Ti with driver
566.14 Studiodriver and Intel HD graphics 630 with driver 31.0.101.2130
Laptop  :Asus ROG Str G712L, W11 home version 23H2, CPU i7-10875H, 16 GB RAM, NVIDIA GeForce RTX 2070 with Studiodriver 566.14 and Intel UHD Graphics 630 with driver 31.0.101.2130
Vegas software: VP 10 to 22 and VMS(pl) 10,12 to 17.
TV      :LG 4K 55EG960V

My slogan is: BE OR BECOME A STEM CELL DONOR!!! (because it saved my life in 2016)

 

walter-i. wrote on 11/1/2020, 12:29 PM

@j-vThanks for your suggestions - much appreciated.

Like you, I have now set the I / O settings "Use hardware decoder" from "Nvidia NVDEC" to "Auto (Intel QSV)".
I also set the video dyn. Ram preview to "0" again.
What was immediately noticeable was that the preview performance was greatly reduced - before I could play "Optimal-Full" smoothly, now I have to set it to "Good-half" so that the preview is smooth.

Unfortunately, even with these settings, the PC freezes after about 15 minutes.
Once again, the resource consumption was inconspicuous and without any noticeable peaks.

walter-i. wrote on 11/1/2020, 4:28 PM

Here is a screenshot of the Task Manager and the Vegas interface during the rough cut.
The displayed values can be regarded as average, and remain in the range even if Vegas freezes.
By setting the "Auto (Intel QSV)" in the I / O settings, the second graphics card is now also involved.

andyrpsmith wrote on 11/1/2020, 4:36 PM

Walter, have you tried disabling the intel HD Graphics in device manager so you just use the Nvidia (enable So4 or you will not have GPU acceleration). I have a Sony Ax100 which uses the same codec as you and I am not having the issues you are. I disabled the Intel graphics ages ago. Worth giving it a try as you can enable it again if no difference. Leave dynamic Ram preview at 0. Also leave enable legacy AVC encoding unchecked. Use driver 456.71 if not already.

Last changed by andyrpsmith on 11/1/2020, 4:46 PM, changed a total of 6 times.

(Intel 3rd gen i5@4.1GHz, 32GB RAM, SSD, 1080Ti GPU, Windows 10) Not now used with Vegas.

13th gen i913900K - water cooled, 96GB RAM, 4TB M2 drive, 4TB games SSD, 2TB video SSD, GPU RTX 4080 Super, Windows 11 pro

walter-i. wrote on 11/2/2020, 11:01 AM

@andyrpsmith

Walter, have you tried disabling the intel HD Graphics in device manager so you just use the Nvidia (enable So4 or you will not have GPU acceleration).

That was my original setting, I only changed the settings as a test on the advice of forum participants, and will reset them again.

Leave dynamic Ram preview at 0.
That apparently causes most of the problems - so I'll go back to 200.

Also leave enable legacy AVC encoding unchecked.
Ok, I won't do that.

Use driver 456.71 if not already.
I had installed it before - so I'm thinking about trying a rollback to 456.38 - I've worked with it for a long time - maybe it's more stable .

I have made a support request in the meantime, I will wait for the answer and then decide.

RogerS wrote on 11/3/2020, 2:24 AM

Which Intel GPU do you have? Is it supported in VP 18? Are you on its latest driver?

If your crashes started when you changed File I/O to that perhaps go back. The drop in performance is more likely from going to the NVIDIA to Intel than changing dynamic ram preview from 200 to 0. Do test only one variable at a time.

This looks like a pretty normal Sony file you are working with, so likely not the problem. Vegas 18 with so4compound enabled and NVIDIA Studio Drivers work happily with this file format.

walter-i. wrote on 11/3/2020, 4:00 AM

@RogerS

Which Intel GPU do you have?
UHD Graphics 630, driver: 27.20.100.8853 - for more information see mei SIGNATURE

Is it supported in VP 18?
yes

Are you on its latest driver?
yes

If your crashes started when you changed File I/O to that perhaps go back.
The freezing started after changing from 1920x1080 material to 3840x2160 material (both media files are from the Sony FDR-AX53)

The drop in performance is more likely from going to the NVIDIA to Intel than changing dynamic ram preview from 200 to 0.
Strangely enough, that's the case with me. In previous tests with VP15 or VP17, this had no noticeable effect on me.

Do test only one variable at a time.
Yes, I take that into account in my tests.

This looks like a pretty normal Sony file you are working with, so likely not the problem. Vegas 18 with so4compound enabled and NVIDIA Studio Drivers work happily with this file format.
Yes, I am surprised too. I read a lot here in the forum, but files of this kind really don't belong to the "problem cases".
And my PC has enough power too.

Here is a screenshot from my GPU and drivers in VegasPro18

RogerS wrote on 11/3/2020, 4:29 AM

Thanks, Walter. I think you've tried a lot of the common solutions.

I also have Intel HD Graphics 630 on my machine. 27.20.100.8853
My main card is the NVIDIA GeForce GTX 1050 (4GB) 456.71
For me, having File I/O set to Intel reduces performance a bit but it's stable.

I also use Sony AVC files (4K and 1080p), though not from the same camera as you- I think yours is the one with the really good stabilization?

Would you mind making one of your problem 4K clips available? I could try testing here and see if I can replicate your issues.

Are there other running applications that might be conflicting with Vegas or competing for GPU resources?

walter-i. wrote on 11/3/2020, 5:17 AM

Thanks, Walter. I think you've tried a lot of the common solutions.

I also have Intel HD Graphics 630 on my machine. 27.20.100.8853
My main card is the NVIDIA GeForce GTX 1050 (4GB) 456.71
For me, having File I/O set to Intel reduces performance a bit but it's stable.

I also use Sony AVC files (4K and 1080p), though not from the same camera as you- I think yours is the one with the really good stabilization?
Yes, this stabilization is of great help, especially because I mainly film on excursions and hikes, and because I don't want to work awkwardly with a tripod. And I am also very satisfied with the quality of the images and the camera sound (for my needs).

Would you mind making one of your problem 4K clips available? I could try testing here and see if I can replicate your issues.
Here are two links (I can only upload a maximum of 100MB to Dropbox)
The jerks at the end of the clips come from the fact that the camera continues to run for half a second after it has been switched off and I keep forgetting to keep a little still.
In addition, the recordings are overexposed, but it was also about making files available "without people".

https://www.dropbox.com/t/f2qXjOmm9lERhTzd
https://www.dropbox.com/t/50enXkDSF4SgaYD1

Are there other running applications that might be conflicting with Vegas or competing for GPU resources?
Firefox mostly runs in the background for me, but - especially during the tests - only Vegas Pro so that there are no uncontrollable side effects.

What I also notice with the 4K material: When the video files are first loaded into the project, there are gaps between many files, which I then have to adjust with "Close gaps". This is not the case with HD-Material.

RogerS wrote on 11/3/2020, 6:31 AM

Hi Walter, I'm having trouble with these files, too.

I made a project like yours- 4K 25p and put each clip on it a few times. I then just made a loop region and played them back a few times. I adjusted the length of clips while playing back. After a few minutes performance would become very poor and the Intel GPU was almost at 100%.

At that point I had to restart Vegas.
I played with the files again for a few minutes and same thing, 0% NVIDIA use plus nearly 100% Intel use and Vegas stops working right. I know you made a support ticket- I suggest also sharing the files with Magix to help replicate the issue.

A side note- I noticed your files appear to be 16-255, which means that if you are in 8-bit full mode you need to manually change them to "full" levels (right-click, properties) as some of the highlights will be cut off. When you do this, or use 8-bit video (legacy) mode, the blacks will look too light, so you'll need to correct that (levels Fx with computer to studio RGB preset for only the blacks will work perfectly- or change input start: 0.063). You probably already know this, but just in case!

If anyone else wants to test, here's the project I used:
https://www.dropbox.com/s/x31dx3nuv3ditbb/Walter.veg?dl=0
(It has the levels fix applied at the track level, too)

RogerS wrote on 11/3/2020, 7:16 AM

A bit more testing and I noticed that I'm hitting bad thermal throttling after a few minutes of playback. I have the system undervolted to avoid this and until now I haven't noticed it as an issue. I'll have to do more testing with my usual files.

When the laptop hits power limits, CPU usage drops, the Intel card appears around 100% and NVIDIA usage drops to 0%.

I also appear to have a memory leak- Vegas is up to 16GB just repeatedly playing these clips. Normally it stays <3GB with a handful of 4K clips.

walter-i. wrote on 11/3/2020, 7:32 AM

@RogerS
Thank you very much for testing my material so extensively and for coming to an - admittedly unpleasant - but confirmatory judgment.

In my request to the support I also included a link to this thread, so the support can already fall back on a lot of information.

Thank you very much for the extremely valuable help regarding the levels - I have to admit that I have read about it here in the forum several times, but I still lack the elementary basic knowledge and precise access. So I am very happy that you gave me explanatory words for exactly my material.

Edit:
In my answer, I haven't seen you post a second post - I hope I haven't ruined your PC 😟

 

andyrpsmith wrote on 11/3/2020, 7:57 AM

Walter, I also downloaded your clips and about to load into V18. i will come back with how it goes.

(Intel 3rd gen i5@4.1GHz, 32GB RAM, SSD, 1080Ti GPU, Windows 10) Not now used with Vegas.

13th gen i913900K - water cooled, 96GB RAM, 4TB M2 drive, 4TB games SSD, 2TB video SSD, GPU RTX 4080 Super, Windows 11 pro

walter-i. wrote on 11/3/2020, 8:00 AM

@andyrpsmith
👍👍👍

andyrpsmith wrote on 11/3/2020, 8:06 AM

So far loaded ok no problem, playback fine on timeline, I can overlap to fade into each clip fine. Preview is Best Quarter (at 4K with no proxy no frame drops with 1080Ti). I will now try some levels and stabilization.

(Intel 3rd gen i5@4.1GHz, 32GB RAM, SSD, 1080Ti GPU, Windows 10) Not now used with Vegas.

13th gen i913900K - water cooled, 96GB RAM, 4TB M2 drive, 4TB games SSD, 2TB video SSD, GPU RTX 4080 Super, Windows 11 pro