OT Lightroom shipping

I would be interested to know if many PSE users are buying this. I would download the trial but I don't know if it would offer much to users such as myself.
Hmm ... Spend $199 and save $100.
http://www.adobe.com/products/photoshoplightroom/
I don't know if there are other "software packrats" here like me, I have bought just about all the paint and photo editing programs that I am aware of. I have also installed many of the open source and freeware goodies out there.
If I could do it over I would just bite the bullet and buy the full fledged Photoshop and be done with it.
This should have been a separate OT I know, need more !C*O*F*F*E*E!

I also downloaded the betas of LR and messed around with them, without fully going over (and very glad that I did not!), and I installed the v1.0 trial yesterday. I imported my 29000 file Elements 5 library overnight, and have tried using it some today. My first impressions just aren't very positive.
First, the reason why I'm glad I did not switch over to LR during the beta period. After installing v1, it tried to convert my beta library file and errored out, saying it was corrupted or something. I had to delete my library and create a new one, which wasn't a big deal for me since I had just imported a couple of folders to test with, but would be if I had completely switched over to using LR.
Next, after importing my Elements library (which it did a good job of, by the way, even getting all the tags), Lightroom has become just frustratingly slow. My PC should be fairly well-spec'd for it, an Athlon 64 x2 3800+ (dual core) and 1.5G of ram, running Vista. Yet the interface just feels clunky, and it uses up a lot of RAM. PSE5 on the other hand is fine. There are also various problems here and there which you can read about on the Lightroom forum.
My overall impression of the software is that it just simply was not ready for release yet. For all the hoopla about the improved workflow, I find that the program simply slows me down too much, and becomes a test of my patience.

Similar Messages

Is Lightroom intentionally made difficult for non-English users?

Could it be that Lightroom is intentionally made difficult for the non-English user? I came to this forum today hoping to find an answer and all I see is problems when I try searching the forum, and complicated instructions on how to, supposdely, solve this issue. The issue I am facing has to do with localization, compatibility, interoperability and compliance. The problem is that I can't use many of the Lightroom shortcuts. Many of the ones that require the use of a modifier key on my keyboard just don't work. So what if I have a Swedish keyboard? Sweden is one of the most computer literate contries in the world, and Sweden has played a major role in the development of early computers and new technologies. Adobe has a presence in this country, and I'm quite sure Sweden is an important market for Adobe. So why not make Lightroom compatible with the Swedish keyboard? Why should I care to go through complicated instructions on how to hacktivate my keyboard by the means of editing config or script files? Why can't it just work out of the box?
I feel like this is intentional. Could it be that Lightroom users are only to be found in English speaking countries like USA, UK, New Zealand and Australia? I don't think so.
Swedish user:
http://forums.adobe.com/message/1459525#1459525
Swiss user:
http://forums.adobe.com/message/4375318#4375318
German user:
http://forums.adobe.com/message/3588746#3588746
http://forums.adobe.com/message/3817657#3817657
How about the ability to change keyboard shortcut bindings, i.e. custom shortcuts? I just found that this is not even possible in Lightroom! That explains why people take these strange measures and kludgy ways of making custom shortcuts in Lightroom. Changing shortcuts is often times tricky business because you have to change them in respect to other shortcuts. It's likely that one will have to change several keyboard shortcuts to avoid conflicts, etc. Lightroom needs a shortcut editor!
One should really not even have to change the default shortcuts, Adobe should choose some intelligent key combinations that make sense, and they should just work on any keyboard. I've tried changing the language from English to Swedish in Lightroom settings. The result of this is that nearly all shortcuts are changed to something else, so I would have to re-learn some of the shortcuts I have already learned using Lightroom in English, and of course this also changes the language of the interface which is not something I want. I will have to change my keyboard layout to English to make this work, or get a secondary keyboard, one with English layout. This is something I will only have to do when I work in Lightroom, because many of the professional programs that I use are working just fine with my keyboard. Perhaps Adobe can make the keyboard localization (shortcut maps) as an option, separate from the interface language setting? And for God sake integrate a keyboard shortcut editor for once!

