Lack of LAB and CMYK support in Lightroom is plain dumb

There is a lack of consistency in Lightroom if it allows you to elect to edit an image in Photoshop but then it can't follow through and display either a LAB PSD or a CMYK PSD. Both these file types are widely used by Pro-photographers. Afterall there is a whole bunch of stuff that's easier to do in Lab or CMYK rather than in RGB. The lightroom development team seem to suggest that photographers shouldn't be doing anything more advanced than Lightroom can handle. Well if you look at pre-print sharpening Lightroom is still awful - LOW/MED/HIGH just doesn't cut it and isn't at anything like pro level. To get any sensible preprint sharpening you've almost gotta go to photoshop. For many images sharpening is best done on the L channel of Lab (along with a whole bunch of other adjustment layer corrections). Most people like to keep these layers and so returning a master file to RGB just isn't an option. Sure there is no further need for editing such an image in Lightroom, but as part of Lightroom's function is DAM then its fairly essential to be able to at least preview all your image files - to know where they are and what you have.
Its just no good boasting about Lightroom's ability to search through images using metadata etc if ultimately it can't find and display your -finished- image versions 'cos they just happen to be Lab or CMYK PSDs.
If Adobe Lightroom team are promoting Lightroom as a pro-photographers tool them you gotta listen to how pro-photographers work and not get lost in your own ideology based rhetoric of keeping Lightroom pure. I haven't yet found two pro-photographers with identical "pure" workflows.
Come on Adobe - we don't want to edit them - we just want to be able to preview them in Library ;-)

Have to say as a working professional who earns his keep from doing raw conversions, proof prints, cutouts etc Lightroom's lack of CMYK support is very much a pain in the a**. I'm not asking for a full set of CMYK editing tools - I've got those in Photoshop thanks very much.
What I am asking for is at least the ability to round trip files from Lightroom into Photoshop, convert to CMYK and reimport the CMYK version into the catalog alongside the RGB file from which it originated and then to allow me to open the original CMYK file back into Photoshop without any tweaks being applied by Lightroom. This would allow Lightroom to really fill the role of a DAM in our studio and allow us much simpler workflow tracking than at present. As things stand we have to save the files in separate locations from our RGB versions on our server and then catalog them using another application.
Come on Adobe please listen to your professional user base as I know I'm not alone in these requiements and the studios that I've shown Lightroom to have all ended up asking the question "What about the final CMYK versions?"
BTW I'm in full agreement with Ian on the other points and without sounding snotty to Don - who I have read many interesting and sensible posts from - maybe if you don't want to cover this ground again just walk a different direction and leave those of us who do NEED this feature to discuss the best way of implenting it. I have also sent this request to Adobe so I'm not just a moaner who sit's here doing nothing about the issues that affect me.
Cheers for now.
Jason Hicking
Replica Imaging Limited - UK

Similar Messages

CMYK ICC profile support in Lightroom: Workaround?

Ok, I know this is not the first time someone has brought this up and I know that Lightroom doesn't internally support CMYK printer profiles, and I'm not expecting it to do that given that the documentation specifically says it doesn't work, and it in fact doesn't work.
I'm using OS X (Lion). I recently profiled a Lexmark C543dn color laser printer with a ColorMunki Photo and the profile works great with Photoshop's "built in" RIP/CMS/whatever, but I can't get ColorSync in the printer settings dialog to recognize the profile. If I use the ColorSync Utility to force the profile on the printer, it also doesn't work.
What I would have expected for colorspace conversions when printing (from lightroom for example) is something like:
Melissa RGB -> ProPhoto RGB (or sRGB, Adobe RGB, whatever, using internal lightroom stuff)
ProPhoto RGB -> LAB (using a generic ProPhoto RGB profile that comes with the system or the software pkg)
LAB -> printer native CMYK (using the custom printer profile I created)
native CMYK data -> printer
So I don't understand why Lightroom or whatever application doesn't "tell" the printer driver that it's getting data in ProPhoto RGB (or whatever) at which point the driver should convert to LAB (or whatever PCS is specified) and then to printer native CMYK with the custom profile.
Does anyone know of a way to make this happen?

