Vegas Pro 21 Build 187 Hang when previewing DJI Action 4 footage

baksideDisaster_Flicks wrote on 12/4/2023, 10:29 PM

So I'm hitting a bug where Vegas 21 Build 187 hangs whenever I try to use .mp4 files from DJI Action 4 camera. All I need to do to reproduce the problem is import the footage and open up in the Trimmer and it will hang. Eventually Windows will detect hang and I can close, or end task to get out but it's basically useless with any of this footage.

I have dump file saved and can upload to Google Drive if someone wants to take a look.

On the same exact system and configuration, I can use this footage fine on Vegas 20 Build 411. I completed a couple hour editing session on Vegas 20 without issue so looks to be unique to Vegas 21.

Here's my system configuration, and yes I am using the latest NVDIA Studio driver from 11/01/23.

OS Name   Microsoft Windows 11 Pro
Version   10.0.22621 Build 22621
Other OS Description    Not Available
OS Manufacturer   Microsoft Corporation
System Manufacturer   ASUS
System Model   System Product Name
System Type   x64-based PC
System SKU   SKU
Processor   12th Gen Intel(R) Core(TM) i9-12900K, 3200 Mhz, 16 Core(s), 24 Logical Processor(s)
BIOS Version/Date   American Megatrends Inc. 2802, 9/27/2023
SMBIOS Version   3.4
Embedded Controller Version   255.255
BIOS Mode   UEFI
BaseBoard Manufacturer   ASUSTeK COMPUTER INC.
BaseBoard Product   ProArt Z690-CREATOR WIFI
BaseBoard Version   Rev 1.xx
Platform Role   Desktop

Item   Value
Name   NVIDIA GeForce RTX 3080
PNP Device ID   PCI\VEN_10DE&DEV_2216&SUBSYS_403F1458&REV_A1\4&22F77229&0&0008
Adapter Type   NVIDIA GeForce RTX 3080, NVIDIA compatible
Adapter Description   NVIDIA GeForce RTX 3080
Adapter RAM   (1,048,576) bytes
Installed Drivers   C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispsi.inf_amd64_e5945553c918086b\nvldumdx.dll,C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispsi.inf_amd64_e5945553c918086b\nvldumdx.dll,C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispsi.inf_amd64_e5945553c918086b\nvldumdx.dll,C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispsi.inf_amd64_e5945553c918086b\nvldumdx.dll
Driver Version   31.0.15.4601

Footage:

DJI ACTION 4 - 3840x2160 50FPS MP4, BitRate: 315kbps Audio : 48kHZ

pb_file:dvtm_ac203.proto; model_name:AC003; pb_version:2.0.1; pb_lib_version:02.00.04;

Comments

RogerS wrote on 12/4/2023, 11:15 PM

Is the iGPU enabled in bios? If not enable it so it can do the decoding.

Can you share mediainfo for the media? I have no idea what mp4 means- is it HEVC? AVC? 10-bit?

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

Can you upload a sample of it so we can test on other machines?

baksideDisaster_Flicks wrote on 12/5/2023, 6:45 PM

Why should I enable iGPU when I have a dedicated GPU?

Here's repro project with couple MP4s from DJI Action 4 camera. Seems to repro the easiest with multiple files.
https://drive.google.com/file/d/1-0t6r41X8BfUb8IlGVpVheX0eSPNvQd7/view?usp=sharing

Most reliable repro, usually hangs somewhere in one of these steps:

1. Start new project

2. Import DJI Action 4 camera mp4s

3. Add one file to timeline and accept project settings change

4. Open file in Trimmer and scrub

baksideDisaster_Flicks wrote on 12/5/2023, 6:48 PM

Media info:

General
Complete name : E:\2023-12-02 GC 1st BC\DJI_ACTN4\DJI_20231201163935_0322_D.MP4
Format : MPEG-4
Format profile : Base Media
Codec ID : isom (isom/iso2/mp41)
File size : 468 MiB
Duration : 55 s 701 ms
Overall bit rate : 70.5 Mb/s
Frame rate : 50.000 FPS
Encoded date : 2023-12-02 00:39:36 UTC
Tagged date : 2023-12-02 00:39:36 UTC
Writing application : DJI OsmoAction4
Cover : Yes
snal : (Binary)
tnal : (Binary)

