Aperture not creating new version of raw image when editing in external editor

I have my export settings set up in Aperture 3.5.1 as editing int Photoshope Elements 12 as Tiff files. When I right click on a raw photo in aperture and say to edit in PSE, it will open it in the program, but only in camera raw.
This happens even when I have made edits to that particular file, such as exposure. This is causing problems with saving back to aperture. I have troubleshot this with Elements and the problem seems to be that Aperture is not creating a new version on export.
Can you tell me what I need to do?
Thanks so much for any insight.

What you have described is not how it is meant to work so it sounds like there is an issue on your system.
Try running the first two first aid procedures (repair permissions and repair database) as described here:
http://support.apple.com/kb/HT3805
I think this should fix the issue, but let us know if it doesn't.
PS: When you drag the image from Aperture to PSE on the task bar, you are sending the JPEG preview to PSE, so that's an unrelated process.
Andy

Similar Messages

IPhoto 11 loosing images when edited in external editor?

Hi guys.
I am using iPhoto 11 and have it set to "edit in external edit" when i right click on an image. The aspp is Photoshop Elements 9 (PSE9) but when i save the image from PSE9 it duplicates it in iPhoto and i can see it as a thumbnail but when i double click it to view all i get is an exclamation mark and no image?

Thanks for the reminder; I think I read that, too, though it sounded dubious. The signal-to-noise ratio on this issue is murky at best. I submitted a feedback for enhancement, in addition to my bug report from yesterday:
I love iPhoto and have used it for years. But iPhoto '11 has a 'terrible new feature' or misbehavior that really needs a second look.
Please change iPhoto '11 back to the way it's behaved for 2-4 generations since using an external editor was first introduced: the new behavior duplicates photos before editing them the first time. The old behavior was to edit the existing photo and use "return the original photo" in the event that a user wanted to rollback the changes.
The old behavior was intuitive and harmonized with the behavior of using the internal iPhoto editor -- i.e., a user was not expected to develop a different workflow or bloat their library size.
The new behavior is neither intuitive nor efficient. It creates an unequal workflow whether the user decides to use iPhoto vs. external editor. That's just not consistent with the behavior of iPhoto for the past several generations of its existence.

System should not creates new version when value of PO increased..

Hi Experts,
Need your help to solve this problem. When i increase value of PO it should retrigger Release strategy but it creates version first, then i have to tick completion indicator and check then only release strategy retriggers..
It should not create new version when change po
Please check below screenshot
Please help

Hi
Please reveiw the following points in note
   - 493900 FAQ: Release Strategy
      4. Why is the release strategy not determined?
     "If you use version management, the determination of the release
      strategy starts when the version is completed.
      You complete a version by setting the "version completed"
      indicator in the version tab."
   - 662993 Resetting an already occurred release
     You edit a purchasing document with release strategy.
     You change the quantity or the price. In spite of that, the
     already set release is not reset.
The release strategy works the same with or without version management
active - the only difference in case - version management is active -
is that if release is to be reset, it will be reset only on version
I hope this helsp to clarify this issue
Kind regards,
Lorraine

Help with resaving images once edited in External Editor

Using Aperture 1.5.3 and importing all my images in RAW from my Nikon D1.
Imports all images just fine.
When I open an image with External Editor I go to my copy of Photoshop CS2 with no problems.
However, don't seem to be able to figure out how to save this image into the same part of the Aperture library once I've edited it (maybe giving it a name like xxx_edit or perhaps what would be better is Apeture recoginising it as a new version). Currently, what I am doing is saving it to a working directory then reloading this image into the relevant part of the Aperture library using Import. Doing this is not exactly efficient and also means that Aperture doesn't recognise this edited image as a version of the original.
Is there an easier way of doing this? Can't seem to find it in the on line manual.
Cheers,
Chris

You're over-complicating it.
Simply hit File>Save once you're done in photoshop.
ian