I'm not a professional, only a hobbyist, so it took me a little longer, but I also have the impression that the new Preview ignores ICC profiles.
I noticed it when moving images between my iBooks built-in and my external Eizo screen. Since the gamut of the second is much larger, images appear rather different on the two screens. In Tiger's Preview, this resulted in colors changing suddenly during the move, when the center of the image passed from one screen to the other. This effect is gone and yes, the images are over-saturated on the 'good' screen.
Jethro555, could you find a solution to the problem?

Lightroom 3 and tethered support...

I work with many professionals on a daily basis and more and more find they like Lightroom. The workflow is smooth and intuitive and the features are useful and effective. The most common complaint however, is the lack of direct tethered support. Reading John Nack's forums some time ago it was noted that the 'Import' feature was an effective workflow. I couldn't disagree more and many many pro shooters fault Adobe for not being able to use the app in a studio environment. Are we finally going to see direct tethered support in Adobe Lightroom 3? Workarounds and plugins are less than ideal.

carson.jones wrote:
Workarounds and plugins are less than ideal.
Well, what exactly would you be willing to pay for this functionality? Now, take it for granted that simply clicking a mouse button to fire the camera and make a capture ain;t enough...I shoot with a Phase One 6x4.5 camera and a Phase One P65+ back. Just clicking the shutter doesn't interest me all that much. I want to be able to set the F stop and shutter speed as well as ISO on the camera. It would also be nice to be able to adjust the user preferences for custom functions and be able to set up and fire a whole series of either HDR brackets or a series of focus brackets...
Is this the sort of functionality your pro would expect/want?
Then you are in for a world of hurt...
The system level support for thee functions are a big investment of engineering support per camera. Exactly which cameras would you expect this sort of support for? Pro level cameras? Mid-level cameras? ALL cameras? Camera Raw/Lightroom support over 230 cameras at this stage (more cameras added each version).
Do you expect this professional level support to be free? What would you pay for this? What would the pros you work with it be willing to pay? Did I mention this would be a massive engineering effort? What features in Lightroom 3 would you be willing to give up to get this sort of hardware support in Lightroom?
Just asking cause what you are asking for has some pretty massive ramifications...

Is there Camera RAW support for Lightroom 4.4 and Canon 7D Mark ii?

I need Camera RAW support for Lightroom 4.4 and Canon 7D Mark ii. Is there a Camera RAW version for me?

Thanks for your help. I checked out DNG on YouTube and understand more
about it. I downloaded the DNG converter and transferred in files from my
camera. Then I imported into Lightroom. It works! Thanks again.
On Wed, Nov 19, 2014 at 5:56 PM, Jeff Schewe <[email protected]>

When will Lightroom and Elements support the Nikon D600?

When will Lightroom and Elements support the Nikon D600? In the meantime is there a workaround so the D600 raw files can be exported to Lightroom or am I simply out of business until Adobe develops the needed patch?
As best as I have been able to figure out I may as well rebox the 600 and go back to my older, supported camera, until whenever.

A: What were you using before your precious D600 showed up today.
A D90 with good glass.
Nikon 70-200 f2.8, Nikon 24-70 f2.8, Voigtlander 58 f1.4, Tokina 11-16 f2.8.
Now I need to get a good FF wide solution for the D600.
Trigger on the D600 is much more stiff than my D90 so I'm having to press down a bit harder to get the AF confirmation. Just need to get used to that I guess.
FYI, JPG files right out of the camera are looking good.
B: Don’t you think Adobe wants to sell you the next generation product/upgrade to accommodate all of our insatiable photographic pursuits???
I had been using Apple's Aperture and switched to Lightroom a couple of months ago. I thought the price was actually quite fair for the power of the LR software. I did have to updgrade my computer's RAM....
C: Have a nice glass of wine tonight and enjoy your $2K investment. I’m personally looking forward to savoring a next generation photographic paradigm.
We did enjoy some vino last night! I was thinking I would possibly jump ship to Sony A99 and just switch to all Zeiss glass with autofocus, but I'm not convinced that the EVF is for me, and I'm really not a video shooter, mostly just landscape and real estate. Also, I the Sony turned out to be priced a bit too high for me personally in comparision to the D600.
Buenos Dias!
EB

