Lightroom 5.6 and Yosemite 10.10 Final

For those who have not upgraded to Yosemite yet, you may want to wait until Apple and/or Lightroom release a maintenance release. I find LR very slow after the Yosemite update. I get the spinning wheel of wait after every brush stroke, crop, etc. This behavior continued even after a shutdown/restart of the OS.
My setup is Yosemite 10.10, the latest LR (5.6 I believe), iMac 2012, not sure of the ram, but I did bump up the ram when I bought the computer. Also a Wacom Intuos 4 tablet. Aside from PS which I haven't tried yet since the update, everything else aside from LR seems to be working ok.
I am sure whatever the glitch is, Apple or Adobe will take care of it shortly. But if anybody has any suggestions on what to do to work around the bottleneck in the meantime would be appreciated.

I have the same setup with Yosemite and do not have any problems with any spinning wheel. My iMac (2011) is a 27 inch with 16 GB of ram. which is the max for this machine. I am on a subscription with Photoshop CC (2014) and LightRoom 5.6. You might want to delete your cache as that could be the problem. I do mine every so often when it reaches about 800 to 900 mb.
Tunney

Similar Messages

Lightroom 5.7.1, Yosemite OS X - Synchronise Folder function doesn't work in Lr. Is there a compatibility issue? I can see the folders/images in Finder but when trying to synchronise folders in Lr it does not recognise that there are any images and theref

Lightroom 5.7.1, Yosemite OS X - Synchronise Folder function doesn't work in Lr.
Is there a compatibility issue? I can see the folders/images in Finder but when trying to synchronise folders in Lr it does not recognise that there are any images and therefore unable to import to catalogue. Anyone has any idea how to make it work. Thanks a lot.

Hi Elba,
Thank you very much for your reply. Not sure, however, that we are talking about the same problem.
I am trying to perform the same function in Lr that I have been doing for many years in the past and has only been a problem in the last few days (possibly coinciding with upgrading to Yosemite, trying to find out whether that is the problem)
I am not intending to sync any files with Creative Cloud but only trying to use 'Synchronize Folder' function in Lr. Normally, I would right click on a particular folder in Lr catalogue and click on that function to check that the Lr Catalogue is perfectly matching my drives where the original photos are actually stored.
The problem that I only started to encounter is that I can see the files on the actual drives but they do not appear in my Lr Catalogue and they are completely invisible to Lr. I simply can not get Lr to recognise them and then import them to catalogue.
If for example, I export images to Ps and then save and close them, they do appear on my drive but are invisible to Lr and I can't get them imported into the catalogue. Import to folder also not producing any results as they are still invisible to Lr.
Completely baffled by it. Any idea what could be the reason?
Kind regards,
Nik

How can I make Final cut pro 7 and Yosemite work?

Hi dear Apple.
I have this huge problem with Final cut pro 7 and Yosemite.
I have tried to install it on a Mac book pro that has Yosemite but it doesn't work.
I have an I mac with finalcut pro 7 working on Lion but I need to upgrade it to Yosemite to be able to use CC Adobe.
I have a feature film worth 6,7 million SEK with Final cut pro 7 and I can't translate it to XML files to premiere cause it is in its last editing process. I get an error everytime I try. Also the last version of Fcp (X) ***** for a professional editor. So.. My only option is to finish this film in Fcp7.
How can I use Yosemite and still be able to keep Fcp7?
Please help me or do something about this issue soon. I bought fcp7 for 11000 SEK at the time that was quite expensive.

