Pro14 aborts on Resolve and Media Composer Export

Offworlder wrote on 4/13/2017, 8:48 AM

Attempting to export an hour-long project to Resolve for color grading, also tried to export as Media Composer.

Trying this approach since my ProRes output has out of sync audio, even after importing back into Vegas. Someone suggested FFmpeg to re-sync and will attempt however...

Export to Resolve exports about 80-90% of the files and then freezes with a non-descriptive log error message (no code)

Anyone experience or have suggested workarounds, thanks

 

Custom workstation build:

ASRock X99 WS LGA-2011, Intel i7-6850K 15M Broadwell-E 6-Core 3.6 GHz , Toshiba OCZ RD400 SSD NVMe M.2 512GB, G.SKILL TridentZ 32GB DDR4, EVGA GeForce GTX 1080 FTW ACX 3.0, 8GB GDDR5X, 8TB Raid 0, 5TB backup/hot swap, NZXT Phantom 630 case. Vegas 14, Resolve 12.5, Affinity Photo - lots of cooling <g>

Last changed by Offworlder

Custom workstation build: ASRock X99 WS LGA-2011, Intel i7-6850K 15M Broadwell-E 6-Core 3.6 GHz , Toshiba OCZ RD400 SSD NVMe M.2 512GB, G.SKILL TridentZ 32GB DDR4, EVGA GeForce GTX 1080 FTW ACX 3.0, 8GB GDDR5X, 8TB Raid 0, 5TB backup/hot swap, NZXT Phantom 630 case. Vegas 14, Resolve 12.5, Affinity Photo - lots of cooling <g>

Comments

john_dennis wrote on 4/13/2017, 11:10 AM

"Export to Resolve exports about 80-90% of the files and then freezes with a non-descriptive log error message (no code)

Anyone experience or have suggested workarounds, thanks"

For a one hour render, you probably weren't watching the preview just before it failed, but I would suggest trying to identify what was being processed right before the freeze. Look for a particular type of media or effect.

Divide and Conquer  

Try rendering just the suspect area on the timeline.

Offworlder wrote on 4/13/2017, 11:45 AM

Interesting, will try, thanks.

 

Custom workstation build: ASRock X99 WS LGA-2011, Intel i7-6850K 15M Broadwell-E 6-Core 3.6 GHz , Toshiba OCZ RD400 SSD NVMe M.2 512GB, G.SKILL TridentZ 32GB DDR4, EVGA GeForce GTX 1080 FTW ACX 3.0, 8GB GDDR5X, 8TB Raid 0, 5TB backup/hot swap, NZXT Phantom 630 case. Vegas 14, Resolve 12.5, Affinity Photo - lots of cooling <g>

NickHope wrote on 4/15/2017, 5:34 AM

In light of this and your ProRes audio sync issue, maybe you could try a different format to export to Resolve. The ProRes implementation in Vegas is still buggy and I would only use it if I absolutely had to, for example for delivery to a client who demands it.

I have never used Resolve but if I did I would try Cineform. To get the Cineform codecs you need to install GoPro Quik|Desktop. Resolve 12.5 Supported Formats and Codecs list is here. Note "Cineform YUV 10 bit in AVI format".

Having said all that, there may be something in your project that would crash any render at the 80-90% point, as John referred to.

Offworlder wrote on 4/15/2017, 1:46 PM

I have to use either ProRes or export to Resolve, if I want my post house to Color Grade, in light of an inability to go down either path, I don't have an option to get them a file to use in Resolve.

I will see if they have imported and worked with a Cineform file first but will certainly explore that option.

The ProRes sync issue is not specific to the entire file as I test rendered a <2 minute file and had the same audio sync drift

As for export and since I have no trust in this platform, I literally have save a new veg file every day (with that date) I have worked on this project for the past number of months, no Veg file will allow for me to export

I appreciate your input ~

 

 

 

