Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums DaVinci Resolve Timeline in smithereens

  • Timeline in smithereens

    Posted by Enginn Heima on April 18, 2025 at 7:13 am

    I’m having a problem with moving an edit between two systems.

    We’re using two MacBooks and our Resolve is up to date on both systems. We need to be able to export a timeline on one system and open it on the other. Both systems are using the exact same project settings and they’re using the same media files that are not on the same hard drives but they are named the same and they are identical except for not being on the same physical hard drives.

    Now, from computer A to computer B, this works flawlessly, but the other way around it’s all blown to smithereens. Meaning that Resolve interprets all the footage totally wrong. Computer A sees a clip named clip005 on the timeline (as in the original media file names on the hard drives) as clip001. It uses clip001 instead of clip005 to assemble the edit on the timeline. All the rushes are wrongly interpreted this way.

    Does any one have a clue?

    Best regards

    Chuck Savadelis replied 1 week, 1 day ago 4 Members · 7 Replies
  • 7 Replies
  • Enginn Heima

    April 22, 2025 at 12:20 am

    No ideas?

  • Van Lutz

    April 22, 2025 at 4:07 am

    I am only guessing. I’m fairly new to DaVinci. But, if it works in one direction and not the other, something is happening to the clips on the other computer. Somehow the names might be getting changed. You need to really look into how it’s built on the timeline.

    I’m just going by an example I came across on my short. I synced video and sound automatically. By doing that, the sound names were erased from the timeline, and they were named after the video clip. For a scene I only used sound from an unused video clip. When I finished the edit, and cleaned up my timeline, and computer files, the sound was missing. Even though the sound file was still in my project and in the computer file, since it was nolonger named after the sound file, davinci didn’t recognize it. Something like that is probably what’s happening.

    DaVinci is great. But, it’s not user friendly.

  • Enginn Heima

    April 22, 2025 at 8:31 am

    Thanks for your reply.

    Unfortunately the names haven´t been changed and are the same on both computers. But they are not on the same physical hard drives, I´m thinking that this could somehow be making the mess.

  • Van Lutz

    April 22, 2025 at 11:56 pm

    That probably is the problem. Because they’re no longer the same clips. That does in a way come down to the name, which is where are they? On your computer, they’re on your HD with your folder and your names. While the names of the files are the same, the location of the folders are different (different computers).

    It’s all a learning curve.

  • Enginn Heima

    April 23, 2025 at 9:20 pm

    I was working on Adobe Premiere for years, before I switched to Resolve, and this was never a problem on Premiere. That being said, Premiere had it’s own problems, and plenty of them 😉

    In any case, if anyone has a workaround for my problems of timeline moves from one computer to another, I’m all ears!

    Cheers!

  • Michael Gissing

    April 25, 2025 at 12:54 am

    My guess is you have clips with the same file name. This is unfortunately a problem with some cameras that reset their file names each time a card if formatted and start their timecode at zero for each clip. Drones are notorious for this as are some Sony & Canon cameras.

    Before editing it is vital that file names are all unique and that duplication is avoided by renaming files to add something to the name to make them unique. Then when you go between systems it won’t accidentally relink the wrong files because the names and timecode are the same.

  • Chuck Savadelis

    May 5, 2025 at 4:04 pm

    Have you tried manually relinking the individual clips?

We use anonymous cookies to give you the best experience we can.
Our Privacy policy | GDPR Policy