Lightroom Is Broken in Leopard

Yes I know this is being discussed in other threads but I wanted to just add to the critical mass in these forums so Adobe will step up the fix.
Not only can I not make a pdf of my contacts because of the module switch problem, I also cant import from a CF card like I normally can.
Come on Adobe.
It's not like this release of Leopard was a surprise. It's been in development for years.
It's out now and we cant use Lightroom in the way I need to.
Please fix it.

"Just to be accurate, members of ADC were notified only Friday that the final GM release version was available for download for developers. Contrast that with MSFT making Vista GM available to developers in Nov 06 with the consumer release in Jan 07 and you might see the differences between being an Apple developer and a MSFT developer. Apple has been known to make last minute changes (it happened with Tiger) that software developers where not told about and had profound impact to developers.
Wake up and realize that any major OS upgrade is gonna whack a lot of developers and you only REALLY know what gets whacked until the final release gets into the wild.
If a user is foolish enough to jump without looking (or taking any precautions) then I would be inclined to say you deserve what you get"
Jeff,
Most everyone knows you have a much closer relationship with Adobe than the average person. How about using that though for a little protection and advise for the average consumer rather than holding Adobe faultless ..
It is perhaps unfair to put all the blame on Adobe here, but they can't be held blameless either. Wacom seemed to have enough time to get something up, and while LR may be 100x the product if not more (from a SW coding perspective), they got it done. Major modules like print not working, or importing from a CF card are pretty basic test functions, and despite what may be a very late code drop from Apple, and unless those functions broke on Friday morning, Adobe still has some basic role to play in alerting its customer base (back to Web Page alert). This is not solely on the consumer. Not everyone is as connected as you, or as smart as a lot of folks on this forum. That doesn't mean that they got what they deserved.. just a little harsh perhaps?
Jay S.