New image version has artifacts when editing in external editor (CS1)

For some reason when I send an image from Aperture to external (CS1 in this case) I'm getting some vertical tearing artifacts in the new image version. These are vertical stripes the entire height of the photo, perhaps 1-2 pixels wide, and the color of the pixels in the stripes roughly matches the area around it, but obviously are incorrect. There are one or two stripes per image.
These are .NEF raw files from a Nikon D100 and the problem just recently began.
The only change I've made on my system is a rather significant one. I installed a x800xt video card. Could this be causing the problem?
Running the latest OSX. Everything else is fine in Aperture.

Changing the video card changes the processing engine in Aperture, so yes, that could absolutely be related to the problem.
However, that card should work without issue -- so not sure exactly what might be going on.
Are you running Aperture 1.5.2 with the digital camera RAW updates from the Aperture page?

Aperture creating new versions unexpectedly

One of my projects in Aperture started behaving unexpectedly yesterday and I still haven't figured out why. I was reviewing proofs with a client and we were making selections and adjustments to some of the images. We were working in a smart album that was filtered on 5-star ratings. We made a few new versions of some of these images within the smart album, made adjustments, and ultimately selected her picks by adding the keyword "pick" to her selected images. In retrospect I probably will change that flow so that when I make my original selects I will rate them as a 4-star and then up it to a 5-star when the client makes their picks.
But for now, back to the problem. All was going well with the workflow until I tried to rearrange some of the images within the smart album. When I dragged the first image to a new location it created new versions of several images. I think this happened multiple times before I realized what had happened, so before I new it the album was filled with duplicate versions. I deleted the duplicate versions, but I find that they keep cropping up unexpectedly. If I go to the parent project and then return to the smart album, it makes a duplicate version of every image in the album.
A light table and a book within the project are now also giving me trouble in that they claim to have images in them, but even with all queries turned off they do not show any of the images (and yes, the "show all images" button is selected).
Any thoughts on what could be wrong?
G5 Mac OS X (10.4.3)

Mmm...I don't think this explanation tells the whole story.
Dragging an image out of the project container and into an enclosed (non-smart) album does NOT automatically generate a new version of the master image local to that album; instead, the album is populated with a new reference to the original version. Dragging that same image again out of the project container - or the first album - to yet another album generates yet another reference to the same underlying version.
Edits performed in any of these containers propagate to the images in all containers (within a particular project, of course), demonstrating that each type of container holds merely a reference to the project's single original version.
The Aperture User Manual is a bit ambiguous in its description (Chapter 5 pg 113) of the distinction between "copying" and "moving" images between projects and albums; I believe that when it refers to copying versions it's really talking about copying REFERENCES to versions between various containers.
So, long story short, I don't think moving images between the various types of containers within a single project can explain your duplicated images.
15" Alu PB 1.25GHZ G4 FW800 1GB RAM 100GB HDD Mac OS X (10.4.6) Aperture 1.1.1

Reason for creating New Version Best practice

Hello SAP Gurus,
We know we are creating new version of the DIR when it is required to make a change in the original keeping in tact the Older file also for reference,
we want to know when a new version of the document is getting created how can we specify, why and what made us to create this new Version, we would like to capture this reason in SAP so the user can easily come to know why this Version is created,
can you please let us know, where actually are we capturing this details while creating the new version,
i know there are lot of free entry fields like Generic object Text field, Long text field, change the description, place the text in the WR log field of the new Version,
which is the best practice so that the user can easily come to know the reason why this new version has been created,
may be they should see this reason details in CV04N search as well, or immediately when opening the new version.
Thanks and regards
Kumar

