| UI | WARN | 00:36:54,798 | Unable to submit frame to GPU scopes, legacy OpenGL uploads not supported (Color Page). | GPUManager | ERROR | 00:36:54,775 | Exception caught while running GPU algorithms. | GPUManager | INFO | 00:36:54,364 | Flushing GPU memory. | GPUManager | ERROR | 00:36:54,364 | Exception caught while running GPU algorithms. | UI | WARN | 00:36:53,956 | Unable to submit frame to GPU scopes, legacy OpenGL uploads not supported (Color Page). | GPUManager | INFO | 00:36:53,921 | Flushing GPU memory. | GPUManager | ERROR | 00:36:53,918 | Exception caught while running GPU algorithms. | GPUManager | INFO | 00:36:53,537 | Flushing GPU memory. | GPUManager | ERROR | 00:36:53,537 | Exception caught while running GPU algorithms. | UI | WARN | 00:36:53,018 | Unable to submit frame to GPU scopes, legacy OpenGL uploads not supported (Color Page). | GPUManager | INFO | 00:36:52,968 | Flushing GPU memory. | GPUManager | ERROR | 00:36:52,965 | Exception caught while running GPU algorithms. | GPUManager | INFO | 00:36:52,629 | Flushing GPU memory. | GPUManager | ERROR | 00:36:52,629 | Exception caught while running GPU algorithms. I didn't help me, because it's a very generic error, but it might give your developers an indication as to where the problem is located.Ĭode: Select all | SyManager | ERROR | 00:36:51,450 | There is no current clip, SetCurrentFrame failed. These all seem to be from the time I started rendering. To finish off, I've included some logging I found while debugging the issue. However, Fusion seems to be lacking in performance and stability compared to After Affects, which was a real bummer. I recently switched from Premiere to Resolve and I've been loving the performance and interface. But there's a reason renderers don't use cached images by default.Īlso, BlackMagic, this no reason for you not fix the issue.
I've looked at the result and it looks fine by me, and because I'm working on a small client, it wouldn't be that big of a deal. However, I don't know what this does to image quality. Now, if you render, the renderer should use the cached images and therefore skip the Fusion compositing part, resulting in a finished render. What your timeline should look like Annotation 010521.png (86 KiB) Viewed 73018 times This means that the bar on top of the timeline turned from red to blue for all frames of the clips that cause problems. Next make sure all frames are cached in your timeline.
That's where you can use one of resolve's features to finish you render.
I noticed that the Fusion frames were rendering in the timeline correctly, however upon final export it fails.
So I've stumbled upon this issue as well, and I might have a temporary solution for some. I determined it was seven frames from the end of the clip, trimmed them off, and the entire piece rendered with no problems.Īny clues as to why this might be happening are appreciated. I could render part of the Fusion clip with no problem, but trying to render the entire clip resulted in failure at the same point every time. I tried Jake Earp's solution, it didn't work. The render failed every time at the exact same point, just before the end of the Fusion clip. Yesterday, I added some titles to a project containing a Fusion clip I had successfully rendered previously. Trying the render again would usually work. The error message would always say that DR didn't have permission to write to the drive and to go to preferences to designate the drive. This was on BRAW material containing no Fusion clips. Typically the failure would occur within the first 15 to 20 seconds of the render and at a different point every time. I have been having intermittent issues with render fails for the last few days, since updating to 16.1.
0 kommentar(er)
