Dan Sherman wrote:If you ripple delete something by accident or not, it's a direct consequence of a direct action taken by you the user. Not to mention the user could see the conflict, and what was going to happen before they did it.
And how is that not the case with syncing? Let's go to the simplest task - user adds new clip into timeline, selects both main audio clip that wants new clip to be synced to, and new clip, executes syncing, and new clip is moved to the proper location in timeline.
If user is thinking ahead, and is afraid of overwriting existing clips, he would put new clip into empty video and audio track. So, there would be no conflict!
If he doesn't want to lose time on that or he is pretty confident that there would be no conflicts, he would just sync and see where new clip lands. If it overwrites part of another clip, that can be easily solved in several ways.
To me that is in essence no different than ripple deleting - I'm not editing every day, and sometimes I cannot predict which clips will be moved/overwritten, so I have to undo ripple deleting, and do what I want another way.
What is the big deal?
Dan Sherman wrote:Clips getting screwed up by a sync is not a direct consequence. The user has no quick way of knowing ahead of time what might happen.
Where is the problem? The whole point of syncing is that the user does not necessarily know exactly where certain clip should end up. If the user would know exactly where the clip should go, then the user would move it there, right? It is the purpose of syncing to move clips where they need to go when user does not know where exactly they need to go.
And after syncing user sees where clips ended up, and can make corrections if necessary.
Haven't you ever used syncing in Premiere or seen somebody use it? It is far from perfects, but it is a great time saver! The issues you are trying to impose are non-issues - the benefits far outweighs potential "conflicts" (which can be avoided with certain workflow).
And software like PluralEyes showed us how syncing can work on unedited timeline. It works great.
What is the issue? You have examples of this function in other software - they are great timesavers, and nobody complains about "potential conflicts".
Dan Sherman wrote:BM only has a few options if they ran into a sync conflict
When clips are put into empty tracks, there will be no conflicts! Even if they are put on non-empty tracks, there might be conflicts, that will be corrected by user.
Dan Sherman wrote:none of them are ideal, and will lead to various levels of frustrated, irritated and irate users.
Wow! BMD better hire some psychologists so that users of their software don't go mad! I wonder how Premiere Pro and PluralEyes users still haven't slit their wrists out of frustration caused by syncing!
Dan Sherman wrote:The manual resolution screens would get expensive to implement because of the many possible conflicts.
If ripple delete can overwrite parts of existing clips, why syncing can't? And if user puts clips that need to be synced into empty tracks, there will basically be no conflicts.
Dan Sherman wrote:As i said, I'm a developer and I gave my opinion about the potential issues with the requested feature, and thus why i think its unlikely to be implemented.
Potential issues you gave are basically non-issues, or at least not serious enough issues so for that functionality not to be implemented. Especially with those two use scenarios that I presented, and most people would probably use syncing in those scenarios (in empty timeline - if PluralEyes and other similar software can do it, why Resolve shouldn't be able to do it?; syncing added clips to main audio in timeline - any conflicts can be avoided by putting new added clips into empty tracks).
If it won't be implemented, it won't be because other reasons, and not because of potential conflict (non-)issues.
Dan Sherman wrote:If the the numbers don't add up to a revenue increase, features don't get implemented
I agree with that. But that has nothing to do with those "conflicts" you mentioned, that are really a non-issue.
And also, "if the numbers don't add up to a revenue increase" does not mean that they don't add up. If I had to guess, I would say they add up - that could win over users of Premiere who don't want to move to Resolve because of syncing, and would also enable faster workflow for Resolve users that need syncing.
I believe it is just a matter of time when they implement it. They will ran out functions to implement that could significantly improve Resolve, so sooner or later they will have to add timeline syncing as a new significant feature. And many people will be very happy with that, even though that functionality could create some "conflicts" in certain situations.