Personal View site logo
DaVinci Resolve 18 and older 17 and 16
  • 459 Replies sorted by
  • @joethepro correct, but I would say it's better to have it separated, more control.
    Cool 3d qualifier with Van Hurkman


    + a bit on matching (and thinking =)

    and shortcut sheet

    Full-resolve12-edit-menu-cheatsheet.jpg
    3300 x 2550 - 1M
  • @GMC It changed to Clean Black and Clean White. A little more to have to fiddle with, but it works well. You can always still use blur.

  • What I am missing in the free version (or haven't been able to find yet) is the denoise function in the matte finesse section - it seems to have gone. In the Resolve 11 lite version it was there. Without it any color qualification will be flawed.

  • The limits are far fewer effects and the transform ranges seem limited. I can only scale things between .25 and 4. Is there some other way that someone can suggest? How would you zoom something from infinitely small to outside the frame?

    You can use free HitFilm version in pair with it :-)

  • @Jspatz asking the big questions. I hate those limits too!

  • I am really enjoying this and believe it can replace PP2015 for many of my projects. Besides great color control, the tracking and stabilizing is fantastic. The limits are far fewer effects and the transform ranges seem limited. I can only scale things between .25 and 4. Is there some other way that someone can suggest? How would you zoom something from infinitely small to outside the frame?

  • Im guessing the bug is there for resolve 11 as well because my a6000 audio doesnt import with xavcs footage.

  • There is a bug reading audio tracks from some codecs on the Windows version of Resolve 12. Blackmagic is aware of the problem. Remember, this is still beta software.

  • @OzNimbus Coincidentally I noticed that my a6000 audio was not being imported to Resolve 11. Is there a known limitation with Resolve and Sony audio files?

  • Does it finally support a7s audio?

  • For some reason my compatibility settings were turned on and set to Windows 7. I am not sure if it installed this way or was picked up from a previous installation. I turned it off and now it runs flawlessly realtime on UHD 422 10bit Prores.

  • It works in Windows 7.

  • Working nicely on iMac Retina 5k with 4GB GPU. I don't think it will replace my other editing applications, but it is a nice upgrade for DaVinci. The new colour management is very handy and gave nice results with some GH4 V-Log test clips.

  • Does anyone have any idea why my performance is so bad. Playback starts at 12fps and within 5 seconds goes to less than 1fps regardless of project or clip size. This is a system that is always realtime with 4k in ppro. 64Gb ram and 2 GPUs (which Resolve reports correctly). There appears to be a bottleneck prior to the GPU. The CPU stays under 20% but the GPU bounces between 0 and 1 or 2%. Any suggestions much appreciated.

  • Are there are new audio tools available within Resolve, or do they support plugins at least to get audio editing capabilites?

  • Interesting. I'm still using CS5 and am not going to rent from Adobe. This may be a viable replacment.

  • BEWARE, backup (zip), 'cause DR12 will overwrite previous versions!!

    Very first impressions: UI much cleaner, after initial shock it looks and feels "clearminded". Nice work on curves section, greyed out/faded options, all modules and almost all graphics have been streamlined (maximized) and objects and tools given space, just love the simple dotted BG behind the nodes, which are much easier to link now. Search search search dialogs. Not fond of the top section, seems a bit like wasted space. Tuttle and open OFX seem to work (at least as in 11). Fuck me even TT meter (64bits wrapper) is working via VST!!! I still don't see myself editing complex projects here (need further deepfrying chicken wings), but for someone delivering FHD there's not much anyone can offer, for free +)
    image
    image

  • I have dual GTX970 on Windows 8. Davinci reports them but does not seem to be using them.

  • @joethepro just a couple of XAVC-S mp4 from Sony A7s, placed on the timeline to test. Weird things are happening with CUDA on Yosemite, unfortunately, but this GPU memory error seemed to be more related to Resolve. I had no such problems with the previous versions of Resolve

  • I'm on a PC with a GTX 650 TI seems to work well.