Another Swiss user on Lightroom forums:
http://www.lightroomforums.net/showthread.php?6867-Flippy-Key-Using-Lightroom-in-english-w ith-a-non-english-keyboard-layout
I ended up removing the Keyboard Tamer plugin and then manually adding following strings to C:\Program Files\Adobe\Adobe Photoshop Lightroom 4\Resources\en\TranslatedStrings.txt. This is by the way something that the Keyboard Tamer plugin does as well, because when I removed it I found two files named TranslatedStrings.txt in the Recycle Bin. The Keyboard Tamer is just supposed to save you the time and effort of manually manipulating these strings.
"$$$/AgLibrary/Menu/View/ZoomIn=Zoom In"
"$$$/AgLibrary/Menu/View/ZoomIn/Key=Cmd+."
"$$$/AgLibrary/Menu/View/ZoomInMinor=Slow Zoom In"
"$$$/AgLibrary/Menu/View/ZoomInMinor/Key=Cmd+Shift+."
"$$$/AgLibrary/Menu/View/ZoomOut=Zoom Out"
"$$$/AgLibrary/Menu/View/ZoomOut/Key=Cmd+-"
"$$$/AgLibrary/Menu/View/ZoomOutMinor=Slow Zoom Out"
"$$$/AgLibrary/Menu/View/ZoomOutMinor/Key=Cmd+Shift+-"
I found this thread helpful:
http://forums.adobe.com/message/1459525#1459525#1459525
I just replaced AgDevelop with AgLibrary. This of course only changes the key binding for Zoom In and Zoom Out in the Library module. Is there perhaps a document somewhere that explains the structure of the TranslatedStrings.txt file? There seems to be one of these files in each of the language specific folders under the Resources folder.
This file is known to be found in:
C:\Program Files\Adobe\Adobe Photoshop Lightroom 4\Resources>dir /b /s TranslatedStrings.txt
C:\Program Files\Adobe\Adobe Photoshop Lightroom 4\Resources\de\TranslatedStrings.txt
C:\Program Files\Adobe\Adobe Photoshop Lightroom 4\Resources\en\TranslatedStrings.txt
C:\Program Files\Adobe\Adobe Photoshop Lightroom 4\Resources\es\TranslatedStrings.txt
C:\Program Files\Adobe\Adobe Photoshop Lightroom 4\Resources\fr\TranslatedStrings.txt
C:\Program Files\Adobe\Adobe Photoshop Lightroom 4\Resources\it\TranslatedStrings.txt
C:\Program Files\Adobe\Adobe Photoshop Lightroom 4\Resources\ja\TranslatedStrings.txt
C:\Program Files\Adobe\Adobe Photoshop Lightroom 4\Resources\ko\TranslatedStrings.txt
C:\Program Files\Adobe\Adobe Photoshop Lightroom 4\Resources\nl\TranslatedStrings.txt
C:\Program Files\Adobe\Adobe Photoshop Lightroom 4\Resources\pt\TranslatedStrings.txt
C:\Program Files\Adobe\Adobe Photoshop Lightroom 4\Resources\sv\TranslatedStrings.txt
C:\Program Files\Adobe\Adobe Photoshop Lightroom 4\Resources\zh_cn\TranslatedStrings.txt
C:\Program Files\Adobe\Adobe Photoshop Lightroom 4\Resources\zh_tw\TranslatedStrings.txt
I will study the structure of this file in Resources\sv\ and try to understand it. And as I find new "flaws" in the shortcut key bindings I will make new edits to the file I saved in Resources\en\ accordingly.
Here's an idea: those of you who don't mind re-learning all the shortcuts - the localized shortcuts for Swedish keyboards - simply copy the TranslatedStrings.txt file from C:\Program Files\Adobe\Adobe Photoshop Lightroom 4\Resources\sv\ and paste it in C:\Program Files\Adobe\Adobe Photoshop Lightroom 4\Resources\en\. What this does it allows you to keep English as your interface language, but it changes the shortcut map to something that's more adopted for the Swedish keyboard layout. You get the same shortcut key bindings as the ones you see when you change the language to Swedish in the settings. But this way you are preventing Lightroom from changing the interface language.
Either that, or add new strings to an empty Resources\en\TranslatedStrings.txt file for each key binding you find to be broken and not compatible with your keyboard. This way you are only making changes to the key bindings that don't work very well for your keyboard, you are not chaning all of the shortcut key bindings. The other key bindings stay the same, the default key bindings found in the English version of Lightroom (or with English as language settings).
This is a way to adapt Lightroom for your own environment. But this is still too complicated and unncessary. A simple shortcut editor built into Lightroom would have solved this. But what are we going to do?... this is up to Adobe... Lightrooms have been complaining about the lack of a shortcut editor since at least Lightroom 2 and Adobe has not listened. So I don't expect to see this feature in the following years to come. It might just come along in maybe Lightroom version seven or something... but who cares?... At that time I might even ditch Lightroom altogether.
Ligthroom 5 upgrade...
I just found out that the new Lightroom 5 is not compatible with Windows Vista. I have the Vista Ultimate 64-bit on my desktop where I use Lightroom. This was not made very clear by Adobe. They simply state that Lightroom 5 works on Mac and on Windows. You have to read the fine print. I almost purchased the upgrade. I'm glad I didn't. I won't upgrade from Vista to Windows 7 just to run Lightroom 5! We, the early Windows Vista adapters, got screwed by Microsoft. Now, we are getting screwed by Adobe too! I see no reason not to support Windows Vista as it is pretty much the same system as Windows 7, and one would expect Adobe to support them both. I found a thread about it where one user asked why Vista was not supported and Adobe failed to give any explanation. They just silently dropped the OS support.
I guess they can do whatever they want. They are Adobe.
But I will not upgrade to Windows 7 because of Lightroom, so I won't upgrade to Lightroom 5. This is a great oppertunity for Phase One to strike with a good deal, such as a discounted migration upgrade for Capture One. I am sure many Lightroom 4 users would be happy to leave the Lightroom ship in favor of Capture One. At the end of life of Lightroom 4 I will probably just go to Capture One, even if I have to pay full price. At least they support Windows Vista.

