Reviews

Adobe’s many-tentacled grip on its users

I’ve been using Photoshop since the late 1990s and Lightroom since its launch in 2007. I’ve been a user of Adobe software for some time, and have owned various software packages from them since that time. But in recent years, I’ve begun to be repulsed more and more by their greedy grip on their users. Their move to subscription-based software was the beginning of my discontent, which was only furthered by their constant attempts to constantly monitor what we do with their software and how we use our computers. I know of no other software company that does this so much, and I find it despicable. I think what they’re doing is a clear invasion of user privacy. Some might say it’s benign, that they’re only trying to keep track of their software licenses, but when you find out that they make most of their money with a suite of services they call Experience Cloud, where they offer “AI-driven solutions for marketing, analytics, advertising and e-commerce”, you get the sense that we’re the guinea pigs for their solutions, and their many “helper” applications that are supposed to only monitor software licenses are likely doing a lot more than that on our computers.

I am also a Mac owner, and in stark contrast to Apple’s constant marketing-speak about user privacy, they never mention Adobe’s many applications that are constantly talking back to the Adobe servers, and they never go into the details of what the many Adobe helper applications actually do on our computers.

At best, the many “helper” applications that get put onto your computer when you install Adobe software can be called sloppy programming, and at worst, you have to wonder exactly what they’re doing with each and every one of those pieces of software under the guise of “keeping Adobe applications up-to-date” and “verifying the status of your Adobe licenses”. Most people probably assume those apps are the various components of the Creative Cloud suite and even though they’re numerous and they can probably tell those apps are in constant communication with Adobe, they choose to tolerate them.

I know things may be different on Windows, where software gets installed in multiple places, but on Macs, applications are and have always been packaged into single files that contain all that a piece of software needs in order to work. Even Microsoft Office on the Mac functioned this way and only used one additional piece of auto-update software to make sure everything stayed that way, and after it moved to the App Store, even that went away. They let Apple handle all their updates now.

Not so with Adobe… They have to be “special”. They have to stick their tentacles everywhere on your computer, doing and monitoring who knows what. I absolutely hate the fact that their Creative Cloud software has to run all the time and talk to their servers all the time, just so I can use their software occasionally. I find it abusive and overreaching and questionable, but for some reason, we’ve chosen to go along with it because we want to use the software.

Have a look at what gets installed with their Photography Plan, where only two apps should be present.

You of course will get Creative Cloud, even if you don’t want it, with its many little apps that invade your computer. Then you get Adobe Lightroom CC, the app that hardcore Lightroom users never asked for and don’t want, because all we really want is Lightroom Classic. You then also get Photoshop, which I might use to create a logo once or twice a year, and I infrequently use to blend different frames together into a single photograph (for focus stacking). If that functionality were offered in Lightroom, I’d barely need to open Photoshop. It’s overkill for me.

Let’s see what we get with Creative Cloud, because that’s the crux of this post. Most people won’t realize that the little red folder called Creative Cloud in the Applications folder isn’t really the whole of it. No, Adobe also puts a lot of helper apps in your Utilities folder.

Whether you want them or not, you get Adobe Application Manager, a second Adobe Creative Cloud folder, Adobe Creative Cloud Experience, Adobe Installers and Adobe Sync. Let’s have a look at each of them.

Look at all the “goodies” you get in the Application Manager folder. Yuuuummmy… I didn’t effing ask for all this, Adobe!

Let’s see what else we get. We get more stuff we never asked for in the Creative Cloud folder.

We also get to be part of a Creative Cloud Experience that we never opted into.

We also get the uninstallers. Fine, okay… although on the Mac, we should simply be able to drag an app from the Applications folder into the Trash (sorry, the Bin) and “bin” done with it.

