Lightroom 1.1- CS3 Workflow Question

I'm primarily using Lightroom 1.1 for processing photos but I also want to make some use of PS CS3, although initially only for sharpening purposes (one small step at a time!).
I'd love to hear from any of you who are doing this successfully with some advice re how to best move back and forth between the two programs for that purpose (sharpening) only.
If someone has successfully laid this out in a book or other web posting I'd greatly appreciate the title or URL.
Thanks.
Mark

As far as English language versions go, I would say no, or at least not yet. This is because Peachpit will already have copies of the current, version 1.0 edition on sale and these would need to go out of print first. That is one of the problem with print media production that is faced by all print authors. One can't release an immediate print update if it makes the exisitng unsold stock immeditately go out-of-date.
Releasing a PDF update seemed to me the fairest solution since this gives everyone the opportunity to get up to speed with the latest changes without ecpecting readers to fork out more money to buy a new book update. But expect much of the content that is in the current update to merge with a future version of the print book. So far, I am aware that Scott Kelby has taken the same route as myself and released a PDF supplement, but I don't know what other authors have planned.
Martin

Similar Messages

InDesign CS3 Workflow Question for a Playbill?

Hi guys,
I am designing a playbill in InDesign CS3. The cover of the playbill is of a different stock than the interior pages.
Should I create an InDesign book with the cover and the interior pages as a separate document, or keep them as one? The pages are the same size, it's just the stock (and probably the finish - the cover may have some embossing) that will be different. The printer has not yet been selected by the client (long story...), so I have no guidelines as to how they would want it prepared... What would be the best generic method?
Many thanks,
Martin

I hate to say this, but in your shoes I'd probably prepare two documents for the moment. One that is facing pages and has the cover included, and one that is a cover-only in non-facing, full-spread-width pages (one or two, depending on if there is printing inside the cover). When it's time to go to print he decision can be made whether to abandon the cover file or delete the cover pages form the body.
Why would I do that? Because it sounds like a fast-track job where the specs could change right up to the point of printing. An embossed cover is going to need separate handling, and will be easier all around as a separate file, but if the client decides to forego that bit, and the run is short, there are plenty of digital output machines capable of handling a cover inline on different stock.
Essentially, there is no right answer in your situation.
Peter

Lightroom + CS3 workflow suggestions please

I have been scanning a lot of old photos and slides from my grandparents, some of which are quite badly damaged and require work beyond the capabilities of Lightroom.
I like the Lightroom non-destructive editing capabilities and the fact that I can create many virtual copies of a photo without taking up more disk space for each copy.
However, when editing in CS3, I am forced to write out a new PSD file each time - thus dramatically increasing the amount of disk space used.
I just wanted to hear how other people structure their workflow when editing Lightroom files in CS3? I want to maximise the flexibility of editing (especially when experimenting with edits that I may later want to undo), while minimising the amount of disk space used (some scans are very large).
Suggestions?

Answered my own question
The problem for me is that I was using two monitors.
The second display was set to Grid view and this is where I select the images. If you then press 'B' to send to the Target Collection then only the first image gets sent.
If you have Grid View on the first display and then select the images and press 'B' all the selected images go to the Target Collection.
The same effect happens with Flagging or setting Colour Labels. Only first image on second screen (Grid View) but all selected images if on first screen (Grid View)
Bug or feature!
Colin

Lightroom workflow question

I am relatively new to lightroom. I have a question about incorporating photos from various sources. What is the best workflow for getting photos that have been emailed (for example) into my lighroom catalogue?
Thanks for your help,
Leora

You might want to set up a single folder to receive e-mailed photos, so you'd first save to that folder from the e-mails, then run Import from LR and add your keywords at that time. You can also run Synchronise once it's set up to be sure you've incorporated of them as time goes on.

Sharpening export workflow question