I am having problems launching the standalone version of Lightroom 6 after I have gone through the install and activation process? Lightroom starts to open but "hangs" before any photos in the catalgue are displayed. I have contacted the chat support twic

I am having problems launching the standalone version of Lightroom 6 after I have gone through the install and activation process? Lightroom starts to open but "hangs" before any photos in the catalgue are displayed. I have contacted the chat support twice but they have not been able to fix the problem.

I went through the activation process yesterday and shut down my PC when I went to bed last evening. When I got up this morning and turned my PC on and then started Lightrom 6 (I upgraded from version 5) it started to launch but then just hung and became "not responsive". I I then uninstalled and then reinstalled the product today but the same thing happened. What is weird is that when I install from the standalone file I downloaded when I purchased the upgrade it looks like it's downloading the software again over the Internet? I have been having these problems for the last four or five days. I have contacted the chat support folks twice and they were able to get it working but whatever they did did not last as the problem reappeared again once the PC was shut down and then started up again.

Printing with a LED Colour Laser Printer - No CMYK support?

Greetings.
I bought an Oki A3+ printer (C9655) three weeks ago to output a large amount of images for the editing and proofing of a book project. The results I am getting are pretty bad as Lightroom cannot see their profiles so they cannot be loaded (they can be seen & loaded in Photoshop CS3 or InDesign CS3). Their technical support is saying that Adobe Lightroom doesn't appear to support their profiles which are CMYK. Although the results are pretty good via Photoshop or InDesign, I really don't want to have to import 100's of images into another app just to print a decent quality preview hard copy.
What I expected would be straightforward in printing whatever DNGs I select from a collection via the Print module is apparently not possible. Is it really true that Adobe won't support CMYK in Lightroom? And if so why? There are threads requesting CMYK support that go back to Lightroom 2 Beta.
What about printing cards on thick board? What about printing a preview of a book project? It doesn't have to be inkjet RGB all the time. (Admittedly quality really looks "photographic" on inkjet but at too high a cost for previews).
LED Colour laser printers like the one I bought using 4 blocks of toners are becoming more accessible & popular. Surely there will be an increasing amount of users who expect like I do to be able to output directly to the printer without convoluted workarounds.
Adobe, could you please get Lightroom to talk to Colour Laser Printers that work in CMYK and manage the colour? Getting the printer to manage colour really gives poor results. The colours are pretty good but the shadows and blacks seriously lack density making the result just unacceptable. I am frustrated I have not been able to do the outputs I bought the printer for and it appears that the solution lies in Adobe supporting CMYK outputs.
Any help would be greatly appreciated in getting a solution soon.
Thanks.
(Mac 10.6.8)

Thank you for your prompt response Andrew
Please forgive me if I wasn't clear. I don't actually have any CMYK files in my catalogue. Nearly all my files are DNG's that were imported from RAW (if they are edited in Photoshop, it's usually in ProPhoto RGB). What I want to do is output collections directly from Lightroom to paper on the Oki. With hundreds of images to print, I really don't want to use Photoshop. The way I understood it, the printer needed CMYK data to be able to print an image but I think I got it wrong (maybe because Oki only supply CMYK profiles?).
From what you say and from looking at the printer settings options, there must be a way to get Lightroom to send data over to the Oki in a language it fully understands (which I think is by letting the Printer manage colour). I have experimented with different options in the Printer settings, but so far all the results are wrong. I'm now looking at loading profiles in the "Graphic Pro" settings. It looks like they need to be loaded with an installer app and it looks like the only way to be able to use them is by storing them on the printer - which unbelievably means paying over £300 for their hard drive!
Hopefully there is a simpler solution. I'm getting the impression the printer has great capabilities but I'm missing out on them because I can't work out how to get the settings right. What I thought would be pretty straightforward (printing a preselection of images from Lightroom) has turned into weeks of complication and frustration.
If you have any more advice to spare, I would be delighted to read it!
Thanks again.

