Mon May 27, 2024 8:24 pm
They certainly do.
However, I think the way they handle betas is not great.
They often break things that worked before, regular tools/nodes/etc., and instead of fixing them until they're usable (even with some minor bugs), they release a new beta on a fixed schedule.
I understand that developing software like DaVinci Resolve is challenging, but this is one area where is not good at, imo. Their approach to betas and updates, in general, is lacking compared to other software companies.
When betas are public, the goal is to have as many different people with different workflows test the software to get a ton of feedback, bug reports.
I've never had this level of frustration with betas and updates with other software (except Topaz Labs, but at least they quickly roll out x.x.X updates to fix issues).
If a tool or feature is completely unusable, it should be fixed immediately, not three weeks later. Or in this case, nine weeks later (if it's fixed in the beta 4, if there is a beta for and not a "final" v19).
When something can't be used, people won't install it, and you'll get fewer useful bug reports.
x.x.X versions should be released every 1-2 weeks, especially once the software is already out, to fix issues. Same thing with betas.
Sometimes, things are implemented without proper testing. Or they are tested, but then they decide to leave it as it is, even if it can't be used or tested properly, with the idea that the next version will be out on a set date.
In the last update, they added support for HDR viewers on Windows. I'm sure this was in the works for longer than the past three weeks, but it highlights the issue. People could wait a few more weeks for HDR Viewers on Windows. It wasn’t there for years, so it shouldn't be a priority for a beta. Bugs should be fixed first.
Windows 10
v20b4
nVidia 3090 - Studio 576.52