And that will manage the appropriate external image copies in a corresponding subfolder, inside whatever destination was chosen for this overall Publish setup. Inside this, creating as needed a number of named Published Folders (Publish Collections) that will each group the photos you need for various particular InDesign purposes. Sure, I envisage: working images (that you can continue to edit) to remain the only image versions inside the Catalog - no reimporting of exports.Ī Publish setup ('hard drive' type) called something like "for InDesign", set up with the export specifications and folder destination suitable for that specific kind of external usage. DO you have any ideas how I may leverage Publish Services or any other approach to get the benefit of the Visual Lightbox and the edited files? Perhaps a second Mirror Lightroom Library with a paralallel folder structure with the exported/published versions? Or is reimporting and Stacking the way to go? Would love your guidance here of best practices! I have a very organized file folder structure on my desktop mirroring the LR catalog with a very logical taxonomy. I have a 55,000 Image Library broken down into folders and collections, these are very high-res images. I do not presently use the Publish function, though I imagine it would be a useful tool in many workflows. I am trying to figure out how to best achieve the benefits of the visual lightbox and the drag and drop simplicity of creating Linked Images in INDD. I realized only recently that any dragging and dropping into my INDD frame only brings in the original, non edited file. My problem is (as I'm sure you understand from my previous question, is how I can use the visual convenience of the lightbox to identify and integrrate with my building of an INDD document. ![]() ![]() Hi Richard, thank you for your prompt answer! There are two benefits to me using Lightroom: A Digital Asset Management system that allows me to visaulize asses in a lightbox and which allows me to batch adjust, batch modify Metadata, as well of course integrate image editing. It is then up to the user whether / when the published external copies should refresh themselves with latest editing.Īnd if separate external uses of an image required different editing, that is what virtual copies are good at. Publish on the other hand will track and accommodate later editing. There is no concept of 'versions' in LrC btw, that would pick up on any subsequent editing of the primary image - did you mean stacking? A reimported export could not update to reflect further edits on the master image: it would need to be re-exported and LrC would not then let you overwrite (because you'd be overwriting something that was itself imported). I am curious, what would be gained by re-importing the exports? Seems to me counter-productive, and far from a no-brainer IMO. Yes indeed the user could be prompted for a saving location, but if multiple publications existed at the same time, then repeatedly selecting the right location for each one, without error, could consume a lot of needless attention IMO.
0 Comments
Leave a Reply. |