|
life is killing me posted:Does anyone know of a way to get LR to import photos to a different location? When you import, you can click on the import location (top right of the import window) and that opens up a dropdown of recent locations as well as a location listed as 'other'. Select that and it opens an Explorer/Finder window that lets you choose a different location and create a new folder if you need to. A little further down on the right in the import window under File Handling is the option to make a second copy. This works in exactly the same way as the import location chooser. If your photos are imported and backed up then you can safely delete the originals on your SD card. Here's my question. I recently started shooting film and I'd like to import my scanned photos with EXIF that describes the camera and lens I used. I can't find a way to add that info. Editing metadata just gives me options to add GPS data and IPTC info. How do I put manual camera data into my files so that they report properly on Flickr? Helen Highwater fucked around with this message at 21:11 on Apr 22, 2016 |
#
¿
Apr 22, 2016 21:09
|
|
|
|
| # ¿ May 3, 2024 08:43 |
|
|
I found this when I searched but it only updates lenses. Bodies still won't be listed.
|
|
#
¿
Apr 22, 2016 21:46
|
|
|
Dehazing tool is pretty neat and that's only available in the subscription version. It even checks on launch - if you launch from the Lr shortcut, the dehaze tool is missing from the Develop tab but if you launch it from CC, then the tool is there.
|
|
#
¿
Aug 4, 2016 12:37
|
|
|
I use Lightroom on two different devices. Mostly on my Macbook at home, but also sometimes on my work PC. Is there a way to sync Flickr albums in the Publish service across different Lr clients? I sometimes edit photos on one machine that I want to publish to an album that was created on the other one and, as far as I can see, there's no way to force a sync of Flickr albums in Lightroom.
|
|
#
¿
Aug 10, 2016 13:01
|
|
|
Bloody Hedgehog posted:So is Photoshop/Lightroom/NIK good for subtle HDR? I don't need to bother with dedicated programs like Photomatix or Aurora? Yeah, Lightroom doesn't give you a lot of control over the composite but the default setting and slider options are very much on the subtle end of the scale. Photoshop's HDR Pro editor lets you push things a lot further if over-produced acid nightmares are your jam. I haven't used the NIK version but the sample image on the site is the sort of awful tone-mapped monstrosity that infests online photography groups.
|
|
#
¿
Aug 12, 2016 14:05
|
|
|
xzzy posted:I didn't think I'd use photoshop much, and then I got it along with the lightroom subscription, and now I tinker with stuff in it constantly. Before that I only had gimp which is definitely the most miserable image editing program ever devised by man. This was me, I only used Lightroom for ages and then I started shooting film in a big way and suddenly my workflow involves a lot of Photoshop. Instead of only busting it out once a month or so for the channel swapping or content-aware spot healing, I'm now using it daily. Then I got asked to do some video so I looked at adding Premier Pro and maybe After Effects but it worked out more expensive to add those two than to just sub to the full suite. So I did that and I'm never going to even install let alone use 80% of the apps but I pay for them anyway.
|
|
#
¿
Oct 20, 2016 21:46
|
|
|
Photoshop works with the original file without any Lightroom adjustments unless you open it in Photoshop as a smart object from Lightroom (or export it from Lightroom first then open the exported file of course).
|
|
#
¿
Feb 3, 2017 18:04
|
|
|
Here's how I do mine. I have one main catalogue. All of my pictures go in there because I don't want to gently caress about with separate catalogues if I can help it. When I import photos, I import them to a folder on an external drive that's named for the collection that the photos will be going into. I also use the option in the import dialogue to make a second copy of the photos to a folder on a different external drive (this second drive gets synced with cloud-based cold storage every few days). I will either add the photos to an existing collection or create a new collection as required. The collection and both folders where the photos are stored (main and backup) all have the same names, usually, this is the same name as the Flickr album that they are going to be uploaded to. By default, if you import photos to the same folder on different dates, each import will be in a subfolder labelled with the date of import. I leave that alone. Note that you can create the destination folders (both the main one and the backup) as well as the destination collection directly from the Import dialogue. Usually I have a separate Flickr album for each month with general walking about shots and separate albums for specific events or shoots. This makes it super easy to find originals for re-editing or re-exporting in the future. Other stuff I do in the import dialogue is add some tags for the camera and content, batch retitle if necessary and choose a medium contrast curve from the development settings. Here's a screenshot of my default import settings. These photos are going into my Kosice May 2017 collection which is also the title of this month's general purpose Flickr album.  Realise that the catalogue is not where your photos are. The catalogue is just a database of file locations and details of the edits that have been made to each image. Your catalogue and your images can be in completely different places. Helen Highwater fucked around with this message at 07:35 on May 13, 2017 |
|
#
¿
May 13, 2017 07:25
|
|
|
I haven't noticed that backups are more complex with different file and catalogue locations. Once a week, I get a reminder to back up my catalogue when I close Lr. I do that with the backup location set to the drive that's synced to cold-storage.
|
|
#
¿
May 13, 2017 16:49
|
|
|
No, they've shared their personal URL to the content which will only work if you are logged in to their account. They need to create a shared URL and post that instead.
|
|
#
¿
Jun 6, 2017 13:13
|
|
|
Does the 'Make a Second Copy To' dialogue in the import panel let you select your server? I have Lightroom import my pictures to my primary external drive (Thunderbolt) and make a second copy to a different external drive that gets regularly synced to online storage.
|
|
#
¿
Sep 13, 2017 17:41
|
|
|
According to that page, there are three packages (plus I guess the $60 'everything except Adobe Stock' package). $9.99 for Ps, Lr Classic, Lr CC and 20GB of cloud storage $9.99 for Lr CC and 1TB of cloud storage $19.99 for Ps, Lr Classic, Lr CC and 1TB of cloud storage. I don't see the value of the second one at all. You aren't just losing half of the functionality of Lr, you are losing all of Ps too.
|
|
#
¿
Oct 19, 2017 00:41
|
|
|
I was looking at downgrading my Adobe sub (I currently have the 'everything except Stock' plan), and it looks as though Adobe are making it super difficult to get the old Lr+Ps plan if you want Lightroom Classic rather than Lightroom CC. I don't want a TB of cloud data and I don't want to not have Ps either.
|
|
#
¿
Dec 9, 2017 01:38
|
|
|
Kilometers Davis posted:Has anyone done this? I’ve hung on but eh I don’t see the point. One of the cool and under-reported things about the Adobe sub is that you sometimes get invited to beta test new features. Right now for example, I'm in a test for the new Photoshop Cheese plugin. It's got all the usual options you'd expect for daily tasks - Cheddar, Mozzarella, Emmental, and then more esoteric selections for specialist stuff - thats when you'd go for something like Tilsit, Y Feny or Mongolian Mare Curds. The strength of the cheese directly relates to the power of the effect too so you get a much more visible result from, say Limburger, than from Gouda. For example, I was at a rodeo event a while ago and I had some nice pictures of horses but the backgrounds were too busy. I wanted to apply a gaussian blur to the background while leaving the horse nice and sharp. To cut the horse out, obviously I selected Mascarpone. Helen Highwater fucked around with this message at 10:55 on Dec 26, 2017 |
|
#
¿
Dec 25, 2017 10:30
|
|
|
If you have a bunch of photos that all need the same basic edits - applying a tone curve, white balance, split toning, etc - you can make those changes in one image, copy them and then paste them to all or some of the other images in your collection. It might be useful to make separate collections for all the photos in a particular location so that you can select and process them more easily. Anything beyond that - crops, exposure adjustment, healing and so on is likely to be per photo anyway and not something you can apply globally.
|
|
#
¿
Jan 2, 2018 16:20
|
|
|
You can also do it in the import dialogue (which is how I do it). Either to add the current import to an existing collection or to create a new collection with those images in it. Then, you can use the navigation pane on the left of the main interface (in any tab) to switch between collections - which you can then filter further with the filter tools in the bottom right. VV Edit: If the photos are already imported, you can right click on any selected set of photos and there's an Add to Target Collection option in the context menu. You set a target collection by right clicking on it in the navigation pane and your current target collection has a + sign after the name. Helen Highwater fucked around with this message at 22:15 on Jan 23, 2018 |
|
#
¿
Jan 23, 2018 22:05
|
|
|
Maybe I'm being dumb and I missed something, maybe I've picked up a random setting somewhere without realising it but, I've found a weird thing with Lightroom Classic since the update. Previously, if I edited an image from a collection in an external editor, the edited image would also be added to the same collection. Lr would create a stack with the original master image and the version output by the external program. If I go back to some older collections, I can see the original CR2 files from the camera import and the tiffs that Ps or ColorEfex or whatever spat out all sitting together in the collection. When I edited the last set, I opened quite a few of the images as smart objects in Ps. As expected, when I saved the image in Ps and came back to Lr, there was a stack with the original raw image and the Ps tiff. However, then I closed Lr and reopened it a bit later. Now I can see the externally edited tiffs in the actual folder where the original raws were, I can see them in the publish service (Flickr in this case), but if I go to the collection - either in the develop or the library modules, I can only see the raws (with Lr edits). I tried Googling this but I can't see any documentation about this change. Am I being a huge idiot? is this actually a thing?
|
|
#
¿
Jan 26, 2018 00:25
|
|
|
|
| # ¿ May 3, 2024 08:43 |
|
|
I just tested it again with a different (older) collection and it worked just fine so I guess that Lr had some weird issue when I closed it randomly. It's strange because after I spotted the issue with this most recent collection, I checked another collection that I'd done some external editing in since the split with Classic CC and the new Cloud CC thing, and that collection also didn't contain any of the externally edited tiffs. Other collections do however and so does the new one I made to test it. Adobe man...
|
|
#
¿
Jan 26, 2018 22:46
|
|