Is It Worth It? Switching From Adobe Lightroom Classic To Lightroom CC

[@brianmatiash]

Have you really looked into what's involved with moving over to Adobe Lightroom CC? There are a lot of preconceived notions out there and I hope this video helps answer your biggest questions.

[@LeroyJavois]

Helpful? That is an understatement! This is the most in-depth video/tutorial on how to switch/migrate on the web to date. Thank you so much for taking the time out to put this together. Adobe should pay you for this. LOL! This really put things in perspective for me. I have my own pros and cons to weigh, but after viewing this, it certainly answers A LOT of questions. Thanks again, Brian, and stay well. ~Lee

[@brianmatiash]

As always, you rock, my friend. I'm stoked that you found the video helpful. I'd also be interested to hear what your pros and cons are.

[@LeroyJavois]

Brian Matiash I'll be glad to share them with you. I'll do so in a separate forum. Thanks my man 👊🏾

[@dennisaustin4268]

This video is a classic. There is so much information I’ve watched it three times. But now it is almost a year later. How about an update? Are you happy with your migration? Your latest video is about ON1. Thinking about alternatives?

[@klledbetter]

Fantastic video! You have helped me to finally decide to migrate from Classic to CC. I love the way you created Albums by years - great idea!

[@CarlLeck]

Thanks Brian for the tutorial. It was very helpful. I really like the concept of uploading photos during trips to the cloud via a phone or tablet. I did upgrade to 1 TB with Adobe but that won't hold my entire catalog of photos. I had in mind to use CC for maybe a rolling year's worth of photos and then move photos off to a local storage (CC classic?) when they age (since I don't do a lot of editing on older photos). Is there anyway to go the other direction going from CC to Classic CC? If not, is there a way to move photos to an offline state so they are not in the cloud? This probably goes against Adobe's goal and I understand that not your strategy but somehow I need to stay within an affordable monthly cost as an amateur. Any advise you have would be appreciated.

[@thomasopiolka8849]

now I can make an informed decision. Thanks for that. Great video and well researched

[@HelenBradley]

Cheers Brian! Helped clarify a few things.

[@VijaykSaha]

Thank you so much for this review!! This has helped tremendously!

[@simonhargreavesphoto]

Great video, many thanks for making it easy to understand, have been considering a solution for back up for a while, but this solves both editing and storage issues. Will definitely give it a try. 😊

[@ronald7482]

Many thanks for this great video I keep my classic because of the handy features

[@AdamRoyer]

I don’t want to (and I won’t) pay Adobe any more money, and cloud storage (or it’s related benefits) is of no interest to me (yet, at least). I’m bummed, however, that Adobe probably won’t improve Classic’s UI (I really like the look of CC’s UI). I’m also going to miss watching your tutorials using the same software that I use. I really hope Adobe offers the use of CC without requiring the use of their cloud services/pricing. Thanks, as always, Brian!

[@dougoh6749]

Great information. I’ll pass on migrating at this time, but maybe will later. Thanks for explaining the pros and cons.

[@WepaPix]

Loved the video! Keep asking Adobe questions!! We surely want answers! Even to questions we don't know we have lol. I will keep watching. I think it's great that we make these videos and help out the community. There is a lot of information regarding lightroom cc that needs to be addressed, regarding workflow and behavior and how the thinking paradigm has changed. I think a good video is explaining how to control what exactly is uploaded to the cloud. I feel like right now everything is really pushed to the cloud. How can we control that? I love this cloud concept but 10TB can get expensive. What if I only really need to sync a few current projects, maybe only the last year's worth and keep the rest on the local NAS storage with perhaps your own managed backup instead of keeping it in the cloud.

[@paulwalker2133]

Thanks Brian, this is an incredibly helpful and balanced analysis of a very complex subject. I really appreciate your guidance and candour.

[@cameraman655]

Indeed, I have been an Adobe user since the mid-90s and despite a few issues, I see no reason to go elsewhere...for now. That said your final points on the Pros and Cons were of great interest to me. The big PRO is the ability to shoot, edit, upload and tweak (at home if need be) from any device from anywhere (depending on internet connection) in the world. I have been traveling with my iPad Pro (12.9) as my sole editing device for over a year and it is (or was) a major hurdle, with the introduction of LRCC late last year, has definitely been a major positive for my workflow, while on the road. Lightroom Mobile was good for what it was, but CC for all of its shortcomings has been a Godsend. The CONs, well, the missing Spot/Healing tool is one that I use to remove objects and the occasional dust spot. It is very annoying to have to send the photo to PS Express or another editor to remove a spot or any object for that matter, it breaks up the workflow. As a side note, frankly, I am finding that Pixelmator's clone/healing tool is far more effective than PS Express's, Adobe might want to do a possible redesign of this tool. As you touched on, additional tools like HDR/Pano, Multi Image editing, 3rd Party support, etc...I use these quite often as well. Still, if Adobe fully develops LRCC into a "full" scale desktop type editor (hopefully PS one day), well, the sky is the limit. However, with Serif's Affinity Photo and rumored DAM editor, as well as Pixelmator Pro, promising an iOS version, Adobe really needs to step it up. Mobile editing is the future. As I mentioned earlier I was an early adopter of PS and I am willing to tough it out for a while, but if Adobe drags their feet on further development or LRCC, and others come along with fully functional editors, I might have to consider defecting.

[@brianmatiash]

I totally empathize with the lack of spot healing/cloning on mobile. I was just editing a photo a few min ago on my iPhone and had to switch over to my Mac to heal some defects. Fortunately, I was able to get the stylization done to completion and have it waiting for me on my desktop, so that was nice. Competition is a wonderful thing and while some of these other companies don't have the war chest that Adobe does, it will spur the need to keep improving. After all, that was Adobe's key selling point with moving to a subscription model: it would allow them to release more frequent updates with agility. They've done an ok job with that to date and I'm hoping to see that trend continue. I know that a big focus of theirs has been speed and performance, especially with LR Classic.

[@cernugaming]

@@brianmatiash I am new to photography and saw this post is over a year old. Did Adobe fix these issues you guys were talking about? I just want to know if i should commit/learn adobes programs or go an alternative path.

[@tomdearie5165]

Thanks for this fairly thorough video, Brian. Much appreciated. It raises multiple serious questions for us that perhaps you can answer. - We will only ever want a small subset of our images in the cloud, for multiple practical and legal reasons. Can we easily and selectively turn cloud syncing on/off for images and and only have a small, select subset on the cloud? All cloud-all-the-time is an impractical and overly rudimentary model for us (and many professional shops). We need more control than that. (That would be true even if Adobe’s cloud storage pricing wasn’t 10x our current cost/TB.) - Just to clarify - it looks like you went through a pretty long process to migrate. Can we expect that, after choosing a few criteria in migration controls, we can simply click one button to migrate our entire catalogue and have it faithfully port to Lightroom cloud with its internal structure completely preserved? - It looks like you said we can’t control the folder hierarchy in the catalogue. Is that correct? If so, what method is available to ensure our library organization survives if we move to a different catalogue solution? Best practice requires that we have complete control over the organizational structure of the catalogue and that it’s portable and can be moved outside of the proprietary ecosystem. Cheers and thanks

[@geoffreyturner4912]

Good video. Convinced me to stay with Classic and buy another external hard drive for back up. Online storage is too expensive, and there are not enough positives for me.

[@RoderickKhan]

Copying and pasting of edit settings in Lightroom CC is available now.

[@BommeltjeNL]

I only recently took a subscription to Lightroom Mobile with 100 GB for 4,58 euros/month and it's one of the best things I did this year. I had photos on my old Windows and Mac computers, on my iPads, on my iPhone and 2 older iPhones, on a bunch of memory cards and on a few drives. I had all my photos, but I could never show them nor could I ever find them when I needed them 😂 Now I have everything in Lightroom Mobile on my iPhone, my iPad and online. Normally I hate subscriptions and everything above 5 dollar/euro gets my no-no, but this is worth each and every cent. I do not understand why there's no LIghtroom Mobile app for Macbooks. You need to buy the expensive subscription for desktop PC and laptops and the edits are not better than mine on my iPhone or iPad. My brother would've got the same subscription if it was available on his Macbook, but he only could do the very expensive subscriptions and he said no-no to those.

[@PhilippUnterreiner]

15:11 One more thing to consider: To this date LR CC doesn't store XMP files together with originals in this local backup. This means it's a backup of your originals, but not of your edits. The only way around this I see currently is going for a full DNG workflow (since edits are stored inside DNG). You could still on the other hand manually export "originals + settings" from the menu, but this kind of defeats the purpose of an automatic backup.

[@Audiotechnical]

Absolutely fantastic video! Thanks so much for providing some really valuable info, exactly what I was looking for. I've got the challenge now of 'cleaning up' my Classic Catalogue as I have soooooo many shots that I just dont need (test shots, portraits where speedlight didn't go off, out of focus etc etc). One really important part of my workflow is the 'export process'. I have some custom presets which export certain crops at a certain size (long edge) and custom renaming to include certain words (including Keywords) that an external server picks up on from an Adobe CC shared folder. I see this could be an issue for me. However, this maybe something Adobe will develop in the future? I'll defo be back. New sub here!

