Vegas 17 Pro crashing while editing 4K

Musicvid wrote on 8/23/2019, 11:28 PM

https://www.vegascreativesoftware.info/us/forum/faq-how-to-post-mediainfo-and-vegas-pro-file-properties--104561/

paul-marshall wrote on 8/24/2019, 6:10 AM

Same here. A lot of crashes editing in 4K even though 4K previews smoothly even with transistions. Try editing using proxy files. I still get a crash occaisionally but stabilty much improved. Preview in 'Preview (Ful)l' mode. Proxy files are 1080p.

kmaultsby wrote on 8/24/2019, 1:55 PM

Ok I found one problem which I corrected. One of my hard drives on my raid dieting so I moved to an SSD drive. I trid again and Vegas still stall No Responds.

General
Complete name                            : E:\projects\4K_testing\Camarillo AirShow_2019\MVI_0096.MP4
Format                                   : MPEG-4
Format profile                           : Base Media / Version 2
Codec ID                                 : mp42 (mp42/avc1/CAEP)
File size                                : 231 MiB
Duration                                 : 13 s 13 ms
Overall bit rate                         : 149 Mb/s
Encoded date                             : UTC 2019-08-17 19:26:10
Tagged date                              : UTC 2019-08-17 19:26:10

Video
ID                                       : 1
Format                                   : AVC
Format/Info                              : Advanced Video Codec
Format profile                           : High@L5.2
Format settings                          : 2 Ref Frames
Format settings, CABAC                   : No
Format settings, Reference frames        : 2 frames
Format settings, GOP                     : M=3, N=30
Codec ID                                 : avc1
Codec ID/Info                            : Advanced Video Coding
Duration                                 : 13 s 13 ms
Bit rate                                 : 148 Mb/s
Width                                    : 3 840 pixels
Height                                   : 2 160 pixels
Display aspect ratio                     : 16:9
Frame rate mode                          : Constant
Frame rate                               : 59.940 (60000/1001) FPS
Color space                              : YUV
Chroma subsampling                       : 4:2:0
Bit depth                                : 8 bits
Scan type                                : Progressive
Bits/(Pixel*Frame)                       : 0.298
Stream size                              : 230 MiB (100%)
Language                                 : English
Encoded date                             : UTC 2019-08-17 19:26:10
Tagged date                              : UTC 2019-08-17 19:26:10
Color range                              : Limited
Color primaries                          : BT.709
Transfer characteristics                 : BT.709
Matrix coefficients                      : BT.709
Codec configuration box                  : avcC

Audio
ID                                       : 2
Format                                   : AAC LC
Format/Info                              : Advanced Audio Codec Low Complexity
Codec ID                                 : mp4a-40-2
Duration                                 : 12 s 992 ms
Bit rate mode                            : Constant
Bit rate                                 : 256 kb/s
Channel(s)                               : 2 channels
Channel layout                           : L R
Sampling rate                            : 48.0 kHz
Frame rate                               : 46.875 FPS (1024 SPF)
Compression mode                         : Lossy
Stream size                              : 402 KiB (0%)
Language                                 : English
Encoded date                             : UTC 2019-08-17 19:26:10
Tagged date                              : UTC 2019-08-17 19:26:10

Other
ID                                       : 3
Type                                     : Time code
Format                                   : QuickTime TC
Duration                                 : 13 s 13 ms
Bit rate mode                            : Constant
Frame rate                               : 59.940 (60000/1001) FPS
Time code of first frame                 : 00:30:00;36
Time code, striped                       : Yes
Language                                 : English
Encoded date                             : UTC 2019-08-17 19:26:10
Tagged date                              : UTC 2019-08-17 19:26:10

