Luminous Landscape Forum
Raw & Post Processing, Printing => Capture One Q&A => Topic started by: JimDK on October 06, 2016, 06:35:51 am
-
Hey gang,
As part of our continued efforts to make Capture One the go to app for Professional Photographers, we are running a short Q+A survey to see how we are meeting your needs. Find the survey in the link below:
https://www.anpdm.com/survey-public/414558477041405F477940/4446594B71494B5E4071
By completing the survey, you will be automatically entered into a draw to win 1 of 3 Capture One Pro Licenses free of charge!
-
As part of our continued efforts to make Capture One the go to app for Professional Photographers, we are running a short Q+A survey to see how we are meeting your needs.
A company that listens to their (potential) customers is always a good thing.
Cheers,
Bart
-
This 'culture' of being responsive to the customer is why I plunked down nearly $300 and dove into CO9 after being abandoned by Apple/Aperture and being unhappy with LR after a year of using it. When I find minor shortcomings in CO I feel confident that PO will resolve them.
-
This 'culture' of being responsive to the customer is why I plunked down nearly $300 and dove into CO9 after being abandoned by Apple/Aperture and being unhappy with LR after a year of using it. When I find minor shortcomings in CO I feel confident that PO will resolve them.
Yes, it looks like Phase One is trying. It used to be different, very hard to get a message across, but things have improved. Hope they keep it up.
Cheers,
Bart
-
I ran out of space in the "What can we do to improve Capture One" page.
-
I ran out of space in the "What can we do to improve Capture One" page.
share here then !
-
Allow for a history of steps, as in LR, that would be a nice feature for those that use a lot of the tool sets in C1, as undo is pretty much worthless, especially if you are going between more than one image. C1 bounces back and forth and within a few steps, it's very confusing.
I know that I am a voice in the wilderness on this, but it's just something I use a lot in LR and find it most helpful, and another reason I don't use ACR.
Paul C
-
It isn't a feature I relied on in LR but man, when you need it it can really save a lot of frustration. Seems like it would be easy to implement but I don't know anything about such matters.
-
share here then !
* First, workflow and speed of use. Lightroom still scores hugely over CO on this. Just thinking about how your customers use your product and how you can make the experience quicker and slicker would go a long way.
* A comprehensive SDK. Opening up CO to plugins would bring fresh ideas into the platform and allow users to better tailor CO to their own needs. I've always been pleasantly surprised by what a good SDK can bring to the table.
* Adjustment Mask painting needs work. I badly miss the elliptical tool from Lightroom. A blur tool. Also, I recently put in a request for something to create sets of luminance masks for layered adjustments.
* Custom search presets can only be applied to collections or folders of images. It would be useful to have an option to make these global, have the filter remain in effect when collection selections are changed.
* Option in recipes to set keywords on exported images. So, for example, when I export a set of images for a client I can have the export recipe tag them as sent to client.
*Expand hotkey sets, make more features hotkeyed. In particular I'd like to be able to assign hotkeys to keywords; hit the hotkey, keyword is assigned to all selected variants. This, combined with a smart folder, would give you a more flexible equivalent to Lightroom's Quick and Target collection feature.
* Extend smart folder searches to include names of collections containing images.
*Annotations: for making notes on workflows, processing details, client notes, whatever. But importantly, annotations should be allowed on folders, collections, smart collections as well as images. this has been a big request amongst Lightroom users for a long time.
* I need to be able to see more clearly what keywords are on images. Currently I have to open up the keyword library to see what keywords I have on an image and the picture gets confused if I have several images selected. I'd like to see a icon on thumbs with a popup list of keywords.
-
We will extend the character limit for the feedback sections :P
Just take the survey again and it should reopen with your last answers (as long as its the same computer). You can then add to your hearts content.
-
It's OK, I managed to condense it to fit. I'll add more if I think of it.
SDK, though. Big thing.
-
I'd like to see the following improvements in Capture One 10, so that I could consider upgrading from v. 8:
1. Deconvolution sharpening as an additional method to what already exists (I assume it's USM-based now?);
2. Output sharpening (esp. for downsized images), something like LR or RawTherapee have.
3. Local adjustments now don't allow me to input negative sharpening and noise reduction values (like you can in LR) -- good for when you want to set a global value, which can then be negated in just some places.
4. Keep improving auto-masking and healing.
5. Better support of smaller players like Pentax (Ricoh) -- more lens profiles and tethering.
6. (Better) support of Pixel-shift technology or X-trans, etc.
-
I've completed the survey even though I'm not a Professional Photographer.
It boggles my mind that your developers can get all that complex color/optics math right yet are unable to fix a simple UI bug which I keep reporting since august last year.
-
UI bugs aren't necessarily easy to track down or replicate. It may also be that your particular bug may not be high on the priority list.
-
* First, workflow and speed of use. Lightroom still scores hugely over CO on this. Just thinking about how your customers use your product and how you can make the experience quicker and slicker would go a long way.
That's interesting to me as I had the very opposite experience and was one of the things that pushed me toward CO. Now, I'm not a pro, I don't catalog vast numbers of images and I don't batch anything. So, I'm curious as to what in CO slows you down? This is meant out of curiosity, not a challenge to your experience. I have found that customized tool tabs in CO sped me up and not having to wait for the "Develop" module to open in LR, as well as the lag switching from Grid to Develop also decreased my processing time, or at least the parts of it that I found frustrating.
-
That's interesting to me as I had the very opposite experience and was one of the things that pushed me toward CO. Now, I'm not a pro, I don't catalog vast numbers of images and I don't batch anything. So, I'm curious as to what in CO slows you down? This is meant out of curiosity, not a challenge to your experience. I have found that customized tool tabs in CO sped me up and not having to wait for the "Develop" module to open in LR, as well as the lag switching from Grid to Develop also decreased my processing time, or at least the parts of it that I found frustrating.
Just because I am disagreeing with you on the other thread, I thought I would jump in and agree with you here :-)
I too have found C1 quicker to use than LR and I have been using LR since version 1. Having said that, it does seem that people who process things like Weddings seem to find LR faster (not all however, as I have also read blogs of wedding photographers who have changed to C1 and find it faster).
Like you, I find being able to customise the tool tabs and have tools repeated in different tabs dramatically speeds up working.
I also find that the "auto" setting in C1 is far more reliable than the auto settings in LR, which helps me get a "good enough" file that bit quicker.
Cheers,
Graham
-
Just because I am disagreeing with you on the other thread, I thought I would jump in and agree with you here :-)
Oh, most of the time someone disagrees with me here, I'm wrong. ;)
Like you, I find being able to customise the tool tabs and have tools repeated in different tabs dramatically speeds up working.
Yes. You can make a tool set for anything. I have one for B&W conversion with each step in my workflow in the order they normally get done. I love that.
My wish list for CO is fairly small and probably reflects my limited needs:
*I want an option to have the originals backed up within the CO Catalog backup, not just the database/modification data. Similar to the the Vault in Aperture.
*I would like to be able to change font sizes within the menus and toolbars. On a 27" 5k iMac at max res and normal viewing distance the text is tiny.
*I would like to see an actual tint scale under the tint slider in the White Balance menu. I do not naturally think of tint in terms of a number or a slider direction.
*Better vignette tool. It is really pretty bad as it exists now. Should be a priority for v10.
* I want to be able to delete an image file completely from anywhere that I am viewing an image. Currently you cannot do that from within a User Collection.
The last two are big for me.
But, my understanding is that v10 is in beta. So I'm guessing that anything we're requesting here is already in the works or will have to wait for v11.
Curious, how long are the version intervals typically for CO?
-
Hi,
A feature I would like to have is to display colours as Lab and not RGB. My understanding is that RGB values are not meaningful unless they are used in a well defined gamut, so they actually say very little about the colour. Lab coordinates are to my understanding unique and well defined.
Mostly helpful when using a ColorChecker for reference, as reference values are available in Lab.
Well possible the setting is available in Capture One already, it has many settings.
Best regards
Erik
-
But, my understanding is that v10 is in beta. So I'm guessing that anything we're requesting here is already in the works or will have to wait for v11.
Curious, how long are the version intervals typically for CO?
Release info is here:
https://en.wikipedia.org/wiki/Capture_One
I seem to remember that there were changes made from V8 or V9 to make interim point releases easier, so maybe we will have a longer wait between versions. Certainly we have seen new features at point releases, not just bug fixes and new camera support.
Cheers,
Graham
-
A feature I would like to have is to display colours as Lab
just pay $$$$ = http://dtdch.com/capture-one-ch/
-
I just started using Capture One 9.3. My main concern is Capture Sharpening and Sharpening for Output, which appear to be weak links. Also, is there any way to softproof like LR can do? I haven't been able to find anything.
-
I just started using Capture One 9.3. My main concern is Capture Sharpening and Sharpening for Output, which appear to be weak links. Also, is there any way to softproof like LR can do? I haven't been able to find anything.
What specifically is the weakness you see in CO's general sharpening? Is it the number of variables available or is it the actual image quality? Output sharpening is done at the time of printing. To me it seems as much of a black box as most of the others. I've used Sharpener Pro which takes paper type and image size into consideration but can't say I see a big difference in the print compared to simple output sharpening when printing from CO.
You can Soft Proof in CO. I do not remember how it compares to LR. I have been satisfied with it.
-
I just started using Capture One 9.3. My main concern is Capture Sharpening and Sharpening for Output, which appear to be weak links. Also, is there any way to softproof like LR can do? I haven't been able to find anything.
Softproof is in the view menu, but it also works by selecting an output recipe, the image then matches the output settings.
Cheers,
Graham
-
Allow for a history of steps, as in LR, that would be a nice feature for those that use a lot of the tool sets in C1, as undo is pretty much worthless, especially if you are going between more than one image. C1 bounces back and forth and within a few steps, it's very confusing.
I know that I am a voice in the wilderness on this, but it's just something I use a lot in LR and find it most helpful, and another reason I don't use ACR.
Paul C
I fully agree.
-
Softproof is in the view menu, but it also works by selecting an output recipe, the image then matches the output settings.
Thanks, but after studying the user manual for 30 minutes I still have no idea how to do what I want: have the softproof image next to the original image so I can adjust the softproof to match the original as closely as possible before printing. One of the worst manuals I have ever seen. Is there any other written material that would explain how to use Capture One?
-
Thanks, but after studying the user manual for 30 minutes I still have no idea how to do what I want: have the softproof image next to the original image so I can adjust the softproof to match the original as closely as possible before printing. One of the worst manuals I have ever seen. Is there any other written material that would explain how to use Capture One?
Ah, not sure how you do that. C1s comparisons are all done through variants and I'm not sure if you can assign different process recipes to different variants.
I agree the manual isn't the best, and I have relied on the many training videos Phase One put out, and available on Youtube or through their web site. https://www.youtube.com/user/PhaseOneDK
There is a relatively recent one (not the best video it has to be said) that covers B/W printing that also talks about soft proofing and there is an older one on printing, but I can't remember the content.
The only books on Capture One I am aware of are:
https://www.rockynook.com/free-ebook-on-capture-one-pro-9/
This is free and aimed at helping the transition from LR and Aperture to C1 and
https://www.rockynook.com/shop/photography/capture-one-pro-9/
Which is paid for, but if you get the free one first there is a 40% off voucher in it for this one. The latter, I think is pretty good, but could do with a bit more depth. I have just looked and there is nothing helpful about soft proofing other than explaining why you should do it and pointing you towards the menu.
Sorry I can't be of more direct help.
Cheers,
Graham
-
" Ah, not sure how you do that. C1s comparisons are all done through variants and I'm not sure if you can assign different process recipes to different variants. "
I also tried that and it appears that the profile is global and different ones cannot be applied to variants of the same image.
As you state comparing images side by side is not possible.
-
This would be worthy of a feature request. I never really thought of doing it that way. I just get close to what I want, then go into soft proof and adjust it the way I want it. But, I can see the utility of a side-by-side.
-
" Ah, not sure how you do that. C1s comparisons are all done through variants and I'm not sure if you can assign different process recipes to different variants. "
I also tried that and it appears that the profile is global and different ones cannot be applied to variants of the same image.
As you state comparing images side by side is not possible.
Yep, since my post I have also tried, and failed.
Cheers,
Graham
-
Yep, since my post I have also tried, and failed.
Thanks for the feedback. I guess you can see why I consider softproofing weak in C1. This seems like a pretty basic task that LR got right around version 4. However, I must say that the tools in C1 for adjusting images and the colors look better to me than LR, which is why I persist in spite of the interface oddities.
-
Thanks for the feedback. I guess you can see why I consider softproofing weak in C1. This seems like a pretty basic task that LR got right around version 4. However, I must say that the tools in C1 for adjusting images and the colors look better to me than LR, which is why I persist in spite of the interface oddities.
I think C1 still suffers from its roots as a fairly simple, but high quality, Raw Processor (using sessions) sitting between a Phase 1 camera and Photoshop. Its only relatively recently that they have started to move into Aperture and Lightroom territory, and they are still catching up on features and capabilities.
When I used it first, there was no interest in cataloguing or using it for anything other than outputing to Photoshop. Like you, I think it will be worth the wait :-)
Cheers,
Graham
-
I kind of wonder if Phase One saw an opportunity when Apple abandoned Aperture. For me Aperture was, and still is more elegant and intuitive, and even better looking than LR. Like myself, many Aperture users just never felt at home in LR. To me it is ugly, clunky and seems pieced together. Now, do Aperture orphans make up a significant enough market to have inspired PO to expand CO? I don't know. But for me, despite evidence that CO is an evolving app and despite the fact that LR has some distinct advantages (particularly in the printing and proofing department...and the vignette too) I have no intention of going back to LR. I used to enjoy working in Aperture. I used to dread working in LR even after I learned it and developed a work flow. Now, I enjoy post processing again in CO. Maybe some of it is GUI stuff, appearance and other intangibles, I don't know.
Also, I'm an amateur and have low volume, which certainly impacts my outlook compared to a high volume pro who needs extensive cataloging and batch processing features.
-
I kind of wonder if Phase One saw an opportunity when Apple abandoned Aperture.
Also, I'm an amateur and have low volume, which certainly impacts my outlook compared to a high volume pro who needs extensive cataloging and batch processing features.
I think a few things happened to encourage the move to being more than a raw processor. Adobe subscriptions, demise of Aperture and the maybe surprising success of Fuji X-trans cameras and the apparent inability for Adobe to sort out how to process them.
C1 is very popular with professionals due to the quality of its raw processing: not all pros work in high volume or need extensive cataloguing. As always its horses for course.
Cheers,
Graham
-
Hello Jim,
Long time C1PRO user, since 3.7.8 and I have happily upgraded and never skipped a version. I'd like to know the follow suggestion I provided in my survey. What is the practicality of making the "Image Core" the "brain" and processing instructions in C1PRO to be modular. I got the idea from the C1PRO Sony version, where I understand—it ONLY contains instructions and processing for SONY cameras and lenses.
With the modular approach, the user can select camera and lense combination and their installation of the Image Core would ONLY contain those the user selected.
From the developer's point of view—if cameras are released, the modular approach could be pushed to be updated on-demand. The user won't have to wait until the next point-release update to feature the new camera and/or lense.
I also got this idea from my biochemistry studies background on the idea of the enzyme-substrate complex. Depending on what binds at the active site of the enzyme (Image Core), the result is different. That way, the user's computer ONLY gets install the ONLY camera/lense instructions and nothing else extra is loaded, not even into any background processes.
Anyone who's versed in programming architecture can provide practical feedback to my idea. How practical is this modular approach? How resource intensive? Will it cost the Phase One more money internally to research and develop?
Thank you,
Ron
Hey gang,
As part of our continued efforts to make Capture One the go to app for Professional Photographers, we are running a short Q+A survey to see how we are meeting your needs. Find the survey in the link below:
https://www.anpdm.com/survey-public/414558477041405F477940/4446594B71494B5E4071
By completing the survey, you will be automatically entered into a draw to win 1 of 3 Capture One Pro Licenses free of charge!