Importing Photoshop "round trip" extra versions

When I need to use Photoshop on an image cataloged under LR, I typically will use the "round trip" process whereby LR creates a TIFF or PSD of the image and passes it to Photoshop. I'm assuming that LR catalogs the new file before invoking Photoshop. (Is that true?) Now, I will often save a low-res jpg of a file I've been working on (making sure it has an appropriate unique name), or I might produce other files (PSDs, JPGs, etc.) in the process of working on the original file received from LR. Those files are *not* automatically imported/cataloged by LR. Is there a way of making that happen without having to manually import the new files (and add to the stack created for the master and initial edited files)?
I envision an automation hook and script to LR (similar to LR's passing the original file to PS) whereby I could pass a file back to LR and tell LR to catalog it. Presumably the filename (identical except for a distinguishing character or extension) would end up right next to the original, the originally edited file, and any other versions I may have created while working on that file.
Sorry for the long way of asking a question. Any thoughts, ideas, solutions?
dds

I am having the same issue. If you don't modify the file name it seems to do the round trip fine. Once the file name changes or I change the file format I need to import the new photo and re-stack the photos in LR. If there is not a way to do multiple round trips we should add it to the feature request forum. I did not know how much I took this for granted in Bridge. Perhaps if I make my new folders auto import? I will try this tomorrow and let you know how it works...

Similar Messages

Photoshop round-trip difficulty...

Since using Ap for a couple of years, I rarely use PS anymore. And, have not upgraded beyond CS2. In the past when I did use it, after an editing session launched from Ap, I was able to simply do File>Save and my modified file went into the Ap library, stacked with the original version. Recently I have tried this when returning after an HDR merge and it no longer works (I get the normal "Save" dialog box)...did I miss something, or must I upgrade to CS3/4 to make this work again?
Any help appreciated..I just upgraded to 2.1.2 and all is well.

No joy with this...I was able to do a "normal" roundtrip with a single image that had been edited. Maybe something about the File>Automate>Merge to HDR in CS-world is unique, since it generates another new image that Ap doesn't know about...I could go back to Photomatix...but I like the tone adjustments in PS...
thanks for the ideas. I'm sure an upgrade to CS4 might $olve the problem...

Round trip from photoshop or portraiture causes problems(TIFF)

And always has to be honest. 2 different computers, with this new LR build and and several before it. Mac OS latest everything and previous builds.. Macbook Pro and imac..
Edit in photoshop CS5 (and previous versions) as a TIFF, apply clone corrections and liquify fashion portraits. Save and close and re-open for some final tweaks in Lightroom. I still get erratic sliders, slow updates when moving sliders and jumping bars to previous values on TIFFs only. Even worse when i edit in Portraiture App and skin smooth, save tiff and return to lightroom. It takes a about 3 minutes to even show itself before editing, keeps flashing up then dissapearing again.
If i remove Tiffs that have been through photoshop or portraiture and synchronise the folder to import them back into Lightoom my problems disapear.. but its tiring. I now find myself using C1 more and more because the transitions between apps are smooth and problem free. However i prefer the flexibilty, speed and control of LRs functions
Others must be experiance this, it can't be fate this is happening on two different computers, old computers that have been replaced and previous versions of Mac OS and Lightroom.

Ernie, the photos are captured by Canon XTi so they are in CR2, saved to my internal HD and then "loaded" to Aperture as referenced files.
As for PS CS3, I am not sure whether I have it set up as a scratch disk or not (if you could let me know where to check it).
Yesterday, I did yet another round trip and found out that when I finish in PS and SAVE and CLOSE, then the file shows up properly in Aperture. What I was doing before was I SAVEd if but did not close. Then I would SAVE AS in PS to make sure I have some kind of a version of the file if the one in Aperture fails to work.
So it seems I cracked it but I would still like to hear what you have to say, or anyone for that matter. It seems to me that the SAVE-CLOSE is crucial.

Aperture 3.03 & Photoshop CS4 round-trip

I'm trying to make a round-trip between Aperture 3.03 and CS4 Photoshop.
Background: I've chosen CS4 Photoshop as my external editor - 16-bit PSD
Problem: When I select an image and "Edit with CS4", I successfully launch the image in CS4. I made a filter change (Lens Correction) and then did a "SAVE" within CS4. The PS version appears "very briefly" within Aperture 3.03 and then disappears.
Attempt at a solution: Tossed "com.apple.Aperture.plist" preferences file and re-launched Aperture.... result - CS4 edited version still disappears in Aperture browser window.
Any suggestions?
Thank you.
Dale

Ensure maximise compatibility is checked when you save the psd file.
Ensure you're in RGB colour space.
What happens when you quit and re-open aperture does it show for a second or stay disappear - does it show a dotted outline? Can you open the file in full screen?
Thanks
M.

When round tripping with photoshop cc, i get a saved psd file with my original raw,the problem is these are high file sizes and taking a lot of space,can i stop this?

when round tripping with photoshop cc, i get a saved psd file with my original raw,the problem is these are high file sizes and taking a lot of space,can i stop this?

That's not the workflow that I use. I have my Lightroom preferences set to create TIF images when going to Photoshop. I keep the original raw file and the TIF image (usually reduced to an 8-bit image) and only export JPEG's when they are needed to send to a lab or to send to someone over the Internet. JPEG files are highly compressed. I only create them when they are needed, and they are discarded as soon as they have been used for their intended purpose. I keep the raw file and the Photoshop-created TIF in my library. This requires extra disk space. But I always have the highest quality files available.

Round trip export/import from Mac OSX iCal

Since there isn't an iSync plug-in for Oracle Calendar (yet?) I thought I'd try a round-trip import/export between Oracle Calendar and Mac OSX iCal. Inconvenient, but it should would because the UIDs in the .ics file would be the same and an import would overlay over the existing entries.
Wrong -- if I export an event from iCal, import it into Oracle Calendar, then export it again and look at the .ics file, the UID is different. Consequently, I get duplicate entries at the end of the round trip.
What good is the "U"-Unique of UID if it isn't kept consistently? From the standard: "Implementations MUST be able to receive and persist values of at least 255 characters for this property."

I've ran into an issue when exporting/importing a .csv file from OSX.And this "issue" is...?
Exporting from? Importing to?
APEX version?
Database version?
Database character set?
Database host OS and version?
EPG, OHS or OAS (and version)?
DAD character set (if any)?
OS X version?
Some, none or all of the above may or not be relevant, but without more information to go on, all you are going to get are random guesses.
http://tkyte.blogspot.com/2005/06/how-to-ask-questions.html
http://catb.org/~esr/faqs/smart-questions.html

The round trip between Aperture and Adobe Photoshop elements is not cooperating I have performed all the suggestions. Any others? Not sure about saving.

i tried all the suggestions on line. none of them are working. Any other suggestions?

i tried all the suggestions on line. none of them are working. Any other suggestions?
Marianne,
how can we possibly answer that? Nobody will know "all the suggestions online". So how are we to know, what you already tried?
What exactly is not working with your round trip? And what did you try already?
What is your Aperture version?
Regards
Léonie

2 round-tripping questions

I just went into my external editor (photoshop elements) and edited a photo that I had exported into PSE from within aperture. I have 2 questions.
1. I have no clue how to make that edited version appear in aperture now. I have tried saving it under three different names. I have turned off the external editor. How do you get back to aperture and see the newly edited photo? There must be something easy I am missing.
2. Can I run my external editor by itself and import a photo from my aperture library without turning on aperture? Or must I always export the photo out of aperture and into the external editor?
Thanks so much in advance.
p.s. I even listened to the "round-tripping" podcast on Inside Aperture. Made it sound so easy.

Keep in mind every time you open an image with the
external editor a new master is created (psd or tiff)
and will increase the size of your Library.
-- or rather, every time you open a new image, or make any Aperture adjustments to an externally-edited image.
If you edit a file in an external editor and save it, and then select it again later and again choose Open with External Editor, as long as you haven't adjusted it meanwhile in Aperture, the same version will be sent rather than a new one being created. This puts a premium on organizing your workflow so that external editing is normally the last thing you do to an image, though you're not limited to that if you need to work the other way.

Round tripping PSD in Cp7/TCS5???

I’m also continually challenged with round-tripping PSD files in Captivate. I can import a PSD layer, but I can’t update the PSD from Cp if the original changes. So I figured that after editing the PSD file I would just import the PSD layer again. But since the PSD layer name hasn't changed, the image in the Cp library doesn't change! So I need to delete the media from the CP library, import the PSD again, and rework each slide where that image was used. Timeline, image properties, etc. Utterly ridiculous!
From my research it seems like round tripping PSD is only an eLearning suite feature, but we’re using Tech Comm Suite. It’s very frustrating and time consuming to work around this arbitrarily disabled function. Especially considering the money we've spent for 4 TCS suites. Why is this functionality not enabled for TCS? I submitted a bug report / feature request and sent it down the black hole to India.
Another stupid inconsiderate decision choice from Adobe. Articulate is looking better every day.

Sorry Sreekanth, but your responses doesn't make sense to me. If Photoshop not being part of TCS is an issue then why is "Import a Photoshop file" an option in Captivate? Further how can Cp see the PSDs as folders in the library, with the PSD layers as images? Also, the fact that Illustrator was included in TCS4 was meaningless since we couldn't import an AI file direct to Cp anyway. We had to export from Illustrator to some other format, like PNG. If we needed to retain transparency of the image, well that was a gamble. By placing AI files into a PSD, then importing the PSD into Cp we had a workflow that retained the image source PSD and AI files, and retained transparencies. If updating a PSD in Cp 6/7 standalone does work, then it looks to us that Adobe did remove functionality when packaging Cp into TCS.
And I did confirm my requirements with an Adobe sales rep before we upgraded to TCS5. I specifically identified this issue to him as part of TCS4. He was surprised that a premium suite like TCS would not offer an option like this. Especially since ELS did include it. He promised to look into it and get back to me. He followed up with email questions about versions of my softwere, but the discussion went quiet and I received no more replies to my inquires.
We've always purchased Photoshop and Illustrator separately. I didn't know these have gone to Creative Cloud only. As technical content developers and curriculum designers we've always used those for our grapic design. It was always weird to us that TCS and ELS were packaged with Photoshop or Illustrator differently.

Round trip to PS CS3 does not show the saved image in Aperture 2.1.1

Good evening everyone; I hope someone can help me to solve this.
I have PS CS3 set as my external photo processing app (exports are PSD 16-bit 300 dpi) in Aperture 2.1.1. When I process the picture in CS3 and then save it(mind you I only SAVE, I do not do SAVE AS) as PSD (or TIFF) Aperture only shows me the original file in preview with the little circle informing me about the round trip to CS3. So the processed file does not show. Instead I only see two identical versions of the same photo.( I mean, I see the master and the version with the little circle).
If I save the work in PS CS3 as jpeg and then import into Aperture, it shows fine. When trying to import the processed and saved PSD and TIFF files, Aperture only shows the original file.
If it helps, I am working on layered pictures (HDR) where I use different parts of different pictures to get wide dynamic range. I export 3 or so photos from Aperture at once to CS3, process them into one, flatten the picture and save it.
And then Aperture just shows me the original file as version.
I have done this before 2.1.1 and it worked. Not sure if I have changed anything that might be causing this.
Thank you for your ideas.

I am sure it is not stacked under the original, unfortunately. Any other tips?
Also, as I mentioned earlier, even if I save the processed file in CS3 as PSD (so I use SAVE AS) and then try to import it into Aperture, it "magically" only shows the orginal (as if it was just importing some layer).

Round trip from Aperture to PS CS3 and back problem

Hi everyone; I hope someone can help me to solve this. I posted it before but the only suggestion I got was to check if the processed photo is not stacked under, which it isn't.
I have PS CS3 set as my external photo processing app (exports are PSD 16-bit 300 dpi) in Aperture 2.1.1. When I process the picture in CS3 and then save it(mind you I only SAVE, I do not do SAVE AS) as PSD (or TIFF) Aperture only shows me the original file in preview with the little circle informing me about the round trip to CS3. So the processed file does not show. Instead I only see two identical versions of the same photo or a layer from CS3.( I mean, I see the master and the version with the little circle).
If I save the work in PS CS3 as jpeg and then import into Aperture, it shows fine. When trying to import the processed and saved PSD and TIFF files, Aperture only shows the original file.
If it helps, I am working on layered pictures (HDR) where I use different parts of different pictures to get wide dynamic range. I export 3 or so photos from Aperture at once to CS3, process them into one, flatten the picture and save it.
And then Aperture just shows me the original file as version. I really need your help with this.
I have done this before 2.1.1 and it worked. Not sure if I have changed anything that might be causing this.
Thank you for your ideas.

Ernie, the photos are captured by Canon XTi so they are in CR2, saved to my internal HD and then "loaded" to Aperture as referenced files.
As for PS CS3, I am not sure whether I have it set up as a scratch disk or not (if you could let me know where to check it).
Yesterday, I did yet another round trip and found out that when I finish in PS and SAVE and CLOSE, then the file shows up properly in Aperture. What I was doing before was I SAVEd if but did not close. Then I would SAVE AS in PS to make sure I have some kind of a version of the file if the one in Aperture fails to work.
So it seems I cracked it but I would still like to hear what you have to say, or anyone for that matter. It seems to me that the SAVE-CLOSE is crucial.

Best workflow for round trip editing?

I understand that iPhoto does not support (yet) round trip editing, i.e. a RAW file can be sent from within iPhoto to an external editor but the resulting edited file cannot be saved back directly into iPhoto but has to be temporarily stored somewhere (i.e. desktop) and reimported into iPhoto using the Import function.
However,this screws up my "roll" filing structure, because the imported file is now part of a new roll and cannot be moved back to its original one.
Sure, I could process my photos before importing but this only postpones the problem. Indeed, next year, there will be an other iteration of Nikon Capture with new features and I will want to reprocess some old files to get better results ... and they will have to be reimported into iPhoto!
Has anyone come up with a suitable workaround that allows an imported file to be part of an existing roll or a solution to merge 2 rolls?
Thanks
Michel

Solved!
It's again RTFM ("Read The F*ng Manual").
Workflow would be as follows:
1. Edit RAW photo from roll, say "Xmas '05", with external editor.
2. Save modified photo as jpg version (so that the modifications are visible in iPhoto) to desktop.
3. Import into iPhoto (this creates a new roll, say "Roll 112", number is automatically assigned by iPhoto)
4. Select all photos from "Xmas '05" and "Roll 112" in the iPhoto library
5. Select Create New Roll from the File menu (all photos are now combined in a single roll, say "Roll 113" with today's date)
6. Rename Roll 113 into Xmas '05 and change the date to keep the chronological sequence
Voila! Roll "Xmas '05" has been updated (just tried it. It works).
I should have completely read the manual before posting.

Round trip between Flash Builder and Catalyst?

Is it, or will it, be possible to go back to Flash Catalyst once a project as been brought into Flash Builder?
I have imported the .fxp project into Flash Builder, made some code changes, then exported a .fxp project out again. I want to be able to edit this in Catalyst so I can make design changes, but when I try to open the project Catalyst says it cannot be opened becuase it has been edited outside of the application. Is there something I am missing or has this simply not been implemented yet?
It would be a shame to not be able to "round trip" from Catalyst to Builder.
Thanks for your time and the product looks very exciting.

Hi Watern,
For the first version of Catalyst, we're focusing on the one-way workflow from Catalyst to Builder (start in Catalyst, finish in Builder). We realize this is a big limitation and hope to address soon after the first release.
There are a number of partial solutions for this problem, which you can find by searching around the forum. Most of them involve dividing the work between Catalyst and Flash Builder as cleanly as possible, which is surprisingly easy to do given the new skinning architecture. Here's an excerpt from a post I wrote that seems to have been lost:
"If you are iterating between Catalyst and Builder on a custom component, you may find it is worth splitting the custom component out in that fashion. I'm planning to write an article explaining this, but here's a preview:
In Builder, create a new subclass of SkinnableComponent. Put the component logic in there.
If you need to add visual logic like "now move the konfabulator 10px to the left", you should make konfabulator a skin part, using the metadata (see Scrollbar.as, in the Flex 4 SDK, for an example).
If your component has states, declare them with the metadata.
In Catalyst, make sure that your custom component has those parts and states.
Then import the custom component into Builder.
In the MXML file for the custom component, change the root tag <Group> to <Skin>. It's now a skin (not a custom component).
In the MXML file for the skin, add the [HostComponent("com.me.MyComponent")] metadata (see HScrollbarSkin.mxml, in the Flex 4 SDK, for an example).
Wherever you are creating the instance, change the code <MyComponent/> to <MySkinnableComponent skinClass="MyComponent"/>. Now you're creating an instance of your skinnable component and assigning it the skin created in Catalyst.
Done! If you make more changes in Catalyst, you'll have to repeat steps 5-7 again (for now!)."
-Adam

Analysis, Design model, round-trip engineering

ok, here's the point.
We work with the problem domain and develop the analysis model. The analyst at this stage doesn't concern himself with the implementation details, some low-level code patterns and the programming language (well, let's forget for now about C's multiple inheritance and Java's workaround for it). So, when most of the analysis work is done, we end up with major classes (populated only with some basic attribs & behaviour; then, we have a high-level representation of business processes and corresponding activity diagrams. Of course, this model will be refined at a later stage, but for now it will do.
Say, we have the model in a project. Now we move to the design level. More and more details are added to the model, sequence/collaboration diagrams are added, we concern ourselves much more with the detailed class behaviour.
And here's the first question. Should we leave the original high-level diagrams intact and produce separate detailed ones? Generally, they represent the same process, but at a more detailed level. What about duplication of diagrams? Or should we elaborate the existing ones (but then we lose the clear and simple bird-eye view of the problem domain).
After that, we make a decision to implement the system as a set of EJB's. So, we've switch to component modeling at system design. UML model for these components differs quite a lot from a traditional one, so it can be quite painful to refactor the existing interaction diagrams. But do we need to do it? I agree that having <<EJBImplementation>>, <<EJBRealization>> , etc stereotypes displayed in the analysis model is not a nice solution.
Another question - is it a good idea to start a separate project for system design and just import/copy the required pieces from a higher-level design model? Or can we get away with combining all stages in one project file?
Please, read all of the above in the light of round-trip engineering. So, finishing after analysis stage, is not an option, but to lead the whole project to as low level as implementation details.
I'd like to hear from you, some hands-on experience with similar projects, your approaches. Feel free to comment on the flow of events.
Best regards,
Andrew

ok, here's the point.
We work with the problem domain and develop the
analysis model. The analyst at this stage doesn't
concern himself with the implementation details, some
low-level code patterns and the programming language
(well, let's forget for now about C's multiple
inheritance and Java's workaround for it). So, when
most of the analysis work is done, we end up with
major classes (populated only with some basic
attribs & behaviour; then, we have a high-level
representation of business processes and corresponding
activity diagrams. Of course, this model will be
refined at a later stage, but for now it will do.
Say, we have the model in a project. Now we move to
the design level. More and more details are added to
the model, sequence/collaboration diagrams are added,
we concern ourselves much more with the detailed class
behaviour.
And here's the first question. Should we leave the
original high-level diagrams intact and produce
separate detailed ones? Generally, they represent the
same process, but at a more detailed level. What about
duplication of diagrams? Or should we elaborate the
existing ones (but then we lose the clear and simple
bird-eye view of the problem domain).Depends on whether you are concerned about the abstract methodology or more concerned about the implementation methodology.
For full process control, on a large project, you will have a architecture design which will always reflect the target system but has little to do with the implementation design. If the architecture needs to change it means something was "wrong" with it (which could come about due to a change order or a refinement of the specification of the system.) There might be other associated high level documents which occupy the same level - such as the project plan. This would typically be the project initiation phase which occurs before software design starts.
Of course you would keep all of the documents. Just as naturally each version would be checked into the version control system.
>
After that, we make a decision to implement the system
as a set of EJB's. So, we've switch to component
modeling at system design. UML model for these
components differs quite a lot from a traditional one,
so it can be quite painful to refactor the existing
interaction diagrams. But do we need to do it? I agree
that having <<EJBImplementation>>, <<EJBRealization>>
, etc stereotypes displayed in the analysis model is
not a nice solution.I doubt that any reasonable system is going to make the decision to use J2EE in the system design process. That is always going to be a architecture or requirements decision (even if it is implicit.) If not then it suggests that there are probably at least three levels to the design process and the J2EE decision is in the top most layer (maybe there is a "high" and "low" level architecture process.) And architecture design must describe why J2EE was choosen and what if any alternatives were considered.
Again this document will be retained (and checked into version control.)
>
Another question - is it a good idea to start a
separate project for system design and just
import/copy the required pieces from a higher-level
design model? Or can we get away with combining all
stages in one project file?
In the abstract yes.
Why? Because in an ideal design environment, a "high" (system) level design is created by a small very experienced set of developers. Then it is handed off to many junior developers for "low" (detailed) design. That doesn't work if you are using the "same" design. This is only somewhat mitigated by design tools that somewhat support this process (or least last time I checked they didn't support it very well.)
Keep in mind that this is the ideal, and it is unlikely (probability wise) that you are working at or with a company where doing this is feasible much less encouraged.
Please, read all of the above in the light of
round-trip engineering. So, finishing after analysis
stage, is not an option, but to lead the whole project
to as low level as implementation details.
Round trip. You start with the documents that have been checked in. You branch the version control tree or just up the version numbers of the docs (depending on how "deliverables" are being handled) and start over.

"Round-trip" feature broken!

all of a sudden after years of trouble-free operation, i started having a problem with round-tripping of my referenced files (most of my library). it happens when using any plug-in or editing with photoshop.
it seems that as soon as i choose one of the "Edit with..." options and it creates a new version, the new version has no name (blank) or displays "null." the image opens in the editor of choice (e.g., CS3, Nik filter), i make edits, but when i return the preview is not updated and full-screen mode does not show the updated image.
if i choose to open the image again in CS3, for example, it will show the edited image.
this problem just started happening out of the blue. here are some recent things that changed on my Macbook Pro:
1. Upgraded from 10.5.5 to 10.5.6;
2. Ran the Aperture database re-indexing and permissions check.
Fortunately, before doing the 10.5.6 update, i performed a backup that i plan to restore and see if this will fix the problem. but i was hoping to avoid this if someone knew what was going on.
Thanks!
Darron.

The round trip feature is back now. I updated iTunes to 5.0.1 today, and that function is available again, but it still doesn't work as the previous version did. Option clicking an arrow in the iTunes music library will perform the specific query I mentioned earlier in the post. Clicking on the arrow from some of the items in my library works intermittently. For example, when I click on Matchbox20 - I am taken to Advanced search page. When I click on Destiny's Child - I am taken to the iTunes Music store page which features all DC albums (this is the proper way it should function). When I click on Whitney Houston's Greatest hits - I am taken to ITMS Whitney Houston page, but not that specific album (which should not be the case). It should just isolate that one album by Whitney. For anyone that has a sizable music collection, this feature of iTunes is invaluable in my opinion. I'm surprised it's not exploited in other software.
Thanks Apple.

Importing Photoshop "round trip" extra versions

Similar Messages

Maybe you are looking for