Forum Replies Created

Page 1 of 2
  • Patrick Woodard

    November 25, 2014 at 10:34 pm in reply to: Davinci Resolve render problem with new Mac Pro

    All signs point to a bad driver/OpenCL bug. I have same issue. I would voice your concerns to Apple as I have. Hopefully a fix will come in the next OS update.

    Patrick Woodard

    Colorist
    http://www.digitalfilmtree.com
    http://www.patwoodard.com

  • I think there might be an issue with the beta links on Blackmagic’s website. The downloaded file is Resolve Lite on my system.

    Patrick Woodard

    Colorist
    http://www.digitalfilmtree.com
    http://www.patrickwoodard.me

  • A solution to this issue is at the top of my feature requests. I tried this process and don’t seen to get the results I wanted. Common source clips seem to get the same version number.


    Patrick Woodard

    http://www.patrickwoodard.me

  • Patrick Woodard

    September 13, 2011 at 6:30 pm in reply to: CS5.5 Timecode Issue

    I got word that Adobe is aware of this and will be fixed in the next update.

    Patrick Woodard

    http://www.patrickwoodard.me

  • Patrick Woodard

    September 2, 2011 at 7:53 pm in reply to: Grade Version Management

    I have the same problem with no solution. I use versions when a linked clip needs discrete adjustments within a scene. When I brought in a new XML I realized all versions default to version 1. I would think adding a option in the config page would be best. Something like pass through current version in all sessions.

    Patrick Woodard

  • Patrick Woodard

    February 17, 2011 at 7:25 pm in reply to: Pre-conform & Common Source Clip Indicator

    The projects I work on originate from SR tape from Alexa or Genesis cameras. They are onlined using Final Cut Pro.

    I’ve decided the best workflow (excluding RED R3D Files) is to self-contain a QuickTime from the final online sequence, rather than linking to media in the Resolve. The reason for self-containg the final timeline has to do with the sequence consisting of speed changes, repositionings, effects, 3rd-party transitions, smooth cams, all of which don’t make it into an edl.

    Some prefer to work off media knowing the limitations of an EDL and simply render in source mode. In FCP you just relink to color material for a finished timeline. I dislike this method for the following reasons – 1. When previewing with a DP or other client I have to explain what we are looking at isn’t final, all the speed effects, repos will be addressed later. This causes a lot of flipping back and forth between applications for previewing and color grading. 2. Every time you render a change you need to re-QC the FCP sequence to make sure the proper clips are relink to the current color changes.

    I prefer to work off of self-contained QuickTime, however the one drawback is losing the connection to common source clips. It would be great if the edl could not only tell the resolve where the cut points are but which shots are linked together based off of the clips names.

  • Patrick Woodard

    October 28, 2010 at 5:13 pm in reply to: Video Tutorial for Davinci Resolve

    I found this at fxphd. Scroll down to see the course description. I haven\’t watched them but was curious if anyone has and could give their opinion.

    https://www.fxphd.com/courses#DAV101

    Patrick Woodard

  • Patrick Woodard

    October 6, 2010 at 3:28 am in reply to: QuickTime Render File Crashes FCP

    Sorry, my bad. Looks like an FCP update fixed the issue.

    Patrick Woodard
    Colorist
    DigitalFilm Tree

  • Patrick Woodard

    September 24, 2010 at 7:08 pm in reply to: Legalize Material

    Thanks for the clarification.

    Patrick Woodard
    Colorist
    DigitalFilm Tree

  • Will the Resolve for Mac Require Snow Leopard or will it run on Leopard?

    Patrick Woodard
    Colorist
    DigitalFilm Tree

Page 1 of 2

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