Custom workstation build: ASRock X99 WS LGA-2011, Intel i7-6850K 15M Broadwell-E 6-Core 3.6 GHz , Toshiba OCZ RD400 SSD NVMe M.2 512GB, G.SKILL TridentZ 32GB DDR4, EVGA GeForce GTX 1080 FTW ACX 3.0, 8GB GDDR5X, 8TB Raid 0, 5TB backup/hot swap, NZXT Phantom 630 case. Vegas 14, Resolve 12.5, Affinity Photo - lots of cooling <g>

Offworlder wrote on 4/15/2017, 2:30 PM

Nick,

The GoPro link is for their camera application how does that install the CODEC you mentioned which Vegas can access? Doing so does not add a profile to Magix and point the GoPro app to a folder with output media in Vegas does not see any media?

 

 

Custom workstation build: ASRock X99 WS LGA-2011, Intel i7-6850K 15M Broadwell-E 6-Core 3.6 GHz , Toshiba OCZ RD400 SSD NVMe M.2 512GB, G.SKILL TridentZ 32GB DDR4, EVGA GeForce GTX 1080 FTW ACX 3.0, 8GB GDDR5X, 8TB Raid 0, 5TB backup/hot swap, NZXT Phantom 630 case. Vegas 14, Resolve 12.5, Affinity Photo - lots of cooling <g>

Kinvermark wrote on 4/15/2017, 8:32 PM

Installing GOPRO studio will install the latest cineform codec.  You can access it when rendering a "video for windows avi" file.  Start with any avi template and then modify it for your required frame rate, size , etc.  (under video format choose cineform codec, then modify for high quality or filmscan if you want to go totally over the top).  

So, this will allow you to render out a single "lossless" intermediate file that will work with Resolve.  Is that what you want?

NickHope wrote on 4/15/2017, 10:26 PM

That's right:

And it also installs Cineform as a Quicktime option, but according to the list in my previous post, Resolve only supports the avi version.

Offworlder wrote on 4/18/2017, 8:41 PM

Installing GOPRO studio will install the latest cineform codec.  You can access it when rendering a "video for windows avi" file.  Start with any avi template and then modify it for your required frame rate, size , etc.  (under video format choose cineform codec, then modify for high quality or filmscan if you want to go totally over the top).  

So, this will allow you to render out a single "lossless" intermediate file that will work with Resolve.  Is that what you want?

 

And so it does - will let you know how it goes. Yes, goal is to get to Resolve so my post-house can Grade. As I have locked the edit, they can then render out directly to web.

Thanks

 

On separate note, wish Magix would understand technical support/customer service is important, if they wish to compete against other NLE's

Last changed by Offworlder on 4/18/2017, 8:42 PM, changed a total of 1 times.

Custom workstation build: ASRock X99 WS LGA-2011, Intel i7-6850K 15M Broadwell-E 6-Core 3.6 GHz , Toshiba OCZ RD400 SSD NVMe M.2 512GB, G.SKILL TridentZ 32GB DDR4, EVGA GeForce GTX 1080 FTW ACX 3.0, 8GB GDDR5X, 8TB Raid 0, 5TB backup/hot swap, NZXT Phantom 630 case. Vegas 14, Resolve 12.5, Affinity Photo - lots of cooling <g>

Offworlder wrote on 4/18/2017, 8:48 PM

Vegas crash ten, Cineform zero. It is difficult to render anything outside the box with this platform without it choking. The platform was more stable when it was Sony Vegas 12 and would go back but alas the veg file will not be backwards compatible.

Last changed by Offworlder on 4/18/2017, 8:51 PM, changed a total of 2 times.

Custom workstation build: ASRock X99 WS LGA-2011, Intel i7-6850K 15M Broadwell-E 6-Core 3.6 GHz , Toshiba OCZ RD400 SSD NVMe M.2 512GB, G.SKILL TridentZ 32GB DDR4, EVGA GeForce GTX 1080 FTW ACX 3.0, 8GB GDDR5X, 8TB Raid 0, 5TB backup/hot swap, NZXT Phantom 630 case. Vegas 14, Resolve 12.5, Affinity Photo - lots of cooling <g>

