Adjustment new version

Making an adjustment with 3.4.2 does not create a new version in the library, is that right? I had to reinstall the application and wipe out the plist, so it's possible I changed a setting. It's nice to have seperate versions of a photo without having to create a duplicate as step one.

OK, I found it. Preferences / Advanced / Create new version

Similar Messages

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

Image adjustment creates a new version, Viewer distorted or disappears

For the last two days Aperture 2.1.2 creates a new version of of an image when I adjust the image.
Then the image will distort in the viewer - applying excessive edge sharpening or becoming blank or only showing a small part of the image. Applying a definition control trashes the viewer image.
This occurs with images that originate from RAW files or from Jpeg. It is affecting images that had been previously processed correctly.
The master files are referenced and held on the same 500GB drive as the library which has 100gb free.
If I export any of the images that are corrupted in the viewer the image created does not have the corruption.
I cannot remember applying any change to the Aperture program, the change in behaviour started in a session where I had worked on about 60 images. I have restarted Aperture and rebooted the computer and the problem persists and corrected any permissions (none reported as being corrected).
Any suggestions please.
Thanks for any comments

Thanks for pointing out the pref option - unchecking the option does prevent the creation of a duplicate version.
However I still get a blank image in the Viewer when I then change the definition or shadows setting, reset it to 0 and the image returns.
Thanks again for pointing to the prefs option -

Aperture creates a new version every time i apply a new adjustment!!!

1.5.6. is my aperture version. and recently it started to create a new version every time i apply a new adjustment. It's not the biggest bother for a couple of images, but for documenting a whole event with 300 images...well that might be a... mighty issue! How do I get this to stop? Any ideas?

Preferences->General->Create new versions when making adjustments.
Uncheck it

Creating stack automatically with new version when new adjustment made

How do I do it? Actually I don't want that to happen but the way I have aperture set up creates a stack every time I have a new version

"Aperture→Preferences→General" has a checkbox for stacking new Versions.
Lots of useful options in Preferences -- worth looking through all of them.

Can´t create new Version from Image with meta/adjustment?

I have some Images (.tiffs) which have Metadata/Adjustments but I can´t create a new Version from them.
Any idea what to do??
thanks appreciate your help!
r

'weeks of work'. that's far too much to just let go of. so...
(re-reading your original message...)
'capturing' means simply importing, right?
but you've made adjustments to the images after import?
and you've added keywords/IPTC/metadata to the images after import?
I'd try:
A. split the tiff project/s into smaller projects (100 images or so) if you haven't already done so. (this'll take a while because Aperture slows down significantly when master images are moved around)
B. export the projects.
C. delete the projects from inside Aperture. there should be none of your 'problematic' tiff images remaining in the library.
D. relaunch Aperture and rebuild the library.
E. import the projects one at a time, rebuilding the library after each import in case there is something in the project's data files that needs fixing.
F. try to do what you want to do with the images in the project.
if everything works ok, then import the next project and repeat steps E and F.

"A newer version is available" error

A little background: I have a SharePoint farm with 2 web front ends load balanced, a application server and a database server, serving content to over 600 users.
I've started experiencing some issues with users on shared accounts. For ease of use (though I don't like it) a number of staff at certain locations all login with the same user account. We use roaming profiles to maintain consistency between the computers and these shared profiles are mandatory. The internet explorer temp files are not redirected and are stored locally.
These staff members regularly have to update a specific excel spreadsheet in a document library in SharePoint. The shared accounts are not allowed access to SharePoint for tracking and security reasons. So users log into SharePoint using their own credentials.
Lately I've been having an issue of when they open a document and check it out to make edits they get a bar at the top that says "A newer version is available. To modify this workbook, open the latest version or save a copy."
I've verified that it's not been checked out and had the user attempt to check this document out and they still get this error. It seems to be random and possibly per different computers.
I first suspected it was an internet explorer caching issue and adjusted setting to clear the cache on close and to check for a new content on every visit to the page. That didn't seem to make a difference.
We're in the process of rolling out IE 7 and I suspected maybe that would solve this issue, but we're still having the problem. I've also tried repairing and reinstalling office 2007 to no avail. I have the latest service packs and hot fixes on Office 2007 and Windows XP. I haven't upgraded SharePoint to service pack 2 yet but I do have the latest infrastructure updates on it.
I’ve seen a little information from searching around on Google but nothing specifically similar to this that has more of an answer then “reinstall office”. Does anyone have any insight into these errors and how I can go about solving them? Thanks!