We also get Adobe Sync, which is another application/service I don’t want and didn’t ask for. Never mind that sometimes it’s stuck on syncing a few photos for weeks on end. I guess it’s thrown in as padding to justify the cost of the subscription plans. “Look, you’re getting the good software, and you’re also getting storage space and a website”… I didn’t ask for it. I just want Lightroom and nothing else!

By now you might think we’re done, but no, you also get a special plugin that monitors your online activity, um, “detects whether you have Adobe Application Manager installed. I bet you didn’t know about this little goody from Adobe, did you? It’s called the AdobeAAMDetect.plugin.

Ostensibly, it’s used to detect whether the Adobe Application Manager is installed onto your computer, but who knows what else it does without looking at its code? All I know is that when I go to my Safari plugins, it’s not openly and transparently listed there. No, it’s hiding in the /Library/Internet Plug-ins/ folder, so you have to know where to look in order to find it. Why? And what else is it doing? Is it monitoring my online activity, just like the apps installed on my computer are monitoring my application usage and who knows what else?

I find all this deeply disgusting, and without opening up each of those apps that Adobe sticks on our computers and looking at the code, we won’t know what they really do. If I didn’t like Lightroom so much, I’d switch to another piece of software in an instant. But I have yet to find a single piece of software that:

  1. Doesn’t have a subscription plan,
  2. Lets me easily edit my photos and, this next one is really important to me,
  3. Lets me easily edit the metadata across all of my photos and update it as needed, and finally,
  4. Lets me import my catalog from Lightroom while keeping my collections, smart collections and collection sets intact, so I don’t have to sort through hundreds of thousands of photos manually.

After 13 years of using Lightroom, the interface is very familiar. I know exactly where to find what I need, but I sure find Adobe’s business practices despicable and would gladly switch to something else. As far as I’m concerned, they’ve stepped over the line long ago and have been invading the privacy of their users intentionally for years.

Standard
Places

At the office

Here are a few photos of objects around my office, taken a few years ago. One of the photos has the exact date and time when it was taken written on it, but not in the typical way, where the camera imprints the text in the corner. I’ll let you see it for yourselves. Enjoy!

See the ColdFusion handbook in this photo? ColdFusion (by itself, without the Java layer recently shoehorned into it by Adobe) was and is the best programming language. It’s so high-level that a few lines of code can do what would otherwise take pages of low-level code in other languages. I find that very elegant.

Standard
Thoughts

Four wishes for Lightroom

It’s 2011, a new year, and it’s likely that Adobe will put out a new version of Lightroom this year. With that in mind, it would be wonderful if the Lightroom team could implement the following features in the next minor or major version of LR:

  • Find and Replace within metadata (details here)
  • Faster navigation and rendering when working with large catalogs (details here)
  • Filter catalog for metadata conflicts (details here)
  • More accurate time of capture for movie files captured with an iPhone 4 or a Nokia N95, or other video camera that doesn’t supply sidecar THM files (detailed explanation here and bug report here)

Thanks!

Standard
Reviews

Time of capture metadata bug in iPhone 4 movie clips

Updated 9/12/10: I’m not sure any more if this is an iPhone 4 glitch or an Adobe Lightroom 3.2 bug. A thread has been opened in the Adobe Lightroom Forum, if you’d like to chime in there.

After upgrading the iPhone with iOS 4.1, I recorded a new video clip, imported it and some new photos into Lightroom, and the same wrong date and time appear for it.

According to a comment on my thread in the Apple Support Forums, the correct time of capture is displayed for iPhone 4 video clips elsewhere but Lightroom. And I also noticed that Lightroom displays the very same incorrect date and time of capture for video clips taken with the Nokia N95.

Updated 9/27/10: I’ve been in touch with Adobe, and it turns out this is a “designed” behavior. That is, because movie clips do not have EXIF data (there is no standard for EXIF data when it comes to them), they are assigned a random date and time as they’re imported into Lightroom. HDSLR video files are accompanied by a .THM file which stores the necessary EXIF data, and that’s why they show up properly.