I have a sharpening workflow question. Say I have pictures from a portrait session I just finished. I have to send 10 pictures the client ordered to a print lab and I also will make some small facebook sized pictures and upload them to my business facebook page. The level of sharpening needed for large prints (I upload to print lab as RGB JPEGS) and sharpening needed for the very small sRGB facebook-sized pictures is different. In Lightroom I have the option to set the sharpening on export and have a bunch of presets that alter the export size, color space, sharpening, etc(WHCC print lab, facebook, Client CD, etc). I don't see how to do that in Aperture. I see they have the option if you have a printer, but not on normal export.
For those of you that have to export batches of pictures in multiple different sizes (with different levels of sharpening), what is your workflow? I could use some photoshop droplets/actions after Aperture export but I was hoping there was a way to avoid the extra step. Am I overlooking an export feature? The BorderFX plug-in looks like the only other option.
Thank you in advance for time and help!
Scott

Frank Scallo Jr wrote:
The thing is guys - Once a file is sized down it WILL lose sharpening - what we are doing is sharpening the full size RAW file or rather what the full size output would be like. Once we export a version sized down it will lose some of the 'bite'. LR has sharpening options on 'output' which is not only smart but a necessity. Adobe realizes that output for screen needs another sharpen. Apple either doesn't know or didn't bother. It makes ANY output for screen less than best.
Bear in mind that there seem to be two separate issues going on here - sharpening adjustments not being applied on export, and resizing.
As far as resizing is concerned, Aperture appears to use something roughly equivalent to Photoshop's Bicubic Sharper setting. Because of this I've never had much problem with Aperture's exports when used for the web, but obviously everyone's taste for sharpening differs which is why an option for output sharpening would be good.
Sharpening adjustments not being applied on export is a separate issue and should be reported via the feedback form ASAP by everyone who is experiencing the bug.
Now printing is another animal - I wouldn't print directly from RAW in aperture either if I'm printing small. Again, LR beats Aperture here as well since they include output sharpening for print.
Aperture has had output sharpening for printing since 2.0 came out (unless it in was 1.5). In A3 you need to turn on 'More Options' and scroll down, I can't remember where it is in A2. I don't know how effective it is as I print via a lab, but it's there and it's been there for a long time...
Ian

Lightroom 2 - Photoshop CS3 - Lightroom 2

Here's my scenario.
All RAW files have been converted to DNG.
I would like to catalog all DNG files in Lightroom (thus, starting my workflow there). If I shoot an ISO 1600/3200 shot, I would first like to run it through Noise Ninja in Photoshop CS3. So I right click on the Image, Edit in Photoshop CS3 (I have both Edit and Open as Smart Object as choices - unsure which is the right one to use). I can want to run Noise Ninja over the image to remove some noise, and then return back to Lightroom (WITH that change) for further editing. Creating new files (like a PSD) to accomplish this isn't a big deal.
I just don't know how to do it! The image in Lightroom after running Noise Ninja still shows noise.
I've tried the above, saved the PSD, but Lightroom appears to ignore it. Does it matter what the file is called? Does it matter where it's located? How do I tell Lightroom to acknowledge the change?
Any help (step by step) is appreciated.
-Craig

I figured out how to create an action, make it a droplet, which creates an exe, and reference it via Lightroom. Now I can Export in Lightroom, run the "noiseninja.exe" droplet (needed to make it "run as administrator" in Vista), and have a .psd auto-imported into Lightroom's catalog. Works pretty well (and fast).
I end up with two versions of the same image - one the original .dng, the other a .psd. Which I understand the reasoning for.
Here is what I don't understand:
When I use Export, the .psd is named the same as the .dng file (CRW_2593.dng is imported as CRW_2593.png for example). If I then go ahead and "Delete from Disk" the CRW_2593.png file, both the .png AND.dng files get deleted! These files are not stacked, one only was selected, etc. This doesn't seem right (as I lose the .dng file by deleting the newly generated .png).
Here's something a bit interesting. If I go ahead and "Edit in" the .dng file (after restoring it from a backup), and use the same droplet (set up via Preferences/External Editing), I will also get a .png automatically added to the Lightroom catalog, though it's name is a little different (CRW_2495-Edit.png in this example). I'm presented with a dialog box before conversion which forces me to "Edit a Copy with Lightroom Adjustments". If I go ahead and "Delete from Disk" the CRW_2493-Edit.png, the original .dng stays! I assume that the "Edit a Copy..." above makes it this way.
Is there a way to make the "Export" function behave the same (with regards to the "Delete from Disk" feature) as the "Edit in" function? I've been through the screens for Droplet and Export a dozen times and don't see any setting that refers to the .dng and .png being linked.
Thanks,
-Craig

