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

Ram Usage

Comments

11 comments

  • Gerald Bonne
    It keeps in memory each image you "browsed"... I had RAM issues when walking through a wedding shoot of over a thousand images.... It eats a lot. But your almost 8G beats my record.

    Did you screen many pictures to reach that much?
    0
  • Andrew Todzia
    There are 290 raw files in the folder, I have converted 21 so far to TIFF 8 bit files, and I am a little over half way through viewing the files. I have viewed in the editor window almost every file up to this point, so about 155 files.
    0
  • Gerald Bonne
    When I did something similar in CO 6 I did not reach 7G, maybe half of it. Did not try in CO 7 yet.

    Why 8bits for TIFF? If you go for lossless I guess you want to do more post processing on them so why not 16bits? (although that is really off topic). 8bits is just good enough for PC viewing (i.e. internet usage) but then JPG should do it. For large prints and more processing at a later stage you really want to go for 16 bits because else you will loose a lot of detail in clipping as soon as you touch the 8bit images.
    0
  • Andrew Todzia
    From my understanding printers only deal with 8 bits so sending 16 bit files to the printer is a waste. I use Qimage for printing and this subject was widely discussed a few years back and the consensus was 8 bit files were sufficient and 16 bit a waste of storage and processing. I don't know if that's right or wrong. I do prints up to 24 x 36 on an Epson 7900. Is there a reason I should rethink the 16 bit files? I am pretty sure Qimage doesn't send 16 bits to the printer. I don't think the Epson print drivers can handle 16 bits.
    0
  • LadyRainbows
    I believe C1 v7 is less restrained or held back on memory usage. This is a good thing, it doesn't need to constantly load and unload date from your memory. I believe this increases stability and speed things up for a lot of users. On the downside... reduce or no support for 32-bit users.
    0
  • Gerald Bonne
    [quote="NN8899721" wrote:
    From my understanding printers only deal with 8 bits so sending 16 bit files to the printer is a waste. I use Qimage for printing and this subject was widely discussed a few years back and the consensus was 8 bit files were sufficient and 16 bit a waste of storage and processing. I don't know if that's right or wrong. I do prints up to 24 x 36 on an Epson 7900. Is there a reason I should rethink the 16 bit files? I am pretty sure Qimage doesn't send 16 bits to the printer. I don't think the Epson print drivers can handle 16 bits.


    I don't know Qimage. I suppose the 8bits is then justified. If you create TIFF's just to print and them erase them you have a point doing it that way. If you want to keep them then you may as well switch to JPEG which will save you lots of disk space.
    0
  • Alain Decamps
    [quote="NN8899721" wrote:
    From my understanding printers only deal with 8 bits so sending 16 bit files to the printer is a waste. I use Qimage for printing and this subject was widely discussed a few years back and the consensus was 8 bit files were sufficient and 16 bit a waste of storage and processing. I don't know if that's right or wrong. I do prints up to 24 x 36 on an Epson 7900. Is there a reason I should rethink the 16 bit files? I am pretty sure Qimage doesn't send 16 bits to the printer. I don't think the Epson print drivers can handle 16 bits.


    It depends on the color conversion Qimage uses lcms an that can do a 16-bit conversion. I don't know if Qimage uses it that way, but it could make a small difference.

    It makes a bigger difference when you do manipulations between c1 and Qimage.
    0
  • NN634756744767534272UL
    currently C1 7 is using 15.8 GB of Ram and climbing .
    0
  • Gerald Bonne
    [quote="NN634756744767534272UL" wrote:
    currently C1 7 is using 15.8 GB of Ram and climbing .

    Damned! I just upgraded to 16G... Should I get 64G?
    0
  • NN634756744767534272UL
    I am posting this here since it relates. I had 16 gb ram and C1 maxed this out. I tried turning off openCL for both display and processing to see if that made any change in ram usage or stability. no change with OpenCL on or off. then I remembered that I had another 8g ram (same speed & type...) in my drawer so I added for a total of 24g. Capture one maxed out all available ram still. So I tried turning OpenCL back on for Display and processing and thats when the magic happened. C1 is now only using about 4g ram at the high end. runs more stable.... So I moved the memory chips around thinking maybe I have bad ram.... same results... So I took out the original ram leaving new 8g ram and C1 maxed out the ram again. SO to simplify

    with less than 24g ram AND opencl on or off ---------------------- c1 seems to have a memory leak of sorts.
    with 24g ram (or more I am guessing) AND with opencl off------- c1 seems to have a memory leak of sorts.
    with 24g ram (or more I am guessing) AND with opencl on------- c1 only uses average 2.5 g ram and is more stable.

    Can anyone shed any light on this for me?
    0
  • Andrew Todzia
    I have 12 GB of RAM and OpenCL is off and C1 maxes out my ram and then eventually freezes after 10 - 30 minutes of viewing and deleting photos. The folder had 3,400 raw files in it from one shoot so I am splitting it up into three folders and see what happens. Tomorrow I am receiving a new video card that is OpenCL capable and has 2 GB of ram so I should be able to turn OpenCL on for viewing and processing. Have to see what that does.
    0

Post is closed for comments.