P: Ability to bulk - batch rename files

Apologies, I didn't realise, I have the Photography 1TB plan which includes Classic

This is a useful workaround, indeed. However, it is intended only for those who have Classic in their subscription. If you have opted for the CC - 1 TB subscription, you have only Lightroom CC and you can't use Classic to batch rename.

This is my workaround for this; When you import images into an album in LR CC a corresponding collection is automatically created in LR Classic (if you have Classic set up to sync) under 'From Lr mobile' You can rename your images there, either individually or as a batch and then the new filename(s) will appear in LR CC once they have been updated by the sync process. Hope this helps. (I have also voted for a proper renaming feature to be added to CC though - along with a bigger caption field) 

If you are doing this professionally, I would very strongly suggest you do NOT use Lightroom (the cloud version) but you should use Classic. Lightroom Cloud is not able to export files than anything but sRGB jpegs, cannot do any custom naming as you discovered, can't do any real metadata editing, and misses almost every feature you need. The target audience of the Lightroom Cloud is people who only live on the net and don't really share images in any real volume. If you do want to continue doing Lightroom Cloud, you should look into a file renaming utility. There are many of those around that allow you to quickly rename a whole folder of images. That is probably the simplest solution. Lightroom Classic of course does all this natively.

Lightroom CC is what I am using. They need to add bulk naming to it. It looks unprofessional to give my clients dorky camera given names. Come on Adobe, get on this!!!

If you come from Aperture, make sure you look at the right Lightroom. Lightroom CC (now called just Lightroom) is not what you want but Lightroom Classic is. It does the renaming of files, it does slideshows with music, it can actually print, it can export to more than sRGB jpegs, it does smart collections, unlimited searches, it can do keywording using hierarchical keywords, virtual copies etc, etc. Lightroom CC (I.e. the cloud version) does none of these things. The cloud Lightroom is only useful if you do nothing with your files and want all your images available everywhere and look the same and rarely share or export images.

Hi Dan,

I have been enjoying Aperture for many years like you. However there is this inevitable moment one has to make the switch. You will keep struggling with limitations more and more: you cannot run macOS Mojave and the next OS is already announced. It is not only Bridge that may cause issues, but you receive no updates for Apple Photos, iTunes and other programs any longer. The longer you wait, the more you cut yourself out. And do not forget, the longer you keep Aperture, the more photos from the past you will not be able to revert from the non destructive changes, like your recent wedding pictures. They will turn into permanent changed pictures after exporting.

I have been comparing different types of software and they all have their issues: no good photo managing capabilities, bad browsing performance, missing features. There is no perfect tool. Lightroom CC is the closest to what Aperture offered.

Sure, I still miss the nice slideshows with music integration I could create before; the smart albums; batch renaming; unlimited search filters. But you will have new features as well with Lightroom and it is catching up on those items with regular updates.

The features that are not supported by Aperture are: synchronisation and an App for an iPad or iPhone. With Lr there is no need to save the full picture on you hard drive -(hence you do not need so much disk space any more). Automatic backup of your photos. Aperture does not support new camera RAW (By the way, RAW will increase your adjustment options tremendously!). The Lr texture, clarity and sharpening tools are really good. Aperture does not have a healing tool. The Lr User interface is easy and clean, simpler than Aperture.

I would consider to give Aperture up. I did it a year ago when I could still run both Aperture and Lr in parallel. Unfortunately you do not have that option any longer. What else will happen when you keep waiting?

Best regards
Hans

I'm gonna go ahead and bump this thread as some may appreciate this story.

I just ran into the same issue for the first time. I'm on a 2013 MBP which still works literally just fine (knock on wood), and recently transitioned over to LRCC because I'd been on Aperture for ages, and figured it was time since it's been a full five years since they discontinued it.

I shot a wedding on two cameras; normally I shoot on one, but my shutter actually broke about 60 seconds before the bride and groom kissed, and so I was forced to grab my second body. And yes, as it turns out, I'm about to turn these photos over, and boy is this file naming getting in my mf way.

I'm still running OS X High Sierra because I want to make sure I can still access my old Aperture libraries, and because I don't give a flying fiddlestick about having "Dark Mode". I discover this thread of tired, poor, huddled photographers who are just trying to delight people in a simple, reasonable way, and I see Bridge as a workaround. Cool, Install Bridge. Oh wait, it crashes instantly on this version of OS X. Just like Lightroom Classic CC (which is why I don't use it).

And so in an act of heroic courage, I put the keys in the dusty ignition of Aperture 3.6, she shudders to life immediately like always, and I import my terrible unalterably-named jpgs that already exported from Lightroom, turn them right back around, and re-export them from Aperture, with perfect, sparkling filenames.

Pour one out for Aperture, with its perfect simple UI, keyboard shortcuts, support for multiple libraries, and yes, custom file naming ability.

I couldn't agree more

I suspect that, besides prioritization decisions, the roadblock is compatibility with sync in Classic. If someone renamed their photos in the CC cloud, and were still syncing with a Classic catalog too, Classic could run into trouble. The Classic files could be offline, preventing them from being renamed. Just a suspicion...