NickHope wrote on 4/18/2017, 9:50 PM

Vegas crash ten, Cineform zero. It is difficult to render anything outside the box with this platform without it choking.

Would be interested to see what comes after "...Vfx" if you scroll right in that window. It looks to me like a Vegas-native FX is causing the crash. You can troubleshoot render problems with this post and the post it links to in section 1. But basically, look in the preview to see what event is being rendered when the crash occurs then see what FX are in use at that point.

The platform was more stable when it was Sony Vegas 12 and would go back but alas the veg file will not be backwards compatible.

You can use this to go back: http://www.focusonvegas.com/movie-studio-vegas-pro-version-faker/

Offworlder wrote on 4/20/2017, 4:40 PM

Will certainly copy and paste, if possible within application to notepad

While I have a lot of layers, about 24, it is mostly just segmented audio and video for finer control. I do have some fx however, nothing outside what came bundled with Vegas, titler pro and various filters. Motion graphics were done in AE and brought into Vegas and no issues with ProRes export crashing at that point.

I can render out for web, just not yet been able to render to anything Resolve requires, will check you link

Thanks

Custom workstation build: ASRock X99 WS LGA-2011, Intel i7-6850K 15M Broadwell-E 6-Core 3.6 GHz , Toshiba OCZ RD400 SSD NVMe M.2 512GB, G.SKILL TridentZ 32GB DDR4, EVGA GeForce GTX 1080 FTW ACX 3.0, 8GB GDDR5X, 8TB Raid 0, 5TB backup/hot swap, NZXT Phantom 630 case. Vegas 14, Resolve 12.5, Affinity Photo - lots of cooling <g>

Kinvermark wrote on 4/20/2017, 9:49 PM

Are you able to render any part  (even a very short test) to cineform?    If you can isolate the problem, it may be something you can leave out for now and replace in Resolve (e.g. a title). 

NickHope wrote on 4/20/2017, 11:40 PM
..I do have some fx however, nothing outside what came bundled with Vegas, titler pro and various filters...

Yes, the "fault module" path in your screenshot points to (I think) Veags' own native FX (C:\Program Files\VEGAS\VEGAS Pro 14.0\OFX Video Plug-Ins\Vfx1.ofx.bundle). That then throws the suspicion onto GPU acceleration of video processing. If you have that switched on in your video preferences, try turning it off.

Offworlder wrote on 4/22/2017, 10:10 AM

Are you able to render any part  (even a very short test) to cineform?    If you can isolate the problem, it may be something you can leave out for now and replace in Resolve (e.g. a title). 

 

I did two tests, at target size and smaller with short segment. Both Cineform outputs with video banding as shown below

Last changed by Offworlder on 4/22/2017, 10:21 AM, changed a total of 1 times.

Custom workstation build: ASRock X99 WS LGA-2011, Intel i7-6850K 15M Broadwell-E 6-Core 3.6 GHz , Toshiba OCZ RD400 SSD NVMe M.2 512GB, G.SKILL TridentZ 32GB DDR4, EVGA GeForce GTX 1080 FTW ACX 3.0, 8GB GDDR5X, 8TB Raid 0, 5TB backup/hot swap, NZXT Phantom 630 case. Vegas 14, Resolve 12.5, Affinity Photo - lots of cooling <g>

Offworlder wrote on 4/22/2017, 10:30 AM

Yes, the "fault module" path in your screenshot points to (I think) Veags' own native FX (C:\Program Files\VEGAS\VEGAS Pro 14.0\OFX Video Plug-Ins\Vfx1.ofx.bundle). That then throws the suspicion onto GPU acceleration of video processing. If you have that switched on in your video preferences, try turning it off.

 

