Aperture 3.3 Bug? Dragging to external editor can modify the original

As a follow-up to the thread below I explored the role of the previews in Aperture:
Edited image appears then quickly reverts to original?
The problem: When dragging images from the Browser to Photoshop (supposedly passing along a preview of the image) the original image file in Aperture could be overwritten.
Experimenting with this I found that the result depended on the size of the image, for the following reasons:
If the Preview size was set to a larger value than the actual image size, then Aperture would not generate a preview for images without a preview, but pass the original image to Photoshop. Saving back the changes in Photoshop would modify the original master image file in the Aperture 3.3. For images larger than the Preview size, Aperture 3.3 would pass a new quasi master to Photoshop - rather wasteful, since this quasi master is not linked to a version and this not accessable in Aperture.
Experimenting showed, that the same happens with dragging to GraphicConverter, but the changes to the original are only visible after quitting and relaunching Aperture.
I would be grateful if someone could check out these observations:
Do you also see, that no previews are generated in Aperture 3.3, if the original image is smaller than the preview size set in the preferences?
Can you confirm, that Photoshop modifies the original image files, if the image does not have a preview image, and if the image is passed by dragging from the browser?
I tested the same in Aperture 3.2.4: Here it seems to be impossible to drag an imageto Photoshop and GraphicConverter, if it does not have a preview image - very sensible.
Regards
Léonie
A modified original image returned from Photoshop:

This still has not been fixed
I just tried again in Aperture 3.4.3:
I Imported this image file (pixelsize 260 × 551) into Aperture:
Then I dragged it from the Browser to "Preview", annoted it with an arrow, pressed "Save".
And now the Aperture browser shows this:
Aperture 3.4.3, MacOS X 10.8.3

Similar Messages

IPhoto 11 bug when using external editor (Photoshop Elements)

In iPhoto 11, my iPhoto database is confused/corrupted whenever I edit a picture in my external editor (Photoshop Elements 8). I believe this is an iPhoto problem because the picture is not corrupted until I quit iPhoto try to re-open the edited version.
Steps I take:
1. Pick a file, and "Edit in External Editor". Duplicate of the file is made (ThisPic.jpg becomes ThisPic_2.jpg), and that duplicate is opened in PSE. I edit the photo in PSE, and hit Save - PSE updates ThisPic_2.jpg. I close PSE, go back to iPhoto, and I can do whatever I want to the file - double click to view larger, export, everything seems fine. When I pick "File | Reveal in Finder" and use either the "modified file" or "original file" option, they take me to ThisPic_2.jpg in the finder.
2. Close iPhoto
3. Re-open iPhoto
4. Now, that file seems to be corrupt in iPhoto. I can see the thumbnail image for ThisPic_2.jpg, but nothing else works. I double click on the file, and I get a black screen with a triangle and an exclamation point in it. When I try to export the file, nothing happens.
The interesting thing is when I go into "File | Reveal in Finder". When I pick the "modified file", it doesn't seem to find it - I am shown the root of my hard drive in the finder. But when I pick "original file", it takes me to ThisPic_2.jpg, and I can use preview to see that my edits are still there.
I copied that file to the desktop, re-imported it into iPhoto, and I can access that photo again through iPhoto - everything works, even after I close and re-open iPhoto.
I reported this through the iPhoto Feedback option. I thought I'd share what I found in case it helps anyone else.