Shipping question regarding lightroom physical box

I am yet to recieve my physical box of lightroom. DHl Tracking number say it will arrive on Feb 26. The wierd thing is it say "Alaska-DHl Express" instead of "continental usa-DHl Express". In past shipments from Adobe, all of my orders originated in California. This order originated in Kennesaw, Ga. Can anyone please verify where their physical shipment of lightroom originated from? It is listed under you Adobe order history. Just click on the order number. I appologize in advance for asking such a bizzare question.

I know this is an odd question but it will save me a lot of time if someone has the answer.

I have just purchased a macbook pro. I downloaded two sd cards, one via lightroom 4 and the other via iPhoto. I can't find the latter card when I try to import via LR4. In fact i can't find it at all unless i open iPhoto. where is it?

Good Evening, I have just purchased a Macbook Pro, and have downloaded two SD cards of a trip to USA and Canada last September. One via Lightrooom 4 and the other via iPhoto. I tried to import the SD card via iPhoto into Lightroom 4 but could not find it. I tried to find this "folder"? via other means with no success. however when I open iPhoto, there it is, so it must be on the Hard Drive somwhere??? I am new to Apple having decided to jump ship from Windows. Would be grateful for any help.

iPhoto is a - like Lightroom - Photo Manager. It's a database. Like any db to get data out you have to export it.
File -> Export
and in this case set the Kind to Original.
iPhoto is a $15 app, LR is somewhat more expensive. As they both want to manage the photos there's no good usage scenario where you use both. Pick one horse and ride, essentially.
This User Tip
https://discussions.apple.com/docs/DOC-4921
has details of the options in the Export dialogue.

