Vegas Pro 17 - Problems with 10BIT H265 Files.

Kloverton wrote on 8/6/2019, 5:55 AM

Hello again. I'm sorry for my emotional post yesterday.

I figured out that certain files don't work correctly in VP17 and it crashes.

Those are 10BIT 21:9 4K HDR Files recorded in h265 from Xperia 1.

Works fine in Vegas 16 though. Thats the module that crashes - Something to do with HEVC.

VEGAS Pro 17.0\FileIO Plug-Ins\mxhevcplug\MXVideoAllocator.dll

i7 7820HK, GTX 1080, 32GB RAM , WIN 10

Comments

Marco. wrote on 8/6/2019, 5:59 AM

Any chance to share a sample clip for download?

fr0sty wrote on 8/6/2019, 6:05 AM

Also, knowing your system specs can help.

Processor, GPU, amount of RAM, Operating system (well, this one isn't important anymore since V17 requires windows 10)

Kloverton wrote on 8/6/2019, 6:12 AM

Any chance to share a sample clip for download?

Sure - https://drive.google.com/open?id=1N_hBNWU9cwmNkkX4tLWbFtyZweq3La7t

fr0sty wrote on 8/6/2019, 6:37 AM

I was able to import the clip just fine, but before I did, I went into preferences, clicked the deprecated features tab, and enabled quicktime. See if that helps. Be sure to reboot vegas after.

Marco. wrote on 8/6/2019, 6:59 AM

This clip is working fine here in VP17 even while Quicktime is still disabled. It's decoded via the mxhevcplug.dll.

j-v wrote on 8/6/2019, 7:12 AM

Here also no problem with that file on laptop from signature without anything special done, also no QT.

fr0sty wrote on 8/6/2019, 1:25 PM

Please send us your hardware configuration (CPU, GPU, how much RAM, your GPU driver version, which you can access via your GPU's control panel. might be a good idea to grab the latest version and see if that helps as well). Looks like whatever your issue is happens to be specific to your hardware and software/driver configuration, and this info will help isolate that.

Kloverton wrote on 8/6/2019, 5:10 PM

Please send us your hardware configuration (CPU, GPU, how much RAM, your GPU driver version, which you can access via your GPU's control panel. might be a good idea to grab the latest version and see if that helps as well). Looks like whatever your issue is happens to be specific to your hardware and software/driver configuration, and this info will help isolate that.

i7 7820HK, GTX 1080 431.70, 32gb ram 2600mhz, 4k gsync tochscreen display. Laptop is - Razer Blade Pro 2017.

fr0sty wrote on 8/6/2019, 5:18 PM

You're having the same issue with both systems?

Kloverton wrote on 8/6/2019, 5:22 PM

You're having the same issue with both systems?

I cant try on my desktop now, cause it's in different country. Those specs were for my laptop.

fr0sty wrote on 8/6/2019, 5:31 PM

I've passed this on to the developers, hopefully they can help find a solution or this can help them find and fix the bug. In the mean time, Happy Otter Scripts' (tools4vegas.com) import assist might help get the file into Vegas for you so you can edit it. You can use it to encode the file to a lossless intermediate format.

VEGASHeman wrote on 8/6/2019, 7:31 PM

Kloverton, I am one of the VEGAS Engineers, and like posters above, I also could not reproduce the problem after downloading the file. But the module you listed (MXVideoAllocator.dll) is a new component added to VP17, so I assume this is a problem related to it. Could you recreate the crash, and send in a problem report, listing your name in the comments field, so we can search for it and take a deeper look?

In the meantime, as you have a GTX 1080 on that machine, you may want to enable the NVIDIA NVDEC hardware decoder (from Preferences -> FileIO), and try to use it instead till we sort out this problem.

Andrey3008 wrote on 10/15/2019, 9:12 PM

Kloverton, I am one of the VEGAS Engineers, and like posters above, I also could not reproduce the problem after downloading the file. But the module you listed (MXVideoAllocator.dll) is a new component added to VP17, so I assume this is a problem related to it. Could you recreate the crash, and send in a problem report, listing your name in the comments field, so we can search for it and take a deeper look?

In the meantime, as you have a GTX 1080 on that machine, you may want to enable the NVIDIA NVDEC hardware decoder (from Preferences -> FileIO), and try to use it instead till we sort out this problem.

I have the same problem, Vegas 17 crashes and the method you described helped me. (switch hardware decoder to use intel changed intel to nvidia)
I have h265 sources shot on iphone 7
win10, i7 2600k, 16gb, gtx 1060 6gb, driver 436.48
comes to the fact that along with vegas the video driver crashes.

Problem Description
Application Name: VEGAS Pro
Application Version: Version 17.0 (Build 284)
Problem: Unmanaged Exception (0xc0000005)
Fault Module: C:\Program Files\VEGAS\Vegas Pro 17\FileIO Plug-Ins\mxhevcplug\MXVideoAllocator.dll
Fault Address: 0x00007FF917CF1758
Fault Offset: 0x0000000000001758

Fault Process Details
Process Path: C:\Program Files\VEGAS\Vegas Pro 17\vegas170.exe
Process Version: Version 17.0 (Build 284)
Process Description: VEGAS Pro
Process Image Date: 2019-08-05 (Mon Aug 05) 02:55:20

NickHope wrote on 10/15/2019, 10:50 PM

@Andrey3008 Update to build 321.

AVsupport wrote on 10/15/2019, 10:59 PM

.. and nVidia Creator drivers if you're using it ;-)