Welcome to the Apple Discussions. I get the same response when I follow your workflow. If you select the thumbnail of that photo and use the Photos ➙ Revert to Original menu option you will be able to view the photo in full size.
Evidently editing in iPhoto with an external editor puts the edits on the duplicated original file and puts that file in the same Masters subfolder as the first file was imported into. Once iPhoto is restarted the links are messed up and the Revert gets rid of the "edited" link and keeps the link to the file in the Masters folder.
It definitely is a bug. However, it's not taking up more space on the hard drive than the edit that resulted in a modified file linked to the original file. There still are just two files.
Subsequent edits to the file with the external editor result is the edits being added to the file with no problems if iPhoto is closed and relaunched. The downside is that if you make 3 edits to the file you can't go back one edit. It's non reversible. The edited version can be deleted leaving the untouched original version.
Subsequent edits to the same file with iPhoto work as usual, with a modified version being created.
So Old Toad, I have just gone from iPhoto 9 to iPhoto 11 and step by step this is what is happening for me.
In iPhoto 9 if I selected photoshop to alter an image it created one duplicate version of the image and put that into the modified folder and that edited image became the image you would see in the events viewer. All very logical.
Now iPhoto 11 is doing the same for me but is creating multiple duplicates ie. everytime I select photoshop to edit an image. One image I edited recently has now got 6 versions in the library. If that is the way iPhoto works then that will be fine as it is doing it's job for me but the caviat is have I got 6 times the memory space being used up or does it just appear that way? If the memory space useage isn't being increased then I am OK with this new way of doing things but if the memory space is being used up then it is a fiasco - especially as apple are concentrating on writing their systems to use up less space than before in line with current thinking.
Look forward to you clarifying this point if you can.

Link externally edited files to the original, like Aperture does

This is one thing I really like about Aperture - when you edit files externally, Aperture keeps track of them, and keeps them associated with the original. That little bit of housekeeping is a very nice touch.

From the way you are describing the display issue this sounds like a bug that I have been screaming at Apple about for about 9 months. The bug is in CoreImage and effects everything in OS X that uses the coreimage library to display PSD files.
The issue is caused by having ANY saved alpha channels in an image, these are either created manually by you or automatically by saving a selection. Check the PSD in photoshop, click the channels tab and look for any channel that is not part of the color model itself, if one is there it is causing the display issue. If you do not need this channel then just delete it, if you must have it for some reason the work around is to load the alpha channel into a blank layer layer mask and then get rid of it. If you need it back reverse the process. Bottom line if you have a save an alpha channel it will display all wild and crazy everywhere in OS X that uses core image.
RB

I am using both PSE 13 and Lightroom 5. When I use Lightroom as an external editor and save the photo, it shows up in PSE13 as an edited file but does not look any different. Why doesn't it appear edited?

I am using both PSE 13 and Lightroom 5. When I use Lightroom as an external editor and save the photo, it shows up in PSE13 as an edited file but does not look any different. Why doesn't it appear edited?

People who have Photoshop, but don't have Lightroom, need ACR so that they can use Raw files. Without ACR they could do nothing with those (they may also like having ACR so that they can work on other kinds of image using the same kinds of adjustments and techniques, as are used with Raw files).
People who have Lightroom, can get access to Raw files regardless whether ACR is present or not. They can use Lightroom on other kinds of image also, using the same methods. LR can pass images directly into Photoshop without passing via ACR (or else does so transparently, which amounts to substantially the same thing).
ACR does not, strictly speaking, even need to be installed for this external editing to happen. In fact, not even PS needs to be - since a different image editor can be used instead, while still retaining the Adobe Raw conversion etc.
Lightroom "subcontracts out" specialised external tasks, in this workflow, but is still your "main contractor": the image is otherwise located, viewed, managed, adjusted/presented and output entirely using LR.
So IMO we can divide image processing into:
operations that involve pixels and layers and layer masks and adjustment layers etc (of the kind done inside Photoshop)
operations that involve parametric edits (of the kind done in ACR where you are not using a Lightroom based workflow; otherwise, done inside Lightroom)
When PS is called in, that's because those tasks are impossible or unsuitable to do in Lightroom. But those tasks can't be done in ACR either - by definition, since LR and ACR have exactly the same image processing "feature set".
Lightroom is irrelevant to the Bridge + ACR + PS workflow. This workflow requires both your PS and your ACR to be current enough, to support your Raw format etc.
ACR and Bridge are irrelevant to the LR + (image editor) workflow. It is in this case, only LR which needs to be current enough to support your Raw format etc.
RP