Converted to Lightroom from Elements 5

I installed the trial version from a link found in a message on this forum and imported from Elements 5. Luckily, I only had something less than 3000 images loaded into Elements and hadn't done serious tagging on most of them. I decided to use this trial version of Lightroom because I only decided yesterday to switch from Elements to Lightroom and ordered the shipped version so, being impatient, I would have to go with the trial version tomorrow anyway.
How did the import go? Well, not perfectly. It went well until the end when Lightroom crashed just after it finished importing. I wasn't even touching the computer when it did that. However, when I brought it up it looked OK.
For some reason it decided to have some of my keyword tags nested and some not. In other words, the same tag would appear nested under something and not nested. I had no idea how to merge tags (surely this is something one would want to do?) so I think I ended up losing some tagging, but I can live with that. Some other tags had lost their hierarchical structure but at least weren't duplicated.
Folders also had lost their structure but that looks to be just an issue of dragging and dropping to fix it. They aren't physical folders in Lightroom.
My most serious issue for me is the capture date. Elements supported not knowing the day and/or month. They are coming in here differently. July 1952 is June 30, 1952. I had previously checked and Exifer does display just what I entered in Elements: if only the year, then only the year, if the month and year, then the month and year. This is not coming over in Lightroom.
I have thousands of slides we are scanning and I almost never know the exact day any slide was taken. I'm lucky to know the month. I was overjoyed that the capability existed in Elements to specify what you do know and not have to make up more that you don't know. I don't know how that is actually stored in the exif info, but like I said, Exifer did understand it.
Any suggestions about what to do? Elements can't simply have used the last day of the month before or the last day of the year before because surely you could specify those dates explicitly.
I'm going to have to get used to working with Lightroom. I was able to do things pretty quickly in Elements. Lightroom has a lot of stuff displayed on both sides and I have to figure out how to move around quickly. In paricular, the metadata area doesn't stay put to type in location, for example. The use more metadata fields and not just tags is one of the major reasons I am switching to Lightroom. I have lots of tags as well. I guess recent keywords are going to be very important.
So now I have to go read the help, which so far doesn't seem very helpful.
I had played around with Beta 4 so I know something about Lightroom.

Can't be physical folders because they came in structured incorrectly compared to my disk. OK, they are physical folders in the sense that they contain what the corresponding physical folder contains but they do not need to have the same structure as your physical folder system.
I was able to drag a couple of folders into the same relationship as my physical structure and it didn't do anything to my actual file system. Hum. I'm going to have to play around with this. The help is not very good.
Version sets did not survive together in any way. Stacks seem to be stacked. I had more version sets, though. I guess I stack them.

I have been exporting lightroom webgaleries to my iweb site without any problem. Suddenly I get the error message "finder can't complete the operation because some data can't be read or written" - error code -36 - thoughts?

i have been exporting lightroom web galleries to my iweb site without any problem. Suddenly I get the error message "finder can't complete the operation because some data can't be read or written" - error code -36 - and the move to the sites folder on my idisk fails..... thoughts?

