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. ⚠️

a question for Capture one 4 processing speed problem

Kommentare

4 Kommentare

  • Paul Steunebrink
    64-bit processing does, in general, not speed up compared to 32-bit unless the 4 GB RAM limit is the bottleneck. In particular this is not the case with Capture One, which is a 32-bits application and will run in 32-to-64 bit conversion, which has a small overhead and won't benefit from > 4 GB RAM.
    Please not that for tethering, 64-bit Windows is currently not supported by Capture One (or any other application from Canon, Nikon etc. that I am aware off).

    You could try to be more specific about what part of the workflow is slow (preview generation, processing to RGB for example). Also you could be more specific about processor and amount of RAM in your computer and hard disk (total and remaining free space). More specific: a multi-core processor and some extra RAM (up to max. of 4 GB for a 32-bit operating system) might help you more, as well as a big and fast internal hard drive with sufficient free space (disk become increasingly slow when filled more than 50%).
    0
  • Phil Hawkins
    [quote="Paul_E" wrote:
    64-bit processing does, in general, not speed up compared to 32-bit unless the 4 GB RAM limit is the bottleneck. In particular this is not the case with Capture One, which is a 32-bits application and will run in 32-to-64 bit conversion, which has a small overhead and won't benefit from > 4 GB RAM.
    Please not that for tethering, 64-bit Windows is currently not supported by Capture One (or any other application from Canon, Nikon etc. that I am aware off).

    You could try to be more specific about what part of the workflow is slow (preview generation, processing to RGB for example). Also you could be more specific about processor and amount of RAM in your computer and hard disk (total and remaining free space). More specific: a multi-core processor and some extra RAM (up to max. of 4 GB for a 32-bit operating system) might help you more, as well as a big and fast internal hard drive with sufficient free space (disk become increasingly slow when filled more than 50%).


    I don't understand what this says; will Capture One v. 4.X work on 64-bit Windows Vista? It would seem to me with CS4 out running on 64-bit Windows, C-One would follow suit. What does "32-to-64 bit conversion" mean?
    0
  • Paul Steunebrink
    In a x64 version of Windows (either XP Pro x64 or Vista x64) a Win32 application runs in a separate and emulated Win32 environment which translates instructions to the lower level 64-bits kernel. Both the application and the user are not aware of this Windows-on-Windows, and there is a minor overhead involved compared to the x86 (=32-bits) version of Windows. My own experiences and performance measures show no noticeable improvement nor delay for CO4.x processing in 32- and 64-bits Windows versions on the same hardware.

    Note that the Windows-on-Windows technique is not unique. On a 32-bits Windows you can run older and now very rare 16-bits applications like you run 32-bits applications on a x64 system.

    So, CO4.x will run on x64 systems, including Vista x64, without tethering. PS CS4 (Windows) is now a 64-bits application and you can benefit a larger memory address space on machines with > 4 GB RAM. I don't see much relevance for CO4 to become 64-bit in the short term since raw conversion should not allocate that much memory. External hardware support like tethering on x64 however should be more welcome in the short term with the increasing adoption of x64 platform.
    My 2 cents.
    0
  • Christopher
    [quote="Paul_E" wrote:
    So, CO4.x will run on x64 systems, including Vista x64, without tethering.

    The reason for the missing tethering is that Capture One installs a driver to facilitate its communication with the camera. 64-bit systems require 64-bit drivers, and even more to the point Vista x64 requires signed drivers.

    So it is just a matter of Phase One compiling their driver with the 64-bit build tools, and getting that resulting driver signed. Not a huge task to accomplish, but time consuming--especially the first time through the Windows "quality assurance" labs.
    0

Post ist für Kommentare geschlossen.