メインコンテンツへスキップ

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

Stacking raw and jpeg

コメント

10件のコメント

  • John Doe
    Why do you need the jpeg in your catalog when you already have the RAW?
    0
  • SFA
    [quote="John Doe" wrote:
    Why do you need the jpeg in your catalog when you already have the RAW?


    Or, indeed, vice versa?


    Grant
    0
  • John Doe
    [quote="SFA" wrote:
    [quote="John Doe" wrote:
    Why do you need the jpeg in your catalog when you already have the RAW?


    Or, indeed, vice versa?


    Grant

    You can always recreate the jpeg version from the RAW file, not the other way around. I never keep jpeg versions in my catalog, it's completely useless.
    0
  • SFA
    [quote="John Doe" wrote:
    [quote="SFA" wrote:
    [quote="John Doe" wrote:
    Why do you need the jpeg in your catalog when you already have the RAW?


    Or, indeed, vice versa?


    Grant

    You can always recreate the jpeg version from the RAW file, not the other way around. I never keep jpeg versions in my catalog, it's completely useless.


    True.

    On the other hand the overhead on the catalogue of having original raws that may never be touched again is not to be ignored either.

    I have contemplated using sessions with RAWs and cataloguing jpgs. By that means I could still get back to the RAWS when needed (slightly indirectly) but hopefully have a highly responsive catalogue.

    I have not done more than a test in principle at the moment.

    A future project.

    I'm sure it would not suit everyone's needs.


    Grant
    0
  • John Doe
    The catalog won't be any less responsive if you catalog the RAWs: as long as you don't zoom in, it will only display the previews.
    0
  • SFA
    [quote="John Doe" wrote:
    The catalog won't be any less responsive if you catalog the RAWs: as long as you don't zoom in, it will only display the previews.


    But I could consider using a managed catalogue with jpgs.

    Smaller file.

    Edit capabilities not vital in any way for search and discovery.

    But it's just an idea at the moment as I mainly work in sessions.


    Grant
    0
  • John Doe
    A referenced catalog would be even smaller. 😊
    0
  • SFA
    [quote="John Doe" wrote:
    A referenced catalog would be even smaller. 😊



    But part of the deal might be for instant delivery for sales of small jpgs ....

    However I do understand that there are a number of ways to approach the matter.

    As a sessions user I don't entirely see the need for an additional referenced catalogue of RAW files.


    Grant
    0
  • Tonyh-s
    I take it the answer is no then 😊

    At the moment I use a session to process the raw and then save a jpeg of the final result so that if I change the raw processing program (as I have done a couple of times) I don't loose all final versions of the photos. At the moment, the jpegs are catalogued in Photoshop Elements as it loads a large catalogue many times faster than Capture One. I was looking at combining everything into a Capture One Catalogue (even though it is slower) but this does not seem worth while now, so I will keep my sessions and elements catalogue.

    Thanks for all the comments though.
    0
  • John Doe
    Well you could always create another catalog in CO to store your JPEGs.

    That said, for archival purposes I would save in TIFF format, not JPEG.
    0

投稿コメントは受け付けていません。