Try this community: MobileMe on my Mac: MobileMe: Apple Support Communities.
And you can continue to use iWeb for some time to come. The following will explain:
It's now confirmed that iWeb and iDVD have been discontinued by Apple. This is evidenced by the fact that new Macs are shipping with iLife 11 installed but without iWeb and iDVD.
On June 30, 2012 MobileMe will be shutdown. HOWEVER, iWeb will still continue to work but without the following:
Features No Longer Available Once MobileMe is Discontinued:
◼ Password protection
◼ Blog and photo comments
◼ Blog search
◼ Hit counter
◼ MobileMe Gallery
All of these features can be replaced with 3rd party options.
I found that if I published my site to a folder on my hard drive and then uploaded with a 3rd party FTP client subscriptions to slideshows and the RSS feed were broken. If I published directly from iWeb to the FPT server those two features continued to work correctly.
There's another problem and that's with iWeb's popup slideshows. Once the MMe servers are no longer online the popup slideshow buttons will not display their images.
Click to view full size
However, Roddy McKay and I have figured out a way to modify existing sites with those slideshows and iWeb itself so that those images will display as expected once MobileMe servers are gone. How to is described in this tutorial: #26 - How to Modify iWeb So Popup Slideshows Will Work After MobileMe is Discontinued.
In addition the iLife suite of applications offered on disc is now a discontinued product and the remaining supported iApps will only be available thru the App Store from now on.
HOWEVER, the iLife 11 boxed version that is still currently available at the online Apple Store (Store button at the top of the page) and those copies still on the shelves of retailers will include iWeb and iDVD.

I cannot open RW2 stills images from my new Panasonic GH4 in Lightroom 5.4, Raw 8.4 or DNG conveter 8.4. Thet do not open in the CC version of Lightroom or Photoshop either. when or how can I resolve this?

The only way at this point I have found to open the files is the SilkyPix software that came with the camera. I have sent SilkyPix an email to see if they will offer a DNG conversion option. At this point only jpeg or tiff is the available option.
So I export all the files out (unaltered) from SilkyPix to tiff, then import into Lightroom 5.4 as DNGs.

photogetgo wrote:
True, and I did contact them about offering a DNG export option which I think would be a good move in any event as other raw for,mats are offering that for future file opening protection
That would solve the issue if they could export the raw data as a DNG. But that's unlikely. They probably don't want to provide you the option of using another raw converter (for whatever silly reasons). It appears they offer the option of saving a DNG of the rendered not raw data but that doesn't buy you anything. Bottom line is, you have to wait on Adobe to update the proprietary raw format that has no reason to be proprietary in the first place. The optional JPEG most cameras provide isn't proprietary and everyone has access to that data the day the camera ships. But for some politically stupid reasons, the camera manufacturers don't do this with the raw data and we all get to wait on every other company who's raw converter we'd like to use to spend the time and money to update the format. It will eventually happen, begging the question why the camera manufacturer's do this in the first place.

I want to cancel the purchase order :Order Number: 13111072125, And I want to buy a Lightroom 5

I want to cancel the purchase order :Order Number: 13111072125, And I want to buy a Lightroom 5

Why is this difficult to cancel the purchase?, Many of the choices I do not know what a select? I can not deal with the difficulty of having a website to retrieve my money! ..
This information can purchase everything that you ask !:
Order Number: 13111072125
Order Date: 04 October 2014
Shipping Address
tariq alkhabra
hail ST20
saudi arabia
Hail 9666
Saudi Arabia
504355777
[email protected]

Lightroom 4 on a MAC and Fujifilm X-Pro1 - can't read the RAF files

When I open the import dialogue the thumbnails are greyed out with "preview unavailable for this file". I continue with the import, which fails, and the message that comes up is a list of the files and "The files are form a camera which is not recognized by the raw format support in Lightroom. (10).
My Lightroom 4 is an upgrade from Lightroom 3 (I upgraded because I thought the issue was with the versio of lightroom I was running).
Is anyone else having issues with RAF file support?

Wow. Not the answer I was hoping for but at least i know know I have to return this camera. I am a little surprised that Fujifil would ship a camera when the raw format can't be utilized. Thank you for poiting me in the right direction Dorin.

Lightroom 4 book problem

