Skip to main content

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

C1 5.1.2 and 64 bits support

Numix-Digital
Hi

Just downloading the lastest version of C1 and i see in the install, C1 installs in "Program files (x86)" not in "Programs" (for 64 bits software) and when I load it, i see in the task manager a *32 after "CaptureOne.exe" so it runs in 32 bits version.

I have Windows 7 Ultimate 64 bits, 16 GB RAM.

It's normal ? 🙄

Thanks.
0

Comments

13 comments

Date Votes
  • Paul Steunebrink
    Yes, CO5.x is a Win32 application which runs perfectly inside the 32-bits environment of Windows x64 versions.
    0
  • Numix-Digital
    I had never noticed it was a 32-bit and I thought it was 64 bits..

    Full 64 bits support is planned ?
    0
  • Paul Steunebrink
    No 64-bits conversion planned as far as I am aware of. By the way, what would be the advantage? Larger memory space? Hmm.
    0
  • Numix-Digital
    larger memory space yes.. why not =)

    why not use the maximum performance of processor architectures and operating systems?
    Many graphic softwares evolve in this direction so.. why not Capture One ?

    Well, thanks for your reply.
    0
  • Andrew Michael
    It's an interesting philosophical question. C1 doesn't need a 64-bit address space, but if you assumed that a 64-bit OS was the norm, would you bother to write 32-bit applications for it?

    Andy
    0
  • Wade Oram
    To put the counter argument, whilst 32 bit Windows is still supported and developed by MS and even a small portion of Capture One users choose 32bit Windows (and there are still some good reasons for choosing to do so), then a 32 bit Capture One has to exist. If, as is the case, this 32 bit version is equally happy running on 64 bit Windows without being performance limited by the 32 bit environment, why would anyone want to go to the expense of producing (with all of the test effort that implies) two Windows versions of a program.
    0
  • Wendy Bunton
    [quote="Paul_E" wrote:
    No 64-bits conversion planned as far as I am aware of. By the way, what would be the advantage? Larger memory space? Hmm.


    It might possibly eliminate the "out of memory" crashes I keep getting, mostly at the most inconvenient times? I've got 24GB on my system; just opening C1 and finding the last image I was working on before the most recent crash causes it to use 1.158GB. When that reaches about 1.25GB I can count on it crashing.
    0
  • Andrew Michael
    [quote="billbunton" wrote:

    It might possibly eliminate the "out of memory" crashes I keep getting, mostly at the most inconvenient times? I've got 24GB on my system; just opening C1 and finding the last image I was working on before the most recent crash causes it to use 1.158GB. When that reaches about 1.25GB I can count on it crashing.


    It runs quite happily on my i5 under 64-bit W7 with 8GB of RAM. As a 32-bit application it can only see 4GB of that, but it certainly shouldn't crash by using 1.25GB. Have you tried running Memtest or something similar recently?

    Andy
    0
  • Robert Whetton
    actually as a 32bit app it can only see 2GB
    0
  • Paul Steunebrink
    [quote="Bobtographer" wrote:
    actually as a 32bit app it can only see 2GB

    Well, ehhh, actually each Win32 application sees a 4 GB address space (2^32 = 4 GB), which is divided in 2 GB / 2 GB for the app and for the kernel each. The 4 GB address space is presented to the application by means of a virtual memory mapper which maps each address to either physical RAM or virtual, i.e. the Windows page file. In other words: it is not related to the amount of RAM.
    An application growing to the 2 GB space for that application can become unstable and could crash.

    More features and other enhancements might lead Capture One wanting to use the much larger memory address space that comes with 64-bits architecture in a near future. Such a change in architecture requires a major release in general, hence CO 6 or later. By the way, the same issues runs on Mac as well. Because the 32-bit platform will stay with us for some time to come (the venerable WinXP comes to mind), the application developer must maintain two architectures for each platform (Win & Mac) which is not an attractive proposition.

    As a result many application developers - like Phase One - will wait to switch over until the new architecture (i.e. 64-bit) has reached critical mass among their installed user base. Translation: now all drop XP, move to the latest Win x64 and give PO a call. That's is not going to happen very soon, I think. But I may be wrong.

    my 2cts.
    0
  • Keith Reeder
    [quote="Paul_E" wrote:
    Translation: now all drop XP, move to the latest Win x64 and give PO a call. That's is not going to happen very soon, I think. But I may be wrong.

    I'll be doing just that in the next week or so!

    😉

    I'm also aware that in its current incarnation, Cap One will not benefit from the additional RAM made available in x64 OS like Windows 7: my current machine only has 2 gb/Win XP and Cap One is both fast and as solid as a rock, so even if it will "only" be able to use 4 gb of the RAM in my new machine, it'll still be a big notional improvement - but according to Phase One, anything more will be a waste right now:
    Capture One does not require (nor is there any performance gain) by running on 64 bit processors. The primary advantage of 64 bit processing is the vastly increased memory that these processors can address. Capture One does not require any more memory than being addressed by 32 bit processors and their operating systems.
    0
  • Paul Steunebrink
    [quote="Keith Reeder" wrote:
    ...
    - but according to Phase One, anything more will be a waste right now:
    Capture One does not require (nor is there any performance gain) by running on 64 bit processors. The primary advantage of 64 bit processing is the vastly increased memory that these processors can address. Capture One does not require any more memory than being addressed by 32 bit processors and their operating systems.

    Thanks for the quote. Note this one is two years old, when CO 4.1.2 was current and Vista x64 was not gaining momentum yet. Since CO 4.5 Pro (Oct. 2008) the application is fattening up significantly IMHO (in particular on Mac by the way).

    That said, you do benefit from the 64-bit processor (which are common place now), > 4 GB RAM and a 64-bit OS while still running Win32 apps. Because now you can give your 32-bits applications are larger portion of physical RAM within their 4 GB address space with > 4 GB RAM in your system.

    It is not necessary to have a 64-bit chain (hardware - OS - app) end-to-end. Start with the hardware, next the OS and last the application, if necessary, and enjoy the benefits of the 64-bit OS + extra RAM while still running Win32 apps. I think a lot of people are overlooking this, feeling a Win32 app will limit their new 64-bit machine. Wrong. Think again. The hardware and OS are providing the resources to the app. And there is much more to provide in the 64-bit world.

    another 2 cts.
    0
  • Keith Reeder
    [quote="Paul_E" wrote:

    Thanks for the quote. Note this one is two years old, when CO 4.1.2 was current and Vista x64 was not gaining momentum yet.

    Yep, caught that, but - it seems to me - it is still likely to broadly reflect the current situation: as I say, in terms of speed Cap One 5 is the best of the bunch of the converters on my machine, including (by a significant margin) Bibble 5, which sells itself on conversion speed.
    0

Post is closed for comments.