The Adobe CS3 Workflow...

Hello,
I'm starting to build RIAs with the Adobe product family.
I've already made a Flex site and I've been playing with Flash and
actionscript before but I have some questions concerning the Adobe
CS3 workflow.
If I see it correct, the design phase for a website (and a
logo) is best done using Photoshop (bitmap-based) or illustrator
(vector-based). Next the design is treated in flash (using the
Flash Authoring tool) to add animation and interactivity (with
preserved layered structure). The result is an animated website
design, which can be converted to Flex components (using the Flex
Component Kit for Flash CS3). These components can be used in my
(flex-based) actionscript project to couple the front-end to the
back-end using Flex functionality.
- Is this simplified impression correct?
- What are the advantages of bitmap-based assets over
vector-based assets? And the disadvantages? When to use which
style?
- What should be handled within the Flash area and when
should Flex kick in?
- What's the best strategy to enrich the Flash design with
Flex functionality? Should I just convert my animated Flash assets
to Flex components and is Flex responsible for integrating the
Photoshop (or Illustrator) design with these Flash components on
the one hand and the server-side back-end on the other hand?
- What are the advantages of using the Flash Authoring tool?
Can I avoid using it and achieve the same by just using the Flash
display architecture directly in actionscript (and mixed with
Flex)? Or can I 'export' the Flash assets (created using the Flash
Authoring tool) to an actionscript project with the purpose to add
the Flex functionality?
- Is it possible to integrate Flash-based Actionscript
(following the Flash display architecture) with Flex-based
actionscript (following the UIcomponent display architecture)?
- Are there good tutorials explaining the 'preferred' RIA
design workflow?
Sorry for my ignorance but I’m having trouble
understanding the big picture. Especially, when to use Flex and
when to use Flash and how to integrate them (using actionscript?)
is unclear. Any help would be greatly appreciated!!!
Thanks,
Stikkos
PS: I’m not sure if this is the right forum for this
discussion so please move the post when not appropriate…

I think we can capture in QT DVCProHD, OnLo CS4 Mac will capture both AVI and QT formats, and the PC will play the AVI's and the Mac will play the QT ones (I *think* the Mac does, we haven't fully tested it yet after the patch)
However, the problem is we have used and shot/captured with OnLo CS3 PC, and so saved terabytes of AVI's in DVCProHD/100, and the Mac CS4 AE and Prem simply cannot see them.
We have many many old project files we just can't use via a Mac machine now.
We can't even swap to QT format in future, because the PC version of AE/Prem can't see the QT formats either.
Basically, Adobe should support both AVI and QT DVCProHD files on both PC and Mac.
I can't even be sure what CS4 PC version offers wrt to codecs, as it *sounds* like the built-in system codec is gone now too, so even a PC running CS4 AE/Prem can't see the DVCProHD AVI's!
Needless to say, we won't be upgrading any Adobe software until we check the software demo's to see if they actually do what the old stuff did, otherwise it's backwards steps and screwing up our workflow to the point we are out of business!
Dave

RED Workflow questions with Mac Pro (including third party plugins)

