17.3 Render Crashes Still A Problem

I have been saying since June 12 that starting with version 17.1 there was a change in the batch render of Davinci Resolve.
viewtopic.php?f=21&t=141341

Every single time when I setup multiple timeline renders, Resolve when it gets to the end of the first timeline render will crash.

It should be noted that the first timeline render does successfully complete. It should also be noted that if I render each timeline individually without using batch render, there are no problems with the final renders.

I really need batch render in Resolve as I often have to render multiple timelines. It was a great feature but every since 17.1, it has not worked properly.

I had hoped that this issued would be noticed/fixed by others but nothing, so I am starting this thread to see if I can find a resolution to the problem.

I even include a short video clip that shows the 4 timelines that are queed for batch rendering. You can see that Resolve stops working and crashes at the conclusion of the first timeline.
Here is the video clip:
https://drive.google.com/file/d/1zZ_o7u ... sp=sharing

Please bring back the batch render in Davinci!

Thanks!

Erik

I've not had this issue myself. I'm not seeing it commonly reported.

You might have to do the Logs thing from the FAQ, so the devs can take a look.

viewtopic.php?f=21&t=90190

I agree Jim that it isn't being reported but I am having no other issues on my system.

BTW, I loaded multiple crash reports and even DRP files on the first thread from June 12th but never got a response or feedback from those reports.

Erik

Maybe post again here so it's fresh.

I agree Jim that it isn't being reported but I am having no other issues on my system.

BTW, I loaded multiple crash reports and even DRP files on the first thread from June 12th but never got a response or feedback from those reports.

Erik

So I have actually had this happen a few times since v17 came out, for some reason it seems to be if I export certain things and decide to use the computer in other intensive programmes, like Chrome (god knows why it's so intensive)

Are you using anything else or just leaivng Resolve on it's own to export?

Hey Dave,

At least I don't feel all alone anymore. So, for me, the crash with multiple timelines happens every time. That said, every time, I most likely have other apps, possibly Chrome open as well. This is how I have worked my entire career to date.

It would be a simple test to try a render that fails every time with nothing else open on the computer but I am not optimistic it will help.

Appreciate the tip though.

Erik

So I have a bit of an update on this problem and I think I have found what the main problem is.

The batch render fails when it is overwriting a previous clip. I often have to do a large number of renders at one time. Likewise, I often have to redo the entire render sequence because of a small client change request, etc.

I instruct DR to overwrite the files when the prompt comes up asking if I want to overwrite. However, this seems to be what is causing the crash. The same renders work IF I delete all of the previous rendered files first.

It is helpful often to not delete these files first for several reasons and I prefer the 17.0 workflow where I didn't have to worry about this problem.

FWIW, I am rendering to 422 XDCAM 10 bit mxf files mostly.

Finally, one question was whether I had too many resources open on my computer while rendering and I have since confirmed this is not related to the problem. I close down everything on the computer and the crash results are the same.

BTW, I have included a couple of new crash reports/drp at this link if anyone at BM is interested in taking a look.

https://drive.google.com/drive/folders/ ... sp=sharing

Thanks, Erik

The batch render fails when it is overwriting a previous clip.

I do this all the time. That's definitely not normal.

Hopefully staff can find something in the logs.

[Dwaine Maggart]

The only log using the 2021 Food BoxP project (also the newest log) doesn't seem to show any attempt to render anything.

But it does have several FrameIO related errors that you don't have permission to access clips. If you were trying to render and got those errors, that could affect the render.

Thanks Dwaine. So if the log doesn't show any attempts to render then the crash must be even defeating the log recording. For sure the log file you have was created immediately upon reopening Davinci Resolve after the crash.

I am not attempting to render to FrameIO as that is another layer of complexity that I won't attempt to use until I get the render situation back under control in DR.

It has gotten so bad that I am seriously considering rolling back to 17.0 or 17.1 even though I lose some of the features with Magic Mask I am currently using.

Erik

[Dwaine Maggart]

It's not rendering to FrameIO, it's trying to read files from FrameIO.

Can you describe "files from FrameIO" in a bit more detail. For example, what steps would need to be taken to check and/or correct this problem?

Turning off FrameIO in the internet account section?

Thank you,

Erik

Can you describe "files from FrameIO" in a bit more detail. For example, what steps would need to be taken to check and/or correct this problem?

Turning off FrameIO in the internet account section?

Thank you,

Erik

Are you connected to frMe.io? If so, can you refresh the login credentials?

[Dwaine Maggart]

I may have incorrectly assumed it was trying to read files, but a closer look at the error does not necessarily support that. It's having an issue doing "something" with FrameIO:

SyManager | ERROR | 2021-08-07 12:53:03,662 | FrameIOHelper: FrameIOHelper::GetComments() request failed, responseCode:3, httpStatus:403, response:{"code":403,"errors":[{"code":403,"detail":"You do not have permission to access that resource","status":403,"title":"Forbidden"}],"message":"Forbidden"}

It could be something as simple as an incorrect login credential.

But I wouldn't expect to see such an error unless the project itself was trying to use FrameIO assets.

I signed out of the FrameIO internet account and did notice an improvement. I only had one crash as opposed to every render crashing. However, I only rendered 4 timelines total so I need to do more testing with FrameIO account deactivated to see if it is a big part of the issue.

BTW, FrameIO integration with Davinci Resolve is falling behind integration with Premier Pro and Final Cut.

FrameIO just announced new version/upgrades for both of those softwares but not DR.

I asked them why nothing for DR and they said that BlackMagic is "controlling all of the integration" separately from FrameIO. So they really can't provide tech support or assistance for problems with FrameIO and Davinci Resolve.

My own experience with FrameIO in DR is dicey. Works sometimes, sometimes the render works but the upload fails, sometimes the render works, the upload says it worked but it didn't. Etc

Erik

For others with similar problems, it seems that FrameIO integration was the real culprit for the render errors. After signing out and no longer using FrameIO in Davinci Resolve, my renders are no longer crashing.

Unfortunately, this issue isn't dead yet. I did notice an improvement after removing my login to FrameIO .(a shame because I would like to use that service!)

However, in two different projects, I experienced more crashing on render.

Some crashes are the entire program disappearing immediately upon completion of the render.

Some crashes are the program "hanging" and having to end task upon completion of the render.

It should be noted that DR pretty much always completes the full render but the crash was almost 100% on the two days I was most recently working.

I have added the latest LOG files for the crashes at this link. I'm hopeful that someone at DR can take a look at the LOG files and maybe point me in a direction to solving the problem.

I have attached a screenshot of the latest LOG files.

Thank you!

Erik

https://drive.google.com/drive/folders/ ... sp=sharing

BTW, FrameIO integration with Davinci Resolve is falling behind integration with Premier Pro and Final Cut.

Erik

The integration with Premier makes sense as Adobe is buying it.