MacBook Crash and Apple Support

Not sure if anyone else has had this experience. First, I am a brand new Mac user. Bought the new MacBook Pro i7 with 8GB of RAM as a switch from my PC laptops.
Any other big crashes out there? Just wondering if there is a systemic hardware issue?
I had the new laptop for a total of 4 days before it crashed hard. on the first full day of use, it started crashing with the veil of grey and the message that a serious error had occurred and I needed to hold down the power button to restart. It crashed a total of 6 times in 4 days (2 days of real use) before I could get to the Genius Bar.
They stated that was obviously not normal and that I should request a new unit from AppleCare, which I did as an advanced replacement. I was hoping to keep my crashing laptop just to get more used to the Mac. However, after the Genius Bar did an archive re-install, the computer immediately crashed twice while in the store.
We then attempted to do an Erase and Install, and the unit would not install the fresh load of Mac OS X. The Genius Bar rep said it definitely looked like a hardware issue since it would not re-install the software, so I had to send the unit back ahead of receiving a replacement.
As for customer service, there was absolutely no urgency to get a replacement laptop to me. It was a customized unit and it is finally due to arrive today, but it has taken 10 days since I ordered my advanced replacement.
I will tell you that this has been a very frustrating and disappointing start to my Mac usage. And customer support could have made that bad experience so much better, but their lack of action and mis-statements actually made it worse.
Sorry, I was hoping for a much better experience. I am still hoping that IF the second MacBook works I can see that I made the right decision.
LewieE

Hi A Brody,
Lemons do happen and while that was a disappointment, the Genius Bar guys did a great job. I will say my expectations were higher for Apple based on everything I heard trying to make my decision to swap from a PC.
The first customer service rep I spoke to when I setup the advanced replacement stated that this unit would be put at the head of the que as it was a replacement for defective unit. The second rep I spoke with said advanced replacements have the lowest priority and it should have been returned as a zero dollar replacement and by him changing it to that, especially since my return unit had been received, would cause it to jump to the head of the shipments. The third person I spoke to said it just had to be processed in the normal 5-7 day shipping replacement and there was nothing they could do.
When a customer has a problem, customer service can make or break that experience. In fact, customers that have had a problem and had a positive resolution to that problem are shown to be more loyal than customers that have never had a problem at all.
Regards,
LewieE

Canon 40D and G9 support

Apple locked down the original 40D support thread which is not a good sign for us Aperture customers who are not able to use our $300 application.
I did find an article that talks about using Aperture with unsupported cameras and I thought it might be helpful:
http://www.oreillynet.com/digitalmedia/blog/2007/09/dealingwith_unsupported_rawf.html
Obviously this is not something any of us wants to deal with for long - especially since Adobe has offered support through Lightroom since September 12th, but it looks like we are going to be forced to find a work around until Apple decides to provide a solution.

Technically, discussing future features that haven't been announced by Apple is against the terms of service for the forum. That might be one reason why 'support my brand new camera' threads tend to end up getting locked.
"Submissions
Stay on topic. Apple Discussions is here to help people use Apple products and technologies more effectively. Unless otherwise noted, do not add Submissions about nontechnical topics, including:
Speculations or rumors about unannounced products.
Discussions of Apple policies or procedures or speculation on Apple decisions."
http://discussions.apple.com/help.jspa#terms
Ian

Panasonic Lumix FZ1000 RAW files support in Lightroom 4

http://blogs.adobe.com/lightroomjournal/2014/07/camera-raw-8-6-and-dng-converter-8-6-now-a vailable.html
The above says that Panasonic Lumix FZ1000 RAW files are supported in camera raw 8.6. I specifically checked before buying the camera. Everything I have ever read on the Adobe website for some 3+ years said that if a file in supported in Adobe Camera RAW, it is also supported in Lightroom. Particularly, the above URL did NOT give any warning about the FZ10000 RAW files NOT being supported in Lightroom 4. I went ahead and purchased the FZ1000, only to find I'm now having problem with Lightroom 4 not recognising the RAW files at all. I'm really annoyed, as I was so careful to check the Adobe website first. WHAT THE HELL IS GOING ON WITH CAMERA RAW AND LIGHTROOM?????