Hi, I just paid for Lightroom 4 after running out my trial and discovered a problem in the book module. I was editing a photo in CS5 and the book went squirrelly. Duplicated parts of pages and inserted them overtop of others which deleted the original pages . When I started replacing the photos they would show for about 10 or 15 seconds then disappear. When I click on the blank page, the film strip goes to the photo I wanted in there but it's not visible in the book page.
I downloaded the patch, rebooted my Mac and the same problem occurs. Anyone know the fix? iMac, 4 gigs RAM, importing jpegs from external drive but exporting them first from iPhoto.
Ben

Please notify Blurb with your complaint. They will respond, however it may be slowly during the holiday season.
I'm not defending Blurb in the slightest as I have ordered the same book three times now and am waiting on a single good (read correct) copy. They have at least admitted fault and credited my account for the charges. I hope to some day have a "good" copy of my book. The last one I ordered is being shipped to a relative some 2,000 miles from me and I won't know the condition of the book until after the holidays to see if it was printed correctly. Had to take the chance as it was intended as a present. Can only hope they got this one right!
But do contact them via customer support and give them a chance to make good. They offer everyone that option!
Good luck and keep your fingers crossed for me...
Stumped

Lightroom 4 importing causing program to crash.

Lightroom 4 will not import files. Windows 7 pop-up states; "there is a problem with this program that is preventing it from running correctly will check for solution". "Windows failed to find a solution must shut down program now".
This prevents the import page from loading or working and no images can be imported using usb or SATA connections. Was able to use computer's built-in card-reader to read from Sd and compact cards, those were able to run in the import window only because of preference setting. "when a Memory card is installed import files" (preference-setting). Any other means of importing files, the out-come is the program crashing and being shut down. All other functions outside the import menu seem to be working. Deleting all catalogs and then using the default catalog setting, failed to clear issue.
System info: Windows 7 64-bit, Intel i7 cpu, 16 gigs of ram, 4 one terabyte hard-drives.
Solutions tried. Removing Lightroom 4, all catalogs, then running defrag, registry cleaner, before attempting to re-installing lightroom 4. Removing lightroom 4 and installing lightroom 3.6 fails to fix issue. Removing all Lightroom products from hardrive,Including the windows program folder, windows programs data folder. Then rebooting re-running defrag, registry cleaner and re-installing lightroom 4 fails to fix importing issue. No way to contact support and links to user group fail to take me to correct user group. Question with the lead as lightroom 4 importing causes program to crash. Takes me to everything but lightroom solutions! Now this takes me to photoshop user group which has nothing to do with lightroom. With lightroom 4 in the question itself, I get everything but lightroom solutions!

Camera raw is built into Lightroom. It is the engine that makes the corrections within an image. You might not see as a seperate program, like earlier versions of Lightroom. Or having to launch it in a new window to work in camera raw. In version 4 of Lightroom it was made seamless and built into Lightroom.
Lightroom 4 was installed in the admin log-in window. I have all useage rights to any file lightroom creates or adjusts. I am thinking that the Photoshop CS6 beta created some working problem within Lightroom 4. Now that the beta-test program is over, I think the problem is a result of removing Photoshop's last build, before the public beta was released. I do hope, Adobe is working on a solution for people experiencing importing problems with Lightroom 4. I am just grabbing at straws here, trying to find something that will work. I think the problem will go away once computer has the new camera raw build 7.0 that ships in Photoshop CS6. With so many versions of camera raw installed on the computer, I think Lightroom is having issues as a result. Let's hope a patch is in the works, Lightroom 4 is useless if importing files doesn't work correctly.
B&H photo is taking pre-orders for the creative suites, right now. The only way to get support is by purchasing a subscription. Otherwise it is a $35.00 per issue fee. So, I am not sure of what upgrade path I will take. Not loving the cloud at all, with this year of Hackers, I seriously doubt that any cloud will prove to be safe to use. Why would, I want to post my hard work to a cloud where anyone can steal it? But that is a different topic.
For right now the only way to import is by creating an empty folder on the same hard-drive that Lightroom resides on. Setting up auto-import in Lightroom Pref. file to check that empty folder. Folder has to be empty to set up. Then dragging image files into that empty folder. I discovered that Lightroom 4 will not open or look in sub-folders for images. Which means you lose keeping a day's worth of shooting seperate from other folders. Where Lightroom version 3.6 you could.There was a second auto-import that worked, with my built-in memory-card reader. Where in the Lightroom pref.file you can tell Lightroom to auto-import, when a memory-card is detected. ( this is the least viable option, because more memory card become damaged removing and reinstalling them). These were the only two methods, I could get images into Lightroom 4 and prevent Lightroom from crashing. Might have to go back to using Nikon NX to import my images and using Bridge to catalog them.

