Opening with external editor always makes new version

i am a fine art figure photographer and portrait artist. almost every photo that i want to finish has to be round tripped to photoshop for retouching. in Aperture 1.5, i could select a photo, open in external editor (photoshop cs3), make my retouches and save the new version. if i wanted to re-visit the image and make further modifications, i could select the round-tripped photo, open with external editor, and the edited photo would be opened without creating a new version.
now in Aperture 2.0, once an image is edited and the new version saved, if i try to re-visit the image Aperture always creates a new version. this is a behavior that i don't want. new versions of photoshop edits are expensive when it comes to disk space. and with 30,000 images in my library, i just can't afford it!
in the preferences, i have the option "Create new versions when making adjustments" unchecked. that's the only option i can see that affects the automatic creation of new versions. any advice on how to edit the image without making a copy would be greatly appreciated!
thanks,
scott
Message was edited by: scott nichol

Hi,
I had the same problem as the OP and was surprised to read that Ian didn't encounter that same behavior. So I started testing several options. This is what I found;
When I open a previously-externally-edited picture from within Aperture, using the keyboard shortcut ⇧⌘ O, Aperture automatically creates a new version.
The same thing happens when I choose 'Edit with Adobe Photoshop CS3' from the Images menu in the menu bar.
On the other hand, when I open a previously-externally-edited picture from within Aperture by Ctrl clicking the picture and choosing 'Edit with Adobe Photoshop CS3' from the pop-up menu, the picture opens in Photoshop without Aperture creating a new version first.
Very strange because the pop-up menu command has the same keyboard shortcut as the commands I used in the first and second attempt.
Hope this helps.
Cheers,
Ivan