Actually had not had GPU (EVGA 1080) on at any point during the edit - it just crashed the application.

 

Magix did have me run a system check and there were numerous instances of app errors like the one below. I also had an older version of Sound forge installed which I later removed however, that was prior to attempting to render out to ProRess

4/9/2017 5:24 PM    Application Error    Faulting application name: vegas140.exe, version: 14.0.0.244, time stamp: 0x58c1d206&#x000d;&#x000a;Faulting module name: vegas140.exe, version: 14.0.0.244, time stamp: 0x58c1d206&#x000d;&#x000a;Exception code: 0xc0000005&#x000d;&#x000a;Fault offset: 0x00000000005a39be&#x000d;&#x000a;Faulting process id: 0x2168&#x000d;&#x000a;Faulting application start time: 0x01d2b1546d166376&#x000d;&#x000a;Faulting application path: C:\Program Files\VEGAS\VEGAS Pro 14.0\vegas140.exe&#x000d;&#x000a;Faulting module path: C:\Program Files\VEGAS\VEGAS Pro 14.0\vegas140.exe&#x000d;&#x000a;Report Id: aa4ea9db-a0e2-4eef-90ad-ad1c394afd48&#x000d;&#x000a;Faulting package full name: &#x000d;&#x000a;Faulting package-relative application ID:    

-----

4/9/2017 4:45 PM    Application Hang    The program vegas140.exe version 14.0.0.244 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Security and Maintenance control panel.&#x000d;&#x000a; Process ID: 3adc&#x000d;&#x000a; Start Time: 01d2b14ee5b898f2&#x000d;&#x000a; Termination Time: 11&#x000d;&#x000a; Application Path: C:\Program Files\VEGAS\VEGAS Pro 14.0\vegas140.exe&#x000d;&#x000a; Report Id: eac97e30-1d43-11e7-bdf4-7085c2071ec7&#x000d;&#x000a; Faulting package full name: &#x000d;&#x000a; Faulting package-relative application ID: &#x000d;&#x000a;    

Custom workstation build: ASRock X99 WS LGA-2011, Intel i7-6850K 15M Broadwell-E 6-Core 3.6 GHz , Toshiba OCZ RD400 SSD NVMe M.2 512GB, G.SKILL TridentZ 32GB DDR4, EVGA GeForce GTX 1080 FTW ACX 3.0, 8GB GDDR5X, 8TB Raid 0, 5TB backup/hot swap, NZXT Phantom 630 case. Vegas 14, Resolve 12.5, Affinity Photo - lots of cooling <g>

Offworlder wrote on 4/22/2017, 10:42 AM

You can use this to go back: http://www.focusonvegas.com/movie-studio-vegas-pro-version-faker/

But does 12, I don't recall render ProRes or anything else which Resolve can read - otherwise at this point not going to allow for Grading as I can render a working MP4 for playback

Custom workstation build: ASRock X99 WS LGA-2011, Intel i7-6850K 15M Broadwell-E 6-Core 3.6 GHz , Toshiba OCZ RD400 SSD NVMe M.2 512GB, G.SKILL TridentZ 32GB DDR4, EVGA GeForce GTX 1080 FTW ACX 3.0, 8GB GDDR5X, 8TB Raid 0, 5TB backup/hot swap, NZXT Phantom 630 case. Vegas 14, Resolve 12.5, Affinity Photo - lots of cooling <g>

Offworlder wrote on 4/22/2017, 11:28 AM

Attempted another ProRes render of the entire segment and system crashed - copied information listed below.

 

-Disabled virus/disconnected from Internet
- No other third-party applications running in background