[@mjstowe1]

Nice comparison. Just what I was looking for since I am torn. I do not print a lot but wanted to print more. The lack of a print module amazes me (as it does others). I get it is 2019, but many still like to print. Unfortunately Photos, Preview etc do not work well with ICC profiles and the prints are hit and miss. Still...I do like the ease of use CC offers over classic. Also, it is 2019 and they have add a few more items that were missing with the exception of the print module. I do not need a ton of storage at this time so the 1TB option would suffice, but I would need to carry Photoshop or Classic as well for printing purposes.

[@dhedc]

Very helpful video. I’m currently happy with Apple Photos and third party apps like Puxekn

[@stephenscharf6293]

Hi Brian, thank you very much for putting this up. I'm in the process of evaluating Lightroom CC and this video was very, very helpful for providing context for use-cases as well as practical examples. One question for you: if you move to Lightroom CC, can you still use LIghtroom Classic? I shoot (like Nicolesy) with the Fuji X system, and really rely on being able to use 3rd party plug-ins within Lightroom Classic like Iridient Developer and Luminar. Thanks again and cheers, Stephen Scharf, Racing The Light Photography.

[@BradleySkaggsNYC]

Great review. You've answered a lot of questions I had. I'm migrating.

[@fusionoievent]

Great job! Very helpful, thanks