Hello Kumar
Hope following explanation will clarify your questions
We have to classify our documents broadly in two category 1) Controlled document --means which under goes various level of / Inspection / review / approval etc with in Organisation e.g. Engg Drawing , Standard Operating Procedure for business purpose, best way for this is use Engineering Change Management (ECM)Functiuon and when you make any up versions, you can track / write key docu ment history in ECM
also when you do up version let say in Micosoft word , you can maintain simple table to track what is purpose of change, in what location you are making chnage and its justification.
For Engineering drawing of 2D /3D we can use Redlining functions to createt the Lawyers to know reviwers observation so that next version thopse are taken care
2) Uncontrolled Document---Generally they are less significant from document Change Control point of view
Hope this is useful
Regards
GIRISH

Aperture creating new version of image for each adjustment applied!

To anyone out there who can sort this one out, I will be forever grateful!
Here's the problem. I'll be jamming away in Aperture, adjusting photos like a madman. After adjusting a random number of photos (it usually varies between 5-30 photos or so after starting Aperture each time), the adjustments panel will no longer update when I click on a new image (i.e. it holds the info from the last image I adjusted and will continue to apply new adjustments to that last image even if another image is highlighted). If I switch to the metadata panel and then back to adjustments it will refresh itself and recognize the currently selected image (although I have to do this for EACH image I want to adjust once it starts acting up like this). The BIG problem is that even if I get the adjustments panel to recognize the selected image at this point, for EACH adjustment I apply it makes a new version of the image. For example, if I first change the contrast, it will make Version 2 of the image and select it (which is what it's supposed to do for the first adjustment, because I have "create new versions when making adjustments" checked in my preferences), but if I then make another adjustment like changing the saturation, it makes Version 3 of the image (from the master, so that only the saturation adjustment is applied and not the contrast adjustment). As you can imagine, this utterly destroys my once incredibly efficient Aperture workflow and makes it pretty much impossible to use Aperture for adjustments unless I turn off "create new versions when making adjustments" in the preferences, at which point it does seem to work again (although I've only tried it on a few images, so not 100% sure it will work properly even then). If I restart Aperture (or my computer), it will work normally again for a few pictures and then will start acting up again with the same problem.
Originally I was running into this problem on my PowerBook G4, and so I figured it was just because Aperture didn't like my wussy G4 processor and was acting up when the load got too heavy (after all, the adjustments would work fine for up to 30 images or so). However I recently purchased a sexy iMac 24" 2.8 GHz and maxed out the RAM to 4GB, but I'm still getting the same darned problem with Aperture on my iMac. Yes, I'm using the same library of photos I was using on my PowerBook G4.
This problem has been plaguing me for about 3 months now (everything else in Aperture works fine so I'm still using it to import and organize my photos, I just haven't been able to make adjustments on large groups of pictures for a while), and I've searched and searched these forums countless times to see if anyone has run into similar problems, but I've not seen a single mention of it. I've also tried EVERYTHING mentioned for similar problems (rebuilding library, vacuuming database, erasing com.apple.aperture.plist preference file, repairing permissions, reinstalling Aperture, making burnt offerings to Steve Jobs), and NOTHING is working. ARRGH!!
For those who might have some words of wisdom to offer this delighted-***-miserably frustrated Aperture user, here are a few more details about my setup:
I have a library of about 37,000 photos, the vast majority of them being RAW .CRW files from a Canon 10D. The 25GB library file is stored on my internal hard drive, and all photos are referenced from an external LaCie 500GB FireWire 400 hard drive. I have a LOT of export plug-ins installed in Aperture, but no image adjustment plugins. I have generated previews turned off for all projects. I've had the same problem on both my PowerBook G4 and new iMac 24" 2.8 GHz. One other thing worth mentioning is that instead of upgrading from 2.1 (which was already giving me this problem) to 2.1.2, I downloaded the full version of 2.1.2 and installed it. I noticed that my 2.1 Aperture.app file was less than 100MB, whereas the 2.1.2 Aperture.app file is over 300MB. Don't know if that's normal or not.
The only other thing I can think of to try at this point is to load a new library into Aperture and import a large group of pictures and make adjustments to them to potentially see if my problem is being caused by Aperture or by the library. Will probably try that tomorrow.
I would appreciate any advice or feedback anyone can offer about this nasty little problem, as it's giving me a serious hormonal imbalance.
THANKS!

