Justine Robilliard wrote:On the other hand, you could for example have the UX set to say basic, intermediate, advanced, developer, so that with each stage, more "features" are unlocked, or more settings become visible.. The problem is how to keep the coding within acceptable standards..I am sure Blackmagic have a solution...I agree it could get messy, something I did not think about...
I've worked on legacy systems that use a setup like that, and it doesn't work well in practice. What ends up happening is you get a lot of users who are 99% happy with one level but they have to enable the next highest level to change that one thing they really want. So you end up with a lot of users in the highest configuration levels, who get overwhelmed.
The Underlying issue is that configurability and usability are at opposite ends of the spectrum. The consumer facing menu and settings windows most people are familiar with break down from a UX perspective when you get into the ream of hundreds or thousands of settings. I'm not sure how many resolve has exactly, but its definitely well into the several hundreds range. You can see how that has already lead to problems for users by browsing various threads on the forum.
At the enterprise level where you regularly have hundreds or thousands of configuration settings, the methodology switches to various forms of configuration files. I deal with stuff like this daily, but it's not the type of thing you want to expose most people to.
I'm not sure what web browser you use, but if you use Firefox and want to see a glimpse of what I mean, type 'about:config' in the address bar and Firefox will display it's underlying settings interface. It's a simple and very powerful GUI based settings manager, but still completely overwhelming to most people.
AMD 7950X | AMD 7900XTX (23.20.24) | DDR5-6000 CL30-40-40-96 2x32 GB | Multiple PCIe 4.0 X4 NVME | ASUS x670e HERO | Win 11 Pro 23H2 | Resolve Studio 18.6.5 B7