Extra Information
   File:                C:\Users\Edit One\AppData\Local\VEGAS Pro\14.0\dx_video_grovel_x64.log
   File:                C:\Users\Edit One\AppData\Local\VEGAS Pro\14.0\svfx_video_grovel_x64.log
   File:                C:\Users\Edit One\AppData\Local\VEGAS Pro\14.0\ocio_x64.log
   File:                C:\Users\Edit One\AppData\Local\VEGAS Pro\14.0\dx_grovel_x64.log
   File:                C:\Users\Edit One\AppData\Local\VEGAS Pro\14.0\gpu_video_x64.log
   File:                D:\ACTIVE PROJECTS\CENTENNIAL\VEGAS PROJECT FILES\CENTENNIAL MASTER PROJECT FILES\VEGAS 14 - CURRENT\CMasterEdit-04_16Final_AudioAdjusted2017.veg

Problem Description
   Application Name:    VEGAS Pro
   Application Version: Version 14.0 (Build 252) 64-bit
   Problem:             Unmanaged Exception (0xc0000005)
   Fault Module:        C:\Program Files\VEGAS\VEGAS Pro 14.0\OFX Video Plug-Ins\Vfx1.ofx.bundle\Contents\Win64\Vfx1.ofx
   Fault Address:       0x00007FF8677CF0B4
   Fault Offset:        0x000000000003F0B4

Fault Process Details
   Process Path:        C:\Program Files\VEGAS\VEGAS Pro 14.0\vegas140.exe
   Process Version:     Version 14.0 (Build 252) 64-bit
   Process Description: VEGAS Pro
 

Custom workstation build: ASRock X99 WS LGA-2011, Intel i7-6850K 15M Broadwell-E 6-Core 3.6 GHz , Toshiba OCZ RD400 SSD NVMe M.2 512GB, G.SKILL TridentZ 32GB DDR4, EVGA GeForce GTX 1080 FTW ACX 3.0, 8GB GDDR5X, 8TB Raid 0, 5TB backup/hot swap, NZXT Phantom 630 case. Vegas 14, Resolve 12.5, Affinity Photo - lots of cooling <g>

john_dennis wrote on 4/22/2017, 12:20 PM

In view of all the issues you have with Prores, have you considered using  Sony XAVC Intra?

Resolve 12.5 opens it easily. 

It is a high quality format that smart renders.

I know, it's not Prores.

NickHope wrote on 4/22/2017, 12:29 PM
But does 12, I don't recall render ProRes or anything else which Resolve can read - otherwise at this point not going to allow for Grading as I can render a working MP4 for playback

No ProRes rendering in 12 but the 3rd party codecs like Cineform all show up as they do in VP14.

Just been taking another look at that list. There are plenty of other near-lossless options. XAVC-Intra and DNxHD/DNxHR for example. I'd give XAVC-Intra a shot before installing those BlackMagic codecs. You can do all of those in VP12.

Sounds like something's not quite right with your VP14 installation. Perhaps a thorough work through this might be in order.

Edit: Ha! JD got there first :)

john_dennis wrote on 4/22/2017, 12:54 PM

"JD got there first"

Even a blind pig gets an acorn once in a while.

Offworlder wrote on 4/22/2017, 12:59 PM

In view of all the issues you have with Prores, have you considered using  Sony XAVC Intra?

 

 

No ProRes rendering in 12 but the 3rd party codecs like Cineform all show up as they do in VP14.

Just been taking another look at that list. There are plenty of other near-lossless options. XAVC-Intra and DNxHD/DNxHR for example. I'd give XAVC-Intra a shot before installing those BlackMagic codecs. You can do all of those in VP12.

Sounds like something's not quite right with your VP14 installation. Perhaps a thorough work through this might be in order.

Thanks to you both for your continued input. As you see below XAVC-Intra crashes about 15 seconds in, just during still image transitions and without any fx at that point.

Will look through the list specific to vp14 (lol, owned vp3 domain and sold to On2 corp. in 2000) which is now up to VP14, so perhaps revenge <g>

 

