Vegas Pro 17 Crashed with HEVC 10 bit clips

Constantine-VanHorne wrote on 8/12/2019, 11:09 AM

  Hello. My name is Constantine.

I a'm a licensed user. (I buy Vegas 16 and now update the Vegas 17)
When i try to import the HEVC, 4k LongGop, 10 bit, 420, 200 mbit (fuji xt3) video clips (70 clips, around 90 GB ) the Vegas 17 is crashed... always crashed. (in Vegas 16 I have the same problem). This problem in Vegas or some issue by Windows?  What i should do? Help Please! I want comfort work with Fuji X-T3 (HEVC 10 bit) footages. Thanks a LOT!

P.S. I did a lot of stress tests on RAM memory, CPU, GPU, open-CL, open-GL - all is well. (Aida64, FurMark, LuxMark, MemTest64)
           

System: Threadripper 1950 - 64gb(GSill 3200 Trident Z) - Vega FE 16 gb - 1000W Seasonic, Win 10 pro, SSD (Samsung EVO960, Samsung EVO 850, WD, Seagate (summury 15 tB)

 

Footage properties:

General
  Name: DSCF7014.MOV
  Folder: Z:\New Projects VII\Villen Italy\Video\ТОП
  Type: Intel HEVC
  Size: 177,96 MB (182 227 968 bytes)
  Created: 30 июня 2019 г., 23:56:26
  Modified: 16 июня 2019 г., 15:34:16
  Accessed: 30 июня 2019 г., 23:56:26
  Attributes: Archive

Streams
  Video: 00:00:07,007, 59,940 fps progressive, 4096x2160x32, HEVC
  Audio: 00:00:07,007, 48 000 Hz; Stereo, PCM

ACID information
  ACID chunk: no
  Stretch chunk: no
  Stretch list: no
  Stretch info2: no
  Beat markers: no
  Detected beats: no

Other metadata
  Regions/markers: no
  Command markers: no

Media manager
  Media tags: no

Plug-In
  Name: mxhevcplug.dll
  Folder: C:\Program Files\VEGAS\VEGAS Pro 17.0\FileIO Plug-Ins\mxhevcplug
  Format: Intel HEVC
  Version: Version 1.0 (Build 8532)
  Company: MAGIX Computer Products Intl. Co.
 

 

Vegas Pro 17 crash report:

Extra Information
   File:                C:\Users\User\AppData\Local\VEGAS Pro\17.0\fileio_x64.log
   File:                C:\Users\User\AppData\Local\VEGAS Pro\17.0\dx_video_grovel_x64.log
   File:                C:\Users\User\AppData\Local\VEGAS Pro\17.0\svfx_video_grovel_x64.log
   File:                C:\Users\User\AppData\Local\VEGAS Pro\17.0\ocio_x64.log
   File:                C:\Users\User\AppData\Local\VEGAS Pro\17.0\dx_grovel_x64.log
   File:                C:\Users\User\AppData\Local\VEGAS Pro\17.0\gpu_video_x64.log

Problem Description
   Application Name:    VEGAS Pro
   Application Version: Version 17.0 (Build 284)
   Problem:             Unmanaged Exception (0xe0434352)
   Fault Module:        C:\WINDOWS\System32\KERNELBASE.dll
   Fault Address:       0x00007FFB4B2EA839
   Fault Offset:        0x000000000003A839

Fault Process Details
   Process Path:        C:\Program Files\VEGAS\VEGAS Pro 17.0\vegas170.exe
   Process Version:     Version 17.0 (Build 284)
   Process Description: VEGAS Pro
   Process Image Date:  2019-07-30 (Tue Jul 30) 03:16:54

Comments

fr0sty wrote on 8/12/2019, 11:12 AM

Does it crash when you try to open 70 at once, or can you just import one clip and make it crash?

Constantine-VanHorne wrote on 8/12/2019, 11:49 AM

One moment...

 

I recorded a video (with Vegas Pro 17crashed) camera to screen, look, please. Maybe its help. Everything is clear there.

Constantine-VanHorne wrote on 8/12/2019, 11:52 AM

Thank you for responding.

Even if I download one by one file, somewhere in the middle of the clip list Vegas will crash...

...5 minutes.. I upload the video. Crashed wen one by one imports...

Alternative link with videos - https://fex.net/s/m1zmxbo

Constantine-VanHorne wrote on 8/12/2019, 12:01 PM

Please HELP! SOS!

fr0sty wrote on 8/12/2019, 12:05 PM

Ok, that gets us started. Please download a program called mediainfo and use it to generate a report on one of your files, then post it here. Also please post your project settings.

A couple things to check out before we move on...

1. Make sure your GPU driver is current. If using an Nvidia card, make sure you use the studio drivers if your card supports them.

2. As a test, temporarily disable timeline thumbnail display by going to preferences>video and changing the setting to not display any thumbs. I don't think this bug is affecting you, but if it is this will isolate the cause.

Please try those 2 things and see if they help, and let me know if they do. If not, we've got a few more steps to nail down the problem so we can get it to the team in the form of a bug report. There's also some alternative import methods we can use to get you going in the mean time.

Edit: I see your project settings in the video (it hadn't loaded yet before)... standard 8 bit project. No need to post those anymore, thanks.

Can you try to import the files by going to File>Import instead of using the file explorer window and see if it does the same thing?

Last changed by fr0sty on 8/12/2019, 12:11 PM, changed a total of 2 times.

Systems:

Desktop

AMD Ryzen 7 1800x 8 core 16 thread at stock speed

64GB 3000mhz DDR4

Geforce RTX 3090

Windows 10

Laptop:

ASUS Zenbook Pro Duo 32GB (9980HK CPU, RTX 2060 GPU, dual 4K touch screens, main one OLED HDR)

adis-a3097 wrote on 8/12/2019, 12:13 PM

I see it crashed the moment you "touched" that eleventh .mov file. What happens if you skip it? Does it crush?

Is the file itself corrupt?

fr0sty wrote on 8/12/2019, 12:15 PM

Another thing to try: Happy Otter Scripts has a tool called Import Assist that can take your footage and transcode it to a lossless intermediate format before importing it. That script kit can be found over at www.tools4vegas.com (currently free while in beta). This is a band-aid solution to get you working while we sort out the cause of this problem, so you aren't delayed on your project.

Last changed by fr0sty on 8/12/2019, 12:15 PM, changed a total of 1 times.

Systems:

Desktop

AMD Ryzen 7 1800x 8 core 16 thread at stock speed

64GB 3000mhz DDR4

Geforce RTX 3090

Windows 10

Laptop:

ASUS Zenbook Pro Duo 32GB (9980HK CPU, RTX 2060 GPU, dual 4K touch screens, main one OLED HDR)

Constantine-VanHorne wrote on 8/12/2019, 12:22 PM

Thanks!

I add a text file with media info properties and screenshot with Project Settings... Please look below.

Constantine-VanHorne wrote on 8/12/2019, 12:27 PM

I see it crashed the moment you "touched" that eleventh .mov file. What happens if you skip it? Does it crush?

Is the file itself corrupt?

 

If I do not use the eleventh file (previus file before crash), then there will be no crashes, but it can happen during work withem little soon.

Constantine-VanHorne wrote on 8/12/2019, 12:28 PM

Ok, that gets us started. Please download a program called mediainfo and use it to generate a report on one of your files, then post it here. Also please post your project settings.

A couple things to check out before we move on...

1. Make sure your GPU driver is current. If using an Nvidia card, make sure you use the studio drivers if your card supports them.

2. As a test, temporarily disable timeline thumbnail display by going to preferences>video and changing the setting to not display any thumbs. I don't think this bug is affecting you, but if it is this will isolate the cause.

Please try those 2 things and see if they help, and let me know if they do. If not, we've got a few more steps to nail down the problem so we can get it to the team in the form of a bug report. There's also some alternative import methods we can use to get you going in the mean time.

Edit: I see your project settings in the video (it hadn't loaded yet before)... standard 8 bit project. No need to post those anymore, thanks.

Can you try to import the files by going to File>Import instead of using the file explorer window and see if it does the same thing?

Can you try to import the files by going to File>Import instead of using the file explorer window and see if it does the same thing? - THE SAME, CRASHED. (this is visible in the video above)

j-v wrote on 8/12/2019, 12:29 PM

Did you let the first added file decide which project has to be used or do you use your own made project?

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 576.02 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)

 

Constantine-VanHorne wrote on 8/12/2019, 12:31 PM

Ok, that gets us started. Please download a program called mediainfo and use it to generate a report on one of your files, then post it here. Also please post your project settings.

A couple things to check out before we move on...

1. Make sure your GPU driver is current. If using an Nvidia card, make sure you use the studio drivers if your card supports them.

2. As a test, temporarily disable timeline thumbnail display by going to preferences>video and changing the setting to not display any thumbs. I don't think this bug is affecting you, but if it is this will isolate the cause.

Please try those 2 things and see if they help, and let me know if they do. If not, we've got a few more steps to nail down the problem so we can get it to the team in the form of a bug report. There's also some alternative import methods we can use to get you going in the mean time.

Edit: I see your project settings in the video (it hadn't loaded yet before)... standard 8 bit project. No need to post those anymore, thanks.

Can you try to import the files by going to File>Import instead of using the file explorer window and see if it does the same thing?

I have AMD RADEON Frontier Edition 16 GB with Threadripper 1950x.

Constantine-VanHorne wrote on 8/12/2019, 1:53 PM

Did you let the first added file decide which project has to be used or do you use your own made project?

 

Yes, I did. I also tried to set 32 bit (full range again 8 bit) ​​in the project settings. Does not help.

Constantine-VanHorne wrote on 8/12/2019, 2:10 PM

Another thing to try: Happy Otter Scripts has a tool called Import Assist that can take your footage and transcode it to a lossless intermediate format before importing it. That script kit can be found over at www.tools4vegas.com (currently free while in beta). This is a band-aid solution to get you working while we sort out the cause of this problem, so you aren't delayed on your project.

Tell, please, lossless intermediate have 10 bit profile?

fr0sty wrote on 8/12/2019, 2:10 PM

So, I did some digging around on that fault module, and found this:

https://answers.microsoft.com/en-us/windows/forum/all/fault-module-cwindowssystem32kernelbasedll/032785b6-daa0-49a7-9078-cd4e34ae234d

This may be more of a windows issue than a Vegas issue. Follow the tips they suggest and see if that helps.

 

adis-a3097 wrote on 8/12/2019, 2:20 PM

And I found this:

 

https://troubleshooter.xyz/wiki/fix-the-exception-unknown-software-exception-0xe0434352/

Constantine-VanHorne wrote on 8/12/2019, 2:43 PM

Thanks so much for all! I'll try. Give you result soon.

fr0sty wrote on 8/12/2019, 9:14 PM

Those intermediates are indeed 10 bit, by the way. Make sure your color space settings match in the encode settings as well.

Last changed by fr0sty on 8/12/2019, 9:14 PM, changed a total of 1 times.

Systems:

Desktop

AMD Ryzen 7 1800x 8 core 16 thread at stock speed

64GB 3000mhz DDR4

Geforce RTX 3090

Windows 10

Laptop:

ASUS Zenbook Pro Duo 32GB (9980HK CPU, RTX 2060 GPU, dual 4K touch screens, main one OLED HDR)

mikelinton wrote on 12/27/2019, 5:41 PM

I have the exact same issue. Similar setup as well. Radeon VII and Ryzen 1950. The footage will play fine in Windows, but drop them into Vegas and the screen will go black and crash the GPU and Vegas. Been an issue since Vegas 16 and have tried a bunch of stuff and nothing seems to resolve it. There are other people reporting crashes in Davinci and just within Windows on the same setup but without any resolution. If you disable GPU acceleration in Vegas it will work but then it's so slow you can't edit the footage. As far as I can tell the only solution is to transcode all your footage into another format. Which is super annoying. I'm assuming it's a combination of the AMD Vega drivers and it trying to decode the H265. I haven't had a chance but will try a different GPU when I can and see what happens.

fr0sty wrote on 12/27/2019, 8:29 PM

I too have a Radeon 7, if someone can share a sample clip to try I will see if I can reproduce it.

BruceUSA wrote on 12/27/2019, 9:40 PM

I am running the same CPU/GPU as you but perhaps in higher clock speed then you. Here is my first hand experience with Fuji XT3 10 bit 4K 50P footage. My system can run smooth in between 48-50 frames but in Draft (half) because Magix have not supports AMD decode in .h264h265. The good thing is I don't get crash or freeze with XT3 footage. At least I have not had it. Just bad scrubbing on the TL. Other then that, it is ok to work with.

Last changed by BruceUSA on 12/27/2019, 9:45 PM, changed a total of 1 times.

Intel i9 Core Ultra 285K Overclocked all P Cores @5.6, all E-Cores @5ghz               

MSI MEG Z890 ACE Gaming Wifi 7 10G Super Lan, thunderbolt 4                                

48GB DDR5 -8200mhz Overclocked @8800mhz                  

Crucial T705 nvme .M2 2TB Gen 5  OS. 4TB  gen 4 storage                    

RTX 5080 16GB  Overclocked 3.1ghz, Memory Bandwidth increased from 960 GB/s to 1152 GB/s                                                            

Custom built hard tube watercooling.                            

MSI PSU 1250W, Windows 11 Pro

 

BruceUSA wrote on 12/27/2019, 10:04 PM

Another option is that you can try to transcode your footage using Rocky Mountain converter (free app) to h264 10 bit. This will get you smooth editing in best full. Give that a try.

Intel i9 Core Ultra 285K Overclocked all P Cores @5.6, all E-Cores @5ghz               

MSI MEG Z890 ACE Gaming Wifi 7 10G Super Lan, thunderbolt 4                                

48GB DDR5 -8200mhz Overclocked @8800mhz                  

Crucial T705 nvme .M2 2TB Gen 5  OS. 4TB  gen 4 storage                    

RTX 5080 16GB  Overclocked 3.1ghz, Memory Bandwidth increased from 960 GB/s to 1152 GB/s                                                            

Custom built hard tube watercooling.                            

MSI PSU 1250W, Windows 11 Pro

 

Musicvid wrote on 12/27/2019, 10:40 PM

Another option is that you can try to transcode your footage using Rocky Mountain converter (free app) to h264 10 bit. This will get you smooth editing in best full. Give that a try.

VEGAS 14 does not support Hi10p profile h264, and I suspect later versions do not either, as it is a lame duck format. Looking at their SourceForge page, I don't see bit depth, profile, or level options either.

Handbrake will encode to 10 bit x265, but through an 8 bit pipeline. That leaves me with VideoRedo 6, a paid solution, that will transcode to 10 bit x265 door-to-door. I can test a source sample if OP wishes

May be quite a bit easier on your decoders than MOV source.

 

frmax wrote on 12/28/2019, 6:39 AM

While probably not the solution to your problem, I recommend that you update from build 284 to the current build 387

I9900K, RTX 2080, 32GB RAM, 512Mb M2, 1TB SSD, VEGAS Pro 14-20 (Post), Magix ProX, HitfilmPro
AMD 5900, RTX 3090 TI, 64GB RAM, 1 TB M2 SSD, 4 TB HD, VP 21 Post, VP22

Monitor LG 32UN880; Camera Sony FDR-AX53; Photo Canon EOS, Samsung S22 Ultra