Hello all,
I’ve been searching many forums for the better part of a day trying to get some workflow questions sorted. I’m experiencing (very) slow export times, and mediocre playback for a machine that should be screaming fast.
Here is what I’m working with:
2014 Mac Pro
-2.7 GHz 12-core intel xeon E5
-64GB Ram
-Dual AMD FirePro D700 6GB
-1TB Flash Storage
Editing all footage off 96TB Raid 6 mini-sas server (getting about 1100mbs read/write rate according to AJA system test) which is faster than any Thunderbolt/TB2 drive array I have.
Media I work with is footage from the RED Epic (normally 5K) as well as DSLR footage from the 5d.
Software:
-PrPro CC 2014 (8.1)
-Magic Bullet Looks 2.5.2
My question(s) pertains to RED post-pro workflow in combination with third party plug-ins and the different approaches to make it more efficient.
Right now, majority of the clients need a 1080p HD master, and they are generally anywhere from 2-8 minutes (usually). So my sequence settings are as follows:
Video:
Editing Mode: RED Cinema
Size: 1920 x 1080
Audio: 48Hz
Video Previews
Preview File Format: I-Frame Only MPEG
Codec: MPEG I-Frame
1920x1080
Maximum Bit Depth unchecked
Maximum Render Quality unchecked
Composite in Linear Color checked
Export Settings
H.264
1920x1080
VBR 1 pass
Target Bitrate 12mbs
Max bitrate 12mbs
Maximum render quality/depth/previews unchecked
Issues I have:
-Playback is fine at 1/2 or even full, but once effects (especially magic bullet looks) start to go on the clips, it’s very choppy and has difficult playback at 1/4
-Export times (especially with magic bullet looks) will take the better part of 1-4 hours for a video that is 3-6 minutes long. This doesn’t seem like it should be the case for a maxed out MacPro
So my questions are:
Do these seem like the right sequence/export settings for mastering at 1080p? If not, what would you suggest?
Would using offline editing help at all?
Do you place your effects on adjustment layers?
Is there anyway to improve export settings when using an array of filters?
Have you stopped using third party plugins for their inefficiency in unreliability and switched to more integrated applications like SpeedGrade?
Is there any other tweaks that you would suggest for RED workflow with PrPro?
Should I consider switching to FCPX or (besides the iMovie-likeness) does it carry problems of its own?

Hi This Is Ironclad,
thisisironclad wrote:
Hello all,
I’ve been searching many forums for the better part of a day trying to get some workflow questions sorted. I’m experiencing (very) slow export times, and mediocre playback for a machine that should be screaming fast.
The biggest issue is that most people have is that updating OS X causes certain folders to be set to Read Only. See this blog post: Premiere Pro CC, CC 2014, or 2014.1 freezing on startup or crashing while working (Mac OS X 10.9, and later).
thisisironclad wrote:
Hello all,
I’ve been searching many forums for the better part of a day trying to get some workflow questions sorted. I’m experiencing (very) slow export times, and mediocre playback for a machine that should be screaming fast.
Here is what I’m working with:
2014 Mac Pro
-2.7 GHz 12-core intel xeon E5
-64GB Ram
-Dual AMD FirePro D700 6GB
-1TB Flash Storage
It's a nice base system. How about an additional speedy disk for media cache files. You also did not mention which version of OS X you are running.
thisisironclad wrote:
Software:
-Magic Bullet Looks 2.5.2
The Red Giant website does not indicate that this software is yet updated to work with Premiere Pro CC 2014.1 (8.1). Proceed with caution here.
thisisironclad wrote:
Issues I have:
-Playback is fine at 1/2 or even full, but once effects (especially magic bullet looks) start to go on the clips, it’s very choppy and has difficult playback at 1/4
I would not use this plug-in until you get the OK from the manufacturer.
thisisironclad wrote:
-Export times (especially with magic bullet looks) will take the better part of 1-4 hours for a video that is 3-6 minutes long. This doesn’t seem like it should be the case for a maxed out MacPro
Again, I suspect your plug-in.
Keep in mind that exports are largely CPU based but you can make sure that GPU acceleration is enabled for AME at the bottom of the Queue panel.
thisisironclad wrote:
So my questions are:
Do these seem like the right sequence/export settings for mastering at 1080p? If not, what would you suggest?
It's OK.
thisisironclad wrote:
Would using offline editing help at all?
No need when you should be able to edit natively. Relinking might also be an issue.
thisisironclad wrote:
Do you place your effects on adjustment layers?
That's one way you can do it with the benefit of being more organized.
thisisironclad wrote:
Have you stopped using third party plugins for their inefficiency in unreliability and switched to more integrated applications like SpeedGrade?
I do. Of course, that's a preference.
thisisironclad wrote:
Is there any other tweaks that you would suggest for RED workflow with PrPro?
Try the following:
Sign out from Creative Cloud, restart Premiere Pro, then sign in
Update any GPU drivers
Trash preferences
Ensure Adobe preference files are set to read/write(Hopefully you checked this out already)
Delete media cache
Remove plug-ins
If you have AMD GPUs, make sure CUDA is not installed
Repair permissions
Disconnect any third party hardware
If you have a CUDA GPU, ensure that the Mercury Playback Engine is set to CUDA, not OpenCLYou have AMD GPUs.
Disable App Nap
Reboot
thisisironclad wrote:
Should I consider switching to FCPX or (besides the iMovie-likeness) does it carry problems of its own?
I really shouldn't answer that question.
Hope this helps.
Thanks,
Kevin