Hi Meg the dog! Thanx for answering!
I know it was left to die 4 years ago. I just think its ****** up.. I work with documentaries and it takes quite a while to finish. I have done one for 6 years now. If I had known that Fcp7 was left to die I would never had started to edit 6 years ago...
I did try this recommended on the forum by another user:
Go to the app location in finder, CTRL click on the app and choose [Show Package Contents]. A folder [Contents] appears, click on it and choose [MacOS]. You'll see a Unix executable. Double click, you'll start Terminal. At the same time fcp will launch. After fcp is launched, close terminal and confirm when asked. Now fcp is up and running. Close fcp and the next time, just open fcp the normal way. DONE!
But it doesn't work for me. I can't launch fcp7.
I have Fcp7 Installed on my I mac and I wonder if that will effect fcp7 if I upgrade to Yosemte?
I tryed to export XML to work on premiere and this is what happends:
Any recommendations? I am going crazy here..

Lightroom 3.2 and Camera Raw 6.2 final releases are available

Lightroom 3.2 and Camera Raw 6.2 are now available as final releases on Adobe.com and through the update mechanisms available in Photoshop CS5 and Lightroom 3. These updates include additional lens profiles support among others. Check out http://blogs.adobe.com/lightroomjournal/. Following the example of Adobe's collaboration with SIGMA, leading lens manufacturers such as Pentax, Tamron and Zeiss worked closely with Adobe to create some of the profiles.
-Simon

Excellent! Now if there were only a way to use my S95 in raw... I guess I'll have to wait another few months

Lightroom 4 and Yosemite

Hi
Has anyone dared upgraded to OSX Yosemite and still maintained Lightroom 4?
I haven't upgraded to Lightroom 5 and with 6 coming in March, I won't be paying to upgrade to 5 when 6 is just around the corner. I didn't see anything in 5 that I thought was worth the full upgrade price, so I haven't upgraded so far.
I'm pretty excited about the things Yosemite can offer Mac users BUT if it all comes at a cost to maintain Adobe products I will just have to hold off until March and upgrade all at once
Lenscurve

Be aware of an unfixed color management big in Lightroom running on Yosemite or Mavericks. More here: Lightroom 5 ICC profiles clipped shadows under OSX
And quantization here: Jao's photo blog: Further quantification of the Mavericks color management problem
This bug has existed since Mavericks and is present in LR 5 and will kill the display of shadow areas in Develop (they will be OK in Library). I have never tried it with LR 4 but I wouldn't hold out hope. Every single Mac running Lightroom on Mavericks or Yosemite has this problem. Haven't found any exceptions yet. I think most people do not notice if you do not care much about the display of very deep shadows but as soon as you notice it you'll see it all the time. You can work around it by turning on soft proofing which will correct the shadow display but that is a kludge.

Exposure problem with Lightroom 4 CS5 and Raw 6.7

Hi all
I have recently upgraded from Lightroom 3.6 to the new Lightroom 4 and am genrally pretty happy with it, I tend to use it along with photoshop CS5 extended and also imagenomic Portraiture, but I have found an annoying little problem in doing this and something that I never suffered with when using Lightroom 3.6 and it is this...
when I take an image from Lightroom 4 and click Edit image in Photoshop CS5 and then use Imageonmic to soften skin etc all seems to work well I then carry out any touching up within Photoshop and once finished save it back to lightroom for any final tweaks etc which is fine and all works smoothly, except once I have saved it back to Lightroom the exposure has been pushed up about 3-4 stops at least , meaning I then have to pull it down again and this can sometimes result in extra editing I could do with out. now I know its not the end of the world and is probably just a bug that I'm hoping will be sorted within Lightroom 4 but I just wondered if anyone else has had a similar problem, is it a bug or am I doing something wrong? (although I'm doing the same with Lighroom 4 as i used to do with LIghtroom 3.6 and that worked fine)
Oh one more thing I should mention to get lightroom 4 and CS5 to work properly together I had to go into the Adobe Labs site and download the Camera RAW 6.7 software for CS5 so it could also be a bug here i guess.

