Better integration with Photoshop: Opening as layers and PSB support.
Implemented
3 things to improve the workflow between C1 and Photoshop. It would be nice to be able to select multiple images and open them as layers in Photoshop. In Lightroom this automatically stacks the images in a single file without opening 3 individual files. This also does not automatically save the files upon opening. When compositing multiple frames, it gets tedious to have to remove each saved file for each iteration you import. Lastly, is Photoshop Large Format support. With only a few layers on top of my Sony A7r IV or GFX 100 files I'm already having to save as a PSB. I would imagine this is a frustration with users of the Phase One IQ3/4 as well.
-
Your first request has been requested years ago already. Unfortunately, it seems unlikey that it will ever be implemented.
0 -
+1 for PSB support
2 -
Hi Brandon,
There is a couple of similar request on this topic.
Thank you for making this request, it will be also taken on board.
0 -
PSB support would be great. I'm using the IQ4 150 and almost every file for me needs to be saved as a PSB.
0 -
Capture One Pro definitely needs better integration with PhotoshopI think Capture One is a fantastic tool with a lot of great features. However, processing RAW files is only half the battle. As a commercial photographer and retoucher, I use Photoshop extensively. And there is no Asset Manager and RAW processor that does everything Photoshop can do for high end retouching and compositing. From a workflow standpoint, I really enjoy the tight integration between Lightroom and Photoshop. There are some features that I just can’t get in Capture One (as of Capture One Pro 12). That being said, I’d like to suggest some features that I think a lot of Lightroom users looking to switch to Capture One Pro would love to see in a future release.Suggestions #1 PSB SupportPSB support is a must. If you shoot with any modern mirrorless camera and you build composite images in Photoshop, your files will indeed be over 2GB in size and PSDs are no longer a viable format. Also, if you plan on using Capture One to replace Lightroom at any point, it's not really possible if you have PSBs in your catalog. Please add PSB support soonSuggestion #2 Edit With > Photoshop (Without Creating Copies)For me personally, this is probably one of the biggest features missing for me. (If you even want to call this a feature…it’s more of a workflow preference.) I would love to see Capture One implement the ability to simply open a processed file into Photoshop without the need to create any additional files. For example, in Lightroom you can make any necessary adjustments to your RAW file and then send a processed version of that file straight into Photoshop (without the need to export or process files out to other formats). Once you’re in Photoshop, then you can decide whether or not you want to save it as a PSD or not save it at all. In addition, you can choose where you want to save that file.For example, if you press Command + E in Lightroom, you’ll open up a processed version of that file with all of your Lightroom adjustments right into Photoshop. You have 3 options at this point. 1. Press Command + S in order save a PSD right next to the RAW file in Lightroom. 2. Press Command + Shift + S, and you can choose where you want to save your PSD. 3. Simply close the image and no additional files are created.Capture One on the other hand, automatically creates a PSD file that sits right next to your RAW file every time you choose Edit With > Photoshop. This creates a LOT of unnecessary PSD files that I have to go back and delete, especially if all you want to do is add additional layers to a photoshop document. It would be nice to simply open a processed file from Capture One directly into Photoshop.Suggestion #3 “Open As Layers In Photoshop” from Capture OneIn Lightroom, you can easily select multiple files and open them as layers that are stacked into a single Photoshop document. It would also be great to see Capture One have an “open as layers in Photoshop” command like Lightroom does.Suggestion #4 Open as Smart Object in PhotoshopThis may be wishful thinking here, but I'd love to see the ability to open a processes RAW file into Photoshop as a smart object, giving you the ability to keep the RAW file intact and make additional adjustments in Capture One. This is a feature that has been around in Lightroom for years and something I use all the time. It would be so great to see Capture One offer the same capability.Suggestion #5 Copyright Metadata:Open a photo inside of Photoshop, and go to File> File Info… There’s a tab that reads “Copyright Status.” In this dropdown menu, there are 3 options 1. Unknown 2. Copyrighted 3. Public Domain. When you have “Copyright Status” set to “Copyrighted” it adds a copyright © symbol into your Photoshop document window of that file, letting you know that the status is set to “Copyrighted” I would think that this metadata is also read across Google search.While it's possible to add and embed "copyright metadata" into your files from Capture One, if you open that file into Photoshop and choose File> File Info..." And look under the "Copyright Status" tab, your files will say always say "Unknown." Sure, "Copyright Notice" will show your name if you added it in Photo Raw. But "Copyright Status" will default to “Unknown” every time. As far as I know, Lightroom is the only RAW processor that allows for “Copyright Status” metadata.When you use Lightroom, and add your copyright metadata, if you open a file from LR into Photoshop, and look under the "Copyright Status" tab, you'll see that it says "Copyrighted." In addition, the Photoshop document window that shows your file name will also show a copyright © symbol.I would like to see this copyright metadata featured added to Capture One3 -
+1 to Suggestion #4 Open as Smart Object in Photoshop
For most of my post-processing needs, CO is great (better than LR IMO in no small part due to the adjustment layers!). However, for some edits I find myself preferring to use PS and, when I do, will have it handle the RAW processing so I can easily adjust from within. As much as I like CO, it's still easier for me to just stay in LR because of this gap.
Other suggestions:
#6: Enable export to EIP from catalog (not just session) for portability. It's curious that CO team saw value in this feature only for session workflows.
#7: Improve the culling experience to be more on par with LR, where can very efficiently auto-advance through images and tag them as accept/reject w/o needing to resort to cumbersome workarounds to simulate something close.
1 -
Roland, auto advance is in capture one currently.
SELECT >> Select next when >> color/star/both
0 -
Roland if your using capture one why would you want to use adobes raw engine for select images. This makes no sense. You’re using capture one for a reason.
0 -
Hi Christopher,
CO targets the end-to-end photographer workflow, not just RAW processing. In general, I prefer CO over LR (primarily because of the adjustment layers), but, on occasion, I still choose PS to edit depending on the image. When using PS to edit, I have it handle the raw conversion so I can make RAW adjustments from within (by having the RAW image loaded as a smart object) instead of needing to go back to CO to make RAW adjustments, re-edit "in Photoshop," and start anew. Unsurprisingly, LR handles this scenario seamlessly. I've been in "paid" evaluation mode of CO for a few years now with the intent of weaning myself off LR, but it's details like this that have prevented me from doing so.
Edit: Regarding auto-advance, I overall stand corrected :-) I was too harsh to say resort to cumbersome workarounds. I tried the auto-advance feature, which is an excellent addition relative to earlier versions of CO, where my mind was stuck when I posted earlier comment. I still prefer the explicitness of LR's reject flag for culling and associated x/u hotkeys to reject/unflag (purely semantics, not a functional thing). I'd like to see a hotkey for unsetting the color tag, because I don't star label all of my photos (even keepers), so they're not a good choice for culling.
-Roland.
0 -
Roland,
You can define a Keyboard Hot Key for "None" related to the value for the colour tag. Would that help?
Also, C1, in sessions, has a "Selects" folder by default with a KB shortcut default to move an image to that folder. Basically the inverse of a "Rejects concept?"
One could invert the inversion and make the "Selects" folder a "Rejects" folder. Indeed one could add a Rejects folder and still point to that (or any other folder) using the "Selects" KB shortcut since which folder the shortcut points to can be changed on demand.
I don't much use Catalogues. Enforced catalogues was one of the reasons I abandoned LR after version 1.4.
However using catalogs you have a similar possibility to create an album and assign to it a "Selects" album function together with a dedicated KB shortcut to include images in that album. In your case you could use the "Rejects" album concept and ignore the terminology.
As a Sessions user I know that the "Selects" folder will be the folder to which image source files and edits, etc,, will be "transferred". I.E. is is a Folder on the disk.
Not being a catalog user I have not checked exactly what happens with the concept in a catalog setting. I assume that no files are moved and the edit data stays where it is in the database. So thinking "selects" rather than "rejects" may be closer to what you need when using a catalog.
For a session, since you get "physical" separation by moving the files into a folder, the concept may be closer to what you are looking for, even if the terminology is inverted.
There is a good case to be made for using a session during the ingestion and culling process so that one is not working with a lot of overhead in a catalog of completed work when one only needs to work with the most current images. However, that is an entirely different point of discussion so I'll leave things there for now.
0 -
Thanks SFA.
"You can define a Keyboard Hot Key for "None" related to the value for the colour tag. Would that help?"
Yes, it does :-) My bad for not exploring more deeply. Feedback to CO team this is should enable this by default since culling is a mainstream use-case. With LR, culling "just works" in a very efficient and intuitive way (i.e., hot keys pre-setup and flag semantics).
There is a good case to be made for using a session during the ingestion and culling process so that one is not working with a lot of overhead in a catalog of completed work when one only needs to work with the most current images.
This makes a lot of sense. Irrespective of CO or LR, I recently started using FastRawViewer to first-pass cull because it's fast and lightweight, so most of the obvious rejects are filtered out before the import process. But I still continue to refine / reject keeper selection from within CO/LR over time, so thanks for the suggestion.
0 -
Roland you’re not making any sense. So for some images you want to use the Ferrari of raw processors but just because you need to send it to PS you settle for a Toyota just because you want smart object editing. Capture one has no control how Adobe allows what to edit a smart object. What capture one could do is develop a plug-in which you can apply as a smart filter. But what your asking for is impossible otherwise and you’re stuck in this indecisive workflow that just doesn’t make any sense to me.
Process your raw, send it to PS for raster editing. Back in C1 export your finals.
Btw you can convert something to a smart object in PS and you can always “replace contents” to an adjusted raw as a workaround.
0 -
@Christopher, as I said, apps like CO/LR are not just about RAW processing. I want to use CO as my photo management solution, with the option to edit in PS in a seamless fashion similar to LR but CO breaks my workflow.
"Process your raw, send it to PS for raster editing. Back in C1 export your finals."
This is precisely what I don't want to have to do, and hence the ask :-). If you're happy with CO for all of your editing needs, then more power to you, but this is not the case for me. If choosing to edit in PS, I want to also retain the ability to make RAW adjustments from within PS, as previously stated. Your Ferrari versus Toyota analogy is hyperbole, IMO.
I didn't suggest that CO control "how Adobe allows what to edit a smart object." Rather, have CO either (1) load the RAW as a smart object when creating a new document using the "Edit With >" action, (2) provide an option to watch for and load new PSx/TIFF files in the same folder as "Open With >" file selection, or (3) some other mechanism. Enabling one of these options would be less than what LR provides (LR carries any adjustments made into the opened PS document), but if committing to edit in PS, then I don't see the incremental value that LR provides here as having a lot of value.
For option (1) PS appears so to support opening a document using an "optional parameter asSmartObject (default: false) to create a smart object around the opened document" via the JavaScript SDK, so there may be a path forward for enabling this (PS is obviously not written in JavaScript, but it's something Adobe has thought about so there may be other solutions or can externally call via JS.) It's not my role to investigate design options for CO -- I am simply providing customer feedback, and I disagree this is an impossible problem to solve.
Your BTW suggestion is helpful. Thank you for that :-) I tried it out end-to-end from within CO and, indeed, this workaround can work for me, and it gives me one less excuse to stay in LR.
-Roland.
Edit: Fix broken link
0 -
Strongly support these suggestions,
Open As Layers In Photoshop” from Capture One - Is a must!
2 -
Are there any news on PSB support?
0 -
Rene, the news is that there is still NO PSB SUPPORT in the latest version of Capture One Pro 22.
Having no PSB support is fine if you're the kind of photographer that literally just processes RAW files using Capture One and exports them to the web. But any working pro photographer who also uses Photoshop to stack layers and do composite and retouching work with 60+ megapixel files is out of luck.
I'm not even sure anyone from Capture One actually looks at this forum to be honest. I think that there are a lot of valid suggestions in this post that the C1 team should seriously consider.
0 -
I strongly support the suggestions, especially PSB support.
2 -
"... any working pro photographer who also uses Photoshop to stack layers and do composite and retouching work with 60+ megapixel files is out of luck"
You don't even need to be a "working pro photographer". There are things that PS can do that C1 simply cannot, nor should C1 try. Any photographer worth his or her salt eventually finds him or herself in Photoshop for certain edits, and better integration w/ PS is the one area where LR reigns supreme over C1. It's no surprise that Adobe would prioritize this, but I see PS integration as fundamental feature. For C1 team to not acknowledge is to be too proud to admit or putting their heads in the sand.
2
Post is closed for comments.
Comments
18 comments