Forum Replies Created

Page 21 of 22
  • Dmitry Kitsov

    February 5, 2012 at 7:17 am in reply to: Expected rendering performance.

    Michael, do you really mean 50fps render as in final output render? If so what are your system specs?
    I am on GTX285 (GUI), plus 2x GTX580s (image processing, Xeon 5690, 24GB. Both hard drives are raid systems with sustained 350MBps. All I get is 15fps ProRes render.

  • Dmitry Kitsov

    February 5, 2012 at 2:56 am in reply to: Expected rendering performance.

    Really? So GPU acceleration id only used for grading process and not the render itself?

  • Dmitry Kitsov

    February 4, 2012 at 5:48 pm in reply to: X-Rite i1Display Pro…
  • Dmitry Kitsov

    February 4, 2012 at 5:46 pm in reply to: X-Rite i1Display Pro…

    Steve, this is from Luminous Landscape:
    “X-Rite Product Manager Steve Rankin posted the following on the ColorSync list Aug 19, 2011.

    As the product manager for our Display Solutions at X-Rite, let me try to clarify a few things regarding OEM and 3rd party developer support for our new i1D3 based colorimeters. There seems to be lot’s of confusion here. First and foremost, X-Rite absolutely does allow OEMs and 3rd party developers access to our i1Display Pro retail instruments. Karl Koch already mentioned it here on the ColorSync List that BasICColor will support our retail product and I now have permission from Eizo to announce that a soon to be released version of ColorNavigator software will also support our retail i1Display Pro device. In addition, while I cannot mention their names, I can tell you that there are more OEMs & developers currently working on integrating our channel device into their software solutions. So, for any other OEMs or third party developers that wish to also support our retail i1Display Pro device, please contact devsupport@xrite.com and ask for our “i1Display Pro License Request Form”. Second, regarding support of OEM versions of i1D3, this is not an X-Rite issue at all. Any software developer who wishes to support an OEM version of the i1D3 device must contact and obtain this ability from that OEM. I hope this clarifies things for all.”

  • Dmitry Kitsov

    February 4, 2012 at 5:43 pm in reply to: Expected rendering performance.

    Thanks, Margus. I am aware of the NR performance hit. I am however not looking for a general philosophical info and race track metaphors. I really am looking to compare the real world performance (for a very specific reason) with relatively simple conditions (ie. 1080p ProRes in – 1080p ProRes Out, one nod, primary color correction only)

  • Dmitry Kitsov

    February 4, 2012 at 5:38 pm in reply to: Expected rendering performance.

    Thanks, Lauri
    By 1 GPU (plus gui) I of course meant 1GPU for acceleration plus 1 for gui (two altogether), and by 2 GPUs (plus gui) I meant three altogether. Could you try running a ProRes render for me (more critical to me as I work mostly with FCP people rather than Avid people)?

  • Dmitry Kitsov

    February 4, 2012 at 11:09 am in reply to: X-Rite i1Display Pro…

    x-rite stated that there is nothing that they do that limits retail probe use with third party software, so , it is actually everything to do with LightSpace.

  • Dmitry Kitsov

    February 4, 2012 at 11:04 am in reply to: Resolve for Windows – codec support

    There are a couple of unlisted codecs that seem to work on windows. Cineform and ProRes

  • Dmitry Kitsov

    January 19, 2012 at 1:00 am in reply to: What does a “wipe-A” mode do?

    Does anyone know?

  • Dmitry Kitsov

    January 14, 2012 at 11:27 pm in reply to: Audio initialization fails

    IS DeckLink card present?

Page 21 of 22

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