iddos-l wrote:Every user on this forum has the right to be heard and cast their vote.
I personally don’t want this feature because I feel it will make a lot of mistakes along the way.
-1 from me.
That's the problem, feelings shouldn't be involved in the development of software.
Hard facts (but mostly logic) is what matter. I didn't see any logical explanation, or examples on how this change would impact the majority of the users in a negative way.
This feature request is extremely logical and simple. And it doesn't remove anything too. It adds something.
And what mistakes? You can create any timeline and drag any video not matching its settings on it. Anyone can make "mistakes" TODAY with Resolve at every step. With this way of thinking, you can literally shutdown every single new feature request.
You realize that at some point, it was not possible to change the settings of a timeline after its creation?
These limitations are a pain. But it changed over time.
Like many other changes that gave us more flexibility. It enhanced the experience of the users, removed friction points, etc.
There are tons of archaic stuff in Resolve. It's an old software that didn't really evolve for a long time
because it was centered around color grading.
Everything else, especially the Edit page, is been remodeled as we speak.
Even Jim (the guy who wrote this feature request) was/is against logical changes, uses "feelings" without giving any examples why a feature request could be a problem. Many of the ideas he was against... were implemented anyway.
But here, he makes total sense.
1) We can create a new timeline that inherits from the project's settings
2) We cannot create a new timeline that inherits from the clips settings (all of the settings)
After the change:
1) We can create a new timeline that inherits from the project's settings
2) We can create a new timeline that inherits from the clips settings (all of the settings)