[@johngriffin5996]

Brian, thank you for the very useful video. For me, it doesn't make sense to take to the Adobe Cloud right now. I'm a hobbyist, stay close to home, and when it comes to my computers, smart phone, and tablet, I don't drink the Apple juice. The new Lightroom CC lacks features which are major parts of my own personal post processing workflow. I use Canon crop sensor DSLRs and shoot RAW format files. My smart phone and tablet are both older and Android. Your video confirms to me that I should stay with Lightroom CC Classic for now and wait for the new version to get more Classic features added before I consider dipping a toe in the Lightroom new-fangled CC version. I will check your KZbin channel, emails, and website/blog for updates. Eventually I probably will give the new version a try when I think it's ready for me.

[@spearfish25]

Thanks for doing this. You oultlined about a dozen reasons why I'd be very sorry for having swapped over from Lightroom Classic.

[@spencer6194]

What're you doing about PRINTING since you've migrated over?

[@DamienJemison]

Hey Brian! Long time, first time. Glad to see things going well for you in the Pacific Northwest. I found this video after being frustrated for the umpteenth time, trying to get photos from my laptop to my desktop, with edits. I'm glad to see I'm not the only one who was frustrated with this process of merging edits between two catalogs. This video helps me move one step closer to using Lightroom CC in 2019, except... 20GB starter plan or even 1TB will not last me more than a couple shoots, so its almost a non-starter from the jump for me. You have your CC catalog setup to copy originals to your Raid drive at home, but that doesn't mean they aren't still sitting in the Adobe cloud taking up space, correct? Something needs to get better with the storage options/pricing before I would ever consider uploading all my originals to their cloud. Are there any features that Adobe has added since you created this video that will help make the decision to switch easier? Are you still using this workflow moving forward into 2019? (You may have answered this in the comments below, thanks) I'm really preparing for the iPad Pro workflow later this year once Adobe drops Photoshop for the iPad. I'll probably give CC a try for the new year, and see how it goes. BUT... big BUT. I'll also keep my Classic catalog up-to-date and hope Adobe gives us a way to export our edits off of their server/CC catalogs and onto my hard drives/Classic catalog.

[@dcraigyoung2305]

Thanks Brian, I appreciate the thorough workflow overview. Wish I would have had this to review prior to my migration, but it wasn't too difficult. Looking forward to greater feature parity, as I continue weigh the pros/cons. Softball question: How do you set the view to keep the My Photos/Albums column open, say, when you hit the Info shortcut or icon, etc.?? It seems you have your workspace set that way. Thanks again, keep going...

[@davosuzuki]

I would love to use some of the pros of Lightroom CC, but as a user of Lightroom and Photoshop since day one, and a pro shooting anything up to 2,000 RAW files 5 days a week, and these days using 45 megapixel cameras…the internet just isn’t anywhere up to scratch here in regional Australia. Migration of existing files is not an option, and uploading of files as I shoot them isn’t either. The cost is just massive to get enough cloud storage from Adobe.Also, I shoot a lot of 5 image bracket sets, and Lightroom Classic CC has the stacking feature, but CC doesn’t. It’s really frustrating seeing the really tempting advantages of being able to access files from anywhere, and work on them with any device, but the system just isn’t there as yet. Unless I’m missing something??

