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 <b>Photoshop</b> 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.<br /><br />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?<br /><br />First, you need to save a Print Preset for each paper size and/or type:<br /><br />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.<br /><br />2. In Epson Print Settings panel choose your preferred Media Type (eg Epson Glossy) and Color Settings to "Off (No Color Adjustment).<br /><br />3. Hit the Save button in the Epson print dialog.<br /><br />Do you have a headache yet? <br /><br />I've probably forgotten something, but it's late and I do have a headache :-(<br /><br />Edited: item 1 to add reference to ColorSync

Similar Messages

  • 24" imac hanging with color wheel of dead using Lightroom 1.3 and Canon 10D

    Trying to download for the first time my pictures from my Canon 10D using Adobe LightRoom 1.3 under Leopard 10.5.1 everytime after +/- 30 pictures the program and the finder hangs option command escape also does not do anything anymore only the color wheel spinning. Only solution a hard reboot.
    Using Leopard 10.5.1 Lightroom 1.3 on my macbook pro (15" led display version) all the picutures from the camera get downloaded without any problems.
    Under all other conditions the iMac so far has been without problems. Is this aproblem in the video driver?
    Thanks,
    Raimond

    Trying to download for the first time my pictures from my Canon 10D using Adobe LightRoom 1.3 under Leopard 10.5.1 everytime after +/- 30 pictures the program and the finder hangs option command escape also does not do anything anymore only the color wheel spinning. Only solution a hard reboot.
    Using Leopard 10.5.1 Lightroom 1.3 on my macbook pro (15" led display version) all the picutures from the camera get downloaded without any problems.
    Under all other conditions the iMac so far has been without problems. Is this aproblem in the video driver?
    Thanks,
    Raimond

  • Finder is still crashing with Lightroom 1.3 and Mac OS X 10.5.1

    The problem reported with Lightroom 1.2 and Mac OS X 10.5 (Finder crashes when trying to read a JPG whose metadata contain some Lightroom specific development settings) is still present with both updates... Any hope Adobe would provide us with a way to fix existing pictures/metadata?

    The Lightroom XMP data for snapshots, which is totally valid XMP data makes Leopard barf because Apple's implementation of XMP in Leopard is not capable of parsing the snapshot XMP. This is most totally Apple's fault...and only Apple can fix it...
    The Photoshop CS3 & Leopard issue with text entry in certain tools is another Apple Leopard fault that Apple will need to fix...
    There is also an issue with Epson print drivers running under Leopard and Lightroom 1.3 where printing is not picking up the correct data and print come out light...the same drivers will work with CS3 because CS3 is using the older, none Leopard pipeline. Also note that CS3 will NOT be able to print out using the Leopard 16 bit pipeline while Lightroom 1.3 will be able to...as soon as Epson revs their drivers...
    Look, Leopard has introduced MAJOR changes well above and beyond the marketing features Apple promotes....eveybody is scrambling...but to Adobe's credit, they HAVE responded well and quickly to those issues Adobe can fix. Those Adobe CAN'T fix will have to be fixed by the companies responsible....

  • Use of Lightroom 1.1 with Leopard

    Hey guys,
    I currently run Lightroom 1.1 with Mac OS 10.4.11. I'd like to upgrade to Leopard, but I'm wondering if I'll have problems with Lightroom when I do so.
    Has anyone had any experience of this ? or can you give me some useful advice ?
    Many thanks for your time,
    John.

    Lightroom runs fine in Leopard.
    BTW: you would be better served by upgrading to Lightroom 1.4.1 (free upgrade from 1.1). Lightroom 2.x (paid upgrade) adds many more features and is capable of running in 64bit mode with Leopard.

  • 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.

  • IMac (Late 2006) Stalls with EFI 1.2 and Leopard

    A few days ago, I installed both the iMac 1.2 EFI Firmware update and Leopard on my late 2006 20" iMac. Since then, I've seen random momentary stalls throughout the system.
    It sometimes happens while scrolling a web page, displaying a sheet, opening a stack, browsing CoverFlow, and so on. I don't know how to intentionally recreate it, it just seems to happen. It often (always?) seems to coincide with some disk activity.
    I don't remember this behavior on the same hardware in the past, so either it's something with the firmware update or Leopard. Has anyone seen anything else like this?
    Thanks in advance.

    Some people reported various bugs after installing the firmware update. Shutting it off and turning it back was all that was needed to fix the bugs.

  • Hi I have been having a problem with Bridge in CS4 recently. So uninstalled CS4 and Lightroom 4.4 and reinstalled them on my Desktop PC. When I turned on Bridge through CS4, My thumb nail images disappeared and a thumb nail icon with CR2 appeared. Now som

    Hi I have been having a problem with Bridge in CS4 recently. So uninstalled CS4 and Lightroom 4.4 and reinstalled them on my Desktop PC. When I turned on Bridge through CS4, My thumb nail images disappeared and a thumb nail icon with CR2 appeared. Now some of my images have disappeared from Light room 4.4, but I can find them in CS4 and Bridge now shows some thumb nails as images and some as an icon with CR2. I have spent two weeks going through preferences etc. to find how to resolve my problem. Please can you Help? Meany thanks in advance
      Derek Randall

    I don't use LR and rarely use the bridge so I can not answers about thumbnails in them,  However thumbnails in windows file explorer and windows dialog for CS2 files will only show if you have installed codec into windows that will produce them. Windows does not do CR2 thumbnails on its own. I use FastPictureViewer Codec package for RAW File and PSD files thunbmail support.

  • I am currently using Lightroom 5.6 and operating on a Mac with OSX Ver 10.9.5. I am receiving an error problem when doing the following -  I am exporting selected photos from a particular Catalogue saved on Drive 1 to a folder created on another Drive whe

    Hi, I am having a little trouble with exporting images to another drive and Catalogue and need some help if anyone can give me some advice
    I am currently using Lightroom 5.6 and operating on a Mac with OSX Ver 10.9.5.
    I am receiving an error problem when doing the following -
    I am exporting selected photos from a particular Catalogue saved on Drive 1 to a folder created on another Drive where a Lightroom Catalogue has been created. In this Catalogue I have arranged for the images once exported to be moved to a different folder - I used the Auto Import process under the File dialogue box.
    When processing the Export I receive an error message for each of the images being exported indicating the following -
    Heading Import Results
    Some import operations were not performed
    Could not move a file to requested location. (1)
    then a description of the image with file name
    Box Save As                                  Box  OK
    If I click the OK button to each image I can then go to the other Catalogue and all images are then transferred to the file as required.
    To click the OK button each time is time consuming, possibly I have missed an action or maybe you can advise an alternative method to save the time in actioning this process.
    Thanks if you can can help out.

    Thank You, but this is a gong show. Why is something that is so important to us all so very, very difficult to do?

  • Endnote X1 and Leopard

    Has anyone tried using Endnote X1 and Leopard? I can't open any files ("the document blabla couldn't be opened"), nor can I create a new library ("Failed to create library").
    Anyone any ideas if this is fixable?

    Fixed the problem. Originally I had no problems keeping the Endnote files wherever I liked, however it now only works with the Endnote files in Users/Library. A bit weird, but I can live with it.

  • Can I run Tiger and Leopard on the same computer

    Hi folks.
    I've been meaning to install Leopard for ages but have never got round to it (I bought the retail box when it first came out). I have upgraded my RAM to 2GB and my hard drive to 320GB with no problems.
    My upgraded hard drive has been partitioned into 2 equal parts of 160GB. These appear on desktop as Mackintosh HD1 and HD2. HD1 is the disk with all my files, music, OS etc and HD2 is empty
    I have 2 bootable clones of my present system - one is on a 160GB external and the other is the original 80GB HD that I replaced.
    My question is this - can I install Leopard on to my 160GB external HD, then clone it on to the empty HD2. If I do this would I be able to run both Tiger and Leopard on the same Macbook?
    Is there any problems with this plan? Would I be able to transfer between the 2 OS and how do I install Leopard on the external drive. Is it just a case of inserting the Leopard DVD and choose the external drive as the target?
    As usual thanks in advance
    Del

    # Original Tiger in the internal HD, New Leopard in the external HD.
    # New Leopard in the internal, Legacy cloned Tiger in the external.
    # Split internal, one partition with Tiger, another with Leopard.
    Leopard is backwardly compatible with older Macs, just make sure yours fulfills the minimum system requirements, both use the same filesystem format, so each can see the other. You can't run both at the same time, unless you purchase the server version of Leopard and run it virtualized. 99.9% of Firewire external HD's are bootable, some USB's are bootable but have to test first. You can choose which system to boot from by pressing the Option key at boot time, before the chime. Just make sure the external HDD is plugged in and turned on if that's where you want to boot from.
    When I migrated my PBG4 from Panther to Tiger, got an external FW HDD, cloned Panther onto it, upgraded using Archive and Install, cleaned up, customized and tested it. When I was satisfied all was ok, cloned the original Panther onto another partition of the external HDD, wiped and tested for failure the internal HDD, then cloned the known good and tested Tiger into it. Only thing that died along the way was my old and ancient Photoshop v2.x, that refused to run on Tiger.

  • 1st generation MacBook, battery and Leopard issues; looking for help please

    I have a 1st generation MacBook that started having battery problems immediately after installing Leopard. it was the same issue many others have complained about; battery life shortened and shutting down while on battery power with no warning. I have never had that problem while using Tiger. I experienced this with both 10.5.0 and the stand alone upgrade of 10.5.1 using an erase and install method.
    (BTW, as a side note: I'm religious about calibrating my battery every month and use a program called "CoconutBattery" to document the results. Prior to Leopard, the battery measured 97-99% capacity. Three days after Leopard was installed it was time for another check, the result was 74% capacity.)
    I had a clone backup of Tiger and immediately restored my MacBook, but the problem followed Tiger. I have Applecare and called support. Both myself and the tech found it rather hard to believe that the battery just suddenly failed coincidentally after the Leopard install. We went through the regular things; SMC reset, firmware checks, diagnostics, repair permissions, etc.
    We believe it has to do with the Battery Updater package. I had gone between both versions of 1.2 and 1.3, but the problem remained with both Tiger and Leopard. The tech decided to send me a new battery (it's on the way) and I wish to try installing Leopard again. As long as I have my cloned Tiger image, all I have to lose is my time, but hopefully, not another battery! I would honestly like to get Leopard running on this machine.
    But... here's my question. In reading through these discussions in both the Leopard and MacBook forum, there doesn't seem to be any consensus of which BatteryUpdater package to use. The Apple tech honestly told me he didn't know. Also, if the BU package "writes" to the battery (which it states it does), can it be downgraded once v1.3 has been installed? I mean, should I leave the battery out, install Leopard, then manually update BU to v1.2 before installing the battery (if possible)? I do plan on testing the new battery with my Tiger install, just to verify it is working as it was before.
    There are a lot of people here claiming to be knowledgeable about Leopard, never had any problems with a variety of machines, etc, etc, so I would appreciate your input. Please don't speculate, but if you're using a version of BU that works with Leopard and your 1st Gen MacBook, I would appreciate you telling me about it. I have tried to document and methodically relate everything I've done so far, but if you need additional information, just let me know.
    I noticed Leopard had installed BU v1.3 when I checked it, so it must use that as default, since I noticed Tiger had v1.2.
    OR, am I way off base on this? Can anyone think of another reason I may have had this problem? Am I barking up the wrong tree by concentrating on the BatteryUpdater package? Is it possible all these batteries are failing under a Leopard install maybe due to some unknown reason?
    Any knowledgeable advice or suggestions are welcome, thanks!

    Well, Ding Dang y'all... it appears the battery was the culprit. I received my replacement battery from Apple and followed the same steps and everything seems to be working fine.
    It sure was strange that the battery started this problem immediately after Leopard was installed... I don't know what to say about that, unless BatteryUpdater v1.3 started the chain of events.
    In case it helps someone else, here's exactly what I did (rebooted through each step):
    - Backed up data; unauthorized computer from iTunes
    - Erase and install from the Leopard disc, while keeping the old battery in
    - Installed Leopard, did software updates except for delta 10.5.1 update
    - Applied combo update of 10.5.1 from separately downloaded file
    - Found BatteryUpdater Bundle (BU) of v1.3, moved to trash, rebooted
    - Ran software updates, BU v1.2 was found and installed
    - Then, swapped out battery to new battery
    - Tested unit, seems to be okay now, no shutdown issues, battery runtime seems normal
    Thanks to all that had advice and suggestions. It was enough to get me to try it again. Now, I have two more machines to upgrade, since these are production machines, I'll probably wait awhile. But, having this is a real treat.
    Have a great holiday everyone!

  • Using Lightroom 5.5 and Photoshop CC2014. Images no longer open in Photoshop when using "edit in" command. Photoshop opens but no image when trying to move between LR and PS. Any suggestions?

    Using Lightroom 5.5 and Photoshop CC2014. Images no longer open in Photoshop when using "edit in" command. Photoshop opens but no image when trying to move between LR and PS. Any suggestions?

    1. You have allowed Apple to auto-upgrade your Mac
    Turn off auto-update here:
    Menu > Apple > System Preferences > App Store
    2. The Icons on your dock are Aliases not real apps
    They point to where the apps really are which is:
    For Pages 5.2.2 in your Applications folder
    For Pages '09 in your Applications/iWork folder
    3. You are alternately opening documents randomly with either version of Pages
    Both Pages have the same file extension .pages and there is no certainty as to which version opens them when you double click on a file.
    right click on the file and choose which version you want to open it
    4. Pages '09 can not open Pages 5 files
    Pages 5 can not open Pages '08 files, and will convert and change Pages '09 and Word files.
    It will also auto save opened files into its own format.
    You can export these back to Pages '09 if you need to:
    Menu > File > Export > Pages '09
    5. Yes Pages 5.2.2 is a marked downgrade
    Pages 5.2.2 has a few improvements but has had over 110 features removed and is buggy.
    Sooner or later you will not be able to open a file or have it damaged in some way and it has a complex obscure file format largely incompatible with everything else, so you will not be able to rescue the contents of your file. If Pages or some third party server/eMail don't trash your file, eventually Apple will do it for you as it did when it released Pages 5 last September. I recommend using Pages '09 for the time being whilst you look for viable alternatives, some are here already and some are on the way.
    For further information about what has happened:
    http://www.freeforum101.com/iworktipsntrick/viewforum.php?f=22&sid=0882463378700 abf43a0f2433506bbbc&mforum=iworktipsntrick
    Peter

  • How do I create an Lightroom HTML Gallery and preserve the - in the file name?

    How do I create an Lightroom HTML Gallery and preserve the - in the file name?
    The hyphen (-) is more search engine friendly, so I label all my photos using hyphens (-) to separate the keywords in the file name
    Here's a sample file name - it's for the "Guess Where Berkeley" flickr site
    guess-where-berkeley-serkes-xx-s-curve.jpg
    I created a Lightroom HTML Gallery and posted it to the following link.
    http://www.berkeleyhomes.com/tests/lightroom/lightroom-test-1/
    Though it looksl like the HML gallery shows the original file name in the web page, it looks like Adobe Lightroom modified each photo's file name by changing the - (hyphen) to an underscore (_)
    Originally
    guess-where-berkeley-serkes-xx-s-curve.jpg
    After Adobe created the HTML photo gallery the name became
    guess_where_berkeley_serkes_xx_s_curve.jpg
    Is there any way to preserve the – rather than the _ character
    Thank you!
    Ira Serkes

    InDesign's interactive PDF support is a small subset of what you can do in Acrobat Profesional.
    I think you probably want to create a button (or change an existing button) in Acrobat Pro that causes Acrobat to close the document -- that should be analagous to "exitting the CD." I assume your autorun file is opening the PDF in Adobe Reader? You have not included it and are not specific, so it is tough to say.
    I believe in Acrobat Javascript you can close the document with this.closeDoc(). You'll probaly need to ask on the Acrobat forums (possiby Acrobat Scripting) for more detail.

  • Using lightroom 5.6 and Photoshop elements 12

    When I am using Lightroom 5.6 and want to Edit In Photoshop the picture transfers over to PS but it won't allow me to use layers.  How can I fix this?

    Usually that means that lightroom sent over the photo in 16 bits/channel and you want 8 bits/channel in order to use layers in photoshop elements.
    After you open the image from lightroom into photoshop elements you can go Image>Mode and click on 8 bits/channel
    or in the Lightroom Preferences (Edit)>External Editing set the Bit Depth to 8 bits/component

  • Integration between Lightroom 4.2 and PS Elements 11.0

    I am using Lightroom 4.2 and PS Elements 11.0. Clicking "Edit in" in LR  when I have selected at least two photos, I get as bottom menu item "Open as layers in Photoshop...". When selecting this item PS Elem. nicely starts up but after waiting for a while no layers are created. Same applies to the HDR and Panorama options. The only LR menu item working is the one moving to the PS Elem editor sec. After carrying out editing of the file(s) in PS Elem and saving (as) there is only the option to include the edited file in the PS Elem catalog (while the version set option is "greyed out"). In the normal Photoshop (CS versions) the edited file is nicely included in the LR catalog. I now have to follow a cumbersome route by importing the file from within LR. Another issue is when 16 bit files are loaded into Elements; there is no warning that layers can only be generated/worked on  in 8 bit mode.
    Yet another, small LR issue, is that when in library mode moving from the center thumbnail grid/pane to the left Navigator, etc and right Histogram, etc. panes, the cursor changes into a double headed arrow passing the separation line and but does not turn back into the cursor (mode). Only moving fast through the separation line or "going over the top" passing along the top menu items helps
    Obviously anyone with some suggestion as how to solve/circumvent the issues above?
    Message was edited by: doctorspek

    Photoshop Elements does not support layes with 16-bit files. Additionally, there is no HDR function in Photoshop Elements. You should be getting an error letting you know this is the case when you try from Lightroom.
    These menu options are designed to be used with Photoshop, not Photoshop Elements and would normally be greyed out. Have you had a version of Photoshop install previously? When looking at the Edit In menu, what does it say at the top? Does it say "Open in Adobe Photoshop Elements..."?
    Saving the file should automatically import it into Lightroom, even if you use the option to add it to the Elements Organizer as well.
    As for the cursor not changing back to normal after crossing over the panel dividing line (which allows you to grow or shrink the panels) is rather curious.
    All of these issues could be caused by corrupt settings files. Deleting these while the applications are closed will cause them to be recreated at next launch (with default settings). I would suggest doing this will all Adobe preferences (not just PSE and LR). Where they are stored depends on what OS you are working on.

Maybe you are looking for