- Posts: 91
- Joined: Wed Jul 22, 2020 10:47 am
- Real Name: Kay Golze
Shrinivas Ramani wrote:Kay,
For issues with stability, please refer to the FAQs for what information we need to follow up. At the least we need a clear understanding of your issue and workflow, a complete listing of hardware, peripherals, OS and driver setup, and a link to a diagnostic log archive captured after a crash.
Using and exporting projects in 8K will invariably depend on getting multiple workflow factors right - GPU processing power, GPU memory, disk throttling, codecs used etc - as well as an understanding of overheads for each effect applied.
Providing this information in context of a bug will help us determine if there are hardware bottlenecks, OS related changes, driver issues, or limitations in our software.
Regards
Shrinivas
Hello Shrinivas, unfortunately I can't answer sooner. I am very aware of the special requirements for 8k video editing. As I work at the limit of the program's performance, the bugs only come to light faster.
However, Davinci Resolve has many errors in very simple functions, like cutting! I want to help you to eliminate these errors. That's why I opened up a new topic for "error reports". The topic is aimed at you, the developers. Here you can see comprehensible errors and if you want to eliminate them. The numerous trivial errors in Davinci Resolve severely restrict the program for a real professional use. I have already lost weeks and months with the program and have not been able to meet deadlines. In principle, I find the idea of the program and the interface very good. The quality can still be improved. To achieve this, I am happy to help.
Best
Kay
8-12k VR production.
ASUS Maximus Z690 Formula, I9 12900K, DDR5 64GB/5200,
2xNVIDIA P6000 24GB, 84 TB Workspace
ASUS Maximus Z690 Formula, I9 12900K, DDR5 64GB/5200,
2xNVIDIA P6000 24GB, 84 TB Workspace