[@jeepdelfuego8366]

It is so hard to find any info on the new Lightroom CC. I had just mastered Photoshop CC last October when Adobe launched the new Lightroom CC. I tried it and liked it from the start. I tried the old Lightroom CC and thought it was too busy and had a hard to understand catalog filing system. I found it to be not intuitive at all. Now that I am comfortable using the new Lightroom CC, I have found that I miss a few, what I think are important, features like red-eye removal, panorama stitching, and a better clone/healing tool. This has made me consider using Lightroom Classic alongside Lightroom CC. I am still debating this and not sure whether to take the plunge. Your video is the best one I have come across since Lightroom CC came out.

[@teleguy5699]

Hopefully, we are on the ground floor of Adobe making this an outstanding new editing program.

[@dookieducay]

my question os how can I sync my presets from cc to classic? also how can i stop synching photos from cloud to classic because i dont want it stored on my mac

[@markandannette]

This was and is very helpful and I am glad to see that the current version of Lightroom CC addressed some of the issues you brought up. I do have a general question though, is it worth having a 3rd party software like Luminar? Lightroom CC can perform the develop tasks that Luminar can correct?

[@EasyBillingInc]

Would you now, not use Lightroom CC (is it called CC now in 2020?) only or will you still use Lightroom Classic as well. Thank you, was a great video.

[@PhilippUnterreiner]

Thank you, super helpful!

[@JonPYbanez]

as an owner of vintage lenses, not being able to use LensTagger in Lr CC means i can't manually set lens info for pictures using those lenses. i do, however, use Lr CC on my aging MacBook Pro and will agree that performance is better than Lr Classic on that machine. eventually, i would like to switch to Lr CC for the cloud benefits but will hold off until it becomes a full Lr Classic replacement

[@nansilent5670]

If you migrate do you lose what was originally organized in Lightroom Classic?

[@dellbridge1]

Thanks for this video. I have not started the migration yet, but this looks like a clear set of instructions to follow. Can I ask a couple of questions? I currently have my photos on a separate drive J:. I plan to set the preference 'Store a copy of all originals in this location', and specify a folder in J. Does the migration make a new copy of the files? Also, what happens if I change the location (or turn it off or back on again) after I have been using Lr CC for some time?

[@markandannette]

This was so helpful for me and I truly appreciate you taking the time to share this, this confirmed my decision to use Lightroom CC the only thing I wish that Adobe would do is integrate 3rd party apps like Luminar 4 do you know if this is coming in the near future. Also on last question, do you have further training videos on Lightroom CC?

[@TheAtaja]

Great video Brian. In short, is Lightroom CC a scaled down version of Lightroom Classic?

[@emilyratcliff7725]

Can you touch on how to permanently change your profile setting? It’s only on my desktop and not my phone app, But every time I’m getting ready to edit the picture it shows up with an orange tint. My originals straight out of the camera show up fine below until i click on them and then they turn redish. I’m not sure what’s happening

[@Graphicshiv]

Great video helped a lot. Questions I have though: 1, Can I use an external editor like affinity photo and DXO Viewpoint 3? I would like to export the tiff file to the mentioned software make changes and then save file back to light-room. You mentioned this was not available but I am hoping 8 months on this might be integrated by now. 2, Do local files save the edits made once deleted off of cloud. e.g. if I upload all my images and work on them in the cloud and once I have finished with the collection and no longer need active use of it. I can delete the cloud version and keep it locally along with the edits? This would at least alleviate the storage issue. 3, Can I take the photo from cloud and make edits on the ipad version of Affinity photo and save back directly to Lightroom CC Thanks in advance :)

[@AdamHawra]

Hi Brian, thanks for this- I've found your video incredibly useful. I know I'm commenting on a video that's almost a year old(!) but I'm wondering if you've got any thoughts on this setup? Whilst I'm still trying out Lightroom CC, I'm doing what Adobe has recommended and have synced photos across by duplicating folders as collections within Classic and checked the 'Sync with Lightroom CC' option. But I kept on going, and going until I'd done this across my entire master catalog. So far this has given me the benefits of local storage (with my originals stored just how I like them) with the ability to edit all of my photos on any device through Lightroom CC. Of course the downside to this is that if anything ever happened to my originals, they'd disappear from Lightroom CC. This also doesn't seem to be using up any cloud storage. I'd really value your opinion on this - is it a valid workflow? Or am I just kidding myself? Even with backups I'm getting twitchy that the photos aren't truly stored on the cloud. Yet I use Apple Photos with my iPhone without a second's hesitation.