General
  Name: MVI_0043.MP4
  Folder: E:\projects\4K_testing\Camarillo AirShow_2019
  Type: AVC
  Size: 172.47 MB (176,609,513 bytes)
  Created: Friday, August 23, 2019, 11:22:26 PM
  Modified: Saturday, August 17, 2019, 10:20:02 AM
  Accessed: Saturday, August 24, 2019, 11:54:19 AM
  Attributes: ArchiveStreams
  Video: 00:00:09.510, 59.940 fps progressive, 3840x2160x32, AVC
  Audio: 00:00:09.449, 48,000 Hz, Stereo, AACSummary
  [TCFM]: 6ACID information
  ACID chunk: no
  Stretch chunk: no
  Stretch list: no
  Stretch info2: no
  Beat markers: no
  Detected beats: noOther metadata
  Regions/markers: no
  Command markers: noMedia manager
  Media tags: noPlug-In
  Name: so4compoundplug.dll
  Folder: C:\Program Files\VEGAS\VEGAS Pro 17.0\FileIO Plug-Ins\so4compoundplug
  Format: AVC
  Version: Version 1.0 (Build 8532)
  Company: MAGIX Computer Products Intl. Co.

j-v wrote on 8/24/2019, 4:19 PM

Do you have a GPU?
I aske this because VP17 also has a very heavy task during editing those files.
I think now that only your CPU has to do that and that it is to much for it.
In VP 17 there is a new option to do that another way.
In Preferences/fileI/O is an option to give a lot of that task to the GPU to decode the AVC and HEVC files if yours can handle that.
At the moment only a Nvidia that suites the specifications of VP17 can do that with the Studio driver 431.70

kmaultsby wrote on 8/25/2019, 12:22 AM

Yes nVidia GTX 1070 8megs of memory and it is turn on\selected

kmaultsby wrote on 8/25/2019, 12:26 AM

I have 430.86 just installed 436.02

j-v wrote on 8/25/2019, 3:05 AM

... and it is turn on\selected

Where?
It has to be selected here

and for speeding up decoding and editing here

I have 430.86 just installed 436.02

That is the wrong one, it is the game ready driver and you need in Vegas the Studio driver

Musicvid wrote on 8/25/2019, 3:48 AM

Try this first:

https://www.vegascreativesoftware.info/us/forum/avc-xavc-s-issues-in-vp15-try-disabling-so4compoundplug-dll--108345/

kmaultsby wrote on 8/25/2019, 8:11 PM

Wait a minute please forgive me if this is a dump question but why is it has to be this driver version? How much Dynamic Ram preview Max should allocate? I have 32GB total on my system.

kmaultsby wrote on 8/25/2019, 8:13 PM

Vegas should be able to work with latest drivers not the other way around. If I go out a purchase a more powerful card I would have to rollback the driver which may cause other problems.

Musicvid wrote on 8/25/2019, 8:29 PM

@kmaultsby

What if it's not the driver?

What if it's the decoder?

Name: so4compoundplug.dll Folder: C:\Program Files\VEGAS\VEGAS Pro 17.0\FileIO Plug-Ins\so4compoundplug

Gave you a link.

kmaultsby wrote on 9/6/2019, 6:04 PM

@kmaultsby

What if it's not the driver?

What if it's the decoder?

Name: so4compoundplug.dll Folder: C:\Program Files\VEGAS\VEGAS Pro 17.0\FileIO Plug-Ins\so4compoundplug

Gave you a link.

Thank you Musicvid for the link. I went through the steps and it still crashed. I am going to do some more testing.

fr0sty wrote on 9/7/2019, 3:11 AM

"Vegas should be able to work with latest drivers not the other way around. If I go out a purchase a more powerful card I would have to rollback the driver which may cause other problems."

You aren't "rolling back" the drivers... The studio drivers are specifically optimized for Vegas 17, game ready drivers often have tweaks designed for specific games, but i've seen them more than once break compatibility with other apps from one driver update to another, so the studio driver is aimed at people like us who produce content.

From Nvidia's website... it also enabled 10 bit (30 bit as they call it) color support on all GPUs (apparently not just in external preview mode).

