Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums DaVinci Resolve Resolve 14.1 doesnt open 14.0.1 projects – CRASH

  • Duke Sweden

    November 22, 2017 at 1:27 pm

    Not yet, but I’ve only opened 2 previous projects so far.

    Dell XPS 8920
    Intel i7 core 7700 build
    GeForce GTX 1050ti
    32 Gigs of RAM
    3 7200 RPM SATA Drives
    Windows 10 64-bit
    DaVinci Resolve 14.0.1

  • Marc Wielage

    November 24, 2017 at 4:07 am

    Same here. I’ve opened a few 14 and 12.5 projects and no crashes there. I’ve had other crashes for other reasons, but not that.

  • Mauro Moreira

    January 17, 2018 at 10:43 pm

    I seems that 14.2 solved some of my problems.
    The only thing that remains is that sometimes when I export Mov or MXF from a h264 source, the render comes out with a lot of Media Offline. Nothing that i tried solved this (slowing down render, etc).

  • Marc Wielage

    January 18, 2018 at 5:19 am

    [Mauro Moreira] “The only thing that remains is that sometimes when I export Mov or MXF from a h264 source, the render comes out with a lot of Media Offline. Nothing that i tried solved this (slowing down render, etc).”
    Is this on Resolve Studio?

    What OS are you using? What hardware (CPU, GPU, RAM, I/O)? What type of camera source files?

    Make sure you check Prefs -> User -> Media Storage to see that all of the source drives are shown in the display. The top-most drive is the location used for Gallery Stills and Cache Files, and the other drives are for source files. As a safety, you could check the Media Page and make sure all the files have valid source directory paths. Relink them if necessary. Also in Project Settings -> Master Settings -> Working Folders, make sure those drive paths are valid as well. As a final step, you might try deleting your current Optimized Media and Render Cache and regenerate them as needed. I have seen Resolve appear to choke when what was actually happening was that some of the Cache files were bad.

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