- Posts: 802
- Joined: Fri Nov 03, 2017 7:22 am
Jerry Suppan wrote:It's unfortunate a single issue like this (DPdecoder.exe) prevents us DaVinci Resolve from being usable. But if Microsoft says there is no fix at the moment, and BMD will not be fixing or eliminating the problem, there is no choice but to consider alternatives in the meantime for productivity. I will wait for a resolution to the problem, IF, there will even be one.
Cheers,
Or you could just not install the insider builds which are expected to both fix issues and introduce other ones. I'm saying this and I'm part of the insider program. Yea, it's fun to get the newest features first but even I'm aware that there's a risk there when opting into something like that on a work computer.
This problem with Resolve getting stuck at "Loading Fairlight" is long-standing. One of the reasons why so many of my feature requests talk about simplifying things or merging code is so that the code-base is smaller and issues like this are less likely to creep up as Resolve gets more features. They absolutely need to fix this issue.
However we opted into a program that puts us on builds of Windows that a statistically insignificant number of people are using and very few software developers get a chance to test their stuff with before it's release. It's a really entitled attitude to get mad at BMD because a version of Resolve doesn't work on a windows build that was released on the same day that it was or several days afterwards.
Sure, make BMD aware of the issue. That's a smart thing to do but you're already aware that this has to do with a particular build of Resolve not working on a particular build of Windows. One or both can be rolled back, and even though you'll lose the very small incremental changes each brings, it will also get things back to a working state for you. You're not being put in some helpless situation here.