Is there an external webcam made for the original iPad?

Is there an external webcam made for the original iPad?

There was an iClops project for awhile, but the folks abandoned the idea, I heard for possible legal reasons.
There is an app, Camera for iPad, that lets you use the iPhone's better resolution camera to take photos for other iOS devices. But it does not work with any video apps. I am not sure why I would take photos with an iPhone for the iPad, unless it was for later viwing on the larger display.

Are there any limitations for importing Apple Aperture Libraries for Lightroom 5.7 ? What can be the hardware limitation importing large Aperture Libraries like 200 gb ? Or is importing larger Aperture Libraries even possible at the moment for Lightroom 5

Are there any limitations for importing Apple Aperture Libraries for Lightroom 5.7 ? What can be the hardware limitation for importing large Aperture Libraries like 200 gb ? Or is importing larger Aperture Libraries even possible at the moment to Lightroom 5.7 ?

dj_paige wrote:
As far as hardware restrictions, the only one I can think of is that you certainly need enough free space on your hard disk to accomodate the masters from your Aperture library.
IIn which case, ensure all your masters are "referenced" in Aperture, and that you then go to Options in the Lightroom import box and import photos in their existing locations.

Saving to Aperture after using Photoshop as an External Editor

I'd be grateful for guidance please. I use Aperture but sometimes use the external editor (Photoshop in my case). When I have finished editing in Photoshop what is the best way to get the finished photograph back into Aperture? Do I have to do another import or is there a way to get the saved photo as another version next to the original but including the work I did in Photoshop. If it is possible I would expect this to be a flattened image (ie not preserving Photoshop layers). Thoughts and guidance would be much appreciated.

The following series of events occurs without fail in aperture 3 and CSPS4:
I place a single JPG image on desktop. Then, in aperture, I create a new project named TEST. I then import this single JPG into aperture, making the choice to store the master on the desktop, rather than in the aperture library.
The JPG image now is in aperture in the PROJECT "TEST". I then select this single image in aperture and send it to CSPS4 to edit.
I can see aperture write a new image to the project with the same name as the JPG but the suffix is now TIFF (note two "f" in this suffix). This happens as photoshop is opening and i can briefly see the TIFF file in the aperture browser before photoshop completes opening.
I then edit the "TIFF" image in photoshop (which is by now completely opened) and SAVE (not save as...) it. Since I have previously chosen 16bit TIFF in the preferences I expect to get this file with the photoshop edits in the aperture project TEST. HOWEVER, the file is written with the suffix "TIF". Note that there is only one "f" in this suffix.
Now, on my desktop I have THREE files, a JPG, a TIFF, and a TIF. Aperture shows only 2 images in the TEST project, the original JPG and the TIFF. This TIFF was written by aperture before i edited it in photoshop. Apparently my edits in photoshop are in the file IMAGE.TIF, which is not in my aperture TEST project.
This has to be a bug regarding the suffexes "TIFF" and "TIF" This would explain why my "edited" file in my aperture project TEST shows no evidence of having been edited.
This has been difficult to explain clearly but perhaps someone has noticed.
imac i7,8GB Mac OS X (10.6.2)

Can't open image in external editor, can't export images

Greetings helpful Aperture experts,
I've just finished transferring aperture from one computer to a replacement unit. Except for being slow on my previous g5, it worked flawlessly at every level. However, now that I've xferred, I can't open Aperture images with an external editor, nor can I export the images to my desktop. Any help along these lines will be gigantically appreciated.
gaylon