Similar Messages

  • Photoshop: values for type, brush, crop, lasso etc tools broken on Leopard

    I posted this in answer to another thread, but decided that it may be helpful to some Photoshop users if it had its own topic:
    The following is a technote copied from Adobe's forums, regarding the performance of several menus for key tool settings in Photoshop CS3 running in Leopard:
    *Changing values for type, brush, crop, lasso etc tools broken on Leopard*
    *Kirsten Harris - 08:58pm Nov 15, 2007 Pacific*
    Adobe and Apple are working closely to provide a fix to a known issue running Adobe Photoshop CS3 and Photoshop CS3 Extended on Mac OS X Leopard (v10.5.1). Currently, when you enter values in numerical fields to set sizes for the brush, crop, marquee, lasso, type, and other Photoshop CS3 tools, those values revert to previously entered values when you try to apply them.
    # While we have identified workarounds for some of the affected tools, this issue prevents people from working as precisely and intuitively as they expect. Providing a fix to customers is a top priority. Please note the following: The fix will be provided through an update to Mac OS X Leopard. Consequently, it is not part of the Photoshop CS3 (10.0.1) update.
    # Apple is collaborating closely with us to get this fix incorporated into a Mac OS X Leopard update. No public schedule is available at this time, but both companies understand the urgency of this fix.
    # As soon as the appropriate update to Mac OS X Leopard is available, we will immediately alert our Photoshop users.
    Affected Photoshop CS3 tools: Art History tool, Blur tool, Brush tool, Burn tool, Color Replacement tool, Clone tools (all), Crop tool, Dodge tool, Eraser tools (all), Gradient tool, Healing tools (all), History tool, Lasso tools (all), Line tool, Magic Wand tool, Marquee tools (all), Paint Bucket tool, Pencil tool, Polygon tool, Quick Selection tool, Red Eye tool, Rounded Rectangle tool, Sharpen tool, Smudge tool, Sponge tool, Slice tool, Type tool
    Workaround for tools with sliders: Instead of typing in a number, use the sliders to change the value.
    Workaround for tools with pop-up menus: Enter a value for the size but don’t press Return/Enter to apply the value. Instead, choose it from the top of the Size pop-up menu to commit it.
    Workaround for tools which do not have sliders or pop-up menus: For certain tools, such as the Line tool, you may want to set up presets that you can load to set common sizes. Alternatively, you can restart Photoshop CS3 to clear the problem. You will then be able to enter values again. However, the issue typically re-surfaces quickly.
    If additional details come to light, our tech doc Values in numerical fields in Photoshop CS3 revert to the previous value in Mac OS X v10.5.1 (Leopard) will be updated.

    Well, that's interesting! Here I thought the problem with my CS1 was just that it was too old, running in Rosetta and all, and would be fixed when I get my Xmas treat of CS3. Wonder if that means when the fix comes from Apple it will also fix the same problem in CS1? Of course, by then I'll probably have CS3.... Thanks for posting this, I would have been mighty annoyed to have plonked down my 200 bucks only to discover that I had the same bugs.
    Francine
    Francine
    Schwieder

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

  • Lightroom Is Still Broken in Leopard

    Well here we are, Nov. 10th.
    Lightroom Still isnt working in Leopard.
    How close are we Adobe?

    For 64 bit Carbon?
    http://arstechnica.com/reviews/os/mac-os-x-10-5.ars/6
    Yeah, I know that for Adobe (and for Microsoft) it's a big deal. Because of the huge code bases and extensive support and code base that dates to pre-OS X days. Basically no "free" 64 bit support as many parts of the UI layer just ain't going 64 bit. Also given the "Hey when is Photoshop going to be 64 bit?" questions it's not something that isn't being considered :-)
    These types of problems though really affect software products that have been around for a long, long time way more than they do other apps. Because none of these SDKs were available in System 6. Well if Photoshop were developed from the start on NextStep maybe it would have been easier but it's a fine line balancing the needs of what's good for the platform in the future and the needs of your existing user base (and the apps they must rely on).
    I mean, you get apps like this that come out of nowhere:
    http://www.naked.la/light/
    Which largely rely on the OS foundations to do the work. Core Image is something that's really cool (modulo performance issues and hardware requirements) that can substantially reduce development time here. But if you're doing cross-platform and there's no Win32 equivalent then they aren't any help.
    Anyway, regarding API choices and legacy compatibility and the like -- I'm glad I don't have to make those decisions :-)

  • 2 problems! - RAM module broken & Snow Leopard not loading

    Hi,
    I have 2 problems:
    I got Mac Mini (late 2009 model, 2,26ghz, 2gb) upgraded from 2GB to 4GB from this Apple Premium Reseller (http://www.stormfront.co.uk/). When I got it back and switched it on and immediately got 3 beeps which indicated bad ram or logic board. The y took it back and said they sent it to their workshop in Exeter and fixed it. When I switched it on I still got 3 beeps. Took it back to the shop they said don't what to do and get the workshop to ring me back on Monday. At this point I'm fuming!!! So I decided to take apart the Mac MIni myself. Upon discovery that one of the memory modules is broken, I bent the bit metal back and it seems to ok after hardware tests and is working now. What can I do about this? I honestly did not break this and know it was the shop but how I van prove this? What would be done about a replacement as I have no longer sold, would I get a discount on brand new mac mini?
    As mentioned above that I took it apart I cant load up Snow Leopard, I just get the Apple logo plus the spinning wheel I can hear some hard drive activity but does nothing ( I left it for 20 mins). I then booted from the SNow Leopard and ran disk verify it came up with errors and said to format and restore, which I have done via Time Machine. But I still get the Apple plus spinning wheel. I know the hard rive ok now because I can boot into Windows via bootcamp. So what I should do?
    Any help would be appreciated.

    it seems that it's not emptying trash for you. only emptying trash will actually free up space on the drive. what exactly happens when you empty trash? does it seem to empty?
    click on the trash in the dock. is there anything inside?

  • LightRoom CRASHING on Snow Leopard OSX 10.6

    Updated to Snow Leopard and LightRoom has become very unstable, It crashes if I try to update a folder location, exporting to web, etc
    Is anyone else going through this? any updates/fixes on the way?
    I tried 32b and 64b, I reinstalled LR but nothing helps... I will have to get my old XP PC up and running on a demo version of LR to meet deadlines.

    You can have the images on a remote drive, just keep the catalog/previews local.
    I finally got it to work, I "formated" my MBP and installed OSX 10.6 from scratch (you have to erase the harddrive) once its installed DONT RESTORE from a timemachine backup.
    So I had to re-install every piece of software and hunt all my serial/activation codes. I did copy my data manually from the TimeMachine backup drive. But this was a half-day event to get this working...
    I also copied my LightRoom presets back so it wasnt their fault.
    Apple sure is taking a step back on this release of OSX, reminds me of the early Vista days....
    Anyway Peace!

  • Printing from Lightroom 2 with Snow Leopard OS

    I have used Lightroom 2 and printed satisfactorily with Epson Stylus Pro 4000 with Leopard OS.  I have now upgraded to  Snow Leopard, and using the latest driver for the Epson 4000, the prints come out very dark with both printer and Lightroom color management.  Any suggestions?

    Thank you for your suggestions.  I have subsequently talked to the Epson Support representative and he said to watch the current drivers for Epson since apparently there may be some Epson driver updates.  I do not know whether any will be a resolution of the problem I continually have with the Epson Stylus Pro 4000 however.  Interesting, I printed an image using CS4 today, and out of frustration, I set the mode as "automatic" under the Print Settings in the Print Box.  It came out very close to the screen rendering, and was not dark like the images printed under the Photoshop settings and the other printer driver settings.  I have never used the "automatic" before since I normally use the ICC profiles for the paper and ink from Epson.  Under Leopard, prior to converting to Snow Leopard, the Photoshop/ICC profiles did not render proper color either, and I used "ColorSync" as a custom setting under the Print Box, and it was the best of the settings.  In any event, nothing seems to fully work under the current combinations with CS4, Lightroom2, Epson, and Snow Leopard.  Unfortunately, the best settings under my former PC setup render the worst possible prints under Snow Leopard.

  • IMovie 08 Broken in Leopard, but old version works

    2.0 Core Duo Macbook Pro. Upgraded to Leopard, then upgraded iLife. iLife mostly works.
    I movie is broken. I can start iMovie 08, but the things like NEW PROJECT, NEW FOLDER, are grey and unselectable. Other menu items are not grey however. I can't open old projects with it. If i drag an old project onto the imovie desktop icon, it just ignores it.
    iMovieHD works fine.

    I'm having the same issues with iMovie I imported 4 hrs of video over Christmas and the new year and edited it into 3.5hrs and then broke the edited version up into manageable smaller sizes for export to several DVD'S using iDVD but when I l ran imovie to do this,the next time i had time available to do this stage, I found the same issues as you ... I hope all this work has not been for nothing . . .
    to check the problem was not with the old files I created a very small new project using the built in camera of only a few second and it has the same issues. . .
    Maybe it's me but i can't find any references to this in Apples online support . . .
    I the past i have used a commercial video editing and burning program on another machine but both need upgrading badly so i opted for a new Mac and the built in software . . . thinking this would be a better long term investment
    At least I now know I'm not the only one with this problem . . . I just wish Apple would fix this issue . . . SOON
    If I wanted unstable beta ware software i would have gone windoze . . .

  • Lightroom 2.2 on Leopard 10.5.5-First query ever placed!

    I had 2 identities running under Leopard and now wish to combine the 20,000 odd photos developed under each. Some of these will probably be duplicates. Is there a novice-proof method to make this happen with the minimum loss of photos.
    As a mid seventies photographer of many years I have just moved across to Mac after 20 years in the Gates camp.-Please bear with me as I try to move into the wonderful world of Lightroom.
    BJM

    I'd take the smallest catalog first. Open LR with this catalog and click on all photos. Then under the file menu, chose export as catalog. In the catalog settings, be sure to include the negative files (your original files). This will create a folder. Put this folder on an external drive, or at least an area where you can get to from the other identity.
    Then switch identities and open LR with the biggger catalog. Under the file menu, click on Import catalog, and be sure the don't import duplicates is checked. This should not import any files with the exact same name.
    Once that's done, you can move and consolidate your folders in LR. It's better to do this inside of LR if you can, you'll have less catalog issues.

  • Dual monitor setup broken in Leopard

    There are numerous problems running an external Cinema Display from a MacBook Pro using Leopard. I've tried with 2 MacBook Pros (one 15", one 17") and 2 different Cinema Displays (24" and 30"). Not to mention everything was fine under Tiger. Both Leopard installations were "clean installs".
    1. Closing the lid of the MBP doesn’t remove the screen from Leopard (Or Spaces).
    2. When the MBP sleeps with a Display attached it never comes back onto the Display, only the MBP’s LCD.
    3. Periodically the MBP refuses to wake when it’s connected to the display.
    4. I can no longer use the power button on the Display to sleep/shutdown the MBP.
    5. Simply plugging the Display sometimes causes it to wake (while the MBP is closed). In Tiger, I had to have the Power Adapter connected to wake my Sleeping MBP with the lid closed (as stated in the documentation).
    Wonder if all this will be fixed in 10.5.1 (hoping)?

    Firefox doesn't always play well with a multiple monitor setup and hardware acceleration.
    Try to disable hardware acceleration.
    *Tools > Options > Advanced > General > Browsing: "Use hardware acceleration when available"
    *https://support.mozilla.org/kb/how-do-i-upgrade-my-graphics-drivers

  • 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

  • Pax broken in leopard?

    Before doing a fresh install of Leopard, I backed up my data files using pax. This is referenced at the following URL. http://developer.apple.com/macosx/backuponmacosx.html I had trouble restoring the files. I limited the archive volume size to 2gb because of the DVD file size maximum, and this resulted in 2 files. I restored from the 1st volume and expected pax to prompt me for the 2nd volume, as described in pax(1). "When required, pax will prompt for the pathname of the file or device of the next volume in the archive." Instead, pax exits after giving the following message. "pax: End of archive volume 1 reached". I am currently downloading Xcode so I can build my own pax. Next time I may try a multiple-volume zip archive.

    My local build of pax was able to restore my files.
    The Leopard pax utility cannot even create multi-volume archives.
    $ pax -w -v -f volume.1 -x cpio -B 200k Downloads/About\ Downloads.pdf
    Downloads/About Downloads.pdf
    pax: User specified archive volume byte limit reached.

  • How to maintain default folder view (broken when leopard clients connect)?

    hi there,
    we run 10.4 tiger server and have the problem that if 10.5 leopard clients connect to the share their changes to the folder view become the new default for everyone connecting after them. with 10.4 clients the default folder view is looked to the settings of the admin.
    is there a way to bring back this feature with 10.5 clients connecting? lock the default folder view of shares?
    this question was asked before by andy lowe (http://discussions.apple.com/thread.jspa?threadID=1571877&tstart=45) but never answered.

    It's "show view options" in English. Also obtained by typing CMD+J
    Those only apply to the top-level folder. Each folder you open uses whatever you've elected to use as the defaults. Select a folder, CMD+J, set the view as you desire, click on Use as Default button. That setting will be used for all windows that you open in the future that have never been opened previously. All other windows that you opened will retain whatever view you previously selected for them.
    If you want to reset everything to one view, close all open Finder windows, launch the Terminal app (/Applications/Utilities/), copy & paste this command into the window that pops up,
    find ./ -name ".DS_Store" -depth -exec rm {} \;
    hit the return key, quit the Terminal app, restart, open a Finder window, CMD+J, set up the view options as desired, click the Use as Defaults button, and close the view options window. Now, every Finder window you open will have this view.
    Once you sort this out, see:
    Switching from Windows to Mac OS X,
    Basic Tutorials on using a Mac,
    Mac 101: Mac Essentials,
    Mac OS X keyboard shortcuts,
    Anatomy of a Mac,
    MacTips, and
    Switching to the Mac: The Missing Manual, Snow Leopard Edition.
    Additionally, *Texas Mac Man* recommends:
    Quick Assist,
    Welcome to the Switch To A Mac Guides,
    Take Control E-books, and
    A guide for switching to a Mac.

  • X11 fullscreen mode broken in Leopard - fix available / planned?

    Hello,
    in Leopard, X11 fullscreen mode doesn´t work.
    Is there already a fix available?
    if not is a fix of this problem planned?
    As we can see here: http://aaroniba.net/articles/x11-leopard.html it is possible to install Tigers X11, but I´d prefer a fix of the version, which comes with Leopard.
    Martin

    There is a fake way.
    To fake fullscreen support with Xephyr:
    $ Xephyr -ac -fullscreen :9 &
    $ DISPLAY=:9 twm&
    $ DISPLAY=:9 xterm &
    It works ok on mine.
    Good source http://homepage.mac.com/sao1/X11/index.html

  • Folder icon broken in leopard?

    just upgraded to Leopard and noticed that when i'm in thumbnail view and change the icon of the folder to an image stored in 'clipboard' - it renders that folder unclickable? what's going on? worked great in tiger! ****....

    The problem is the size of the picture you are using. I forget about this sometimes and still occasionally get the "unclickable" icon problem. Don't remember what the size limit is, but if you go beyond it you get the problem. You can either open the source image in Preview and resize it, then do copy and paste (and remember NOT to save the changes!), or else use something--an Automator workflow, CocoThumbX or an Applescript--to create a thumbnail for the image, then do GetInfo on the image file and copy the thumb and paste that. You shouldn't notice pixelation problems unless you are using CoverFlow view. In CoverFlow if the view is more than 128 pixels you will notice a degraded view, since normal thumbs created by any of the options are 128x128.
    Francine
    Francine
    Schwieder

Maybe you are looking for

  • How to set up iPhone 5 iOS 6 email with IMAP over SSL on a custom port?

    Basically I have the same problem as this guy 5 years ago but the thread contained no useful answer. Maybe there are people out there who became smarter in the meantime? Please help me out how to get my iPhone read emails via IMAP over SSL on a custo

  • Is it possible to stream a Google Hangout session from iPad 2 to the TV?

    Hosting a Google Hangout with 15 people at my house, to family in Seattle. I know I can download Google+ and participate (but not instigate) a Hangout session but can I connect the iPad 2 to the TV (via a composite cable or VGA cable or . . . ) so th

  • Continual SMB Problems

    I really have searched for the answer to my specific problem but nothing has really satisfied my problem as of yet. Much to the chagrin of everyone I work with, I purchased a Mac two years ago. I had major problems getting my E-mail set up with Entou

  • Convert datetime to 24hr

    Hi , I have written a SQL query query to select the max date of a column from a table:  SELECT MAX(datecolumn) from dbo.tablename I get result as '2014-01-23 22:53:39.683' when I execute  this in Management studio, but when I do the same in a package

  • Help on Clustering of tables

    Hi, The below is an example of 3 tables for which i want to cluster. I have the following structure of the 3 tables: Table A Primary key -> referenced by Table B Table A & B Primary key -> referenced by Table C I have done the following: 1. This is t