Changing color space when opening in external editor

Hi
Is it possible to have aperture open a raw file in Photoshop in a colourspace other than Adobe RGB and also in 8bit rather than 16bit.
Also I notice that it only saves as PSD or TIFF if you want to have the retouched file linked to the original master. Is there a work around to change this to jpeg but maintain the link to the master file.
Thankyou

OK
I understand why, in the interest of maintaining max file integrity that apple restricts exporting to 16bit and PSD or TIF.
However Adobe 98 is'nt always the best or most convenient colourspace to open a file with an external editor. What i'm looking is the option to change the export colourspace.
PS: I'm only looking for the option when using the 'Open In External Editor' option. I know when exporting files out of aperture that there are many more options.
Thanks

Similar Messages

  • 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

  • Error "Expected end of color space" when opening converted OTF - PDF.

    Hi experts,
    I need help. I'm converting from otf to pdf and it works fine. However when i tried putting a bitmap 256 color to the smartform and generate pdf with CONVERT_OTF FM the pdf result in an error "Expected end of color space" when opening the document and it goes blank.
    Can anyone tell why ?
    Thanks,
    Felix

    Hi Peter,
    I can open it with another acrobat version. However, the image is not displayed. Do you know why?
    Thanks

  • Match color space when opening image in photoshop

    hi, i have new macbook air and when i export image from lightroom as TIFF (pro photo RGB) and import to photoshop, it asks what to do that embedded color space does not match with settings, therefore i changed that in photoshop (edit/color settings to pro photo rGB ), however my question is:  if there is any problem because my notebook display is set (system preferences) to "color LCD"
    when i set my display as pro photo RGB, it base blue tone, i must use Apple's preset called "colour LCD"

    Good day!
    if there is any problem because my notebook display is set (system preferences) to "color LCD"
    Your screen profile should generally not be set to your RGB Working Space as this would kind of negate Color Management.
    And in the absence of a proper custom profile the maker’s default profile seems to be a valid choice.
    Regards,
    Pfaffenbichler

  • Lightroom 4.2 changes color temp when opening existing image

    I have installed LR 4.2 two days ago, and have run into a serious problem.   When in develop mode, when I click on an image in the film strip, LR opens the image and changes the color temperature dramatically.  The blue/yellow slider moves to the far left.   I think this is the only change, but didn't check.
    The action is not in the history, so I cannot undo it.  When I quit and restart, the change is still there.  There is no way to recover the pre-existing setting.
    This is a serious problem obviously, so any advice on how to proceed is welcome.  Can I convert my catalog back to 3.6?
    Thanx,  Job Honig

    foto18, you're not alone in this: I have the same exact issue, and can't get to understand what's in LR's mind.
    I can even show pictures changing temperature in preview/full screen just because i select/deselect them.
    Of course, this throws away hours of previously done work - but maybe it's just me?
    Here and example: picture #2 is a virtual copy of #1. Right now, #2 is selected (we're in edit mode).
    Now I hover onto picture #1, and - voila'! - the temperature goes down. And if I go back and select #2 - bang! - temperature of #1 goes up again; on its own that is. This is bizzarre to say the least.
    Help much appreciated. Would love to provide this as a bug report - because that's what it really looks like anyways - rather than a forum input.
    Thanks,
    .salvo

  • 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.

  • When trying to open in external editor I get this warning when going to Photoshop CS6: Could not complete your request because an unexpected end-of-file was encountered.

    Aperture: When trying to open in external editor I get this warning when going to Photoshop CS6: Could not complete your request because an unexpected end-of-file was encountered. I can export and open via Photoshop or open directly from file-just not through external editor. Gerry

    Hi gerry,
    does this happen for a particular image only, or for all images?
    And does this happen only from your account or also from other user accounts?
    Léonie

  • 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 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

  • Error -50 when using an external editor

    Having finally graduated from iPhoto 2, I found some "interesting" behavior in iPhoto '08...
    iPhoto objected when I tried to save an externally edited photo back into its slot in iPhoto -- nothing lost, just an error dialog and the edits were not applied. Since it was repeatable, it made me curious.
    When you choose external editor to edit a photo in iPhoto 8, the first thing iPhoto does is stash a copy of the original (and activates the "Revert to Original" menu item for that photo). Just editing in iPhoto 8 doesn't do any of this until you accept the changes -- that's an important distinction, because if you change your mind with the external editor (and make no edits, or cancel them without saving), that stashed copy stays in the "modified" folder.
    For all practical purposes, it's "forgotten" unless you happen to choose "Revert to Original", in which case, the extra photo is unceremoniously purged. Now, if you don't think about purging that forgotten copy and later decide that you actually do want to edit that photo in an external editor after all, iPhoto will again stash a copy while your external editor is opening. It gets stashed in the same folder that already has the previously stashed (and forgotten) image file. If the file were overwritten, there would be no big problem, but it does not get overwritten, and you can't have two files with the same name in the same folder. So the finder appends a "_1" to the end of the file name -- and THAT sets up the problem. When you finish editing and save the file back to iPhoto, you will be (unintentionally) trying to add a file to your collection that iPhoto doesn't know about. The filename change to avoid a conflict in the folder is not reflected in the iPhoto 8 database.
    Older iPhoto versions would have let that pass (and that's why there were always problems with database corruption), but the newer version catches the attempt and simply doesn't allow the save to take place.
    That's the "why it happens", but it's only my second day with iPhoto '08 and I'll need a little more time to work out how to selectively fix the problem without damaging the database -- a database rebuild does not purge those stashed photos (and you wouldn't want it to because most of them are the originals for photos that were actually modified).

    Brie Fly:
    I tried to replicate that using Photoshop and could not. When starting an edit with PS a file is created and remains is I abort the edit in PS. However, if I edit again with PS and save the original modified file is changed with no other file being created.
    What 3rd party editor are you using? The only time I get a _1 file is when I move a file to an event that has the same file name as a file already in that event.
    What system are you running and are you at iPhoto 7.1.1, iLife Support 8.1.1 and Quicktime 7.3?
    Happy Holidays
    TIP: For insurance against the iPhoto database corruption that many users have experienced I recommend making a backup copy of the Library6.iPhoto database file and keep it current. If problems crop up where iPhoto suddenly can't see any photos or thinks there are no photos in the library, replacing the working Library6.iPhoto file with the backup will often get the library back. By keeping it current I mean backup after each import and/or any serious editing or work on books, slideshows, calendars, cards, etc. That insures that if a problem pops up and you do need to replace the database file, you'll retain all those efforts. It doesn't take long to make the backup and it's good insurance.
    I've created an Automator workflow application (requires Tiger), iPhoto dB File Backup, that will copy the selected Library6.iPhoto file from your iPhoto Library folder to the Pictures folder, replacing any previous version of it. It's compatible with iPhoto 08 libraries and Leopard. iPhoto does not have to be closed to run the application, just idle. You can download it at Toad's Cellar. Be sure to read the Read Me pdf file.

  • "open in external editor" not working

    I use "open in external editor" a lot to edit pictures in Photoshop, but it has stopped working. Now it launches Photoshop, but doesn't open/load the relevant image.
    What has changed since I had this working?
    I had a couple of kernel panics, and used "archive and install" to re-install Tiger, and then 10.4.3.
    I am using iphoto 5.0.4 and Photoshop CS 8.
    Any remedies/help gratefully received.

    Hi Nige,
    It is a Photoshop problem and probably because it is missing files.
    this is an old copy/paste from MacFixit it.
    Try this suggestion I copied and pasted from MacFixIt first
    "Photoshop CS: Fix for file opening problem Yesterday we reported that since installing Mac OS X 10.4, Photoshop CS refuses to open any new files or create any new documents, reporting a "program error" when one tries to do so. Our previously reported workaround involved re-installing Photoshop CS, but MacFixIt reader Bryan Schappel now offers a faster solution:
    "This happens because the Archive and Install option does not copy over a necessary folder for Photoshop. The critical folder is called 'ScriptingAdditions' and is stored in the main Library folder. This folder contains one file 'Adobe Unit Types' that makes Photoshop open files that have been double-clicked or dragged to the PS icon in the Dock.
    "Simply move this folder (and file) from the 'Previous System' backup to the Library folder, relaunch Photoshop and all is well again. No need to completely re-install.""
    I copied an pasted instead of putting the link in because it is not on the front page and you would have to search around to find it. Hope it is ok to do that here. If you don't still have the folder then you have to reinstall PhotoShop.

  • "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.

  • PS CS6 Smartobject - Changing color space not working

    If I initially open a smartobject from ACR into PS CS6 using one color space, eg. sRGB, should it then be possible to click back into ACR and change color space to Adobe RGB ???
    This is important to me, since working most of the time in sRGB, batch editing lot's of files (for timelapse-video, hence sRGB), but sometimes it may be nessecary to go back and use Adobe RGB to make a best possible print of one of the stills.
    This is not working for me. I thought I should be able to do absolutely non-destructive editing when working with smartobjects from ACR, but this may seem to not be the case.
    Ole

    I understand now that a copy of the original RAW file is made when working with SO.
    Still, when checking what color space I am working in (in PS CS6), after changing from sRGB to aRGB, PS still tells me I am working in sRGB!!
    So what I am asking, going back from a SO in PS, into ACR, to change the color space, does not work.
    Is there a workaround for this?
    Or is it something I still do not understand here?

  • 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

  • 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.

Maybe you are looking for