Thanks, ok, here is the info step by step:
When I try to pick any raw image, I am not able to export from Aperture. When I go into the finder and select "show master" then I am able to export from aperture. However, it seems that I am not able to export an image full size. I selected export image to full size jpg to my desktop. Nothing happens except that the window that indicates the image is exporting is open and it says estimated time less than a minute. Yet, there is nothing happening. Additionally, before I transferred Aperture over to my new g5, I could right click an image and had the option to open an image with external editor. Now, no such menu item is apparent. An update, the menu box that lets me know that my image is exporting is still open but there has been no progress. It will just sit there forever, or until I force Aperture to quit. Here's another strange goings on: One of my folders of raw images appear to be pixelated and of very poor quality, even when viewing the masters. The images have already been published by the client in their annual report, so I know that what I am seeing on the screen is not reality. Should I just uninstall Aperture and reinstall? Also, what will this do to the thousands of images in my libraries? Thanks so much for your input and help. In no way am I an expert, but I've been successfully using Aperture since it came out. That was on my G5 dual processor mac with pre intel configuration. Now, these strange things are happening with my new replacement G5 with the Intel processors. Thanks again.
gaylon wampler

Photoshop as external editor: can I change TIFF file options?

I've set up Aperture 2 to use Photoshop CS2 as an external editor. When I save the file it is added to my library (like I expect) but it's a 57 MB file. (16-bit TIF).
Is there a way to edit the file in Photoshop and then save it in a reduced size, so that Aperture will still recognize it? I tried doing a Save As… and picking ZIP compression, but Aperture seems to have missed that file and only seen the uncompressed one. (I wrote on the picture so I could easily tell which version I'm looking at in Aperture).
I can always export and re-import, but it would be nice to have this working from within Aperture.
When working with Photoshop I usually use ZIP compression, which Aperture handles, and sometimes convert from 16-bit to 8-bit for the final product (when it won't be printed). I'd like a way to send the files to Photoshop in 16-bit and get them back into Aperture in whatever format I like, in just one Aperture step. Is this possible, or will I have to Export Version, then Import and manually stack?

1. Aperture doesn't support ZIP-compressed TIFFs, just uncompressed and LZW-compressed.
2. Aperture is only looking for the file it created - if you 'save as' into a new file Aperture has no way of knowing about that file.
You best bet is to reduce to 8-bit, then save as using LZW compression - but save over the open file.
Ian

External editor: Can you list more than one?

Is it possible to list more than one external editor in Aperture's preferences? I know you can install plugins but would like to have more than one app listed.

I'm also missing the possibility to add more than one external editors which I use for specific edit jobs.
I posted a feature request concerning this via the "Aperture Feedback".

Customizing filename when using an external editor - can only one filename be used by all editors?

I have a number of external editors defined for my LR 3.3 Win7 application. Within my Preferences, when I customize how an editor, say, Photoshop CS5, handles a file, I can set the name of the edited file - e.g., {Filename}-ed.psd . However, if I change the edited filename for another external editor, say to {Filename}-SilverEfexPro.psd, that filename is used for all externally edited files. What am I doing wrong? Thanks!
Dilip

A side note here; just because it _opens_ the file in your external editor with that name the first time, doesnt' mean that's the name it has
to be saved as. When you go to save it, select save as, instead of save. I beleive I have used this technique before, and LR still "finds" the file.
Sometimes even when I don't *want* it to find the file!
Cheers!

Lost pictures by dragging them to iphoto - can see the ipmeta

Hi,
I have just tried to drag 4.700 photos from an external harddrive to iphoto.
When 236 pictures was still to be imported the import freezed. The only way I could continue was by saying stop import and not saving the pictures. I removed the usb and hoped that the pictures would not be deleted at the external hard drive, but they did.
I shot down the imac and it started to read the pictures, but I said stop without saving as I at that moment thougt they still would be at the external hard drive.
The situation is now, that I can see the ipmeta, but I cannot see the jpg pictures.
Is there anaway that I can get the pictures again?
I have unfortunately not set up the time machine.
I have tried to see if i could find the jpg files again by shiftaltcmd when i dobble click at Iphoto but without result.
Please help me.
Henning

I removed the usb and hoped that the pictures would not be deleted at the external hard drive, but they did.
iPhoto has no way to delete photos from that HD, so whatever has happened there wasn't done by iPhoto. I would suspect the drive failed, and that caused the freeze in the import.
You can try a file recovery utility on the drive such as File Salvage
The situation is now, that I can see the ipmeta, but I cannot see the jpg pictures.
Where do you see this?
I have tried to see if i could find the jpg files again by shiftaltcmd when i dobble click at Iphoto but without result.
That's not an iPhoto command. Hold down *the command and option (or alt) keys* while launching iPhoto. Use the resulting dialogue to rebuild.
Regards
TD

Move a file to external disk and remove the original

This is a script that was supplied to me on these forums it has been working well, but all the transferring of the files took place locally so a 'Move' command does it eactly what it says, however I now need to move it to an external drive, as a result it leaves trace of the original file.
How can I make it MOVE and remove the origial File please?
set fileMatrix to {¬
          {folderName:"BHS", prefixes:{"BH70", "SM70", "AL70", "BH11"}}, ¬
          {folderName:"Bu", prefixes:{"BU40", "BU11"}}, ¬
          {folderName:"Ca", prefixes:{"CW"}}, ¬
          {folderName:"Da", prefixes:{"ES20", "AM20"}}, ¬
          {folderName:"Di", prefixes:{"DV25", "DV11"}}, ¬
          {folderName:"Do", prefixes:{"DJ30", "RA30", "DJ11"}}, ¬
          {folderName:"In", prefixes:{"GT55", "CC55"}}, ¬
          {folderName:"Fr", prefixes:{"FR10", "FR11", "FR17"}}, ¬
          {folderName:"No", prefixes:{"TM17", "NN_"}}, ¬
          {folderName:"Ma", prefixes:{"MA65", "MF65", "FI65", "MC65", "MH65", "MB65"}}, ¬
          {folderName:"Pr", prefixes:{"PR_"}}, ¬
          {folderName:"To", prefixes:{"TM15", "TM11"}}, ¬
          {folderName:"Wa", prefixes:{"WA35", "WA11"}}, ¬
          {folderName:"Se", prefixes:{"SE_"}}, ¬
          {folderName:"Mik", prefixes:{""}}}
tell application "Finder"
--set theHotFolder to ((path to pictures folder) as text) & "HotFolderDone"
          set theHotFolder to folder "StudioA:Users:StudioA:Pictures:HotFolderDone"
--set foldericon to ((path to pictures folder) as text) & "Icons:Rejected Folder Done"
          set foldericon to folder "StudioA:Users:StudioA:Pictures:Icons:Rejected Folder Done"
--set fakeTrash to ((path to home folder) as text) & "FakeTrash"
          set fakeTrash to folder "StudioA:Users:StudioA:FakeTrash"
set a to alias "Scratches:Workings"
          repeat with matrixItem in fileMatrix -- look for folder
set destinationFolder to (folders of a whose name starts with folderName of matrixItem)
                    if destinationFolder is not {} then -- found one
                              set destinationFolder to first item of destinationFolder -- only one destination
                              set theFolderName to name of destinationFolder
                              repeat with aPrefix in prefixes of matrixItem -- look for files
                                        repeat with startFile in ((files of theHotFolder whose name starts with aPrefix) as alias list) -- move files
                                                  try
move startFile to destinationFolder
                                                  on error
activate
                                                            display dialog "File “" & (name of startFile) & "” already exists in folder “" & theFolderName & "”. Do you want to replace it?" buttons {"Don't replace", "Replace"} default button 2 with icon 1
                                                            if (button returned of the result) is "Replace" then
                                                                      set {fileName, t_ext} to {name, name extension} of startFile
                                                                      if exists file fileName of fakeTrash then -- and it also exists in the fakeTrash Folder.
                                                                                set name of file fileName of destinationFolder to "this is a unique name" -- or whatever
                                                                                set newName to my getUniqueName(fileName, t_ext, fakeTrash)
                                                                                set movedFile to move file "this is a unique name" of destinationFolder to fakeTrash
                                                                                set name of movedFile to newName
                                                                      else -- not exists in the fakeTrash Folder.
move file fileName of destinationFolder to fakeTrash
                                                                      end if
move startFile to destinationFolder
                                                            else -- "Don't replace"
                                                                      if not (exists folder "StudioA:Users:StudioA:Desktop:Rejected Folder Done") then
                                                                                set theLastFolder to duplicate foldericon to desktop
                                                                      else
                                                                                set theLastFolder to folder "StudioA:Users:StudioA:Desktop:Rejected Folder Done"
                                                                      end if
                                                                      delay 0.5
move startFile to theLastFolder with replacing
                                                            end if
                                                  end try
                                        end repeat
                              end repeat
                    end if
          end repeat
          try
                    if (count theLastFolder) is 0 then delete theLastFolder
          end try
end tell
to getUniqueName(theName, theExtension, someFolder)
     check if someFile exists in someFolder, creating a new unique file name (if needed) by adding a suffix
          parameters -          theName, theExtension : a file name and his name extension
                              someFolder : a folder (finder item or alias)
          returns :     a unique name
          set {counter, suffixes, divider} to {0, "abcdefghijklmnopqrstuvwxyz", "_"}
          if theExtension is not "" then set theExtension to "." & theExtension
          set theName to text 1 thru -((length of theExtension) + 1) of theName -- just the name part
          set newName to theName & theExtension
          tell application "Finder" to set theseNames to name of items of someFolder
          repeat while theseNames contains newName
                    set counter to counter + 1 -- hopefully there aren't more than 26 duplicates (numbers are easier)
                    set newName to theName & divider & (item counter of suffixes) & theExtension
          end repeat
          return newName
end getUniqueName

I do not have the time to read through your whole script and give specific answers, but the general principle is fairly easy. You're moving with the Finder, so your move command is going to be of the form:
tell application "Finder"
move file xxxx to folder yyyy
end tell
For cross file system moves (which are as you point out actually duplications) just add a line after each move that sends the old file to the trash:
tell application "Finder"
move file xxxx to folder yyyy
delete file xxxx
end tell
the Finder has an empty trash command that you can use at the end of the script if you like.
One gotcha: because move has two different behaviors, the second code block will throw an error if you try to use if for a local move (it will move the file properly, then try to delete the file it moved, which is obviously no longer there). For clarity, I'd use duplicate rather than move for if you're working across file systems. That's what you're actually doing, and if you use the move command you may confuse yourself when you come back to look at the script a year down the road.

[bug tracker issue] Any way to modify the bug detail of mine?

Greetings,
I just found i can't modify the bug report after i reported a new bug in the bug tracker of archlinux.
it is quite inconvent and weird, since it's quite common that you want to update the bug detail or change something wrong.
at least , in my opinion. -_-
so Is any reason for such restirction?
and is any way to make me modify my bug report?
-Roadt
Last edited by roadt (2009-12-28 06:55:52)

Just add your update as a comment.

How do I move my library to an external drive and delete the original on my local hd

i have final cut x and yosemite. im running out of space on my hard drive on my mac book pro. i would like to copy all my old libraries to an external storage space and then delete the library from my local hard drive. im nervous to do it incase i lose the files. what is the best way to do this? thank you in advance

If the libraries contain all the media - which is the default - then all you have to do is drag them to the external drive using the Finder.
In any case, start by dragging a library to the external.
Now open that library in FCP X, select it under "Libraries" and open the Inspector - you should see something like the picture below.
Most likely, for Media, the location is "In Library", which means that most or all content should be inside the library. To make sure, click "Consolidate". This will copy anything that may have been stored outside the library, so that the library is completely self-contained.
You can now safely delete the copy of the library from the internal drive.
Tip: one of the things that uses most space is transcoded media - especially optimized media. You can safely delete that by going to File->Delete Generated Library Media.

Aperture 3.3 Bug? Dragging to external editor can modify the original

Similar Messages

Maybe you are looking for