"Create new versions when making adjustments" - Lion, Aperture 3.1.3

I recently upgraded to Lion, and then shortly thereafter to Aperture 3.1.3.
While I don't seem to share everybody else's issues with Lion nor with Aperture, I do have one of my own.
In Preferences -> Advanced, I have a box titled "Create new versiont when making adjustment."  It is checked.
My expectation, (and the way things have always worked under Snow Leopard) is that if I select a master image and begin to make adjustments to it from _any_ feature int he adjustments pallette, that I new version will be created, stacked next to the original, and that the changes I am making will be made to the new version.  This is _not_ what is happening.
Instead, the changes are applied directly to the master image.  This is annoying, and will probably be fixed in an update...    I thought the work around would be to manually create the version for the time being, until Apple sorts this out.  That didn't work either.
If I manually create a version, and then proceed to make adjustments to the version, Aperture dows what I would have expected in the first place.  It creates a new version and applies the changes to that.
For example, I right click on a master image and select "New Version form Master"  A new version, titled "... - Version 2" is created.  When I begin to modify Version 2, a new version is created titled "... - Version 3" and my changes are applied to this version... leaving me with the master and Version 2 which are now duplicates of each other.
Even more interesting is this:
Images that were imported into Aperture prior to the Lion upgrade, and the 3.1.3 patch behave as expected, in that a new version is created when adjustments are applied to a master image.
Images that were imported into Aperture _after_ the upgrade to Lion and the 3.1.3 patch act as describd above, in that no new version is created when adjustments are applied to a master image.
So...  Here are the questions:
1. Is anybody else experiencing this?
2. Does anybody know how to restore the correct behavior?

Alright,   I have solved the problem.
Some time ago, I thought it might be neat to import pictures with the Auto Exposure adjustment in place.  What I didn't realize was that if the master image is in the library with adjustments on it, it downs't create a new version when you add additional adjustments.
As soon as I disabled that, and imported some new imges the probelm went away.
Also... I went back to the six or seven project that I had imported while use Auto Exposure and removed that adjustment from those images...  
All is resolved.