I do appreciate the many RAW file formats being created by the camera manufacturers, as I have had varying cameras with the varying formats, and so am very aware of the whole business of making sure how those formats will fit into my software. And, as already stated, appreciate Adobe's efforts to deal with all those formats.
This whole exercise has been upsetting, and there has been some good advice and info provided in this discussion.
And unfortunately, some input that has been a little too technical and not particularly helpful. I feel that some of the input was a little too critical and didn't recognise that maybe some of us aren't so are highly involved and knowledgeable in Adobe products and the technicalities of how the software works, dot versioning of software, executable coding etc. because we don't need to, and shouldn't have to. I have bothered to learn Lightroom well in terms of its functionality including matters raised by you (eg making LRoom edits visible in other software, knowing that LR is not making changes to the actual files, rather they are in sidecar or xmp files etc.). I have bothered to learn a reasonable amount of computer-related info to understand things in plain English terms, such as "to have PShop and LRoom to recognise my RAW files, I need to have ACR. To have them run on my PC, they must be compatible with Windows operating system version xxx. For many people, this level of knowledge should be enough.
I have NOT said I expect Adobe to get advance copies of file formats from manufacturers; I have NOT said that I expect Adobe to support every new camera model immediately.
The technicalities of the coding and whether Lightroom "uses" the ACR plug in or not is not quite so much the issue, and I don't find the statement that "Lightroom does not use the Camera Raw plug-in" helpful. I don't think it's really right either. Lightroom - one way or the other - DOES "USE" ACR as the ability of Lightroom to recognise files is very much dependent on the version of ACR that you have. LRoom may not use the ACR plug in as PShop/Bridge in the exact same way (eg for the actual editing of files such as exposure, white balance etc.), but Lightroom DOES USE the ACR PLUG IN.... in regard to the file recognition issue.
And Yes.... I made a mistake. Somehow, despite what I thought were good efforts to research the Lumix's support in PShop CS6, Bridge, ACR and Lroom 4, I got it wrong. I will accept that it was my mistake and I'll accept my part in this, but I won't be made to feel that that it's been "totally" my fault, stupidity, whatever.
Thanks to all the people who have provided useful comment and input to my original question and subsequent responses throughout this discussion. I will indeed now consider options like the DNG converter. I was aware of the whole cloud thing, and had been thinking I would upgrade in perhaps a couple of years time (for both Pshop and LRoom) - I'll have to consider upgrading sooner rather than later.

I have installed Adobe Lightroom CC. In the process of launching, a popup appears, that says: "AN INTERNAL ERROR HAS OCCURRED. Cannot create the required folder: /Users/(my user name)/Library/Application Support/Adobe/Lightroom/Develop Presets." So e

I have installed Adobe Lightroom CC. In the process of launching, a popup appears, that says: "AN INTERNAL ERROR HAS OCCURRED. Cannot create the required folder: /Users/(my user name)/Library/Application Support/Adobe/Lightroom/Develop Presets." So even though Lightroom CC is installed, it will not launch. What do I need to do to allow it to launch?