Yet Another Workflow Question

Ok I too, like many others here, am new to the Mac (thanks to Apple's I'm a Mac, I'm a PC ads that my wife couldn't get enough of). I have done some searching around and I see that there are quite a few iMovie workflow questions out there. I have not quite found what I am looking for however, so I thought I would make my first post tonight. So here it goes...
I have 3 different ways I capture video:
1. Canon Vixia HF10 (HD)
2. Canon Powershot (SD)
3. Blackberry Storm (SD...I know it isn't a good phone)
I record everything to SD cards. I am wanting to know the best way to store my raw video for editing at any time. Do I copy the AVCHD file structure (for the Vixia) and .avi files (for the other non HD) to my hdd, or do I just import into iMovie '09 and let it reside there, or both? I noticed that iMovie had an archival option (which appears to just copy the AVCHD structure to my hdd), which is why I ask. I want to always keep my raw video in case I decide to go back later and create a new video.
After I have the raw video archived, I would like to know the best way to use iMovie. Depending on where I end up storing the raw video, should I keep the imported video in iMovie once I am finished with a project, and then reimport it at a later date if need be? Or, do I leave it in iMovie as events? I guess this all rely depends on the first question...where do I store the raw video for archival purposes...
Finally, when exporting my iMovie project, should I store that in more of a, pardon the Windows reference, "My Videos" folder with a original size, web optimized size, and ipod optimized size? Thus, keeping the actual exported version of the project separate from the raw video?
I hope I have asked the right questions here. I appreciate any and all help I can get!
Ron

Welcome Ron to the  iMovie boards..
very interesting : 'switchers' care sooo much for 'storage strategies' ..
the by Apple intended workflow/concept for iApps is:
any 'photocam' related material (still or movin') comes-in via iPhoto, and is stored in an iP Library (=you can tell iP to create 2/many Libs, if you prefer to organize manually....)
any 'camcorder' related material HAS to be imported by iM - why? because, iM has some internal routines to make such material editable (codecs, thumnails, stuff....). the same material as 'file by Finder' does not import.. in most cases!
storage..
iP stores in its Library (local/internal HDD and/or ext. HDD)
iM stores in Events (local/internal HDD and/or ext. HDD)
to make Projects/Albums accessible to any iApp, you should keep your fingers off that structure.
Erasing Events 'kills' projects.
allthough, once 'shared to media browser' there's a 'copy' of your project WITHIN the project file. (= the socalled Media Browser is no single Folder somewhere hidden in the system)
there's this Spacesaver feature to erase any Event content which is not in use in any project to keep Events lean.
use the Archive feature from within iM to keep things easy and convenient.. if you miss a single file of the SDcard file-structure, the whole card's content is kaputt ..
summary:
• use iApps as intended.
• use iP for cameras, it stores 'raws' (the avi too)
• use iM for camcorders, use Archive to store raws..
• purchase a dozend of HDDs to store your material..

Problems with editing images from Lightroom to Photoshop CS3

I just installed Lightroom onto my new MacBook Pro and just installed a new version of Photoshop CS3. When I hit the "Edit image in Photoshop CS3" button in Lightroom it won't open Photoshop and therefore won't let me edit the image in CS3. Does anyone know what might be wrong? Any info would be helpful.

I'm running Lightroom and Photoshop CS3. "Edit image in Photoshop CS3" works fine for me. I'm on an iMac and had Lightroom installed first, only thing I noticed is it takes PS a little longer to open up.

Lightroom to Photoshop CC noise/sharpening workflow question

Most of my images I process 100% in Lightroom. HOWEVER, I do at times need to send and image from Lightroom over to Photoshop CC to finish. Then when finished in CC the image goes back to Lightroom 5 as a TIFF. My question is should I apply sharpening and noise reduction in LR5 prior to sending the image to CC? Or should I apply sharpening and noise reduction after the end of the round trip to CC and back when the image arrives back in LR5 as a TIFF. And yes I have tried a number of different ways. I have tried sending the same image from LR5 with sharpening and NR applied as I would if I were finished. I have sent the same image over to CC with just the default sharpen and noise settings AND I have zeroed out the settings. I sent all images to CC as 16bit TIFF. I tried those various ways and have gotten mixed results. So I was looking for someone with expertise as to what the best procedure is to take when using this workflow.

Getting mixed results is normal as it depends on the initial image and what happens in PS. If you’re changing the overall toning or local contrast in PS then the noise will be different and probably needs more tweaking afterwards.
I would generally go part way toward my final Detail settings in LR, then do what I have to do in PS, then do more in either PS or LR as appropriate.
What I usually do in PS is use Smart Sharpen after I’ve resized down to whatever my final size is—usually my screen size for desktop wallpaper, because I like how PS SS works, an in that case I’ve probably done all my Detail work in LR and only do the resize and SS in PS.

Bridge, Lightroom, InDesign workflow question

Hey everyone,
I've been using Adobe InDesign CS5 and Apple's Aperture software together (on a Mac) to do design projects over the past year and a half or so. I'd never been that interested in Adobe's other applications until recently, when I got a Creative Cloud membership, and now am reveling in the bounty of creative possibilities. Recently i've been interested in integrating Bridge into my workflow and transitioning away from Aperture to Lightroom (as i imagine many other people are considering/in the process of doing right now). I've been taking some video tutorials on Lynda.com and recently came across Terry White's "Bridge CC vs. Lightroom" youtube screencast (http://www.youtube.com/watch?v=vd8XLYG8A0s#t=20). While I really appreciated Terry's perspectives and find them helpful, I think he polarized the "Design" (Bridge) and "Photography" (Lightroom) paradigms that he used to distinguish the programs: Bridge is a file browser for working numerous file types across creative cloud applications, whereas Lightroom is a tool for photographers to do powerful non-destructive edits.
Part of what I've liked about using Aperture with InDesign is that (however buggy this feature is) I can directly access my Aperture library from within the OS X open dialog box, thus allowing me to use files that i've edited and keeping all my work in one library. However, from what i've learned so far, and what Terry's video didn't (directly) address is what are some good practices for using edited photographs within an application such as InDesign. It seemed in the video he simply exported image files from Lightroom into folders, and then I suppose you could use mini-bridge to browse that folder. But i'm wondering if there isn't a better or simpler way to do this, and I'm wondering if i could solicit opinions from folks as to how they work between Everything i've tried to do in my workflow is minimize steps and keep track of the proliferation of images i work with. As much as I see that Lightroom is a better maintained tool than Aperture, it sure is nice to be able to directly access those image files from within InDesign…
Very new to all of this. Thanks in advance for everyone's help.
Quin

Hey everyone,
I've been using Adobe InDesign CS5 and Apple's Aperture software together (on a Mac) to do design projects over the past year and a half or so. I'd never been that interested in Adobe's other applications until recently, when I got a Creative Cloud membership, and now am reveling in the bounty of creative possibilities. Recently i've been interested in integrating Bridge into my workflow and transitioning away from Aperture to Lightroom (as i imagine many other people are considering/in the process of doing right now). I've been taking some video tutorials on Lynda.com and recently came across Terry White's "Bridge CC vs. Lightroom" youtube screencast (http://www.youtube.com/watch?v=vd8XLYG8A0s#t=20). While I really appreciated Terry's perspectives and find them helpful, I think he polarized the "Design" (Bridge) and "Photography" (Lightroom) paradigms that he used to distinguish the programs: Bridge is a file browser for working numerous file types across creative cloud applications, whereas Lightroom is a tool for photographers to do powerful non-destructive edits.
Part of what I've liked about using Aperture with InDesign is that (however buggy this feature is) I can directly access my Aperture library from within the OS X open dialog box, thus allowing me to use files that i've edited and keeping all my work in one library. However, from what i've learned so far, and what Terry's video didn't (directly) address is what are some good practices for using edited photographs within an application such as InDesign. It seemed in the video he simply exported image files from Lightroom into folders, and then I suppose you could use mini-bridge to browse that folder. But i'm wondering if there isn't a better or simpler way to do this, and I'm wondering if i could solicit opinions from folks as to how they work between Everything i've tried to do in my workflow is minimize steps and keep track of the proliferation of images i work with. As much as I see that Lightroom is a better maintained tool than Aperture, it sure is nice to be able to directly access those image files from within InDesign…
Very new to all of this. Thanks in advance for everyone's help.
Quin

Lightroom/photoshop workflow question

I have a scenario that I can't seem to get working the way I want.
Scenario: I edit a file in photoshop with multiple layers (.tiff or .psd). I then add that file to my lightroom catalog and would like to have it automatically updated in lightroom when making changes in photoshop. I know this is possible when using the "Edit in Photoshop" option but I can't seem to get it working when I had the file in photoshop first.
If I import the file into lightroom and then make changes in photoshop the changes are not applied in lightroom. If, in lightroom, I choose "edit in photoshop" then I get a flat image generated from the lightroom file that does not have all my previously created photoshop layers.

If you have an image imported into LR then any changes to that image in, for example, PS will automatically be reflected in LR. Aside from being able to see previews in Library, all your Develop adjustments will still apply to the updated image too.
There are two concepts that need to be understood here. Firstly, LR does not support editing in layers, it was never designed to do this, but neither does it destroy them if they exist. It simply processes whatever Develop adjustments you have to the whole image as if it were flat. Secondly, it is a non-destructive editing platform, which means that all adjustments made in LR stay in LR unless you export the image. Then the adjustments are used to create a new file and, bringing in concept one, this file would not have layers.
So if you Edit In > Photoshop > Edit a copy with Lightroom Adjustments, then you’ll end up losing your layers.
If you can put up with not having your Lightroom adjustments when you need to make pixel-level edits, then simply Edit In > Photoshop > Edit Original. Once you have finished your editing, save and overwrite the file and when you go back to LR, you will automatically have your new pixel-level edits + all your existing LR develop adjustments all in a file that retains its layers
What’s more, there’s no reason why you can’t edit the file outside of LR. Because it’s already linked in the LR catalog, when you next open LR it will recognise that the image has changed and update the preview automatically. Using this method invariably means that some metadata changes. LR does not update externally modified metadata automatically but instead prompts you with an arrow in the top right of the grid and filmstrip previews. Clicking on this give you options on how to manage the metadata conflict.

Two workflow questions, (1) importing and (2) saving/exporting

Apologies if the below questions are too elementary. I've just started using Lightroom. I've been trying out various editing/organizing programs and I haven't yet found the perfect one. Can someone tell me if Lightroom is capable of the following:
1. I shoot in Raw+Jpeg format. When I copy images from my camera to my computer, I always create a new folder that represents my event and put the jpegs in \Pictures\[Event]\ and the raw images in \Pictures\[Event]\Raw\. Is there a way to instruct Lightroom to perform this function through the import module, i.e. have a single import event that copies jpegs in an \...\[Event]\ folder while copying dng to \...\[Event]\Raw\ and importing only the dng files into my Lightroom catalog. Is this possible?
2. Also, can someone explain how Lightroom handles edits? Say I've edited a dng in my library. Is the dng file changed on my computer itself? How about the jpeg (remember, I copy jpeg+dng to my computer)? Is there a way to instruct Lightroom to automatically (i.e. default behavior) overwrite the jpg file when any changes are made to the dng file, but prevent the dng file from being overwritten? What about instances where I also want to overwrite the dng - how do I accomplish this?
Thanks.
=|

theNE0one wrote:
I completely understand and appreciate how Lightroom treats raw images. However, if I shoot Raw+jpg, what difference does it make whether or not the jpg file changes? If my raw file is untouched, I don't also need to make sure that the jpg remains in its virgin state...even if the majority of users prefer to keep both untouched, at least allow the option for people that want a different method of handling their files!
Lightroom has no feature to overwrite your JPGs automatically.
Might I suggest a workflow change ... shoot raw only, when you need a .jpg, have Lightroom export one for you.
If Lightroom handled Face/Places/Sharing well, I wouldn't need to mess with a second program (i.e. Picasa), but right now it doesn't look like it can handle what I want. I understand that I can use Metadata/Keyword tags to identify People and Places, and that there are plug-ins to upload to Picasa web albums, but these options aren't executed well enough in LR3 for me to give up Picasa. The plug-in doesn't work nearly as cleanly as the native Google program, and "Faces" is a chore in Lightroom. Picasa can automatically detect faces and makes tagging/organizing/working with images much easier. While I'm on the topic, can anyone explain why such a useful feature (that's available on free and basic image software) is not included in Lightroom? Is there any possibility that it'll be included in the final version of LR3? What about the upcoming Aperture 3? Is it that "Faces" is perceived as a basic consumer feature that isn't used in higher-end software? Will this always be excluded from this "class" of software?
Using LR3 Beta to decide whether the software works the way you want isn't a good idea. I'm guessing, but I don't know for sure, that the uploading to Picasa will work a lot better in the finished product. Hard for me to imagine a program being easier to tag/organize than Lightroom, and while I don't use Picasa, I can't see how it could be easier in tagging and organizing. It is my opinion (and you might think differently) that using two different organizing software programs on your photos is more trouble than it is worth, especially since you have to constantly "synchronize" the two different organizers.
No one here works for Adobe, and even if there was someone here from Adobe, they can't tell you what will be in future releases. We can only guess, and we don't know.
Finally, can you explain xmp? I've done some keyword tagging on my images within Lightroom. If I were to later use another program, would the keywords be picked up? From your explanation it sounds like there are two aspects to a file, the image section and the xmp section. Is the xmp section the part that includes information about the photo? I.e. settings, metadata, etc.??
Keywords that Lightroom writes to xmp should be readable by almost every other photographic application. But please be aware that Lightroom, by default, does not write keywords to the photo files. You have to specifically tell Lightroom to do so, by either turning on an option, or by using Ctrl-S on selected photos. Xmp includes all the metadata, which includes captions, keywords, Lightroom edits, and basically any information supplied by the user rather than by the camera.

RAW workflow questions - image degradation over several edits with 08?

I currently use Aperture to manage (and edit) my digital photo library. After reading about iphoto 08, the only major thing I can see preventing me from using it would be the RAW editing.
An example would be a photo taken in RAW format and edited in iPhoto. It is saved as a JPEG. Any future editing ontop of that jpeg and the image begins degrading as levels of compression are added ontop of it (I think).
In Aperture, the raw file is maintained and any editing to the RAW file becomes non-destructive as the RAW format is retained in "real time" (so to speak).
I know iPhoto also retains the original RAW file, but not the edited RAW file.
My question is this: with the great extra features of iPhoto (such as easier integration with .Mac) I am seriously considering a switch, but am concerned about image degradation. For all the semi-pro users, what is your RAW workflow in regards to iPhoto? Do you edit the file once, then when editing is required in the future just re-edit the JPEG or go back to the original RAW?
For any former Aperture users who switched to iPhoto, was it worth it?
Thanks!!

Terence,
Once again, thank you for a most helpful answer. I was wondering about the same issue. I guess this means that when you edit RAW files in iPhoto, it uses a similar approach than Aperture and Lightroom now. With far less options of course, but if you just doing basic editing of white balance and shadow/highlight, iPhoto is an appealing alternative.
If I understand correctly the Raw conversion is done at the system level, so iPhoto and APerture even use the same conversion engine, right?
Thank you
Bo

Lightroom 1.1- CS3 Workflow Question

Similar Messages

Maybe you are looking for