Similar Messages

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

  • 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

  • "Create new versions when making adjustments" checkbox - do I check it??

    I have been using Aperture for many months. I'm not sure why, but I looked at my prefs the other day and the checkbox above was unchecked. Two important questions:
    1. Which way should this be set??
    2. Is Aperture still keeping the original separate from any edits I am making? PLEASE tell me that my originals have been kept separately!!! : )
    Thanks in advance,
    Erik

    1. It's a Preference. It should be set the way you prefer.
    2. Aperture never adjusts the master.
    When you look at an unadjusted image in Aperture, you are seeing +Version 1+. You can adjust Version 1, or you can create a new version and adjust that. Or you can set the preference, and when you make adjustments, a new version will be created automatically. This can cause unwanted versions to accumulate. Or maybe they are not unwanted.
    The Master is never affected, just the versions.

  • 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

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

  • No new version when modifying a TIFF?

    I exported CR2 to PS, returned the TIFF to Aperture. But when I make a change in the TIFF, it produces another version.
    "Create new versions when making adjustments" is NOT checked.
    Is there anyway to modify such a TIFF without having another version created?
    Thanks

    Hi,
    Not wishing to be pedantic but helpful here. The version is not a ghost in one important sense: it is a collection of edit instructions to apply to the underlying master. Hence it is mere kb in size vs the TIF or RAW or even JPG master.
    It also explains some of the lag between clicking on a version thumbnail and seeing the resulting image fully rendered and available for further editing. The more complex edit instructions and the more of them (spot/patch, straighten especially) will give rise to a slower rendering of the image .... which is where Previews come in useful to give a better feel for the image while all the instructions are being applied in the background.
    That said, the Aperture engine is still slow for spot/patch and straighten edits especially, but this must be balanced against the disk I/O time that would be consumed reading multi-Mb RAW or TIF files. Oh for instant disk access and read time with infinite processing capacity!

  • Image Disappears when Adding Adjustments in Aperture 3

    I am experiencing odd behavior when using the adjustment tools in Aperture 3. I tried to crop an image and instead of staying on screen for me to finish the adjustment, the image disappeared. I was able to save it by undoing. I created a version of the image and I could crop that OK. I have Add New Version when Making Adjustments checked but it does not seem to be working.

    I've had a similar "disappearing" image problem when trying to apply the retouch tool. I don't have the "create version when applying adjustments" preference checked though. Hopefully these issues are additional 3.0 bugs that will get fixed in 3.0.1. Be sure to report the issue to Apple using the "Aperture > Provide Aperture Feedback" menu item.

  • 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

  • How can I create a slideshow that depicts only a version of a photo rather than the original? Since the original and new versions are saved together, the aperture slideshow often choices the original rather than the desired version to display/

    How can I create a slideshow that depicts only a version of a photo rather than the original?   Since the original and new versions are saved together, the aperture slideshow often choices the original rather than the desired version to display.

    There are two things we use the name "Slideshow" for in Aperture:  a Slideshow Album, used for making Slideshows, and the Slideshow that is made.  (Imho, it is a design mistake to not call the containers used to create Slideshows, Books, etc., "Albums".)
    The Slideshow will use the Album Pick from any Stack.  A good way to use Aperture is to promote the Image you want to regularly use (such as, for example, a Version with adjustments) to the top of the Stack.  This makes it the Stack Pick, and will be the default Album Pick.  If you haven't done that, you can still change the Album Pick for any Stack in a Slideshow Album.  Expand your Stack(s), select the Image in each Stack that you want to be the Album Pick (and thus shown in the Slideshow), and "Stacks➞Set Album Pick".  (Note the keyboard shortcut; there is also a Toolbar icon for this.)  The change is immediate.  The Slideshow will always show the Album Pick (or, if there is not one, the Stack Pick) for every Stack in your Slideshow Album.

  • HT1550 I'm having trouble with importing them into iTunes and converting them at the same time. when i hold down option over the files i can't find where its supposed to say create new version. is this if you're in iTunes?

    I'm having trouble with importing them into iTunes and converting them at the same time. when i hold down option over the files i can't find where its supposed to say create new version. is this if you're in iTunes?

    You can't do it in one step. Add to iTunes first, Once the tracks are in iTunes you may convert to a different format.
    tt2

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

  • 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

  • Problem in creating new versions for existing DIR using CV01N

    I am working in SAP ERP 6.0 EHP 4.0 system.
    I have problem in creating new versions for existing DIR using CV01N
    I create a DIR version 00 with functional location and mpd cycles. Then when i try to create a new version by copying the contents created from already created document.I change the MPD cycles in the new version and save it.
    once when i display the first document created the mpdcycle specified in version 01 is copied to the 00 version.
    The document is inconsistent where versioning of document doesnot work properly wrt MPDCYCLE and MP HEADER.
    The problem which i found was the document identification guid remains the same for all the document versions getting created.
    The same is working fine in SAP ERP6.0 EHP3.0 sytem.
    Please someone help me in resolving the above issue.
    Regards,
    Prasad.B

    There is a change in the standard code.The reason for the above problem was  because of a missing Enhancemnet point in a standard function module 'CV110_DOC_CREATE_WITH_TEMPLATE'.
    IS-ADEC-MPD  - Enhancement to copy MPD data
    ENHANCEMENT-POINT CV110_DOC_CREATE_WTEMPL_01 SPOTS ES_SAPLCV110.
    +*$*$-Start: CV110_DOC_CREATE_WTEMPL_01----------------------------------------------------------$*$*+
    +**ENHANCEMENT 1  ZSF_AD_MPD_SAPLCV110.    "active version**+
    +*** copy MPD relevant data from templ. doc to current doc**+
      +**CALL FUNCTION 'MPD02_COPY_MPD_DATA'**+
        +**EXPORTING**+
          +**is_draw = ls_draw**+
        +**TABLES**+
          +**ct_drad = lt_drad.**+
    +*ENDENHANCEMENT.**$*$-End:   CV110_DOC_CREATE_WTEMPL_01----------------------------------------------------------$*$*+
    Created a custom enhancement point similar to SAP ECC6.0 EHP 3.0 system.
    The reason was the buffer was not getting cleared previously.After inserting the above code the DIR's are getting created withot any issues.
    Regards,
    Prasad.B

  • Most options in itunes "create new version" greyed

    itunes only gives me the option to create an apple lossless  version when i select a song in my playlists or general music section to create a new version.
    This doesn't make sense as most of my music was uploaded using applelossless.  The average song size  is 35 mb for a 5 min. song. This doesnt seem to me to be a compressed song/file.
    The other options "create ipod or iiphone version" and create ipad/tv version are greyed out.  Why?
    I do need the create iphone version .  How to do this and what happened to create MP3 version as an option here?
    thanks

    LIkewise, I have a mac mini belonging to a client and I told him to compress ( "create a new version" of his video library) he said all items greyed out. I collected it Friday , sure enough all  his m4v with drm and his mp4 ( without DRM) will not allow him access to create a new version. I dragged one his films into my account. Authorised the account and it plays etc, the create new version option is there for my whole library bar this film. I am tempted to strip out the DRM but I dont know if it will resolve. I would love to hear from Apple !!!!! or someone older/ younger but wiser what may be the issue.
    Regards
    PC

Maybe you are looking for

  • Windows Reactivati​on Error

    After successfully dowloading the Microsoft office Home and Student 2010 I was unable to open any of the pre-paid for files such as Microsoft Word. So, I deleted the files and attempted to re-activate Microsoft Office Home and Student (it cearly stat

  • Itunes wont read music unless CD or ipod is connected

    I just switched my ipod library over from my mothers computer to my own PC and now itunes wont let me play my music unless the ipod is plugged it. It also wont play the cds i had on recovery disks unless the disk is in. I get a message that says... "

  • Unable to finally close blanket purchase agreement

    Hello, I am unable to final close the blanket agreement due to error: "Open releases exist against the purchase document." I checked and all the releases status are closed, the amount billed matched amount received. Does anyone know how to fix this?

  • Sometimes type won't obey styles!

    I'm working with type and creating new styles...sometimes I size the type to what I want and then create a new paragraph style. I assume that new style will "know" the attributes of the selected type...which it does, but as soon as I click "OK" the t

  • Mac Mini and OS X 10.4.10 Update, complete failure

    I have tried to install the 10.4.10 update on my Mini Mac intel core duo 2 times. To put it simple, 10.4.10 does not agree with my mini mac. It does install and I can log out an log in again, BUT! the next day it does not boot anymore!!! I installled