Zum Hauptinhalt gehen

⚠️ Please note that this topic or post has been archived. The information contained here may no longer be accurate or up-to-date. ⚠️

Batch converstion too slow

Kommentare

4 Kommentare

  • Ulf Liljegren
    I did a test on my Laptop which is a 1.7Ghz Centrino with 1GB RAM.
    Jpeg High Quality 100% 300dpi
    Fuji S2 10 file ~14min at the same time a Canon 10D develop 10 file in a little over 4min.
    This is one of the disadvantages of the Fujis diagonal chip read out.
    Tim difference there is nothing we can do much about when the developing engine of Capture One is made for liniear chip readout data which all cameras are except Fuji S2 and S3.
    0
  • key5000
    Which mean it will take more than a day just to develope 400 images from my wedding?

    I will consider trying Bibble Pro, it took much less time than C1.
    0
  • Ulf Liljegren
    True, it will take shorter time, but you will also get a quality there after.
    You can do quick proof in Capture One, when doing this we put speed over quality and in normal processing we do opposite.
    The choice is yours.
    0
  • Permanently deleted user
    I do definitely agree about the quality, at least with Bibble. Bibble has a known limitations in quality with S2 files:

    http://forums.dpreview.com/forums/read. ... e=12004195

    However ACR does a very nice job and is fast. In the end I prefer C1 due to the a \"certain quality\" that is hard to define and the great workflow.

    That said, I do find it hard to believe the difference in performance is strictly do to a diagnal pixel layout. All the other engines have to deal with the same issue and don't seem to be so significantly slowed. It would make me, and probably other S2 users, feel better if the P1 engineers put a some effort into verifying there isn't some other explanation. The difference is pretty extraordinary.
    0

Post ist für Kommentare geschlossen.