I’m not clear from the 2 posts what should be deleted.
One says:
Deleted the registry hive \Software\Microsoft\Windows\CurrentVersion underneath
HKEY_CLASSES_ROOT\Software\Microsoft\MasterAggregatorForIPP\OleDbHandlers\{E1D2BF40-A96B-11d1-9C6B-0000F875AC61}.
The other says:
HKEY_CLASSES_ROOT\Software\Microsoft\MasterAggregatorForIPP\OleDbHandlers
{E1D2BF40-A96B-11d1-9C6B-0000F875AC61} System
Does that mean delete the key \{E1D2BF40-A96B-11d1-9C6B-0000F875AC61} or the values underneath it? And where does System come into play? I don’t see that in the registry on the PC’s I’ve checked.
I’m not sure how \Software\Microsoft\Windows\CurrentVersion relates to HKEY_CLASSES_ROOT\Software\Microsoft\MasterAggregatorForIPP\OleDbHandlers
{E1D2BF40-A96B-11d1-9C6B-0000F875AC61} System
Thanks.

SMSY: Newer Version Exists in Solman 7

Hi,
I Have a SolMan 7 system on SP15 and it seems that SMSY is not updating data correctly. I had an old 4.6C R3 server system registered and it was sending data to SLD from rz70. It was later upgraded to ECC6 and when data is sent to SLD it gets registered version 700 (<host>:5xx00/sld). SMSY has been setup to update itself from SLD but it gets registered as a 4.6C R3 server system where as i thought it would have been picked up as a ECC6 system.
What i did was:
1. completely delete the system from SMSY, logical components etc
2. trigger rz70 to send up to date info to SLD
3. in SolMan run landscape fetch job and let SMSY update
4. checked SMSY and it comes up with a yellow exclamation box next to it saying "Newer Version Exists".
I redone the steps above but still its comes into SMSY as a R/3 server.
Any suggestions as i have searched OSS notes for a long time but there is nothing.
Thanks,
Mani

Thanks Andreas,
Will this adjustment remain the same after the next job is run to fetch data from SLD? i am worried when it fetches data from SLD and populates SMSY that it will change to R/3 Server type product.
Mani

How do I create new versions of a large number of images, and place them in a new location?

Hello!
I have been using Aperture for years, and have just one small problem. There have been many times where I want to have multiple versions of a large number of images. I like to do a color album and B&W album for example.
Previously, I would click on all the images at one, and select new version. The problem is this puts all of the new versions in a stack. I then have to open all the stacks, and one by one move the new versions to a different album. Is there any way to streamline this proccess? When it's only 10 images, it's no problem. When it's a few hundred (or more) its rather time consuming..
What I'm hoping for is a way to either automatically have new versions populate a separate album, or for a way to easily select all the new versions I create at one time, and simply move them with as few steps as possible to a new destination.
Thanks for any help,
Ricardo

Ricardo,
in addition to Kirby's and phosgraphis's excellent suggestions, you may want to use the filters to further restrict your versions to the ones you want to access.
For example, you mentioned
I like to do a color album and B&W album for example.
You could easily separate the color versions from the black-and-white versions by using the filter rule:
Adjustment includes Black&white
or
Adjustment does not include Black&white
With the above filter setting (Add rule > Adjustment includes Black&White) only the versions with Black&White adjustment are shown in the Browers. You could do similar to separate cropped versions from uncropped ones.
Regards
Léonie

