Forum Replies Created

Page 4 of 64
  • Rohit Gupta

    November 12, 2014 at 4:01 am in reply to: Resolve reading mysterious timecode

    Thanks for sending the files. The problem is due to the fact that your encoding app is not updating the timecode in the Cineform metadata. When using Cineform, Resolve currently gives higher priority to the timecode in Cineform metadata. Moving forward, we will change it to just use Quicktime timecode.

  • Rohit Gupta

    November 8, 2014 at 1:24 am in reply to: Resolve reading mysterious timecode

    Two clips are enough. You send me a PM on BMD forum or Reduser

  • Rohit Gupta

    November 7, 2014 at 9:02 am in reply to: Resolve reading mysterious timecode

    We need the clips so we can reproduce the problem here, and debug it.

  • Rohit Gupta

    November 7, 2014 at 3:54 am in reply to: Resolve reading mysterious timecode

    Please post a sample so we can check it out!

  • Rohit Gupta

    November 7, 2014 at 12:14 am in reply to: Resolve reading mysterious timecode

    Please post a sample of the original, and the sample of the transcoded file.

  • Rohit Gupta

    October 27, 2014 at 9:35 am in reply to: Resolve 11 – GPU and Frame Blinking problem

    I suppose you will have to provide about this black flickering at top then. If you have purchased the full version of the software, you can contact BMD support with the details, and send the clip and project which will show the problem.

  • Rohit Gupta

    October 27, 2014 at 6:59 am in reply to: Resolve 11 – GPU and Frame Blinking problem

    Are you using Intel or AMD processor?

  • Rohit Gupta

    October 27, 2014 at 6:17 am in reply to: Resolve 11 – GPU and Frame Blinking problem

    Do you have the dongle securely plugged in when running the full version?

    Make sure you are using the version downloaded from the Blackmagic support website and not from any 3rd party site/source.

  • Rohit Gupta

    October 24, 2014 at 6:37 am in reply to: Resolve 11 lite CUDA driver issue

    >>From new RAW files to dnxhd 36 – speed: just 4-11 fps
    >>From already used source RAW footage (used to render out to dnxhd yesterday) now when rendered again

    Your bottleneck is your source drive. When the files are cached in RAM, the render is fast. Get a faster drive for your source!

  • Rohit Gupta

    October 24, 2014 at 3:15 am in reply to: Resolve 11 lite CUDA driver issue

    On Windows, CUDA is automatically used if you have a NVIDIA GPU.

    What is your source footage? Please post details on your system specs.

    Can you try doing a DNxHD to DNxHD render, and see what speeds you get?

Page 4 of 64

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