The problem was solved today. Here's the full story. I'm a Mac user. At first I installed Lightroom CC on my iMac (desktop). I had this problem so I called Adobe, and was referred to a "special unit" . After about an hour the tech solved it for me ... we did a screen sharing and she took control of my computer for a loooong time. Because of language difficulties, at first I wondered if she knew what she was doing but she eventually solved it. Although she couldn't explain exactly what she was doing, she summarized it by saying "it was a permissions problem." I asked if I would have the same issue later when I installed it on my laptop (Macbook Air). She said probably not.
But I did. The same internal error popup arose on launch and launch did not complete on my laptop. I tried chat but no joy so I eventually called Apple Care. I had noticed that on my laptop (and the iMac for that matter), that there was no Library folder after my user name. The Apple tech explained that the Library folder is actually there but it is hidden because it's very easy for users to do some very nasty things to their computer by going astray while in the Library folder. The folder is actually there, but they hide it. I did remember seeing that the tech helping me with my iMac had typed the work "Library" while she was controlling my computer. Basically she had activated the hidden Library folder so she could open the path that Lightroom was trying to follow to create that "Develop Presets" folder. For some reason, the inability to create that folder in the launch process was preventing launch from being completed. The Apple tech said she didn't actually have to do that and activated the Library folder by use of the Go selection on the menu bar. Anyway, once that complete path was replicated and opened, the next step was to go to the Lightroom Permissions field and add my user name to the user categories already there and enable "read and write" permissions to my user name. Once done, I shut down my laptop, and then rebooted. I launched Lightroom and then boom, voila, heavens to betsy, etc. it launched and suddenly a dismal weekend turned into a great one.
I am not a geek, so I hope this makes some sense. I also hope Lightroom launches again tomorrow and beyond!

Scanner NEF not Supported by Lightroom 2?

I am trying to decide on some workflow options for scanning negatives with a Nikon scanner. It has been suggested that raw image data from a Nikon scanner can best be processed by having the scanner output in NEF format and using Nikon Capture NX 2 as a raw editor. The basis for this suggestion is that ACR does not support scanner NEF. Apparently, neither does Lightroom 2, or so I am told. Having reviewed comments in Adobe forums, some seem to hold the opinion, often vociferously, that scanner NEF is not truly raw data, is a complete waste of time, and scanned images should be output as TIFFs rather than NEFs. Also, despite the official line that scanner NEF is not supported, scanned images that were output as NEF, and saved as NEF images, seem to be working just fine in Lightroom 2, although I haven't tried a full processing workflow on them yet. (In the interests of full disclosure I hold out the possibility that I may have somehow converted these images into a conventional form of NEF at some point after scanning).
I apologize for that lengthy introduction. Here are my questions: (1) How is scanner NEF different from "true" raw image data; (2) what are the consequences for optimization of scanned NEF images in Lightroom 2 -- am I simply using Lightroom tools without getting the full benefit of processing "true" raw information, as in the case of TIFFs and JPEGs; (3) what does it mean that Lighroom 2 and ACR do not support scanner NEF anyway since I am (apparently) able to open and process them in Lightroom 2; (4) if Lightroom 2 does not fully support scanner NEF, is there anything to be gained by outputting to NEF (rather than TIFF) and using Nikon's proprietary RAW editor (which I am told does not officially support scanner NEF either, but still works) instead of LIghtroom 2 for NEFs?

Short answer - scan the images as TIFF and make life easier for yourself.
Longer answer:
1. A true raw file is still in it's mosaiced form whereas a scanner NEF is a fully rendered TIFF with a different extension
2. Same as editing a TIFF, PSD or JPEG. The adjustments are parametric and therefore only readable in Lightroom and ACR. In order that you can actually open them into Photoshop or another editor it will be necessary to export the files as TIFF, PSD or JPEG.
3. It means that they aren't treated as true raw files. Refer to above.
4. There is nothing to be gained.

Two related questions: ColdFusion 10/Java applications and J2EE supported servers