"Available today, the latest NVIDIA Studio Driver provides optimal support for the latest releases of top creative applications including Magix VEGAS Pro v17, Autodesk Arnold, Allegorithmic Substance Painter 2019.2, Blender 2.80, Cinema 4D R21, and Otoy Octane Render 2019.2.

30-bit color support

In addition, this new NVIDIA Studio Driver introduces support for 30-bit color across all product lines, including GeForce and TITAN, for the first time, allowing for seamless color transitions without banding. With 24-bit color, a pixel can be built from 16.7 million shades of color. By increasing to 30-bit color, a pixel can now be built from over 1 billion shades of color, which eliminates the abrupt changes in shades of the same color. "

andyrpsmith wrote on 9/7/2019, 5:31 AM

VP17 is working just fine with game drivers 436.15 (1080Ti). I am editing Sony XAVCS 4K using Preview Full (uses Proxy files). I have disabled so4compoundplug for AVC as it has always slowed everything down since its release. I do not have HEVC files. As NVIDIA does not hardware decode XAVCS just yet the GPU never goes above 11%.

fr0sty wrote on 9/7/2019, 5:42 AM

One working case on one hardware config isn't enough to say for sure that there isn't an issue with those drivers. There have been a number of people on these forums helped by upgrading to the studio driver, and being that Nvidia says it is optimized for Vegas, one would expect better performance and stability from it. Magix appears to be taking a wait and see approach, however, they still don't officially endorse the studio drivers.

AlesCZ wrote on 9/11/2019, 1:53 PM

I also have frequent crashing. It is good to save a project often.

i7 4790k, GTX 1080, GTX 1070

fr0sty wrote on 9/11/2019, 4:02 PM

Do you have both of those different GPUs in the same system? That's probably why. Your CPU is also below 17's minimum specs for 4k.

AlesCZ wrote on 9/12/2019, 6:02 AM

The processor is good. It is an older processor, but still powerful. Yes, I have both GPUs on one PC. I use GPUs to rendering 3D animations.

kmaultsby wrote on 10/12/2019, 8:02 PM

Well Vegas Pro 17 still crashing even with the latest update. I was thinking this was a 4K issue but it is occurring on regular HD projects this the latest. While playing back clips in the timeline the preview window playback black after pausing and playing back clips.

NickHope wrote on 10/13/2019, 12:39 AM

Try closing your VEGAS Explorer window. If that doesn't work, try closing your VEGAS Project Media window too.

paul-marshall wrote on 10/14/2019, 3:49 AM

I get frequent crashes/freezes when editing in 4K but if I edit using proxy files then no crashes. It's hard to pin down what I'm doing when it crashes. Usually I think it is just after splitting a clip on the timeline then starting to preview it. No amount of preveiwing crashes unless there is splitting clips. Editing in 4K is smooth and comforrtable but making proxy files takes a long time so I hope it can be fixed.

paul-marshall wrote on 10/15/2019, 6:30 AM

I wondered if it was related to this thread about crashing with Auto-ripple so I spent time editing without auto-ripple turned on (4K, no proxy). I got the impression it was much more stable. However it did crash after about a half-hour and a lot of edits. More tests needed.

Former user wrote on 10/15/2019, 8:20 AM

Do you have both of those different GPUs in the same system? That's probably why. Your CPU is also below 17's minimum specs for 4k.

What aspect of his i7 4790k is below minimum spec. It's a 4Ghz base (factory), is it something other than frequency that makes it beneath VP17 minimum specs?

From my limited memory and understanding of Intel history the Gen4 series intels was the last big jump in efficiency, making my gen3 I7 K series pretty obsolete.

j-v wrote on 10/15/2019, 9:59 AM

What aspect of his i7 4790k is below minimum spec.

It has only 4 cores and for 4K in VP17 minimum amount for editing is 8 cores.
Look at the specifications (for 4K edits)