Video
ID : 1
Format : HEVC
Format/Info : High Efficiency Video Coding
Format profile : Main 10@L5@High
Codec ID : hvc1
Codec ID/Info : High Efficiency Video Coding
Duration : 55 s 680 ms
Bit rate : 67.0 Mb/s
Width : 3 840 pixels
Height : 2 160 pixels
Display aspect ratio : 16:9
Rotation : 180°
Frame rate mode : Constant
Frame rate : 50.000 FPS
Color space : YUV
Chroma subsampling : 4:2:0
Bit depth : 10 bits
Bits/(Pixel*Frame) : 0.162
Stream size : 445 MiB (95%)
Encoded date : 2023-12-02 00:39:36 UTC
Tagged date : 2023-12-02 00:39:36 UTC
Color range : Limited
Color primaries : BT.709
Transfer characteristics : BT.709
Matrix coefficients : BT.709
Codec configuration box : hvcC

Audio
ID : 2
Format : AAC LC
Format/Info : Advanced Audio Codec Low Complexity
Codec ID : mp4a-40-2
Duration : 55 s 701 ms
Bit rate mode : Constant
Bit rate : 317 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 : 2.11 MiB (0%)
Default : Yes
Alternate group : 1
Encoded date : 2023-12-02 00:39:36 UTC
Tagged date : 2023-12-02 00:39:36 UTC

Other #1
ID : 3
Type : meta
Format : djmd
Codec ID : djmd
Duration : 55 s 680 ms
Bit rate mode : Variable
Title : DJI meta
Default : No
Alternate group : 5
Encoded date : 2023-12-02 00:39:36 UTC
Tagged date : 2023-12-02 00:39:36 UTC

Other #2
ID : 4
Type : meta
Format : dbgi
Codec ID : dbgi
Duration : 55 s 680 ms
Bit rate mode : Variable
Title : DJI dbgi
Default : No
Alternate group : 5
Encoded date : 2023-12-02 00:39:36 UTC
Tagged date : 2023-12-02 00:39:36 UTC

Other #3
ID : 7
Type : Time code
Format : QuickTime TC
Duration : 55 s 680 ms
Frame rate : 25.000 FPS
Time code of first frame : 19:51:18:00
Time code of last frame : 19:52:13:16
Time code, stripped : Yes
Default : No
Alternate group : 2
Encoded date : 2023-12-02 00:39:36 UTC
Tagged date : 2023-12-02 00:39:36 UTC

Former user wrote on 12/5/2023, 7:19 PM

I confirm VP21b187 crashing

Also my vegas changed aspect ratio on crash with a white rectangle . @baksideDisaster_Flicks do you get the same sort of crash ?

baksideDisaster_Flicks wrote on 12/5/2023, 7:45 PM

I don't get aspect ratio change but same style hang. Looks like we have a bug here.

RogerS wrote on 12/5/2023, 7:45 PM

Why should I enable iGPU when I have a dedicated GPU?

Because QSV decoding works better in VEGAS than NVDEC, especially with HEVC.

RogerS wrote on 12/5/2023, 10:56 PM

For what it's worth I can't trigger this crash with my laptop (Intel QSV decoding). I tried the timeline and most of the clips in the trimmer, too.

john_dennis wrote on 12/6/2023, 12:57 AM

I haven't been able to reproduce your issues with the machine in my signature.

baksideDisaster_Flicks wrote on 12/6/2023, 1:41 PM

So Intel works, Nvida doesn't. I didn't buy a $1k GPU not to use it, and I didn't buy Vegas 21 not to use it but right now my only choice is Vegas 20. So someone from Magix going to take a look at this?

VEGASDerek wrote on 12/6/2023, 2:14 PM

Yes...someone from Magix has been looking into these hangs.

j-v wrote on 12/6/2023, 2:29 PM

@baksideDisaster_Flicks
Vegas is more than only a videoplayer
For that more ( changing video, making stories, render to all kind of destinations) it needs and uses your Nvidia when selected in Options/Preferences/Video

GJeffrey wrote on 12/6/2023, 4:12 PM

Have you tried using the experinental hevc decoder in VP21?

RogerS wrote on 12/6/2023, 6:26 PM

So Intel works, Nvida doesn't. I didn't buy a $1k GPU not to use it, and I didn't buy Vegas 21 not to use it but right now my only choice is Vegas 20. So someone from Magix going to take a look at this?

@baksideDisaster_Flicks What you paid the money for is the ability to do fast 3D calculations and it excels at that. In VEGAS that's found in preferences/ video.

NVIDIA also includes separate circuitry for decoding and encoding: https://developer.nvidia.com/video-codec-sdk

Unlike 3D, decoding isn't really any thing much different than what Intel can do with the integrated GPU. Intel's been at it for the longest and has support for formats that AMD and NVIDIA do not. Speedwise there aren't big differences between dedicated and integrated. VEGAS works best with Intel QSV for decoding and has for some time. I built my machine around an Intel K CPU for that reason.

It certainly shouldn't crash but even when it works NVIDIA is inferior to QSV in VEGAS (both my computers have NVIDIA GPUs) so the best approach at present is a combination of both of them, not one or the other. Decoding is controlled by preferences/ file io.