I have two related questions:
1. CF10 and integration with Java Web applications
We have a couple of Java applications running on JRun and interfacing with CF9 applications. The JRun clusters were created through the JRun Admin and, apart from lack of Axis 2.0 support, have served us well for years now. And, as would be the case, the ColdFusion9/Java/Flash application is a critical public-facing application that the business uses for bidding on projects.
It appears that with ColdFusion 10 on Tomcat, we will not be able to run those Java applications on a Tomcat-CF10 JVM cluster. Is this correct? IF so, what are our options?
2. J2EE Application Servers supported by Adobe for CF10
Which of these is correct?
A. This URL (http://www.adobe.com/products/coldfusion-enterprise/faq.html) states "ColdFusion 10 supports IBM® WebSphere, Oracle® WebLogic, Adobe JRun, Apache Tomcat, and JBoss."
B. This URL (http://wwwimages.adobe.com/www.adobe.com/content/dam/Adobe/en/products/coldfusion/pdfs/cf1 0/coldfusion10-support-matrix.pdf) states:
"J2EE application servers: WebLogic Server 10.3, 11.1, WebSphere Application Server 7, ND 7 JBoss 5.1, 6.0, 7.1.0"
I *think* "A" above is wrong re. support for Adobe JRun. It does not specify a version of Apache Tomcat unless it is simply referring to the custom version the comes with CF10.
Option "B" above shows no support of Adobe JRun or 'standard' Apache Tomcat.
Thanks,
Scott

Question 1 above was answered: "No support for Java web applications under CF10's custom version of Tomcat"
Question 2: No answer yet: Is Apache Tomcat (NOT Adobe's customized version) supported for CF10 J2EE deployment? I do not see any installation instructions on how to install CF10 on Apache Tomcat 6 or 7.
Is anybody using Apache Tomcat as their J2EE app servers and, again, NOT Adobe's customized/limited version?
Thanks,
Scott

How to select matching RGB and CMYK colors

Starting from scratch for a client, how do I select matching RGB and CMYK pairs?
Say we find a nice red colour in RGB for screen use, how do I then find the correct CMYK for print? And what assumptions do I have to make when doing this, if any?
Would it be the same for the other way around (choose CMYK first for print and then find the RGB equivalent)
Is it more sensible to start with a Pantone colour and then find the RGB and CMYK equivalents for that?
Many thanks
RobbieG
(I'm working with Ai, Ps and Id CS6)

Yes. Better to start with Pantone reference books where you are viewing the color in a reflective environment. As already mentioned, color on the monitor can be deceptive. And, I think the others are basiclt saying that you should have everything calibrated and use color management policies in your apps. There is a way to find CMYK equivalents using Photoshop's color palette. Let's say you have an RGB Red as the foreground color in Photoshop. If you double click on the swatch you will get Photoshop's color palette which lists the RGB percentages, CMYK percentages, LAB percentages, and HEX web color for that Red. You can go further and select "Custom" and the Pasntone Spot color palette opens and gives you the closest Spot color value for that Red. This however, depends on your color settings. That's why I recommend you start with the Pantone swatch book and get the perecentages of CMYK from their formula guide which is set to industry standard color.

RAW and JPEG cataloging in Lightroom?

I use Lightroom to catalog and develop my RAW files, and then create JPEG's for typical uses. But I don't end up with the JPEG's in my Lightroom catalog, and I think that would be helpful finding the ones I want, the way I do with RAW files.
Is there a way to catalog both my RAW and JEPG files with Lightroom?

For online JPEG's I use Save for web and devices in Photoshop. For large JPEG's for publications, I convert to SRGB and use Save As from Photoshop. For images I am going to print, I also save TIFF's.
Probably due mostly to lack of knowledge on my part, I seem to be able to "milk" better final images if I send them from Lightroom to Photoshop in Adobe ProPhoto format, after initial "developing" in Lightroom. I may be overkill, but I think I can tell a difference doing it that way with my NEC PA301WSV monitor.
I like some of the Photoshop tools better than the Lightroom versions, like the spot removal tool, and the clone stamp. There are also several other tools in Photoshop that I use from time to time. On the other hand, there are some tools in Lightroom that I like better, like the graduated filter and the adjustment brush.
I've also seen several discussions recommending not sharpening the RAW files in Lightroom, and waiting to do the sharpening in Photoshop. I haven't explored that fully to decide if I think that has merit.
My entire workflow may be a screwy abnormal mess, but I'm totally open to suggestions, and I do appreciate any suggestions. I just may not be swurft enough to get my arms around them
Thanks very much for taking the time to reply.

Lack of LAB and CMYK support in Lightroom is plain dumb

Similar Messages

Maybe you are looking for