[@veliagonick8781]

very, very helpful--I will stick to Lightroom classic.

[@paulwalker2133]

Just one tip - you could have opened 'recent catalog' when you're having to open the newly created catalog (to save you hunting through the Finder)

[@brianmatiash]

I'll have to check again because I seem to remember those newly exported Collection Catalogs not showing up in Recent until after you manually open them.

[@adrian-alexandruneculcea206]

Hi! 2 years later I am dealing with this dilemma. Seeing this process convinced me that Lr, and by that Adobe it is not the way. The storage cost it's absurd, and the ease of use is not there. I will keep using Lightroom Classic until a better "digital asset manager" (I think that is what it's called) to arrange and sort my photos (and edit them) but I will NOT storage them on adobe shiny golden servers. I will prefer to use Dropbox and/or Google for 12$ a month each, for unlimited storage, and the ability to have control over the folder structure and storage location. Plus, files synced from Classic appear as smart previews in CC (Mobile). Good enough for a fast export with no storage requirement. Adobe is way too greedy.

[@mulletATheart]

There is a better workflow for plugins. Use Photoshop as the middle man. Edit in Photoshop. Most (if not all) of your LR plugins can also be installed in Photoshop. From Photoshop, send it to the plugin. It feels like a waste at first, until you realize you can choose to save each plugin's touches on their own layers, making it a little less destructive.

[@florintudorphotographer]

Grate tutorial Brian ;) Do you by any chance know a way to synchronize the raw photos from one user to another, let’s say from a photographer to a photo editor, but without having to sign out from an account just so that your editor can log himself in and edit the photos? Thanks in advance, Tudor.

[@CompleteMisc]

I am contemplating migrating my entire Lightroom catalog to Lightroom CC. I have watched a number of videos on the migration and think I have a good handle on how to make it work the best. The question I have yet to see anyone answer is this: Once I migrate my catalog, what happens if I want to edit a photo back in Lightroom Classic to take advantage of features not yet available in Lightroom CC? Do I open my old Lightroom catalog in Classic? Are the files found in some other catalog? How does the syncing work in this scenario?

[@danielreim]

Coooooooool! Working stable

[@blickfangQ2]

Thank you, that was really helpful! How do you manage double image names? Like IMG_1990 from last year and now I want to add IMG_1990 from this year because my new phone starts to count at 0001... without renaming on import, this makes me nervous...

[@rimileitao]