Thanks for the reply RB, but my current workflow depends on me creating new versions when I make adjustments. I suppose as a temporary solution I will probably have to either turn this preference off or just be willing to constantly restart Aperture. At least I finally found another thread with the same problem, so finally I don't feel completely alone in the far reaches of the Aperture universe. For anyone who is interested, here is the link to that thread:
http://discussions.apple.com/thread.jspa?messageID=8555067
It appears this problem is closely related to the ubiquitous black viewer problem that seems to be plaguing far more users than my issue (although I've run into the black viewer problem a few times myself), as both problems force Aperture to output the following message to Console:
Main Thread Exception in Aperture: * -NSCFArray objectAtIndex:: index (1) beyond bounds (1)
It seems that both of these problems existed in Aperture 1 and 1.5 up until the 1.5.6 upgrade which seems to have fixed it, but then with Aperture 2 the problem seems to have returned. At least that's the gist of what I've been reading on a number of threads. Whatever the case, I hope Apple gets this sorted out in their next update!
As it appears there is no proper answer to this problem at the moment, I'm gonna go ahead and mark this thread answered (and since you were kind enough to at least take the time to reply RB, you can be credited with the answer... thanks!).

Create new album with new versions of selected images

Is there an easy way to create a new album containing new versions of the currently selected images?
Some explanation where I need that feature:
First I go through the images and adjust them for the some purpose. Then I need the same images in another place also and I now that there I need them to be a bit brighter or cropped differently or something. So it would be nice to be able to just select the images and say "I want a new album containing new versions of these images".
Is that possible somehow? Have I just missed something while reading (riffling through) the manual...

There is not such an option but it could come in handy. You can use Aperture's feedback to suggest it.
For now the only way would be duplicate versions and move them to another album.

I have a new Mac and I migrated mi old one to this. I can not open iTunes because a message stating "iTunes Library.itl" can not be opened because it was created in more recent version of iTunes. There is not a new version to download.

I have a new Mac and I migrated mi old one to this. I can not open iTunes because a message stating "iTunes Library.itl" can not be opened because it was created in more recent version of iTunes. There is not a new version to download. How can I fix this?

Go to iTunes > about iTunes. What version are you running? If necessary, hold down the option key while starting iTunes and create a new, test library so it will start.

I am able to 'create a new version from original' but when I try to export the original, I only get a .jpg with the XMP file. The original is obviously there but why can't I access it please?

In Aperture 3 when I right click on an image I am able to 'create new version from original' which suggests that the original is there. When I try to export the original I only get a .jpg with the XMP file. These particular images are from 2010, has the RAW file become disconnected somehow? Please, how do I get access to the RAW file for editing in Ps? Thank you. Thomasrevil.

Sorry leonie, 'Use RAW as Original' is not an option for the image shot with the Canon.
Then your Import settings must have been different, when you imported the Canon photos.
You can check, if there is still a hidden raw file somewhere. If the image has been imported as a pair, you should see the "J" badge in Browser and Viewer, if you enable badge overlays. This indicates a pair, with the jpeg as original.
Select one of those images, and then relocate the original files "File > Relocate original" to a folder, where you can inspect it. Use "File > Show in Finder" after ward. Look, don't touch .
Then put it back, using "File > Consolidate".
Do you see your raw files in the folder, or is only a jpeg there?

Create new versions when making adjustments?

Hi,
What does anyone suggest this setting should be set to? It's on the Advanced Tab in Preferences.
I think it was un checked when I installed the Trial Version.
The help file stated the following:-
+Create new versions when making adjustments” checkbox: Select this checkbox to have Aperture automatically create a new version when you adjust a selected image. The adjustment is applied to the original version and the new one is left untouched.+
So when I edit an image the the software makes a copy and the original is altered? What happens if it's left un checked?
Any help on the whole editing thing would be gratefully received.

This is just a way to automatically create a new version when you make an adjustment. The new version is stacked with an unaltered version, allowing you to quickly see them side by side. What you have to remember is that the *original file is never altered*. This is all virtual. What is called original in this case is in fact an original version, not the actual file. The actual file is called the Master. Very important to understand the distinction.
I personally leave this off. I never use RAW files without adjustments so there's no point in keeping an unaltered version around, plus it tends to quickly multiply versions and just creates clutter. If I want to see the original file I just hit M (this is the default command key for Show Master). Hit M again and I'm back to my version. If I've created a version and want to do a new different looking one starting from scratch, I can select New Version From Master: presto a new "original"!
If I've worked on a picture and want to create a BW version, chances are I want to keep the work I've already done as a starting point. In that case I select Duplicate Version and do my BW on the new version. Again, I'm never actually duplicating files and I'm never actually altering pixels, original or otherwise. This is all a set of xml instructions that Aperture applies when it displays the files.
Helping?
Message was edited by: Jade Leary

Preference to "Create New Versions when making adjustments"

Isnt the option in Preferences "create new version when making adjustments" seem irrelevant when Ap doesnt touch the original (master) anyway? How is this option intended to be used? Most of the imags for me would be slight tweeks so I wouldnt necessarily want every one of those showing as a 'full new version'.

yeh, that would seem logical wouldn't it - to create a new version for each session... but that's not what happens.
i mostly use the HUD and don't close between adjustments but i do sometimes use the side panel which i also don't hide/close between adjustments. i can't remember whether making adjustments via the side panel creates new versions for every adjustment, certainly this behaviour happens when i use the HUD and i'm fairly sure i would have tried the side panel to avoid this annoying behaviour but i can't say for sure and will have to test the side panel behaviour next week if i get time.
even with the preference for 'create new versions' turned off, there seem to be certain images that always create a new version when i make an adjustment - whether using the HUD or side panel. I haven't figured out an exact pattern to this but it seems to be something to do with those files that have been 'sent to external editor'. subsequent adjustments within aperture always create a new version - haven't a clue why...
just as an aside, sometimes when i make adjustments (particularly sharpening or noise reduction) i get single pixel wide horizontal lines of noise appearing across my images, which are there when i print or export too, not just screen artifacts due to a badly processed preview...hmmm...anyone else noticed this or has found a post about ways to avoid this?
all that said, aperture is a godsend for my workflow
MacBook 2.0 White Mac OS X (10.4.8)

Creating new versions and file size?

Hello. My understanding is creating new versions in Aperture consumes very little file space (i.e., for adjustments, etc). I'm finding I like to have the "create new version" property enabled so I can have multiple choices in a stack per image in my projects.
Can someone please confirm this? I don't want to waste a bunch of space if I don't have to.
Thanks!

all that is done when creating a new version is a "sidecar" file that gives aperture instructions on what and how to convert ...
so, it consumes very little space ... go ahead and version away ... this is really a key feature to aperture ... with iphoto, every new version was an actual new file as well ...

Elements 11 will not let me download my raw images.......................MAC PRO 10.6.8 OS

Elements 11 will not let me download my raw images.......................MAC PRO 10.6.8 OS
Says file not supported but all the tutorials says it will supoort and edit raw images

Every camera has its own raw format and ACR must be updated for each new model that appears. The canon 70D requires at least ACR 8.2, which theoretically requires PSE 12. You can use the adobe DNG converter (free) to convert your files to DNG files that your version of ACR can understand, or upgrade to PSE 12, or use the Canon software to convert and use PSE for further editing. You could also try doing a manual install of 8.2 to see if it would work for you. Is this the mac app store version of PSE? That is much harder to update.

Aperture not creating new version of raw image when editing in external editor

Similar Messages

Maybe you are looking for