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

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

RAW/JPG as one thumbnail?

kgb_maine
I am considering bringing C1 7 into my workflow... currently I shoot with Canon capturing a RAW & Jpg simultaneously. In my current import & browsing solution (BreezeBorowser Pro) I can treat those files as one. I see one thumbnail per file name, even though I have imported a CR2 & JPG. Can I do this in C1 7?
Thanks
Kevin Brusie
Portland, Maine
0

コメント

3件のコメント

日付 投票
  • jeremya
    I'd also love something like this.

    Let me choose to manage the files "as one". JPG for quick preview, RAW for actual work... I think I'll go file a support/feature request now. 😊
    0
  • SFA
    I have, for some years, used an application that embedded a JPG (user specific size) of the current edit status of a RAW file (or any other supported type come to that) in what was effectively its sidecar edit file. This provided a quick access to to the latest edit of the image - at least to the limits of how well a (usually compressed) jpg could present how a fully processed RAW file could be displayed.

    RAW files already have jpgs embedded in them for rapid viewing purposes - usually set to small sizes to keep file sizes down. Whether they are visible for thumbnails depends on having an application that can interpet the RAW file to extract the jpg data. As I understand it this is waht provides the instant in-camera display of images if shooting RAW only (or choosing to display from the RAW file if shooting RAW + JPG). However so far as I am aware this is not usually updated in any way by any RAW convertor software.

    In effect, where accessible, either of the above options would be an alternative method of obtaining an instant "thumbnail" type view without needing to open an application's own thumbnail file or to re-process the image from the edit files. However the embedded jpg ex camera would not display as per latest edits (if any).

    In the other application I have used, mentioned above, the original and edit files reside in the same folder (usually) and in those circumstances the in-built browser, sorted to disply by file name, will usually show the files side by side or as a single file if 'stacked'. There may be many variants of each original file - C1's browser uses much the same display concept.

    If shooting RAW +JPG, assuming both file types are Imported to the same folder sorted by name, the RAW and the original JPG would place next to each other. Edit files subsequently created (also jpg) would then co-exist in the same place too. Usually.

    This can get confusing. Care required.

    However if it comes to culling or moving the files each file is treated individually if not stacked and in any case the oriignal RAW and JPG files, though easily seen being next to each other, still need to be separately selected for housekeeping purposes.

    When I started shooting RAW + JPG I came to the conclusion that the purposes of each file type, for me, were very different and that 99% of the time I would not be editing jpgs. The jpgs to me are, primarily, a backup on the day and sometimes a fast way to share something quickly without having time to process the entire shoot. Once I have the RAW files safely stored and backed up I don't often have a need to for the jpgs at all. That led me to leaving the jpgs on their card and then discarding them once my RAWs and their backups were in place. (Obviously that is not the case if I have only shot jpg or the purpose of the image means the jpg will be fine as it is and I can discard the RAW!) I should perhaps mention that most of my images are shot on a camera with 2 cards so I separate RAW and JPG by card. However it is quite possible to separate when importing to Capture one as well when I use alternative cameras. (As you likely already know!)

    On that basis, which is where I think your BreezeBrowser comparison comes in, the "manage both files as one" requirement is not of regular interest from a personal point of view although at one time I thought it would be. When I realised that I hardly ever touched the (separately) imported jpgs the problem was solved by not importing them in the first place! Much easier, less time consuming and nothing lost from my point of view Of course I appreciate that your needs may be different.

    From a development point of view the concept may look easy but I would guess that very quickly there would be requests for extra layers of complexity and anything provided would add to the processing overhead in some way so performance issues would need to be considered. One way or another it's probably not as simple to implement as it seems. However there would be no harm in putting it forward as an enhancement request to see what happens. You may gain from saying explicitly what the 'file pairing' feature needs to work for. Basic controls for moving and culling? Keeping edited variants for both the RAW and JPG files in line (as far as possible)? Other things too?

    Just some thoughts that might assist the cause.


    Grant Perkins
    0
  • jeremya
    That's great info Grant.

    I posted a feature request with Phase One and here was their reply:

    "To certain degrees we can do this.
    We have View->Global filters where you can hide JPGs

    If you want to rename file, you have the option in batch rename to pair RAW and JPGs"

    So, at least here we have partial ability to work with them together as a 'unit' of sorts.
    0

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