Thanks for the clear tutorial. But it makes no sense that these import features are not hard coded into the application itself. Why do we need to import small batches at a time? Adobe could simply give is the granularity as to when would the photos be imported to the cloud (such as limit #GB per week/month). In addition, turning folders into collections in L Classic is just plain nightmare. It should be as easy as drag a parent folder to the collection pane. Or, even better, why there is no option to convert folders into collections during import into LCC? In sum, Adobe keeps missing on key features to make their apps usable. Thank you for your efforts anyway.

[@shailabshrestha8026]

how do we put watermarks using new lightroom cc ?????

[@dyingshadow6425]

Fantastic video. However, nearly one year later and CC still has the feature shortcomings listed. Seems that Adobe has no intention of making this a powerful solution.

[@lewrumford4467]

Thanks! Very helpful! Here is my question: After migrating to CC, should one continue to sync between Classic and CC? Said differently, if one wants to take advantage of some Classic capabilities not yet in CC, do you (A) use the Classic sync function or (B) just treat Classic as a stand-alone editor like On1 by exporting from CC then working in the stand-alone editor, and then re-importing to CC. Adobe seems very unclear on the relationship between CC and Classic after migration. It sounds like bad things might happen in A as well as wasting disk space with duplication of saved smart images in Classic and CC, but I have seen no prohibitions by Adobe and the sync function appears to stay "on" by default. Thanks again!

[@inabechhoefer807]

I have this question, too!

[@NotDoneB4]

Lots of problems with this - unless they do a lot of work I think this experiment will fail. Collection problems - as you import each year it produces it's own set of albums (collections in LR Classic CC) so you end up with separate Albums for each year instead of one Album spanning many years. Export (sharing) problems - you can't change some settings like sRGB to aRGB - at least not that I could find. Also each device iMac - iPad - Android seem to have their own ways of sharing. For instance on my iPad Pro I could only share one photo at a time to a Dropbox folder. I had to go to my iMac to share multiple photos. I'm so glad I only loaded the 1st ten years of photos to this - they're mostly jpg and are well under the 20gb of free storage. I also kept all those photos in a separate LRCAT so I can just open them all in LR Classic CC.

[@vincentb.6889]

Damn I'm so close to migrate to this. The only thing is folder management. Right now, my photos are in folders with a name representing the event. If I migrate to LRCC, now all my folders will be created based on date. You create albums and everything in LRCC but let's say I cancel my subscription and migrate to a new app, I'll lose all this metadata. That's a though choice :S

[@pscottphoto2435]

Brian, have you tested importing photos tagged in Lightroom CC into your Stock service? Do tags that you add from your mobile devices show up in the stock service? Tags from Lightroom CC don’t sync back to Lightroom CC Classic, which makes it seem like there is something funky with the new tagging implementation. Moving forward, are you maintaining dual catalog systems? In other words, right now are you importing photos from this month (Jan 2018) into Lightroom CC Classic. Or have you really migrated away from it? The storage cost is unrealistic for anyone who has years upon years of photos in their catalog. We can say that it isn’t required to put all of our back catalog into the cloud, but honestly... that’s the whole point right? Having access to all of our photos from anywhere. Thanks for disclosing that you are getting the cloud service for free. It would be interesting for you to disclose how much it would be costing you if you were a normal like us. Is it $100 a month for storage on top of the monthly Creative Cloud cost? Most of all, thank you for taking the time to share this info. Please continue to do so!

[@brianmatiash]

Thank you for the kind words and for watching the vid! Disclosing that Adobe provided me with the gratis storage space and software was a "must" for me. I take expenses like these very seriously, ESPECIALLY if I'm going to recommend them to all of you. Getting this space provided to me has allowed me to conduct real-world experience tests without the burden of cost, so while it's not 100% accurate (because the end-user would still need to pay for this storage), it hopefully sheds some light on what to expect should you decide that the investment is worth it. As far as the cost itself, any storage costs beyond what's included in your plan would be extra. So I believe that if you got the 10Tb plan, it'd be $100 + the cost of your subscription... BUT, I am not 100% certain on that. As for your question about tags syncing from a mobile device to stock, that all depends on how you have your preferences set on Lightroom Mobile (on your mobile device). There is a preference to share the metadata with granular controls to include Caption, which will send over the Title and Caption. Sadly, tags that you add-regardless of whether you added them on a mobile or desktop device-do not transfer over. To recap, I can add a title, caption, and tags to a photo on my iPhone. I can then save the full res file locally on my phone and upload it to Stocksy via the Chrome app. All of that works great. However, only the title and caption flow through. The tags, sadly, do not. I am hoping that Adobe adds that in their eventual quest to achieve feature parity with Classic. Moving forward, I aim to abandon LR Classic altogether once I migrate my entire library. That is not to say that I won't keep it. I'll still need it for merging HDR and Pano images (until/unless those features get built into LRCC). I meant what I said - the current iteration of LRCC v1.1 meets about 90% of what I need to do with photo management and editing. It's not perfect, but being on the bleeding edge rarely is. Let me know if you have any other questions. Cheers!

[@pscottphoto2435]

Regarding tagging: Thanks for the clarification. I'm extremely apprehensive about how keywords are being handled in the new Lightroom CC. If you get some time with your connections at Adobe, maybe you can bring up the subject and get clarification. It's pretty clear that Lightroom CC is saving tags in it's own internal database and not embedding them into the EXIF data of the image file. I have a hunch that this keyword implementation is necessary to work with their Sensei (machine learning) features. Brian, I'd be interested to see a video on how the Adobe downloader works. After you've gone to all the trouble to put your entire photo collection in the Adobe cloud.. and then sometime in the future decide you want to move it out. What do you get back? What sort of file structure (we know there is no file structure in the cloud)? Do tags you added in Lightroom CC get saved to the file Exif data before you download it? Or is all time spent keyword tagging in Lightroom CC only valuable inside the Adobe ecosystem? Thanks!!

[@andrewsutcliffe5757]

@@brianmatiash Hi Brian, I'm considering moving over to Lightroom CC. Have all of the features you need been added now? Thanks.

[@brianmatiash]

Sadly, no. LRCC still lacks merging to HDR or Pano, as well as no geotagging controls. These are some critical features that I use all the time, which is why I switched back to Classic a few months ago. I'll gladly go to LRCC again when these features are baked in.

[@andrewsutcliffe5757]

@@brianmatiash I don't understand after all this time how two huge features are missing like that. Thanks for the reply.

[@robertyanal3818]

Question: Suppose I "migrate" (say) 100 raw photos to Lightroom CC, which are then uploaded to the cloud. Suppose each raw file is 25MB, so that the total storage space is 100x25=2500MB or 2.5GB. Now there is 2.5GB of photo files in the cloud. Suppose these 100 photos are accessed on my iPhone or my iPad. Have they been DOWNLOADED to my iPhone/iPad? In other words, is there 2.5GB of photo files now on my iPhone or iPad? If not, what exactly is going on?

[@LevanenG]

No, you don't need to download all those files in your device. Think Lightroom CC as Onedrive, Dropbox or Google Drive: You can work with your files online, and you can download to your device if you want, but is not mandatory

[@curtiswrigley]

For my workflow cloud is way too expensive. For a non pro who takes a lot of photos, i cant afford a car payment to store my photos in adobes cloud. This missing import and export features is another showstopper for me

[@marcrjacobs]

Hi Brian; Thanks for a great video, I learned a lot. I am already completely on Lightroom CC. After I got there I backed up and deleted my Lightroom Classic catalog and photos. Then re-initialized LR Classic and turned on Sync from LR CC. This is how a maintain a FULL backup of non-destructive photos, because I have a local catalog as well. It is a pain and seems unnecessary... is there a trustworthy way the do backups from LR CC and keep non-destructive photo edits> All I can find is a way to backup originals and that’s useless. Are we truly at the mercy of Adobe with our life’s work?

[@PhilippUnterreiner]

15:11 Question: What's your opinion on not having control over actual folder hierarchy. I understand that Adobe's concept is about having a clear split between photo management (done in LR) and foto file storage (done in backend), which is different from the "LR classic model". But from a longterm user perspective, let's say one day you decide to migrate e.g. all your fotos to a different service or do another third party cloud backup. You will lose all the work done in terms of photo-management - which before used to be at least partially software-agnostic.

[@mpmeyer]

What is your workflow to import RAW photos using only your iPad or iPhone?

[@brianmatiash]

I’m going to put that video together in the next week or two. Need to iron out the workflow.

[@mpmeyer]

I had started to work that out myself, but does not seem optimal. 1. Put iPad/iPhone into airplane mode. 2. Import into iOS Photos with the camera connection kit card reader. 3. Open LR Mobile. Create a folder for the new photos, then add all photos from the "Last Import" folder of the Camera Roll. 4. Open iOS Photos, Open the "Last Import" folder, select all photos, delete. Open "Recently Deleted" Photos, delete the ones you imported. 5. Put iPad back onto wifi, LR should sync.

[@KC_79]

Adobe - "After cancellation, your allowed cloud storage is reduced to 2 GB. If you are over your storage limit, you have 90 days to reduce your online usage. After 90 days, you could lose access to some or all of your files saved on the Creative Cloud servers." Google - "Everything in Google Drive, Google Photos, and Gmail will still be accessible, but you won't be able to create or add anything new over the free storage limit." For cloud storage I will choose Google over Adobe any day. LOL

[@PhotographerSteve]

Be careful. Specifically, be more truthful... when you said 'Adobe didn't pay you....to make this video'. Well, they did. They give you (as you explained) the full CC suite + 10tb storage. They gave you over $800 in Storage and SAS. That's not exactly insignificant. Overall, the information you provided is specific and generally accurate and your explanation is clear. but you may want examine how you explain your relationship and payment in kind from Adobe in the future.

[@sarimner]

most people have data cap outside the USA? Most people in the USA have data cap... :P as far as i Know.. :P 207 providers have data caps in thr USA!

[@Don-md6wn]

I read enough without watching this video to realize that it is time for me to move away from Lightroom, which I have used for 99% of my photography software needs over the last 5-6 years. I never have used Photoshop. I'm not going to pay a monthly fee to have my RAW photos sitting out in the Cloud, presumably unavailable to me if I ever was to leave Adobe in the future (or at least unavailable with the processing that had been done to them in Lightroom and/or Photoshop). I upgraded from Lightroom 5 to 6 almost 3 years ago for $79. Now Lightroom 7 is going to cost $120 a year (with price increases on the way, I'm sure) plus monthly storage costs. No thanks. I'm not going to rent software and I'm not going to have some large corporation holding my RAW photos hostage. Frankly, after I process the RAWs, I can just save them in files and folders as JPEGs and be done with the RAWs. I will use my Lightroom 6.3, which I own, in combination with Canon DPP and/or DxO PhotoLab (available for purchase, and it now includes the Nik Suite, which is great for local adjustments) and figure out over the next year or two how to modify my workflow to eliminate Lightroom.

