Bug: Unique timeline names are enforced, but not always

A big issue with the current Resolve scripting API is that there's no way to find the Media Pool Item that represents a Timeline.

The only way is to search through all the bins for a clip that matches the name of the timeline. However, while Resolve enforces unique timeline names when you create or rename a timeline regardless of which bin it's in, it doesn't enforce unique timeline names when you paste a timeline to another bin.

I feel that being able to paste a timeline into another bin while keeping the timeline name is a bug. Seeing as we're not allowed to rename a timeline to be the same name as another timeline in another bin.

Pasting a timeline to the same bin shows the expected behavior of appending "copy" to the timeline name.

I just found that pasting a timeline into a parent bin adds the "copy" suffix. Pasting into a sub bin retains the original timeline name.

Maybe I misunderstand, you're trying to identify which mediapool items are timelines? This would do it:

Code: Select all

#!/usr/bin/env python

# Get a list of timelines in the current Resolve bin.
# Igor Ridanovic, metafide.com

def get_timelines_list(bin):

    binItems = bin.GetClipList()
    timelinesInThisBin = []

    for i in binItems:
        itemProperties = i.GetClipProperty()
        if itemProperties['Type'] == 'Timeline':
            timelinesInThisBin.append(i)

    return timelinesInThisBin



if __name__ == '__main__':
    projectManager = resolve.GetProjectManager()
    currentProject = projectManager.GetCurrentProject()
    mediaPool = currentProject.GetMediaPool()
    currentBin = mediaPool.GetCurrentFolder()

    timelines = get_timelines_list(currentBin)


That's the approach I guess most people are using, but there are two issues with it:

1. Timelines can have duplicate names if they're copied to a subfolder, so you can't be sure which Media Pool Item is the right one if you're matching it with a Timeline object.
2. The "Type" property is a translated property and basing code logic on it will fail if the Resolve GUI is set to another language.

The way I approach these issues now is that I offer the user the opportunity to automatically rename duplicate timelines first, to make them unique. And for the "Type" property I translate from whichever language Resolve is set to, but it will of course break if there are more or updated translations.

Both are bad workarounds.