Jump to content

Craig Joiner

  • Content Count

  • Joined

  • Last visited

Everything posted by Craig Joiner

  1. As Harry says, kepep a complete full copy of your lightroom catalogue. Best to copy the entire folder and subfolders. That way, in the unlikely event of disaster, you won't loose anything including your previews which can take a long time to rebuild if you only have the catalogue backed up. The current (June 2019) Alamy Lightroom Bridge definately runs fine in LR Classic. I don't think it's been updated for a while because Alamy haven't made any changes that have affected it since June 2019.
  2. Someone who has an image they want to use and they don’t know who the owner is? Wasn't that what the Orphan Works was all about? I’m not expecting GIS to become a stock library and make us all rich of course, but this does make Google Images a slightly less hostile place for our images IMO. If it means a perspective buyer can find the image owner (or acting agent/library) with the click of a button and ultimately license the image then that has to be a good thing, right?
  3. Exactly right Harry. Sorry I should have been clearer (trying to multi task is never a good idea!) Just add the required details to one image then while that image is still selected create a preset (sorry I mistakenly said template originally) and you can add the Licensor metadata to your preset. And thanks for the v6.14 update. I see now that Licensor URL has been around since 2008 after the PLUS coalition got it added so relatively new but not new new. It's been in beta for several months so although officially only became standard from 31st Aug when the Google Images c
  4. Lightroom Classic does support Licensor URL but I might have read somewhere it was a relatively recent metadata field so possibly only available in later Creative Cloud versions. It's under 'IPTC Extension'. Scroll down to 'Rights' and 'Licensor' is there. Click on that and it'll open up with a number of fields including the Licensor URL field. Relatively easy to create a preset in LR and then apply it to all existing images and on import. More info at: https://iptc.org/standards/photo-metadata/quick-guide-to-iptc-photo-metadata-and-google-images/ Edit: You cannot
  5. Try the 'Embedded & Sidecar' option. With this LR just pulls the full size preview your camera embedded in the RAW file and is much faster. It won’t match what you eventually see in the develop module, but useful for checking critical focus at 100% etc. during initial culling. Craig
  6. The current system doesn't do this either. It does, however, minimise the risk to an acceptable level as the image is immediately removed from sale and not subject to further downloads/sales until it is removed from public view. Waiting months for a deletion while still visibly on sale is asking for trouble, not to mention difficult to explain should the publisher stumble across it. In any case, Wim was suggesting the kill switch should kill anything in the pipeline too & I agree.
  7. +1 for a kill switch. I sometimes license images direct to magazines that still demand the same images are not used in rival magazines for 6 months or more. Personally I thought the current restrictions were too blunt an instrument but I've come to live with them. However, if Alamy remove the editorial block I'm stuck. Deleting the image completely isn't an option because takes 6 months. A simple kill switch in addition to the proposed options seems like a reasonable compromise to me and would cover all eventualities. Craig
  8. Steve, You don't say which version of Windows you are using but as you refer to Microsoft "Photos" I'm assuming you're using windows 10. The default photos app in Windows 10 is not colour managed and images look very over saturated on wide gamut screens (as do desktop wallpapers 🙄). The old windows photo viewer can be reinstated however, see https://www.ghacks.net/2018/07/16/how-to-restore-the-windows-photo-viewer-on-windows-10/. This seems to be compatible with version 4 colour profiles. Craig
  9. Good point! Last time I did that, that feature of plugin wasn't working correctly and it kept reverting back so I'd forgotten about it. It was quickly fixed I hasten to add.
  10. The same happens if you submit a new updated version of an image. Have you tried clearing the Alamy data for the affected images in Lightroom? That often works but it depends on your matching criteria as to whether it will correctly match the newer images on Alamy. I match by filename only and when stuck have found that renaming the files in lightroom to match the version of my filename Alamy have applied to the newer image works (usually they append _1 from memory). You still need to clear the Alamy data in Lightroom for those images before re-syncing but once matched
  11. Not necessarily. The key here is ‘Any information supplied for display...’ If this personal info is added to the caption or keywords then yes, that is a breach. If it’s the standard IPTC contact & copyright sections then, as that is deleted / replaced by Alamy, it’s really only a waste of his time. Of course, if he supplies images direct to buyers or puts them on his own website it’s still a worthwhile thing to do.
  12. Double click on the 'Scale to Megabytes' option in Post-Process Actions in the bottom left of the Export dialogue in Lightroom to add it to the export options. Then it's just a matter of adjusting the max % value until you get the required megapixels. It's a bit of a fiddle and I never really understood why the max sixe is 33.33MP allowed by the plugin as Alamy accept much larger.
  13. The key is getting your file names to match the ones you used when you sent the images to Alamy. If there are consistent differences (such as a simple prefix or suffix) then the plugin can be set-up to account for that. If, like me, you radically changed your file naming along the way and lots of your images with Alamy have filenames significantly different to your current filenames in LR, then this is a bit more tricky. They way I handled this was ask Alamy to send me their metadata spreadsheet of my images and this contained the filenames I originally supplied. It was then a simp
  14. +1 The Sony appears to be a fine camera (but no better than any of its peers), but the system (ergonomics, menu, button location etc.) is very different to the Nikon system (and arguably not as mature). Running two very different systems side by side seems counterproductive. I get that people have switched to Sony in the past because they wanted the advantages of full frame mirrorless, but with the Z6 and Z7 pretty much matching the two Sonys, unless you didn’t like the Nikon system, there is no need. If it were me, and given the OP's previous regretted swit
  15. Why not wait for the Nikon Z6 to arrive in a couple of months before jumping? Seems to me that this camera has all the advantages you are looking for in the Sony but retains the Nikon system (button locations, menu system etc.) that you know plus with the FTZ lens adapter you can keep all your existing F mount glass (unless you have the older screw type AF lenses of course). The Sony system is very different to the Nikon system and I wonder if you were frustrated by these differences when you previously moved to Sony? if so then perhaps the A7III will be no different? If it were me
  16. In my experience disabling right click has no effect as the majority of infringers simply lift the images from Google where they found the image and never visit the originating site.
  17. Indeed. Edit -> Catalog Settings Then in the Metadata tab check ‘Automatically write changes to XMP' Make sure you also uncheck ‘Include Develop settings in metadata inside JPEG, PNG, and PSD files’ otherwise every edit you make in the Develop module is also written to the file on the fly which can cause Lightroom to slow down, unless you want need all your edits also stored in the files. I’d personally not recommend writing any data to images. With this setting on, Lightroom will be making lots of writes to your precious image files which increases the risk of c
  18. By default Lightroom only stores the metadata in it's database and unless you tell it to save the data to the original file, it doesn't make any changes to the image file on your hard disk. I would always advocate using the same workflow for all image types as it reduces the chance of human error and unexpected consequences such as you have found. So, I will always export from Lightroom as I know all my metadata will be correct and any image edits (no matter where made) will be in the exported images. I never use the original files on my hard drives and I never write changes to images from Lig
  19. You need to fetch the Alamy data for images on Alamy before anything will be visible in LR. Part of this process will automatically match images in your LR database with images on Alamy but it’s a manual process which needs to be kicked off from the Export dialogue in LR (Ctrl + Shift + E on a PC) and selecting 'Fetch Alamy Metadata', but if you haven’t done so yet, check the instructions at https://www.lightroom-plugins.com/downloads/Alamy%20Uploader%20Manual.pdf first which explains all the options and how to match images. Lots of useful stuff is downloaded (check out 'Alamy Plus'
  20. I thought that LR should flash up a warning when you try and open a raw file in PS with an older version of ACR. This warning will give you the option to render the file in LR before opening it in PS thus ensuring all newer features are included. Perhaps this has accidentally been suppressed? Try resetting all warning dialogues LR preferences (general tab) and see if the dialogue now comes up. If that doesn't work you can always export as a tiff file then re-import into LR and/or open in PS.
  21. Just to add, one of the great things about keywording in LR is that it remembers your keywords so that when you type those same keywords into new images it offers up the keywords previously used as you type which can speed up keywording and helps eliminate (or at least reduce) typos. At a more advanced level You can also add pseudonyms to keywords so 'Beech Tree" could have the pseudonyms 'Tree', 'Beech', 'Fagus sylvatica' and these pseudonyms are automatically added to the exported images and will all appear in AIM as tags. Then there are keyword hierarchies which can be useful too...
  22. You can always re-import your tiff/jpegs into LR once finished in PS and then add the keywords. Then just export as jpegs from LR and upload to Alamy.
  23. It's only metadata (keywords, captions etc.) that can be updated by the plugin. You cannot replace images on Alamy with newer versions. You would have to upload re-processed images as new images and delete the images on Alamy you are replacing.
  24. If the only difference is a fixed suffix or prefix that is missing at one end then you might be able to account for this in the plugin using the options in the matching section. If that doesn't work I believe you can change filenames in Lightroom to match Alamy, run the plugin to match images and then change the filename back and the Alamy reference sticks. Bit of a fiddle but as a one off exercise it should work. Best test it on a couple of images first though! Alternatively Alamy used to provide a spreadsheet of all your metadata and it was possible to manually update all your file
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.