- Posts: 60
- Joined: Thu Jun 02, 2016 12:40 pm
So this message that started bothering everybody since the release of 14.1 unfortunately is still here.
Problem:
- GPU Memory Full error comes up. When going through media, when editing, when rendering. After clicking OK, the video is frozen on all tabs. Sometimes saving doesn't work as well. The program needs a restart.
Here are the conditions:
- Windows 10 PC. Dual XEON, 32GB Ram.
- GTX 1080 8GB
- Simple 1080p Timeline of H.264 content New/Old project it doesn't matter. In fact, the bug can be triggered by simply mouse-hovering through a clip in the Media tab.
- Content with RAW, ProRes or material with other compression don't cause this problem
- I can't be sure (maybe I was lucky) but it seems some limited H.264 material doesn't cause it but most do.
- It could happen the very first second or after 5 minutes of work. At some point it will.
- A similar bug existed in 14.1 when video field processing was enabled. This was fixed in 14.1.1. This is not that bug. Video Field processing is disabled.
I have posted a full log/info dump at this tread before.
The only hack to this is to generate optimised media to another format before start working. Of course this needs some decent praying to work since occasionally it will still drop the message and crash the software during the optimised media generation process. Then, there are things like scene cut detection that there is no way around it. It will crash sooner or later. So I have to, generate optimised media of the original clip, export and scene cut detect the exported clip. Of course, on export, "use optimised media" must be enabled otherwise it will crash.
So, the question is, are other people experiencing this?
And to the Black Magic support people that actually know: could this actually be a codec situation? Does Resolve use external codecs for H.264? I haven't changed a thing codec-wise for ever. This started happening exactly since 14.1 upgrade but maybe there is some incompatibility?
Since the database was upgraded after 14.1 I can't really go back to a prior version.
I would appreciate some help or seeing into this issue. Thank you.
Problem:
- GPU Memory Full error comes up. When going through media, when editing, when rendering. After clicking OK, the video is frozen on all tabs. Sometimes saving doesn't work as well. The program needs a restart.
Here are the conditions:
- Windows 10 PC. Dual XEON, 32GB Ram.
- GTX 1080 8GB
- Simple 1080p Timeline of H.264 content New/Old project it doesn't matter. In fact, the bug can be triggered by simply mouse-hovering through a clip in the Media tab.
- Content with RAW, ProRes or material with other compression don't cause this problem
- I can't be sure (maybe I was lucky) but it seems some limited H.264 material doesn't cause it but most do.
- It could happen the very first second or after 5 minutes of work. At some point it will.
- A similar bug existed in 14.1 when video field processing was enabled. This was fixed in 14.1.1. This is not that bug. Video Field processing is disabled.
I have posted a full log/info dump at this tread before.
The only hack to this is to generate optimised media to another format before start working. Of course this needs some decent praying to work since occasionally it will still drop the message and crash the software during the optimised media generation process. Then, there are things like scene cut detection that there is no way around it. It will crash sooner or later. So I have to, generate optimised media of the original clip, export and scene cut detect the exported clip. Of course, on export, "use optimised media" must be enabled otherwise it will crash.
So, the question is, are other people experiencing this?
And to the Black Magic support people that actually know: could this actually be a codec situation? Does Resolve use external codecs for H.264? I haven't changed a thing codec-wise for ever. This started happening exactly since 14.1 upgrade but maybe there is some incompatibility?
Since the database was upgraded after 14.1 I can't really go back to a prior version.
I would appreciate some help or seeing into this issue. Thank you.