Greg Huson wrote:Peter Benson wrote:While you're here, Greg, kindly inform us
• What kind of video files (i.e., the CODEC type) did you start with, and
• What CODEC type did you transcode them to, and
• At what data-rate are the transcoded files?
When the project has opened, I've been able to make a .drp, which then imported into a new database...
...The project worked fine for months, and only developed this odd behavior a few weeks ago. I'm thinking it's something added about that time that created this issue. The only things we've been adding periodically are graphics (.psd) and AAFs. No new footage.
Today it took 3 tries to open the project, not bad. Yesterday I worked on it most of the day after 3 or 4 attempts to open.
...I don't entirely grasp the relevance of Peter's questions to a crash that happens when opening the file...
...The image files are almost all DNG Raw, about 65Tb worth (again, no problem until recently, and those have been attached for months....
...I'm beginning to feel the need to render out sequences as 'submasters,' just in case!)
...The data rate for DNx and ProResHQ is roughly the same for HD 23.98 - about 175.
The project is local, not shared...
1) Ok, by "175" near the end of the above quote, do you mean to convey...
"The data-rate for your DNx... and ProResHQ [transcoded] files is...about
175 Megabits per second...MegaBytes per sec. or what, if you don't mind telling?
(It's not clear what 175 means, without the useful qualifier after it.) 2) Conveying the type of files you're editing along with their and their data-rate provides some useful insight for those able to assist you -- especially since you have yet to attach a Resolve diagnostics log.
I was recently made aware by Dmitriy at BMD Customer Support that lack of integrity of a huge project that's been lying on a system for a good number of months, with increasingly more executed on it occasionally, especially an edit project with
highly-compressed files -- such as I have here, in a 7-month long-in-the-tooth project, containing over 700 event elements in the timeline, most of which are an H.264 in an MPEG4 wrapper -- and others of which are 29.98 fps AVCHD at 50MB/sec.
I have more reason to be nervous I think, than even you do -- due to the stress imposed on the CPU here!
This project here, is an experimental test of my resolve to try BMD's editor for the very first time -- and on a moderately powered ASUS gaming PC,
and without transcoding.
If I were you, I''d make your backups of the database as well as the project itself (with stills and LUTS if applicable)
apart from the RAID too.
Here's hoping someone can guide you in looking for yet
another[i/i] type crash log that may well be lurking on your machine, that might even reveal something that's gone amiss within your computer's OS environment, and not Resolve, as you have imagined.
As an example, after Resolve failed to SAVE or SAVE AS or even open, I found a somewhat useful, though not as comprehensive "Davinci Resolve Diagnostics Log" on my PC, within
C:/AppData/Programs/Blackmagic Design/Resolve/Support if I'm not mistaken about that path [i](I'm currently away from the machine). That aforementioned "Diagnostics Log" fortunately, in plain language, revealed even to this novice crash log reader, that I had developed a WindowsMM [MultiMedia Player?] output device error, causing a conflict with Resolve-connected USB MIDI surface controllers (Softube Console 1 hardware/software audio plug-in -- and Mackie MCU Pro Universal Controller).
That WindowsMM device error, fighting within the OS environment, was preventing Resolve from opening most of the time, but opening sometimes -- and saving sometimes, but no longer able to effect a "Save As" operation.
I fixed it myself by disabling, then immediately re-enabling 3 or 4 drivers, one at a time, within Windows 8.1
Device Manager > Sound, video and game controllers
Hope all this provides you impetus for more ideas, and apart from consideratiob of insights offered you here, your retrieving and providing a useful, pertinent log is well critical in speedily having people aid you in tracking down the culprit.
By way of encouragement, let me presumptuously assert that you likely *do* have a useful log, but you may need to fish a bit more earnestly for it.Cheers.
Peter
RS 14.3.0.014 | MiniMonitor | DTV 10.9.7 | Win64 8.1 | ASUS ROG G751JL, Intel i74720HQ, 24GB DDR3, 1TB 5200RPM[only!], 500GB EVO 850 SSD, GTX965M | Mackie MCU Pro | Softube Console 1 | Shuttle Pro 2