Lightroom,Nik plugins and color spaces

I'm having an issue and not sure who is holding the smoking gun. I have the Nik ultimate collection installed which covers Lightroom and Photoshop CS5 extended. I work primarily in Lightroom and apply most corrections globally but occasionally i need to do localized adjustments so the photo gets shipped off to Photoshop. Here's a typical scenario:
1) From Lightroom edit in Dfine 2.0 for noise - as copy with Lightroom adjustments which gets copied as a tiff.
2) From Lightroom edit in Viveza 2 - as original since we're now working with a tiff and I don't want a copy for every single thing I'm doing.
3) Edit in Photoshop
Now there's two issues at this point:
1) The edits do not show up in the Lightroom history - it's like nothing happened.
2) Photoshop will complain that the assigned profile is sRGB. Really?
#1 is a PITA because if I want to rewind I have to start all over since there's no history - what exactly is responbsible to set an edit as history? Lightroom or the plugin?
#2 is by far the most serious as it degrades the work in a seriously bad manner. I mean, WTH - I'm moving along in ProPhoto Ferrarri space and all of a sudden - *boom* - I'm running in sRGB moped mode.
I looked at edit->Preferences->External Editing -> Additional External Editor and indeed when I select the Nik plugins from the combo box preferences the default for the plugins is sRGB. I can change to ProPhoto and quit. I repeated this for each plugin assuming that somewhere the setting was remembered. Nope LR acts dumb as a rock and shows sRGB as the defaults for all except the currently selected plugin.
So my questions are:
- who's gonna own up to the problem - LR or Nik?
- how can I work around it?
- how can I make LR remember the settings? Not a registry key nor INI file in sight to set them - so where/how are the plugins tracked?
Thanks for any help!
Jon

Jon,
The User Interface for changing how external editors are invoked is about as smart as your average chunk of granite.
After you change the Color Space to the one you want, you have to click on the Preset box and choose "Save current settings as new preset...". Not exactly intuitive, but there you are.
Hal

Printing in Lightroom Produces Wrong Colors

I have searched these forums and found a couple of topics that have to do with incorrect or wrong colors being printed by Lightroom but none of the suggestions proposed seemed to help. So, I think that I have something else going on that is causing me problems.
The vital statistics: I am using Lightroom 1.4.1 on Vista Home Premium with an HP C7280 All-in-One printer. The pictures I am trying to print are DNGs converted by Lightroom. When printing in Lightroom, I select the option to have the color managed by the printer.
Basically, any picture that I print from Lightroom looks darker than the original. So, I tried a couple of different tests to try to find out what is going on. I exported a picture to a jpeg and printed that with the Microsoft Office Picture Manager and it printed fine.
I was curious what would happen if the photo was printed from Photpshop CS3. So, I created a copy of the DNG file from Lightroom and edited it in Photoshop. I printed the picture from Photoshop with the color set to be managed by the printer, and Photoshop also printed the photo with a dark look. I then changed the Color Handling to "Photoshop Manages Color" and the Printer Profile to sRGB, and the picture printed perfectly.
In addition, I tried printing jpgs from Lightroom, and I got the same dark results. Any suggestions as to what is going on will be very much appreciated. Thank you in advance!
Michael

