Image Data Read Out and Editing Time
We are writing the year 2023 A.D. and it is still impossible to
1. Read out how big an image file is (I mean what the heck. I'm supposed to use a database to sort files and can't differentiate the size of a file in a simple overview — I need to actually look it up in Finder? Sure I get the resolution but some files have layers and the size is a great indicator to see which one is layered and which one isn't ... doesn't C1 know that in photography, sometimes you work in Photoshop and have layered files?)
2. Edit the Time or Date (not even within the database)
All we hear back on this subject is that C1 would "never write on a RAW file" because that's a feature. And? Who said anything about writing on the original RAW file. This is a database after all. You could just keep that in the xmp or file system or whatever it is called. It's also pretty obnoxious to claim you can't change the date in a software whose main product are camera backs who, at least in the past, consistently tell you the date is 1970. And then you are supposed to sort your files using date. Very useful to have all files sorted into 1970/mmdd_projectname /irony
3. Ability to export copies of RAW files or PSD (including all layers) using recipes (you have to use CMD-D just for that - please take away the use to consistently have to export things twice! I just want to tick all recipes - including a "export original file" option and not have to remember to do things several times: 1x for layered PSD, 1x for RAW, 1x for any other exports... such a waste of time energy and so many mistakes that are bound to happen!)
Any database will allow you to read out the basic data of a file and also to make adjustments. That's just a basic function.
This can't be all that hard, can it?
It is also getting a little bit annoying it is still not addressed.
-
Wolf,
1. Personally I am not interested at all in a perfect database for PSD files, but I might not have your use case, can you tell us which use case you have?
2. possible in version 23
3. Your point is to bring the functin to export originals via an processing/export recipe?
0 -
1. Not sure why there needs to be a more detailed explanation — we may have layered PSD’s in the database or generally may be interested in knowing how big a file is when sorting and organising the database. We may want to have all files in C1 rather than separating them into other folders… people have different needs and work in different ways. As to why we may have PSD… well, I guess in some instances retouching is still more precise and indeed more flexible in Photoshop.
Does that answer the question why wanting to see the size could be useful?
2. Great that alone may help me make a buying decision.
3. Recipes are a very convenient way to archive your files from your harddrive to a RAID once the job is done … except you cannot have an export recipe for RAW files or layered PSD’s …
So I have to run a CMD-D on all of my RAW, PSD and TIF files … and then run recipe’s to export Client JPG’s into my dropbox (typically from a finalised TIF/PSD or RAW file) .
It would be great if a recipe could also just copy the original RAW/TIF/PSD files without changing them. Then literally I would just have a bunch recipie’s switched on at all time and everything would be automated.
For example
1. Recipe exporting all files in their original state (including layers if any) to ARCHIVE using a naming convention based on date and project name2. A bunch of recipes for JPGs in various resolutions to Dropbox to share with Client
It could be called “Export Original File” or “Copy Original” … there is that optikn in the CMD -D menu but not for Recipes!
Hope this makes sense.
0 -
Hi Wolf, I suggest you submit a feature request to the company for each of your items if you didn't do so already.
https://support.captureone.com/hc/en-us/requests/new
Btw. I like your third point.
0
Post is closed for comments.
Comments
3 comments