Feature Requests
Implemented
Capture One fits the bill for image quality and speed of operation... but the feature set is still severely lacking and it doesn't look like v21 will fix that at all. Here is a quick list of the top of my head for things that are necessary in this day and age...
1. Effective LoCA correction. The "Purple Fringing" tool is just a joke. It's ineffective at best and there's no way to correct for the green side of the focal plane.
2. Robust plugin support. There's still no way to attach a fully featured editing deck. Do you still expect us to click on every tool for every edit we make? With great tools like the Loupedeck and even just a midi controller offering such a better way to do things, why hold off on allowing people to support your software?
3. Export previews with originals when moving between sessions and/or catalogs. Just a check box that would send the generated preview with the originals, just like you do with the "Include Adjustments" option.
4. Taking the original filename out of NON PHASE ONE cameras when tethering. I've submitted this to support and been given the same generic answer you can find on the forums. Honestly, I've already moved away from Capture One for tethering, but would be more than willing to come back if this single feature were implemented.
5. Searchability of tools. There are just so many that you only need occasionally. Having them all in one big search box would make it so much easier to find the lesser-used ones.
6. Dual monitor workspaces need to save correctly. My setup now changes EVERY TIME I open Capture One. I reported this as a bug and was told it was my problem. It happens on multiple machines with fresh installs of Capture One.
8. Noise reduction needs to preview correctly when being applied. The difference between proof view and regular view is huge.
9. Crop and rotation should really be merged as a single tool. Sychronising across multiple images means using the excessively featured copy/paste function or about the same number of clicks to do it manually.
9. Sessions need a way to know which files were already in a folder instead of having to search the folder every time. A folder of even 500 images can take a very long time for Capture One to recurse over, especially if that folder is on a spinning drive.
Just for example, I have sessions that I use as "browsers" for my archive. Every time I open a folder, no matter how many times I've opened it before, Capture One has to go over every single file to make sure it's there. My desk rattles with the hard drives being accessed and I wait 5 minutes or more for it to open the folder completely. Since I've already accessed this folder and generated previews for the files, why not save a quick little database file there that tells Capture One what's in the folder. That way it could load instantly and only need to check if a file exists when I actually click on that file or try to export it. Less wear on my hard drives and on my patience with Capture One in one quick change.
There are plenty more to share, but these are the basics.
-
"4. Taking the original filename out of NON PHASE ONE cameras when tethering. I've submitted this to support and been given the same generic answer you can find on the forums. Honestly, I've already moved away from Capture One for tethering, but would be more than willing to come back if this single feature were implemented."
Do you mean 'use a different name than the original file name while tethering non-PhaseOne cameras'? You can already set the filename in the shooting menu. I've set mine to use the session name plus a counter so it's "session01-0001.raw" or whatever.
Or did you mean something different?
"9. Crop and rotation should really be merged as a single tool. Sychronising across multiple images means using the excessively featured copy/paste function or about the same number of clicks to do it manually."
While cropping you can also rotate the image by moving the cursor to the corner of the cropped image - then it turns into the "rotation" tool.0 -
9. part 2
You need a catalog.
Then request a version of C1 that requires all known files to be Imported and correctly managed only within C1.
Probably best if they are in fact what C1 calls "Managed Files" and the folders used to store them are compete inaccessible in any way other than via C1.
Also disable any potential for "round tripping" that might break the "has to be imported" requirement by needing to monitor folders for files possibly being returned by a third party program.
For point 6 - you probably need to use the Hot Folder tethering option.
Some recent cameras form one or two apparently support writing to internal memory cards when tethered so perhaps that is what you are referring to so that the "backup" copies n the cards have the same names as the fully tethered images? Maybe they do already? I don't own any of those cameras so cannot check.
My Canons, if fully tethered, do not access the internal camera functions that would generate camera file names and I see no reason to do so since the internal cards are not used. Historically that has been the case for most cameras thus making the request somewhat moot.
If shooting tethered I'm struggling to find a need to use a camera generated image name when a C1 generated name can be made much more useful.
For point 5.
The "Create floating tool" option provides a consolidate list of all available tools.
0 -
On C-M-B's points:
4 - See SFA's response.
9. Please re-read the original statement. I'm talking about sybchronisation and speed for multiple image editing.On SFA's points:
9(2). No. Managed files are the EXACT opposite of what I want. This means creating a whole separate file structure within capture one that doesn't represent anything physical on my drive. What I want is for Capture One to not recursively check for files every time I open an existing session. Just like disk sync programs work, there are much more efficient ways to do what it is doing.
6. The need here is simple. Capture One is unreliable. It crashes constantly and the tether breaks more often than not. I need to know that the files I'm shooting to my card (yes, I shoot to two cards as well as capture one) have the same names so I can simply copy them at the end of the shoot and know that I have what I shot.
RIght now, I'm having to use the dinky solution of tethering through Fujifilm's X Acquire into the capture folder of my session just to get files in. We were still getting about 10 crashes a day and ended up just using Lightroom, which worked flawlessly.
My requests are not for workarounds but actual fixes to the program.
0 -
For 6.
Fuji cameras are one of the two manufacturers that have recently allowed connection protocols on some cameras that provide for shooting to in-camera memory as well as to computer disk directly.
Most others (and I thing all others in the past) have not offered that facility. Things may change in the future. It might be a case of the Manufacturers agreeing to release code and authorisation to access the camera systems in order to replicate in camera controls direct from the RAW converter applications.
Meanwhile the Hot Folder option seems to be the prevailing method where in-camera file naming and storage are required.
Out of theoretical interest, have you investigated whether the need to write out to 3 storage locations with, in the case of one of them, a different file name has any effect on connection reliability?
For a while I experimented with (untethered) shooting to 2 internal cards (1 RAW, 1 jpg) and a cable connected external device while in a "field" shooting mode. The idea was to be able to make jpgs available for instant viewing if required. As an experiment I realised it slowed down shooting speed (sports stuff) due to slower release of camera buffer (not ideal) but the main problem was working out how one might create a non-bulky but firmly connected solution for the camera to external storage that did not impeded the handling of the camera.
For 9 part 2.
You want to a access a folder that is not managed by the application it is entirely logical that the application needs to check the content on access to the folder.
If doing that there is probably little performance difference between simple reading what is currently there (as C1 does with sessions) and checking a list of previously "known" files to see if they are still there prior to looking for any additions.
The time taken to pre-load memory with the intent of seeking to provide a more rapid in-session editing experience may be unwelcome but the alternative would be to load and prepare on demand and that would likely make the editing process experience somewhat clunkier. Less so, perhaps, with a catalog style database of similar size to a typical session in terms of number of images.
I get the impression from many comments that Macs are in some situations slower than PCs - opening sessions ans catalogs for example. As PC user (a rather old PC at that) I don't see performance issues of the sort that Mac users often describe, though that does not seem to be true for everyone.
To balance the comment a little, in other situations Macs seem to be speedier than PCs depending on configurations, etc.
0
Post ist für Kommentare geschlossen.
Kommentare
4 Kommentare