Cannot open project after database upgrade

Hi,

I have been working on a project for months in Davinci Resolve 14, but recently, I began getting messages popping up saying "GPU memory is full - reduce the timeline resolution or number of correctors". I did as instructed and reduced the timeline resolution and deleted some old grade versions but the message still kept popping up so I restarted my computer etc and I was still getting the messages.
After reading some forums I thought that if I upgraded the software it might fix the problem. So I installed DaVinci Resolve 15 public beta and "upgraded" my database and stupidly, I didn't backup the database beforehand.
All of the projects are visible in the upgraded database with the correct moving thumbnails and all of the projects open successfully except the one I urgently need... It begins to load and gets to approx. 90% and then Davinci Resolve 15 crashes. As I am on a deadline I went out and purchased a new MacBook Pro with Intel HD Graphics 630 / 1536 MB + Radeon Pro 560 / 4GB .... and downloaded/installed Davinci Resolve 15 and I'm still having the same problem opening the project I need.

- Attached is the crash logs .tgz file
- I tried to upload both computer systems information (new and old) but it said the file/s were too large, so I have uploaded to google drive the system information for the original computer and the brand new computer, and a copy of the .drp project.
- google drive download link: https://drive.google.com/open?id=10Qd6Q ... JB-Tvm3w7U

I really hope you can help me get this working again as I am on a deadline.

Many thanks,
Blake

Hi Blake,

I tried to load it on my MBP(2013) and it crashed my macbook. The logs where not conclusive on te crash nature other then the obviousmessages of missing media and lut etc.
Then i loaded it on my main hackintosh workstation with lots of mem/gpu resources and it actually loaded after some errors like missing LUT and unsupported video mode (?).
This could indicate a resource issue . The project may have become too big (or some part of it) that triggers a crash on a low powered machine.
I have re-exported it , maybe that helps who knows. Try it.
https://cloud.tachyon-consulting.com:55 ... Cbzkx0C7Hh

Some extra things to try. With Resolve sometimes resources issues only get triggered if it hits an error in combination with tight resources. So looking at your crash log i would work my way backwards from the end and fix these missing media issues one by one. Then maybe Resolve does not go into a meltdown.
The last file it seems to seriously complain about is QT_Assembly_101217_version for grade.mov. Secondly a few LUT's

[0x7fff9a13f380] | SyManager.ProjectManager | INFO | 2018-07-13 09:02:55,207 | Loading project (Copy of FINAL GRADE 2) from database (Local Database) took 6576 ms
****************** Flushing GPU Buffers
[0x7fff9a13f380] | SyManager.Signals | INFO | 2018-07-13 09:02:55,319 | Current project pointer (Copy of FINAL GRADE 2) is changed
[0x7fff9a13f380] | SyManager.Signals | INFO | 2018-07-13 09:02:55,319 | Current timeline pointer (Assembly_101217_version for grade) is changed
/Volumes/CANDY/CANDY MUSIC VID RUSHES/A003/CAM1_2017-05-12_0213_C0000/CAM1_2017-05-12_0213_C0000_001903.dng: Cannot read TIFF header.
[0x7000050a4000] | IO | ERROR | 2018-07-13 09:02:55,873 | Failed to read frame frame from video frame </Volumes/CANDY/CANDY MUSIC VID RUSHES/A003/CAM1_2017-05-12_0213_C0000/CAM1_2017-05-12_0213_C0000_001903.dng>, error: <Can't open file for reading.>
/Volumes/CANDY/CANDY MUSIC VID RUSHES/A003/CAM1_2017-05-12_0213_C0000/CAM1_2017-05-12_0213_C0000_1903.dng: Cannot read TIFF header.
[0x7000050a4000] | IO | ERROR | 2018-07-13 09:02:55,873 | Failed to read frame frame from video frame </Volumes/CANDY/CANDY MUSIC VID RUSHES/A003/CAM1_2017-05-12_0213_C0000/CAM1_2017-05-12_0213_C0000_1903.dng>, error: <Can't open file for reading.>
/Volumes/CANDY/CANDY MUSIC VID RUSHES/A003/CAM1_2017-05-12_0213_C0000/CAM1_2017-05-12_0213_C0000_001903.dng: Cannot read TIFF header.
[0x7000050a4000] | IO | ERROR | 2018-07-13 09:02:55,879 | Failed to read frame frame from video frame </Volumes/CANDY/CANDY MUSIC VID RUSHES/A003/CAM1_2017-05-12_0213_C0000/CAM1_2017-05-12_0213_C0000_001903.dng>, error: <Can't open file for reading.>
/Volumes/CANDY/CANDY MUSIC VID RUSHES/A003/CAM1_2017-05-12_0213_C0000/CAM1_2017-05-12_0213_C0000_1903.dng: Cannot read TIFF header.
[0x7000050a4000] | IO | ERROR | 2018-07-13 09:02:55,879 | Failed to read frame frame from video frame </Volumes/CANDY/CANDY MUSIC VID RUSHES/A003/CAM1_2017-05-12_0213_C0000/CAM1_2017-05-12_0213_C0000_1903.dng>, error: <Can't open file for reading.>
[0x700005c69000] | GPUManager | INFO | 2018-07-13 09:02:55,886 | Flushing GPU memory...
[0x700005c69000] | GPUManager | INFO | 2018-07-13 09:02:55,893 | Loaded Shaper LUT 'RED_to_ALEXA_LUT_v1/RED_IPP2/LUT_CUBE_32/RED_IPP2_to_AlexaV3Rec709_Iridas32.cube'
[0x700005c69000] | GPUManager | ERROR | 2018-07-13 09:02:55,968 | Failed to read Shaper LUT 'Arri/RED_IPP2_to_AlexaV3Rec709_Iridas32.cube'
Urgent message: Missing Look Up Table||3D LUT: Arri/RED_IPP2_to_AlexaV3Rec709_Iridas32.cube

