Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums DaVinci Resolve Selecting Fullres premium puts Resolve into more than 15 minutes spinning wheel

  • Selecting Fullres premium puts Resolve into more than 15 minutes spinning wheel

    Posted by Mikhail Puzyrev on January 26, 2011 at 7:03 pm

    I have 12 parts by 40 minutes each. Selecting fullres (2k r3d) and pressing format puts resolve into longlong hanging with raid disk activity which can be interrupted only by forcing app to quit which I don’t like or pressing config multiple times and waiting for half an hour. What’s going on with it?

    2008
    285
    120
    4disk raid5
    system on ssd

    Mikhail Puzyrev replied 15 years, 6 months ago 3 Members · 3 Replies
  • 3 Replies
  • Sascha Haber

    January 26, 2011 at 10:14 pm

    It probably does through them and creates thumbnails or something.
    2008 and fullres is a problem.
    Even 2010 is.
    Rocket would solve it, but only for processing and playback.
    I am grading a feature on a machine with a rocket and we decided to process everything to 16 bit DPX with proper Redcolor2 and carefully selected head and tail room.
    Its just much more flickable.
    I suggest you do the same and keep the Red files for safety.
    But grading on them…well..the 10% real life quality gain you have to pay with 90% performance loss.

    A slice of color…

    DaVinci 7.1 OSX 10.6.6
    Dual Xeon 2,4 RAM 24 GB
    RAID0 8TB eSata 6TB
    GTX 285 / GT 120
    Extreme 3D+ WAVE

  • Peter Chamberlain

    January 27, 2011 at 1:44 am

    Hi, Are you reporting that you have 480 minutes across 12 sessions, all r3d in one project?
    And therefore you are loading the source clips of all these r3d’s, unknown original clip lengths, into the Media Pool? Normally this type of program would be handled with one of the sessions and therefore just the source clips for that session in the Media Pool. Obviously you can have more, but at some stage, you will run out of system memory keeping all those clips indexed.
    Try splitting the project in to 12 parts, one for each finished program to confirm it works to your expectation.
    Peter

  • Mikhail Puzyrev

    January 28, 2011 at 6:54 am

    Thanks everybody! I’ve just split project into three projects each holding 5 parts (one is 4), and responsiveness came back!

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