-
Posts
660 -
Joined
-
Last visited
Profile Information
-
Gender
Male
-
Location
York, UK
Alamy
-
Alamy URL
https://www.alamy.com/stock-photo/?cid=GCM6BKZXEJ2YQYKWXJSJZJNQEZSQ47PF97F4B2K9KTZYR7W6839EN5NTTHJU2Y5Z&name=Russell%2bWatkins&st=12&mode=0&comp=1
-
Images
1413
-
Joined Alamy
20 Nov 2011
Recent Profile Visitors
1,640 profile views
Russell Watkins's Achievements
Forum regular (2/3)
920
Reputation
-
Russell Watkins started following How was your September 2023? , Images licensed April 2024 , Images Licenced Feb 2024 and 5 others
-
Images Licenced Feb 2024
Russell Watkins replied to Doc's topic in Stock photography discussion and contributor experience
Low $. Country: Worldwide Usage: Editorial, For editorial use digital and social media platforms associated to Global Radio titles Media: Website, app and social media Start: 01 February 2024 Duration: Unlimited -
That is sad but a good innings from one of my favourite photographers. Thank you Mr Erwitt; you have given me a great deal of pleasure.
-
I'm using an unsatisfactory patchwork of Neofinder and Affinity/Pixelmator/Fuji image processing apps at the moment. I fear I am fast reaching the stage where I just have to suck it up and go back to LR and PS as, in spite of everything, they are probably the best overall if you want an efficient and effective DAM and image processing solution.
-
Further to my post above, and prompted by @Thomas Kyhn's, I wonder if there's something inherently difficult about adding a database to something? Aperture and then LR were developed (and so started out) as databases that happened to be able to do some image processing too. Aperture's database was the best I've used but LR was no slouch. I'd still be using Aperture today if Apple had not binned it. I liked LR too but, y'know, Adobe and subs... On the other hand, Capture One have seemingly had/have difficulties getting their database to play ball. And Photo Mechanic promised database functionality for years before they finally released it; it was a brilliant metadata handler when I used it without a database. Perhaps getting databases talking to other code has unintended consequences. (Yes, I have been very promiscuous when it comes to DAMs).
-
I know that now that it has both sessions and catalogs. I used Capture One up until v20. My point was that it was developed (pun intended) in a different way to LR and Aperture. Phase One bolted on catalogs to Capture One as an afterthought after they bought Media Pro (which was Microsoft's Expression Media DAM software) and saw which way the wind was blowing. AFAICT, in spite of that, for some reason, Capture One have paid scant attention to the catalog side of the code but concentrated on the raw development aspect.
-
Phase One have a different market, I think. They are targeting photographers who connect their camera direct to computer and shoot in what they call "Sessions", so there's no ingestion needed. Then when the photographer wants to find an image, they'll look for, say, the folder from June 2023 containing headshots for Joe Bloggs PLC (that will likely be called 2306-JoeBloggsHeadshots or similar) and the shot will be there in that session folder from the shoot. They're not really going for the "woman eating ice cream in front of the Eiffel Tower" crowd which is what Lightroom and Photo Mechanic and to some extent, Bridge and the now-defunct Aperture et al excel(led) at. And as has been said many times in this thread, there are many who don't realise that this type of granular search function is the prime feature of a DAM like Lightroom.