Unfortunately, Lightroom cannot print to this specific printer without tricks. The reason is that HP does not provide color management in the driver (which is why you have to use sRGB in Photoshop - shudder!) and does not provide icc profiles for it. This is HP not providing good drivers for their consumer-oriented printers, and Lightroom expecting at least reasonably modern printer drivers. Photoshop will print to anything by using the working space fall back that really is a hack. Unfortunately, Lightroom does not provide the same hack. In your case, there is a trick you can use, which is to find the "HP color Laserjet RGB" icc profile that HP ships with their laserprinter drivers. It is just an sRGB profile masquerading as a printer profile. If you use that in the profile field in Lightroom, it
should work.

Embedding Lightroom HTML gallery with Dreamweaver

I'm new to Dreamweaver and have used it to build a portfolio website. I've created HTML image galleries using Lightroom and would like to integrate these galleries into my existing page design. Lightroom generates an Index file, as well as Context and Resources folders. I've seen an earlier discussion about using LR to upload the galleries to my host, then edit the HTML to link the gallery pages to my other web pages. This strikes me as cumbersome for two products made by a single company.
What I'm after is a clear answer about if I can embed these HTML galleries quickly and easily into my existing page design? My other solution is to use the Airtight SimpleViewer gallery, but since it's using Flash, my galleries won't work on Apple mobile devices.
I'm using Dreamweaver CS5.5 and Lightroom 3.
Thanks in advance for any help.

You can't edit a flash gallery with Dreamweaver.
To make changes to the LR flash gallery you would require a copy of the original fla file and a copy of Flash to edit it.
The index file you see is the one that loads the flash player to play your gallery. The message is what is seen in a browser that doesn't have flash player installed.
You can make amendments to the gallery itself by changing the xml files, although the changes you can make here can also be made in LR itself so why bother?
You can embed the gallery itself in your own html page. Using insert, media and then finding the gallery.swf file. As long as you then upload everything in the correct locations (including the scrippt files abd the new html file in the same folder structure it will work.
There are other flash galleries that are far easier to embed available. However in order to make serious changes to flash galleries of any type you will require the original fla file and most designers are not going to give you that! Adobe does give away the fla's for the galleries that ship with PS.

Lightroom and RAW

Hello ALL, I'm on a G5 Mac, latest version of lightroom, running OS 10.5.x 2ea 1TB HD's, 4Gigs RAM.
I've been using Lightroom 1.x since Beta. I love the app. I also shoot both RAW and jpeg with my D300. Previously, I was using a Finepix S2 Pro and shot in the RAF format. Those RAW files looked great. However, my RAW files from the D300, when I import them with the jpeg, look dull and soooo boring. is there a way to change that so they look more like the jpegs with regards to color, etc instead of the true RAW image. I'd rather just shoot raw, and forget the jpegs but I don't want to have to go through all these steps.
Thanks
J

One answer to your problem would be to use Nikon Capture NX2 for Development. I do this for a number of images that present development challenges, or where I need to do some very finite local corrections, etc. I then export the image (or images) as a jpeg and import into LR using 'nx2'to the original filename.
If I need to rework the image, which has been saved as a NEF after development in NX2, I simply go to the jpeg image in Explorer (R menu in LR)find the original filename.NEF and then (R menu) open with NX2 do the work and hit save. I do not know what the equivalent would be on a Mac.
If any changes are made, then synchronize that folder in LR.
No other converter will will replicate the images that NX2 produces from a D300 initially--or faster. You can come close with the right preparation, a preset or two, perhaps a camera calibration, but it will take work and to replicate what NX2 will do.
And if you want to do some serious work on your images, NX2, although a bit slow with a few operations (depending on your machine specs), will allow you to do serious local corrections, and other specialized adjustments far easier and faster with greater control than LR 1.41 or LR2 at this point in time-- may be a different story when it LR2 is optimized and all the local corrections and other new features revealed when it ships.

OT Lightroom shipping

Similar Messages

Maybe you are looking for