There have been several posts over on the Lightroom forum, and other non-Adobe forums also, about this issue: it seems that there's a bug in ACR 6.7RC which causes the image to be over-expose, compared with the setting applied using PV2012 in LR. I guess this is the kind of thing a Release Candidate is supposed to flag up! I was all set to upgrade my own ACR to ensure that PS would recognise my LR4 edits (I normally avoid RC versions and wait for the final), but all the reports of this problem have stopped me from doing so.
In the meantime, best option so far as I'm aware is to process the image in LR (you get the option when you choose to edit in PS), meaning that it does all the rendering before passing it over to PS (otherwise, ACR handles the conversion of the raw file into TIFF). This does however mean that smart-objects and so on are temporarily out of the equation.
I'm sure this will all be resolved pretty soon.
Edit: in fact, one of the posts I mentioned is about ten posts down in this very forum: http://forums.adobe.com/thread/974963?tstart=0
M

Lightroom 2.3 and Camera Raw 5.3 Available - Note from Adobe

Lightroom 2.3 and Camera Raw 5.3 are now available as release candidates on Adobe Labs.
Lightroom 2.3, http://labs.adobe.com/wiki/index.php/Lightroom_2.3
Camera Raw 5.3, http://labs.adobe.com/wiki/index.php/Camera_Raw_5.3
Regards,
Tom Hogarty
Adobe Systems