/Volumes/CANDY/CANDY MUSIC VID RUSHES/A005/CAM1_2017-05-12_0643_C0005/CAM1_2017-05-12_0643_C0005_006313.dng: Cannot read TIFF header.
[0x7000050a4000] | IO | ERROR | 2018-07-13 09:02:55,974 | Failed to read frame frame from video frame </Volumes/CANDY/CANDY MUSIC VID RUSHES/A005/CAM1_2017-05-12_0643_C0005/CAM1_2017-05-12_0643_C0005_006313.dng>, error: <Can't open file for reading.>
/Volumes/CANDY/CANDY MUSIC VID RUSHES/A005/CAM1_2017-05-12_0643_C0005/CAM1_2017-05-12_0643_C0005_6313.dng: Cannot read TIFF header.
[0x7000050a4000] | IO | ERROR | 2018-07-13 09:02:55,974 | Failed to read frame frame from video frame </Volumes/CANDY/CANDY MUSIC VID RUSHES/A005/CAM1_2017-05-12_0643_C0005/CAM1_2017-05-12_0643_C0005_6313.dng>, error: <Can't open file for reading.>
*** Init[238]: Failed to open movie file at "/Volumes/CANDY RUSHES/CANDY/guide QT_Assembly_101217_version for grade.mov"
*** Create[68]: Init() failed with 2
*** BMDMacQuickTimeReader[230]: Movie::Create() failed
[0x700004e15000] | IO | ERROR | 2018-07-13 09:02:56,043 | Failed to create decoder for /Volumes/CANDY RUSHES/CANDY/guide QT_Assembly_101217_version for grade.mov
[0x700004e15000] | IO | ERROR | 2018-07-13 09:02:56,043 | Failed to open video file </Volumes/CANDY RUSHES/CANDY/guide QT_Assembly_101217_version for grade.mov> for decoding, error: <Codec is not opened yet.>
[0x700004e15000] | IO | ERROR | 2018-07-13 09:02:56,043 | IOVideoDecoderFacade can not decode file /Volumes/CANDY RUSHES/CANDY/guide QT_Assembly_101217_version for grade.mov of type QuickTime
Assertion failed: (IsPlanForThumbnails()), function CreatePlan, file GsTaskClipGraphThumbnailPlanner.cpp, line 51.


Some required information is missing for email crash report, the crash archive will not be updated



------


I also tried to delete all but your main assembly timeline and saved that off, but my macbook still crashed so as expected the issue is in your main timeline itself.

The only other suggestion i can give you is that if it is a big paying project you temp rent a bigger box to load it on (as it does load on 2 of my non laptop osx machines without issues. ) to save face and the day and swallow the costs.

Also maybe BM can chime in and pinpoint / remove the exact offending thing in the project that lifts it over the edge for your laptops.

Hi Glenn,

Thank you so much for going to all that trouble!
Unfortunately I still wasn’t able to load the file you uploaded for me but I’m so relieved to hear that you found a way of opening it one way or another.
Yes it desperately needs a good clean up. Just before the file stopped working all together I changed a lot of the original project settings to low res formats in an effort to reduce the gpu memory and I get the feeling doing that may have confused it? I wasn’t very careful in my choices either. But I won’t be playing with fire again that’s for sure!
Also from memeory there are 17 video tracks so I thought the first thing I would do when I can finally open it is split them up into different projects? And then maybe I can work that way on my new MacBook Pro?
So I may have to hire a bigger box, by that do you mean a desktop computer or an external GPU?

Thanks again,
Blake

I took a peek at the DRP and my advice would be to not to try to run a color session with 20 video tracks plus 23 nodes on each shot in a laptop. This is tough on a big machine. (It is possible the new eGPU-equipped machines could do it.) Light duty stuff like maybe ProRes 422 HD and a half-dozen nodes can work fine, but you'll take a big speed hit if you try any NR or OFX plug-ins.

I had no problem importing and running the DRP on a 12-core Trashcan Mac with dual D700s and 64GB of RAM, but without the media, it's hard to say whether you could get real-time out of it. My advice would be to collapse the timelines and get it down to (maybe) 2 video tracks -- 3 at the most -- and see if that helps.

Worst comes to worse, you could in theory export the XMLs for the edit list, grab all the stills and export the DPX stills + DRX files, and then rebuild the session from scratch. This might involve retracking windows and stabilization, but I've had that work on occasion (depending on the Gallery options).

Use this experience as a positive one: always export a DRP at the end of the day, particularly on a project you've been working on for many days (let alone months). Don't change versions in the middle of a project. Backup the project database before switching to a new version. Keep backup copies on removable drives just in case everything fails. Paranoia is sometimes justified if you can avoid project file disasters.

No worries man. Wish i could have helped you out of your ****. But at least you know the project itself is not damaged.

So I may have to hire a bigger box, by that do you mean a desktop computer or an external GPU?

Thanks again,
Blake

I would definately go for some desktop model with a beefy gpu. I had it next to my bigger workstation also opened on a smaller test VM with only 16Gb mem and a GTX1070 card (but it did have 24 cpu cores btw , but cpu should no be an issue just for opening).
So you could try of course to play with an eGPU but as you are on a deadline, i would not bother and go for safe. Then finish your project on that box rather then messing for hours trying to reduce the footprint etc.
Then drink some whiskey to forget about it and move on knowing you have a happy customer (which is what counts in the end if you want continued business)

And the rest i would end with Marc's ending.
Learn from it !