baksideDisaster_Flicks wrote on 12/8/2023, 1:12 PM

So Intel works, Nvida doesn't. I didn't buy a $1k GPU not to use it, and I didn't buy Vegas 21 not to use it but right now my only choice is Vegas 20. So someone from Magix going to take a look at this?

@baksideDisaster_Flicks What you paid the money for is the ability to do fast 3D calculations and it excels at that. In VEGAS that's found in preferences/ video.

NVIDIA also includes separate circuitry for decoding and encoding: https://developer.nvidia.com/video-codec-sdk

Unlike 3D, decoding isn't really any thing much different than what Intel can do with the integrated GPU. Intel's been at it for the longest and has support for formats that AMD and NVIDIA do not. Speedwise there aren't big differences between dedicated and integrated. VEGAS works best with Intel QSV for decoding and has for some time. I built my machine around an Intel K CPU for that reason.

It certainly shouldn't crash but even when it works NVIDIA is inferior to QSV in VEGAS (both my computers have NVIDIA GPUs) so the best approach at present is a combination of both of them, not one or the other. Decoding is controlled by preferences/ file io.

Vegas 21 has a reliability issue, I'd like to see that fixed. It should work out the box without me having to monkey around with my system. Vegas 20 just works and I'm no stranger to Vegas, been here since 6.0. With that, thanks for the tech dump I'll look into QSV and enabling it to see if it works any better.

RogerS wrote on 12/8/2023, 4:36 PM

This isn't new to VP 21 and NVDEC has issues with many types of footage from 15 on (intermittent crashes are worse than immediate in my book as you don't know when they'll cause trouble).

Of course we want the problems fixed and until that day comes need to do what we can to keep working.

baksideDisaster_Flicks wrote on 12/12/2023, 9:56 PM

This isn't new to VP 21 and NVDEC has issues with many types of footage from 15 on (intermittent crashes are worse than immediate in my book as you don't know when they'll cause trouble).

Of course we want the problems fixed and until that day comes need to do what we can to keep working.

Works fine in Vegas 20. This is a regression in Vegas 21. I can edit with same footage all day, same pc, same config with no issues. Right now I guess what I need do is still edit in Vegas 20. 😠

pajam wrote on 12/16/2023, 8:32 AM

This isn't new to VP 21 and NVDEC has issues with many types of footage from 15 on (intermittent crashes are worse than immediate in my book as you don't know when they'll cause trouble).

Of course we want the problems fixed and until that day comes need to do what we can to keep working.

Works fine in Vegas 20. This is a regression in Vegas 21. I can edit with same footage all day, same pc, same config with no issues. Right now I guess what I need do is still edit in Vegas 20. 😠

It worked well for me in Vegas 21 build 108 and another 187, 208 kept crashing. I selected IGD in the bios and now the 208 is very stable, it hasn't crashed yet. Both cards allocate work as needed. Vegas settings see below

RogerS wrote on 12/16/2023, 6:43 PM

What's IGD mean? IGPU?

Dynamic ram preview amount looks needlessly high, VEGAS can also use ram for other things.

pajam wrote on 12/18/2023, 1:27 AM

IGD is the same as IGPU - IGD is integrated graphics

The dynamic preview of RAM is functional this way and does not limit me in anything yet. 😉

RogerS wrote on 12/18/2023, 2:07 AM

@pajam Dynamic ram preview takes away memory VEGAS can use for other purposes. At present VEGAS is doing more to cache frames in video ram and your iGPU uses shared (system) ram for this.

You are welcome to test it yourself- you will see no performance benefits from dynamic ram preview after a few GB.

pajam wrote on 12/18/2023, 2:48 AM

OK, thanks for the advice, I'll try it.

baksideDisaster_Flicks wrote on 12/19/2023, 2:32 PM

Still reproducing with new Vegas 21 Build 208. 😭

Reyfox wrote on 12/21/2023, 6:47 AM

Ok... I decided to add my 2 groszy, cents, pence, to the conversation. My computer specs are below in my signature.

I have had zero issues with the footage with timeline playback, editing and using the Trimmer. None.

Oh, and it looks cold out there!!!

Robert Johnston wrote on 12/23/2023, 4:46 PM

@baksideDisaster_Flicks No problems with your project on my system as long as I use Nvidia Geforce 2060 RTX Super for the decoder. Playback is a smooth 50 fps, even at Best - Full.

If I use the Intel 630 HD integrated for the decoder, playback is bad. The Intel 630 HD isn't that great. Later versions may prove better. If I use HEVC (experimental), playback is bad.

Vegas 21 Build 208.