[@teleguy5699]

Understood, but to someone new to photo editing, and being a retired enthusiast willing to learn, this new Lightroom is perfect timing. I feel bad for people who are used to Lightroom realizing that it's probably changing forever. The problem I have had with other editing programs that are "cheaper" is that they are so hard to learn with confusing tutorials that it gets frustrating and it makes me not want to put the time in to get the best of my photos.

[@Don-md6wn]

Gary, before you invest the time in learning Lightroom, you might want to take a look at DxO which is available for a free 30 day trial. I have been shocked at how much better DxO's RAW converter is than Lightroom's. DxO has algorithms that correct for your lens/camera combination and also something called Smart Lighting which automatically fixes minor highlight clipping and lifts shadows. My images look better at the DxO default settings than they did after I finished processing them individually in Lightroom. I have cut my processing time by probably 2/3 and am getting better results, after 6 years in Lightroom and only a few weeks with DxO.

[@teleguy5699]

Thanks Don for the tip. Does it preserve your originals?

[@Don-md6wn]

Gary, you can keep the unprocessed RAW originals in case you ever want to revisit them. Since I already had Lightroom, I use it to download the RAW photos from my memory card. I go through them and apply keywords (which will be part of the metadata in the output JPEGs from DxO) and do obvious deletes, but don't do any processing in Lightroom. I then open DxO and in the Organize tab, I go to the file structure of the computer and click on the folder that day's RAW images are stored in. That opens them all in DxO, as virtual files; the changes applied by DxO, both the automatic ones and the ones you do, don't alter the original RAW file. You'll see the photos with DxO's defaults applied (there are blue boxes that show you which defaults have been applied; you can reverse any of them but I never do because I experimented and find they improve the images). I highlight the whole group and put in +10 for vibrance and +10 for microcontrast. I look for any dust spots and use a DxO tool that does a great job of matching the surrounding content and fixing the dust spots. The vibrance, microcontrast and dust spot removals on one photo are applied to the entire batch if you highlighted them all. I then go through the photos individually to see if they benefit from applying DxoO ClearView, which is their equivalent of Dehazing in Lightroom (from what I understand; Lightroom only makes Dehazing available in their monthly subscription product). Many photos benefit greatly from it, particularly when they have moving water or in landscape shots under foggy conditions or with detailed subject in the far distance. It basically sharpens into Their default is set at 50. I may leave it at that, reduce it, or click it back off. I also look to see whether DxO Smart View, which is automatically applied uniformly, might work better for a particular image by applying it using the "spot weighted" tab. I try that if there's an area in the foreground that is a little too dark. You just click on the spot weighted tab, put a little box around part of the area that's too dark, and the Smart Lighting is applied in a different way and slightly changes the exposures throughout the picture. What DxO's smart lighting appears to do is to vary the exposure, shadows, highlights, etc. slightly around the image as needed, based on the characteristics of the camera and lens, and the subject matter in the photo. If you shoot people in the image for example, the smart lighting algorithm will usually recognize the presence of a face and increase the exposure of it or lift shadows to make it look more natural. If it doesn't, you use the spot weighted tab and put a box around the face. I use their crop tool if needed. Then I pick the keepers and export them as JPEGs into folders by subject matter. I still have the RAWs under the Lightroom structure. That's basically my entire workflow now. I find the DxO algorithms to be so good that I'm not going through each image monkeying with all the individual settings in the basic panel like blacks, whites, highlights, shadows, or using the grad ND filter and spot functions to work on specific areas that are too bright or too dark. DxO also has these capabilities, I just find that I almost never have to use it in a properly exposed photo. Their algorithms take care of it. And I never get weird colors that cause me to have to go to the camera settings (landscape, standard, neutral, etc.) and try different ones like I sometimes do in Lightroom. One interesting thing is that the JPEGs produced by processing in DxO, at a 100% quality setting, have much bigger file sizes than when they are processed in Lightroom. I have a couple of external hard drives with plenty of storage, so I'm not concerned with that. I've seen varying explanations for the bigger file sizes online.

[@teleguy5699]

Thanks again Don.

[@donnachatman4585]

Sorry, it all sounds good but not willing to pay a monthly subscription fee forever. Makes no sense to me...

[@LensShark]

Slowest pillow ever. lol

[@swissheartydogs]

way too expensive.

[@GoA7250]

I have a computer... I have plenty of space. I don't use the cloud... It's a scam.

[@rudylantican6307]

teach you a lot of the fundantals of soft. You don't even need to sit through the entire tNice tutorialng to get a good grasp on the basics.

[@GonneVlaD]

lol look at tNice tutorials dude