Hi All:
based on the good work of Dorin above (post #19), he did a timeline of various releases of Lightroom from Adobe and it shows that from "version x RC" to "final release version" was around 1 month.
as it is already exactly one month now, it must not be too much longer till they will release the LR2.3 Final Version.
As for what Robert said in post #23, well, there's never any "guarantee" on a problem-free piece of software, or, for that matter, anything one purchases or anything in life, actually!! Yet, one can make educated extrapolations, right? From the range of comments thus far on LR2.3RC, it appears that it is the best version yet of LR2.x. This leads to the conclusion that it is probably a "good bet" that this version will likely lead to the least amount of issues, right? Maybe not "zero issues", but most likely, the least amount of issues from the various LR2.x versions available.
So by waiting, say, merely 1-3 more weeks approximately, i can go directly from LR1.4 (which i've been using for many months) to LR2.3 Final Release Version. It seems like it is a prudent and conservative move or plan.
What do the good folks here think, please?
thanks in advance for helping me to mull this over. If i were a PC expert, i'd be thinking about this less. as i'm just a somewhat competent user, and not a whiz, i thought that a bit of care and planning it out intelligently can possibly reduce frustrations later.

Lightroom 3.2 and Camera Raw 6.2 Now Available

Final releases of Lightroom 3.2, DNG Converter 6.2 and Camera Raw 6.2 are now available. Additional details here: http://blogs.adobe.com/lightroomjournal/2010/08/lightroom-3-2-and-camera-raw-6-2-now-avail able.html
Regards,
Tom Hogarty
Lightroom, Camera Raw, DNG Product Manager

function(){return A.apply(null,[this].concat($A(arguments)))}
function(){return A.apply(null,[this].concat($A(arguments)))}function(){return A.apply(null,[this].concat($A(arguments)))}Hudechrome wrote:
You have a wild hair about Bridge, Noel?
Not at all. I like good tools, and from everything I read Bridge is marvelous. I don't have anything against Bridge, I just don't need it.
As a computer engineer, I use my computer for WAY more than just Photoshop. As such, I do everything I can to have the operating system (via Windows Explorer) integrate things for me.
For example, via right-click or double-click or drag and drop onto icons:
I access my configuration management system from Explorer (Tortoise SubVersion).
I do searches (grepWin) from Explorer.
I compare things (Beyond Compare) from Explorer.
I start Photoshop and other image tools on raw and processed image files I manage with Explorer.
I start my development tools (Visual Studio and a host of utilities) from Explorer (e.g., double click .sln files).
I access my web sites with Explorer (via WebDrive).
I get file paths from Explorer (right click, Send to Clipboard as Name).
I access office management apps from Explorer (e.g., double click .doc or .xls files).
This is an abbreviated list. Explorer can be a VERY powerful integrator, and is at the center of my computing world at a higher level. So now you can start to imagine why I prefer Explorer for image work.
-Noel

Lightroom 1.3 and Leopard 10.5.1

Hi
Just downloaded and installed Lightroom 1.3. Print module now finally works!!
But, Lightroom still doesn't print using profiles. I am using an HP B9180 with all the latest drivers. I had a print made using Lightroom 1.2, then 1.3 before resetting the printing system and 1.3 after resetting. No difference. Printing via Photoshop, the prints come out great, as they should.
Any help would be appreciated.
Shrey

With Photoshop and the NEW drivers you'll find that Color Matching is automatically set to one or other of the two settings (i.e. ColorSync or Epson Color Controls) and locked down. The actual setting is defined by the print workflow (i.e. Photoshop Manages Colors <ColorSync> or Printer Manages Colors <Epson Color Controls>) . Lightroom uses a different pipeline, as Jeff has been explaining, and on the Epson side appears fairly complex. Just to confuse you - with Lightroom you'll "sometimes" find that the Color Matching options are user changeable, but thankfully ONLY when you press the Lr Print Settings button (used for configuring your print presets). On the other hand, hitting the Lr Print button will result in the Epson Color Matching options being locked down in accordance with the rules I described above for Photoshop. So what does this all mean for you? First, you need to save a Print Preset for each paper size and/or type: 1. Assuming you have your own media profiles for the printer, when setting up from Lightroom Print Settings button set Epson Color Matching panel to ColorSync and Profile pop-up to Automatic. 2. In Epson Print Settings panel choose your preferred Media Type (eg Epson Glossy) and Color Settings to "Off (No Color Adjustment). 3. Hit the Save button in the Epson print dialog. Do you have a headache yet? I've probably forgotten something, but it's late and I do have a headache :-( Edited: item 1 to add reference to ColorSync

Camera RAW and Yosemite?

I just updated Aperture 3.6 and Camera Raw 6.01. According to all the info it should read files from my new Canon 7D Mark II.
http://support.apple.com/en-us/HT203996
Well it doesn't!
Adobe Camera Raw also doesn't work with the files from this camera in Photoshop/Lightroom.
Very frustrating as I like to shoot everything in RAW.
Anyone have suggestions on why Aperture with latest Camera Raw and Yosemite don't play well together? Or even better how to make Aperture work with these files... Thanks - Roger

I was able to figure it out. I downloaded Camera RAW 6.01 from this address
http://support.apple.com/kb/DL1777?viewlocale=en_US&locale=en_US
and manually installed it. Apparently the App Store update didn't take. After this install all is working as it should.

How do I print accurate colors with Photoshop CS4 and Yosemite?

I recently upgraded to OS 10.10, Yosemite. I can no longer get accurate colors printed for photos from Photoshop. I have Photoshop CS4 and I use an Epson Stylus Photo R2400 printer. I am able to use Photoshop for everything but printing accurately. I downloaded all recommended drivers for the printer, reloaded profiles for the printer and even tried a trial of Photoshop CC. Nothing resolves the problem. My prints look kind of solarized. Black and white photos have green areas where there should be black. Please help.

I thought my problem could be Lightroom is in ProphotoRGB color space, and my printer is Adobe1998 color space. To test this, I changed the color space of my patches from prophoto to AdobeRGB. I checked my colors in Photoshop, and made them match the RGB number I specified. It was interesting to note that (128,128,255) had a noticeable shift to purple. the other colors shifted slightly. Now I printed the test page with Lightroom managing color and the printer managing color. Both images came out similar.
This study came about when I was printing some images, and the sky had a definite purple shift. So, I took the image into Photoshop and converted the colorspace from prophoto to Adobe. Printed the image, and the image came out much better.
So the question now is, do I need to convert each image I print in Photoshop, or am I doing something wrong in Lightroom?

Lightroom 2 Catalogs and Folders

Hello,
I am new to lightroom 2 and digital photography in general. I am having a hard time understanding how to organize my files and how to use catalogs. I have been taking an online class through Lynda.com, and have watched this section several times and am still stuck. I really do not want to go much further until I understand catalogs and develop a logical organizational flow. I am using a Mac. Any help?
Thanks

Hi All:
based on the good work of Dorin above (post #19), he did a timeline of various releases of Lightroom from Adobe and it shows that from "version x RC" to "final release version" was around 1 month.
as it is already exactly one month now, it must not be too much longer till they will release the LR2.3 Final Version.
As for what Robert said in post #23, well, there's never any "guarantee" on a problem-free piece of software, or, for that matter, anything one purchases or anything in life, actually!! Yet, one can make educated extrapolations, right? From the range of comments thus far on LR2.3RC, it appears that it is the best version yet of LR2.x. This leads to the conclusion that it is probably a "good bet" that this version will likely lead to the least amount of issues, right? Maybe not "zero issues", but most likely, the least amount of issues from the various LR2.x versions available.
So by waiting, say, merely 1-3 more weeks approximately, i can go directly from LR1.4 (which i've been using for many months) to LR2.3 Final Release Version. It seems like it is a prudent and conservative move or plan.
What do the good folks here think, please?
thanks in advance for helping me to mull this over. If i were a PC expert, i'd be thinking about this less. as i'm just a somewhat competent user, and not a whiz, i thought that a bit of care and planning it out intelligently can possibly reduce frustrations later.

Airdrop iPhone to MAC (ios 8.1 and Yosemite)

Hi
my airdop between my iPhone 6 and my MacBook Pro (finals 2011) doesnt work. It works with another iphones, but not with my mac. It`s something about the bluetooth version or something like that?
hope for an answer.
Thank you

Same for me - Macbook Pro mid-2012 Yosemite and iPhone 6 8.1; the Mac can see (& drop to) the phone but not vice versa (which is obviously the far more useful function!). All Apple advice says this should work - I have tried all the suggestions but no change. Older iPad similar.
Sop I am back to emailing myself! Please can Apple fix this?

I have lightroom 5.7 and a macbook pro 10.9.5. Occasionally when I am editing a photo in the develop module, I suddenly get a "file not found" message and the editing ceases to work. There is no "exclamation" icon below the histogram box in the Library

I have lightroom 5.7 and a macbook pro 10.9.5. Occasionally when I am editing a photo in the develop module, I suddenly get a "file not found" message and the editing ceases to work. There is no "exclamation" icon below the histogram box in the Library module or on the photo in grid view, and the histogram is gone. What is going on? Trying to find it using the "find missing photos" in the library menu does nothing.

Why does iTunes make me log in every time I open it since upgrading to v.12.0.1.26 and Yosemite?

Since upgrading to itunes v. 12.0.1.26 and Yosemite (same day), iTunes has been making me log in every single time I open it.
Not only that, but it makes me log in several times, for iCloud, for iTunes match, for whatever else we do on iTunes. It gives me like five different reasons to log in, and I have to type my password in five times.
Can anyone tell me what is going on here and how to fix it? Thanks!

Back up all data before proceeding.
Launch the Keychain Access application in any of the following ways:
☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)
☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.
☞ Open LaunchPad. Click Utilities, then Keychain Access in the icon grid.
Select the login keychain from the list on the left side of the Keychain Access window. If your default keychain has a different name, select that.
If the lock icon in the top left corner of the window shows that the keychain is locked, click to unlock it. You'll be prompted for the keychain password, which is the same as your login password, unless you've changed it.
Right-click or control-click the login entry in the list. From the menu that pops up, select
          Change Settings for Keychain "login"
In the sheet that opens, uncheck both boxes, if not already unchecked.
From the menu bar, select
          Keychain Access ▹ Preferences ▹ First Aid
If the box marked
          Keep login keychain unlocked
is not checked, check it.
Select
          Keychain Access ▹ Keychain First Aid
from the menu bar and repair the keychain. Quit Keychain Access.

Lightroom 5.6 and Yosemite 10.10 Final

Similar Messages

Maybe you are looking for