Similar Messages

  • No new version from Open With External Editor?

    Is there a way to not create a new version every time I use "Open with External Editor"?
    If I want to open an image in PS, just opening it creates a new version in Aperture, even if I don't make any adjustments to the image in PS.
    I've deselected "Create new versions when making adjustments" in the preferences.
    Thanks for anyone's insight!

    Not sure this will help, but I noticed this problem as well a while ago, but have since developed a work around...
    All my files start off as RAW. When I use "Open in External Editor", Aperture generates a new version with a bulls eye target (this is my C2 version). If manipulate this image in CS and save it when I close, it remains as a bullseye target (look at the lower right corner in full screen). If I reopen this specific image, no new file will be generated. If I manipulate it in Aperture, a new file will be generated (but without the bullseye target) and if I then use "Open in External Editor" another new file will be generated.
    I have never checked to see what happens with a primary PSD file imported. And I am sure the meaning the bullseye target is in the manual someplace.
    So my workflow is RAW file-->all my desired aperture adjustments-->open in external editor for final clean up and modification. I end up with my original RAW file (Aperture modified and restorable to original by removing all selections) and one CS2 file. If I want several version off of my first CS2 file, I duplicate version of the CS2 file, and the open the bullseyed version NOT the new duplicate version image.
    Hope this helps...i know is seems wierd, but it works
    steven

  • Deleted RAW file after "Open with External Editor"

    I opened a file in PS using the "Open with External Editor" command and saved and it saved the update in Aperture but I needed to make anothe change so I did the same as before using the "Open with External Editor" command. Aperture created another "version" so I attempted to delete the version and it deleted all the versions as well as the "Master" RAW file. I went into my trash to find the RAW file and PS file that I wanted to keep but the RAW file was not there. I don't understand why it would put the PS file in the trash but the RAW file is nowhere to be found. Is there another place that it would go?
    Dual 2.7 G5   Mac OS X (10.4.8)   5GB RAM

    If the master was inside the Library then after deleting it, should be in the Trash, inside a folder called Aperture.
    If it was a referenced master it should be still in the location it was unless you ticked the box 'send master to trash', in that case it'll be the same as if it was inside the Library.

  • Setting color space in "Open with External Editor"

    This has been touched on in the forums, but I wanted to ask the question outright: Can you set the output color space to something other than AdobeRGB when you use "Open with External Editor"? I can't find any way to change it... I like to work in ProPhoto, I saw some like to work in sRGB.
    Regardless of how the presets are set in the Version Export or the Presets, it will only come in to Photoshop as AdobeRGB.
    Anybody know?
    Ted

    This has been touched on in the forums, but I wanted
    to ask the question outright: Can you set the output
    color space to something other than AdobeRGB when you
    use "Open with External Editor"? I can't find any
    way to change it... I like to work in ProPhoto, I
    saw some like to work in sRGB.
    Regardless of how the presets are set in the Version
    Export or the Presets, it will only come in to
    Photoshop as AdobeRGB.
    Anybody know?
    Ted
    Well, to answer my own question, I now have it on good authority, actually the best authority, so good I can't say WHO, that there is NO way to specify a color space when using "Open in External Editor". Other than writing a script.
    Hopefully this is an oversight, and will be in the next update!
    Ted

  • Open with External Editor Profile sRGB instead of Adobe RGB

    Hi,
    I know in the export presets I can adjust what profile aperture will use. But what about when I open with External Editor. I like doing this because I can open my image in PhotoShop make my adjustments then save it and have aperture manage my files. But when I do this it opens the file with Adobe RGB, my lab and I sometimes want Adobe RGB. How can I change this without exporting the file and reimporting the file. Thanks.

    Aperture uses a color space larger than AdobeRGB and sRGB. When an image is sent to Photoshop is converted to a 16bit AdobeRGB PSD file in order to get the largest color space to work with.
    sRGB would be necessary when exporting to the web and/or send it to a printer that requieres that color profile, and that's why you have it in the export presets.

  • "Open with External Editor" command bug?

    Seems to be a bug with "open with external editor" command. If I try it just after Aperture has been opened, it usually works (sometimes not). And then after a couple of photos being edited in photoshop, it sometimes stops working. When I try it, it simply gives me SBBOD for a few seconds (which it does when it's working as well), and then nothing happens. No new master created in Aperture, and nothing in Photoshop. If I restart the program, it usually takes care of the problem, and it will work again for a bit. Sometimes restarting the program doesn't even work, and I have to reboot. Very strange.
    Any one else getting this? Any ideas?
    I'm using 1.1.1 and Photoshop CS2.
    powerbook G4 1.5 Ghz   Mac OS X (10.4.6)   2 GB RAM, ATI Radeon 9700 (64MB VRAM), 80 GB ATA HD (5400rpm)

    Anyone out there? No one else experiencig this "bug"?
    Help, please.

  • Open with External Editor Adobe Camera Raw = HOW?

    When I export a RAW file to the External Editor (I've chosen Photoshop CS3) I would like for it to open in Adobe Camera Raw, just like any RAW file that I open in Photoshop outside of Aperture.
    However it bypasses Adobe Camera Raw and opens directly in Photoshop.
    I have the "Prefer Adobe Camera Raw for JPEG files" and "for Supported RAW files" boxes checked in the Photoshop Prefs.
    I see some chatter about Hot folders and Automator around here, but no definitive answer/workaround.
    If Aperture doesn't support exporting to Adobe Camera Raw, it is a HUGE leg-up for Lightroom in the RAW workflow department.
    Please tell me I'm missing a checkbox somewhere... Thanks.

    buttermaker wrote:
    Please tell me I'm missing a checkbox somewhere... Thanks.
    You're not missing a checkbox, you're missing a fundamental issue of how Aperture (and LightRoom for that matter) work.
    When you use the Open in External Editor command, Aperture will convert the RAW file, apply any adjustments you have made, and send the resulting PSD or TIFF file to the external editor.
    The original file is NOT sent and there is no option to do so. Why not? Because Aperture Versions do not exist as discrete image files - the adjustments are shown on-the-fly each time you view it, saving on the space taken up by multiple TIFF/PSD/JPEG files for each Version. As ACR uses a totally different RAW conversion & adjustment engine from Aperture, Aperture wouldn't be able to display any changes made in ACR without including the entire conversion engine of ACR, which Adobe might not be too happy about...
    In other words, if you want to use a different RAW convertor you will have to export the Master, convert it in the other app, and then import the resulting 'normal' image file back into Aperture. The same is true for LightRoom.
    Ian

  • Open with External Editor

    Hi
    When I try to Export to External Editor (to Photoshop) the opened image is 95Mb. These are originally raw images from a Canon EOS 1Ds Mk11 which open in Photoshop as 45Mb.
    Anyone know why the images are opening as twice the size but dimensions and dpi are the same?
    Regards
    Doug Hall
    eyetwoeye

    It might be true that if you use external editor and send 16 bit file and return 8 bit it creates some problem, I do not agree on the general statement.
    Canon raw (I shoot Nikon but that is beside the point) files are really 12 bit color but is called 16 bits and once in PS, it remains 16 bits. The original question is apples-to-apples comparison. both images are supposed to be 16 bits. So the question is why is the file bigger in one instance than another. The only thing I can think of is that the file size may differ because PS will process raw file as PSD and Ap sends the file as TIF. I often find that PS saved TIF, JPEG files are smaller than from other apps for the same image.
    I don't think anyone is suggesting that one converts the file from 16 bit to 8 in the external editor.
    Cheers

  • 16bt files with external editor

    Am I missing something very obvious?
    No matter what I do, I am unable to export to external editor (photoshop) and have them open as 16bt files. They always open as 8bt.
    What am I doing wrong?

    No, you are right. My nice 16 bit file goes to 8 bits
    when opened in the external editor. Needs to be fixed.
    Needs to be fixed and we should not be forced into Adobe RGB (1998)! What if the scene gamut exceeds this? I can’t get ProPhoto? Or the scene gamut is much smaller but I want 16-bit sRGB?
    Is there any logic in how Aperture is providing this encoding? Again, I suspected it was based on the EXIF data the camera writes to the RAW file based on the matrix. I’m lazy but should set my Canon to sRGB, shoot RAW and see what Aperture thinks it should use. But that doesn’t matter because having only sRGB or Adobe RGB (1998) doesn’t cut it.
    Why not allow us to setup as we do with Export how we want the Open with External Editor to handle all this?
    From a color management perspective, this application is hopeless lame. Hard to believe it’s from the company that started the ICC and introduced ColorSync. We can’t control the rendering intent for output color spaces. The Histogram doesn’t tell us squat about the rendered image and there’s no RGB info palette (that again should tell us the values AFTER we produce a true RGB image. How can they call this a Pro tool?
    Message was edited by: digitaldog

  • New Photo in OS X option to edit photo with external editor such as Photoshop has been removed. will this be back!

    Hi
    I have just updated my iPhoto to Photos in OS X and i have noticed that the option to edit photo with external editor such as Photoshop has been removed. will this be back!
    Its now a pain to send a photo directly to my favourite photo editing software.
    Ross

    Thanks Terence
    Totally understand being a new app and not an update.
    So i'm a ammeter photographer and i like the way i can view my photos in iPhoto and i'm happy with the new App for this also, however i like to edit my photos in PS from time to time and i shoot in raw. As i can no longer select edit in external editor from the photo app i tired to drag a RAW photo to PS but this didn't work. i then tried dragging to desktop but this then made a jpeg so i loose my raw advantage. I would like to be able to find my original raw photos easily so i can edit them in PS.
    Hope that makes sense?
    Ross

  • Open untagged JPEG with external editor, then be attached with sRGB profile

    Hi there,
    I wonder why I open untagged JPEG with "external editor" (Photoshop CS) , then the JPEG will be attached with sRGB profile. Of course my color setting on photoshop is "Use the embedded profile".
    I think sRGB is the default RGB space of colorsync utility , because the profile is also sRGB when you check "Add Colorsync Profile" on iPhoto 6.
    Anyway , I want to set up total Adobe RGB workflow , so does anybody know how to change sRGB profile to Adobe RGB profile when opening untagged JPEG directly with external editor?

    Thank you for your reply , Lloyd.
    I am sorry , but I noticed my misunderstanding message.
    As you know , you can change raw and other image files to tiff or psd for external editor. You can select that on the preference. At this situation , if you pass nontagged image file to external editor , then automatically sRGB profile is attached.
    I don't think this is related to export preset for JPEG file.

  • I just opened an "old" project in a newer version of iPhoto and the pages in the book doubled in number with the seam in the middle of each page.  Suggestions?

    I just opened an "old" project in a newer version of iPhoto and the pages in the book doubled in number with the seam in the middle of each page.  Suggestions?

    Start with Try the following:
    1 - delete the iPhoto preference file, com.apple.iPhoto.plist, that resides in your
         User/Home/Library/ Preferences folder.
    2 - delete iPhoto's cache file delete the contents the following folder:
    User/Library/Containers/com.apple.iPhoto/
    Data/Library/Caches/com.apple.iPhoto
    3 - reboot, launch iPhoto and try again.
    NOTE: For Mavericks, 10.9,  go to your Home folder and use the View ➙ Show View Options menu to bring the this window:
    where you can check the Show Library Folder checkbox.
    If that doesn't help continue with:
    1 - launch iPhoto with the Command+Option keys held down and rebuild the library.
    2 - Run Option #4, Rebuild Database.
    Happy New Year

  • Open in external editor -- original color space workaround

    I was frustrated--like other's whose posts I've read--by the fact that when opening files (tiff, jpeg, psd) in an external editor they are all converted to the Adobe 1998 rgb space.
    I am working around this comfortably and by using some Automator actions that I got from Ben Long's Complete Digital Photography site: http://www.completedigitalphotography.com/?p=414#more-414
    In my Pictures folder I have an Auto Processing subfolder with Photoshop droplets and lots of 'hot folders' tied to Applescript folder actions. I made two new folders: OPEN in Photoshop & IMPORT to Aperture
    The Open in Photoshop folder has attached from Automator the following actions from the default Finder suite: Open Finder Items and Move to Trash.
    The Open action is self explanitory, the next step of moving the recently opened file to the trash guarantees that I can't save to the source file. This forces Photoshop to do a Save As even if I hit command + S. The Save As prompts me for a location and I choose the Import to Aperture folder.
    The IMPORT to Aperture folder has attached the Import Photos action from Ben Long's Aperture suite. By selecting the Delete the Source Images After Importing Them option and the Show Action When Run option I get a prompt asking what project to add the new files to and the old files are deleted from my hot folder after the import.
    This isn't a perfect round trip solution because I still end up with two copies of the image in Aperture--even if I was just opening the source image to tweak an adjustment layer. I might create an Applescript that would prompt the user and delete the precvious copy of the image if desired.
    Like many of you I was feeling blue yesterday about rumors of changes in the Aperture team at Adobe. Blue not because I beleive Aperture's going away, instead because I expect if this rumor is true that we will see some delays in the short term while the new team gets up to speed.
    While I am waiting for that to happen I intend to use this discussion site to find creative workarounds for Aperture's current limitations and share them as widely as possible. Many of you are already doing the same.
    Thanks!

    Yes you could do that.
    I was part of the alpha/beta test group for Adobe CS2. Most of my work was with scripting and automation, especially for Bridge. I did have a very good dialog with Bruce Fraser, Seth Resnick and other testers whose opinions are as good as fact in my book.
    The consensus was that most digital cameras--certainly the pro models--had a color gamut substantially larger than Adobe RGB (1998). Note that ACR give the option of developing an image into sRGB, Adobe RGB, Color Match RGB, or Pro Photo RGB; 8-bit or 16-bit. That's the way I want it in Aperture.
    If you use the perceptial rendering intent (this is almost certainly what Aperture is using as its undisclosed default setting) then you will compress the wider gamut of the camera into the smaller Adobe RGB (1998) gamut. If in Photoshop you used the Convert to profile command and choose the perceptial rendering you would probably expand the color gamut back out a little bit. Why bother? Aperture really should have options for open in external editor like the very good export version settings.
    I have in my Aperture library a bunch of 16-bit grayscale scans and some CYMK files that seem to be working fine with the workflow above and Automator actions. (Lab files won't import.) I wouldn't want to go through the convert to Adobe RGB (1998) and reconvert to proper space with these files. My workflow is letting my store these files in Aperture and still edit in native color spaces in Photoshop with minimal effort for a round trip. I like it.
    P.S. I said in my original post that it would be easy to write an Applscript to delete the orignial file in Aperture when reimporting a slightly modified Photoshop version. It may be possible but its not easy in the current version which only has a bare skeleton of Applescript functionality.

  • "Open in external editor" difference in 1.5?

    In 1.1.2 I used to open a file in PS2, make adjustments, add layers, etc. and save back to Aperture. Occasionally, I would then straighten or crop in Aperture, and then re-open in PS2 for further edits at a later time. If I remember correctly, when I did this layers would still be preserved when I opened the file in PS2.
    However, when I go through the same steps in 1.5, the file is flattened when it is opened in PS2 that second time (after straightening or croppping or whatever in Aperture). Could someone check this on their system and let me know if they see the same behavior (I've been having strange issues with 1.5 that others don't seem to have, so I want to be sure it's not my computer).
    Also, is anyone out there still running 1.1.2 that could check the same thing? I may be losing my mind, but I'm almost certain that layers were preserved all the way through.
    Thanks,
    Chris

    Incorrect. They shouldn't flatten PSD files -- in fact with "open in external editor" they never have -- not even in the 1.0 release.
    The "flatten" issue was with 1.0 when you imported PSD files into Aperture... and this was because of Aperture's stated goal of "never touching a master file." This (somewhat annoying) behavior was changed in 1.1. But no version, to my knowledge, flattens PSDs that have been created in Photoshop with "open in external editor."
    I just tried this with 1.5, and I am able to see and edit the layers I created on a PSD file that I previously created via "edit in external editor" which was Photoshop. So that works fine in 1.5, as it did in 1.1.2 and previous version.
    However, I have noticed a couple weird things:
    1) It's creating a third version when I do this, from the original master
    2) Deleting any version created via this manner pops up a dialog "do you want to delete this master and all versions?" which is disconcerting as I just want to delete the extra version, not any versions. It works as expected, but the dialog could use some work I think.

  • Edit with external editor ignores colorspace setting?

    Hi,
    I've successfully gotten Export presets to write files in my desired colorspace (ProPhoto). There is a similar setting for the Cmd-Shift-O "Open in external editor" export in the Preferences pane. But, no matter what I set it to, it ships an AdobeRGB file to Photoshop.
    Am I missing something, or is this a bug?
    Ben

    Works fine for me and have never had an issue so that means A) it works B) Not a bug that affects everyone. I am on the latest version of Aperture 3 but have never experienced this in any version. Might be a problem with your preferences in Aperture - try trashing them.
    Also make sure that your photoshop preferences on color handling are setup correctly to respect the embedded profile and is not converting it to working space on open. This is usually the case with issues like this.
    RB

Maybe you are looking for