IDLE event problem with newer versions of the flash player

Greetings,
I have an issue that seems to be related to newer versions of the flashplayer in how they handle IDLE events. I have an IDLE event handler that works as expected with flashplayer version 10.0.45.2. With flashplayer 10.2.153.1, the IDLE event does not fire when my flex application is not in focus (browser minized, different browser tab in focus,etc...). Or when it fires, it's usually after a longer lag than normal. Has anyone experienced this issue? Thanks

Thanks for the reply. Are there any fixes/workarounds for this issue? Say I have a need to create a timer that fires every 10 minutes regardless of whether the player is in focus or not, how do I implement such a timer? Same goes for the IDLE event, I want to be notified if the application has been idle for X minutes regardless of whether it's in focus or not.Prior to 10.2 (and per your reply, 10.1), this all worked fine in flex without needing to adjust for the player being in focus.

How to fade in and fade out audio in the new version of Imovie?

Please help me!
how to fade in and fade out audio in the new version of Imovie?

There is a tiny dot at the beginning and ending of an audio clip that can be moved to adjust fade in and fade out.

Dump-A newer version of data type "ZMNFLOCK" was found than one required

Hi,
I am getting dump in program when there is a select query on ZMNFLOCK table.
Error analsys is given as
Error analysis
The data type "ZMNFLOCK" was loaded from the database during the program run.
    However, a type of a newer version than the one requried was found here.
What could be the problem? my BASIS person says this is somewhere related to ABAP.
should i Adjust & Activate database by going to SE14 for ZMNFLOCK table.
Also noted that error is random in nature and its not coming everytime.

Hi,
There could be an issue with in the table, As Dataelement or domain related to any field in table may have changed, And that field is not getting used aal the time, That's why Dump is coming randomly.
The best possible solution is to Activate and adjust database table through SE14, This will update table with all the updated versions.
Thanks
Saurabh Siwach

Do newer versions of project files build on older ones?

I'm asking this for a friend.
The project in question has been revised several times. If one was to delete the older-version project files to recover some disc space, would it also delete the same resource files used in the newer versions?

To be clear, I hope your friend is not relying on auto-save to save their projects. Auto-saves in the auto-save folder are snap shot of a project file saved at adjustable intervals. These do not overwrite the active project file (Like what Final Cut X does). Your open project should be saved manually and often. You can "Save As" to create a new or back up project (redundant in most cases in my opinion).
What I recommend is to go into the Auto-save preferences and set it to save every 5-10 minutes, and raise the number of copies from a default of 20 to 100 or more. It really depends if you want to back up hours or days of work.
Also, when loading an autosave project, be sure to choose the project file by date\time created and not the the auto generated filename. This is because after the autosave project version limit has been reached, the numbering in the file names will rollover and then save over the 1st one, then second, and so on.
Lastly, when loading an autosave project, immediately do a "Save As" to you main project folder, outside of the auto-save folder, or else premiere will create a whole new set of sub folders, including an autosave folder.
I've seen confused editors trying to find their project, and they have like 4 levels of autosave folders and they have no clue what they have worked on.

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

Error: A newer version of data type was found than one required

Hi Experts,
we made a changes to a table and then transported the table to the quality system. But a program which is referring to this table, results in dump with the below error message.
Error Message>>>>>>>>>>" A newer version of data type <TABLE> was found than one required "
The issue occures inspite of
1. re-activated the table and send to quality system
2. Re-activated the program
3. Activated and adjusted database in SE14.
Please let me know the correction to be taken to resolve the issue.
Regards
Suresh Kumar

This happens when you modify your new data element, domain while another program is currently using it.
Simply get out completely of the program, re activate the program, reactivate the table. You might need to run se14 to convert the database table but this does not happen frequently. Try first to reactivate the program
Dean
Edited by: Dean Ton on Mar 8, 2012 9:54 PM
Edited by: Dean Ton on Mar 8, 2012 9:56 PM

Adjustment new version

Similar Messages

Maybe you are looking for