Extra Information
   File:                C:\Users\Edit One\AppData\Local\VEGAS Pro\14.0\dx_video_grovel_x64.log
   File:                C:\Users\Edit One\AppData\Local\VEGAS Pro\14.0\svfx_video_grovel_x64.log
   File:                C:\Users\Edit One\AppData\Local\VEGAS Pro\14.0\ocio_x64.log
   File:                C:\Users\Edit One\AppData\Local\VEGAS Pro\14.0\dx_grovel_x64.log
   File:                C:\Users\Edit One\AppData\Local\VEGAS Pro\14.0\gpu_video_x64.log
   File:                D:\ACTIVE PROJECTS\CENTENNIAL\VEGAS PROJECT FILES\CENTENNIAL MASTER PROJECT FILES\VEGAS 14 - CURRENT\CMasterEdit-04_16Final_AudioAdjusted2017.veg

Problem Description
   Application Name:    VEGAS Pro
   Application Version: Version 14.0 (Build 252) 64-bit
   Problem:             Unmanaged Exception (0xc0000005)
   Fault Module:        C:\Program Files\VEGAS\VEGAS Pro 14.0\OFX Video Plug-Ins\Vfx1.ofx.bundle\Contents\Win64\Vfx1.ofx
   Fault Address:       0x00007FFC7C0BF0B4
   Fault Offset:        0x000000000003F0B4

Fault Process Details
   Process Path:        C:\Program Files\VEGAS\VEGAS Pro 14.0\vegas140.exe
   Process Version:     Version 14.0 (Build 252) 64-bit
   Process Description: VEGAS Pro
 

Last changed by Offworlder on 4/22/2017, 1:00 PM, changed a total of 1 times.

Custom workstation build: ASRock X99 WS LGA-2011, Intel i7-6850K 15M Broadwell-E 6-Core 3.6 GHz , Toshiba OCZ RD400 SSD NVMe M.2 512GB, G.SKILL TridentZ 32GB DDR4, EVGA GeForce GTX 1080 FTW ACX 3.0, 8GB GDDR5X, 8TB Raid 0, 5TB backup/hot swap, NZXT Phantom 630 case. Vegas 14, Resolve 12.5, Affinity Photo - lots of cooling <g>

john_dennis wrote on 4/22/2017, 1:25 PM

Boot from a Windows 7 Professional Installation Disk.

Before installing anything:

Open a CMD window

Type diskpart

Type list disk

Note your current boot disk number n

Type select disk n

Type clean

You need to start over.

Offworlder wrote on 4/22/2017, 1:42 PM

Thanks but at the point I am not going to do a clean install, there is not a lot on this new box.

I just ran a short test render Sony YUV and 10-bit YUV @ 1080 and was able to open in Resolve, but is it lossy or lossless?

Rant - Perhaps Magix should have spent more time before rolling out ProRes as it is in beta from my perspective. I've been using Vegas since V4 however, given the new owners lack of commitment to technical support, for me it may be time to move to a different NLE such as Resolve, then it is all in one package.

 

 

Last changed by Offworlder on 4/22/2017, 2:21 PM, changed a total of 2 times.

Custom workstation build: ASRock X99 WS LGA-2011, Intel i7-6850K 15M Broadwell-E 6-Core 3.6 GHz , Toshiba OCZ RD400 SSD NVMe M.2 512GB, G.SKILL TridentZ 32GB DDR4, EVGA GeForce GTX 1080 FTW ACX 3.0, 8GB GDDR5X, 8TB Raid 0, 5TB backup/hot swap, NZXT Phantom 630 case. Vegas 14, Resolve 12.5, Affinity Photo - lots of cooling <g>

NickHope wrote on 4/22/2017, 10:37 PM
I just ran a short test render Sony YUV and 10-bit YUV @ 1080 and was able to open in Resolve, but is it lossy or lossless?

8-bit lossless. 10-bit slightly lossy. Big files. See here: https://www.vegascreativesoftware.info/us/forum/di-comparison--105912/