Quoting from Davide M.’s (Adobe) response:

So I then had a look at our bug database and it turns our this is a known issue with mobile phones although somewhat out-with our control. Movie files do not technically have EXIF data or at least the standard has not yet been established. Since the import process can assign a timestamp to a movie file, we ignore this time stamp since it can be inaccurate, as shown by the example of your video file being changed by the simple process of email. Other applications while appearing to work fine, in fact are simply showing you the files creation date. If you were to duplicate the file, you will see that the timestamp in these other applications will change to the time the file duplication took place.

The reason why most DSLRs work is because they create a sidecar file containing that information. Files with no timestamp, such as the ones from the iPhone and the Nokia N95 do not create this and hence default to 1/1/04 when looking at the Loupe information overlay.

In the example you used, the Canon 7D creates a .THM sidecar file with the same name as the video file it generates. This contains all the data associated with the video file.

Still, this is problematic behavior, as it introduces erroneous times of capture in these movie files. So I asked Davide if it would be possible for Lightroom to be updated so that it writes a more accurate time of capture for these movie files. Thankfully, he agreed to log it as a feature request. Time will tell if this will make it into a future LR update. Quoting him below:

That’s certainly something I can log in our feature request list. Because this has been deemed ‘as designed’ by our engineering team (due to the lack of EXIF data in movie files) it is not technically a bug. None the less, I can see that this would be a useful addition to our application. Thanks for bringing this to our attention.

Thank you, Davide!

After downloading a few movie clips taken with an iPhone 4 (running iOS 4.0.1) onto my computer, I saw right away that their time of capture was incorrect, even though the iPhone’s time had been set up correctly. I took a few screenshots of the movie clips in Lightroom, which you can see below. Click on each to view them large.

This time metadata error happens when using either the main (back-facing) HD video camera, as shown above, or the front-facing VGA camera, as you can see from the screenshot below.

It looks like iPhone 4 records the same time for all video clips recorded with it, set at 1/1/04 1:44:24 AM.

It goes without saying that any digital video camera worth its salt will record the time of capture properly. The question, naturally, is when Apple will fix this glaring bug?

For comparison purposes, here is a screenshot of a Canon 7D movie clip, also shown in Lightroom. The time of capture was recorded properly, as was to be expected.

Standard
Thoughts

Where’s the SmugMug Publish Service for Lightroom?

I love the Flickr Publish Service in Lightroom 3, and would love to see SmugMug make their own.

The only thing missing for the Flickr service is for it to know which photos I’ve exported and uploaded to Flickr before the service became available, in previous versions of Lightroom. I for example have either tagged the photos uploaded to Flickr with, obviously enough, “Flickr”, or have added them to a Flickr collection in Lightroom, so I could easily find them.

Here’s where SmugMug has the chance to shine! I’d love to be able to publish my photos to SmugMug directly from Lightroom, using the Publish Services functionality, so I could always sync up any photos that I’ve re-developed or where I’ve updated the metadata. But for this service to really stand out, it needs to know which photos I’ve already uploaded.

You can see where this is going, right? I’ve already tagged all my SmugMug photos, and have already placed them in collection sets and collections that match my SmugMug categories breakdown exactly. With a little bit of computing power and some smart algorithms, the folks at SmugMug could put together a killer Publish Service for Lightroom that incorporates all the Flickr functionality and bests it by matching my already-uploaded photos.

What about the cost? The Flickr Publish Service is free to use for all Flickr users, but you cannot re-publish uploaded photos if you’ve changed them in Lightroom. (You can, but if you’re not a Pro, it’ll wipe out any comments and faves on the photo, so it’s not advisable.)

SmugMug could use a similar approach. Their Publish Service could be free for basic SmugMug users, with limited functionality, and it could offer full functionality to Power and Pro users. (I myself have the Pro membership.) I’d even be willing to pay a one-time fee to download and install the service, because I think the functionality would be amazing.

Standard