Delete multiple master images: hangs

When I choose multiple images for delete I get the infinite spinning beach ball. I searched for similar posts and did not find anyone with the same problem.
Deleting one image at a time works ok.
I have to force quit and restart. When the project is opened again I see that the images were in fact deleted. This is very repeatable.
This is a reasonably serious bug for me since doing the pruning of images outside of aperture will require a raw-enabled viewer.
It would also be nice to have a hot-key for deleting a master image, and a way to get rid of the "do you really want to do this" dialog.
nmurray

Hi nmurray,
a number of posts here which concern hangs, spinning beachballs, performance and the like point to a single conclusion:
Rebuild your library.
In order to do that, quit Aperture, and restart it while pressing the Alt key. (You can let go of the Alt key after the startup screen has appeared.) After having started, Aperture will then ask you whether you really want to rebuild the library as that may take some time (and if you have a large library, you might want to do this before preparing and having dinner with friends. Spend a nice evening while Aperture is keeping your Mac busy. Have some wine. Maybe a walk).
The hot key combination is Command-Backspace. The confirmation dialog is there for a reason - after all, you're telling Aperture to delete a master. However, to dismiss it, just hit the Return key on your keyboard.
The best way to get rid of several masters is to select them, press Command-Backspace, hit Return, and then sit back and wait while Aperture is throwing your masters into the trash. Don't ask me why a simple delete takes so long; I have the impression that the way Aperture works with its libary has significant room for improvement.
Cheers,
Karl

Similar Messages

Use Referenced Masters To Avoid Accidentally Deleting A Master Image File

If you use Managed images it is possible to delete the master file accidentally. If you delete versions of an image using File -> Delete Version and the version you are deleting is the last remaining version for that image, Aperture 3 will delete both the version and the master image. If you subsequently empty Aperture Trash and then System Trash that master image file is gone forever. In Aperture 3 there is no warning that you are about to delete a master image.
A workaround (although a weak workaround) is to use Referenced Image Masters. Then when you delete the last version which includes the master image from Aperture, you can uncheck the box "Move referenced file to system trash." and no master image file will be deleted. The downside to this workaround is that when you really want to delete a master image file, it must be done via Finder.
The best solution would be for Apple to fix this bug so that when you select "Delete Version" it only deletes the version image and reverts to the master image. That way the master image can only be delete via the command "Delete Master Image and All Versions."

There is no bug there.
I had some trouble wrapping my mind around the file-Master-Version-Image-(Preview) complex that flows, sand-like, through the entire working of Aperture. (I like a thing to be represented by itself and itself alone, and to exist in one place and one place alone. I was comfortable with the seeming precision of the location-based "file+path" metaphor for the existence of these virtual things. Aperture quite cleverly moves beyond that.) Two things helped me move forward:
- understanding the difference between Projects and Albums, and
- separating my Library into a storage area and an output area.
Projects are, for me, storage containers. (I have said elsewhere that the mis-naming of "Projects" is the single worst interface decision made in Aperture.) They have a privileged relationship with your Images: every Image must "live" in a Project, and "lives" in only one Project. It may help you to think of "Image+Project{Path}" as functionaly equivalent, within the Aperture Library, to the file directory "file+path" mentioned above.
Albums are, for me, output containers. I create Albums every time I know I will output a set of Images.
In practice, I work on Images in each. In general, I develop my digital captures in the Project that holds them (and I rigorously stick to "One Project = One shoot"), I create Versions and add them to Albums as needed for output (they are automatically made the Album Pick), and I tweak them for output and then output them from Albums.
You may be wondering (if you've read this far) -- "What has this got to do with deleting Masters?" A lot. Note the difference in the context-menu between a Version in a Project and a Version in an Album. The menu for the Album contains two delete commands: "Delete Version", and "Remove from Album". The Versions live in Projects, and only visit Albums. As Terence correctly points out, if you delete the last Version, your expectation should be that you are deleting that Image from your Library. My suggestion is that you adopt something similar to what I've set up, and delete Versions from ONLY Projects (never from Albums). This way you will never unknowingly delete the last Version (because Images can be in only one Project, and if you delete the last Version from that Project you know you are expunging that Image from your Library).

No warning when deleting a Master image that is linked to Virtual Copies?!

Scenario: I am trying to clear out old images to free up storage space, so I go back though thousands of images looking for weak . unrequired shots.
Problem; when dealing with "mass deletions" it is near impossible to detect which images are "Master copies" from which I have any number of Virtual Copies. And when you hit delete you might well be ruining Virtual Copies without knowing it.
Surely there is a way to warn you that pics, X, Y & Z are linked to Xcopy1, YCopy1 & Zcopy1 etc, and give you an IMAGE SPECIFIC option to see those copies and make a choice of delete the master or not? I can't beleive Adobe think its user-freindly to have people trawl through each image to check before a deletion?
I know others have expressed similar concerns, and it seems a REALLY glaring omission in an otherwise decent ptoduct.
Comments from Adobe staff more than welcome.

eddybaby66 wrote:
Your response implies that you know how another person wishes to use the product, and it is clear that you do not know this. Being so prescriptive is no way for Adobe to look at an issue like this either.
your responce to the observation from the above forum member is a little inelegant and harsh. It is a very good way of telling you where there are VC's of images, but as you said, your methods are your own. Doing things your way and then asking for help and then biting like that is, well up to you how you reply to those offering help and positive suggestions
I dont' expect Adobe would be so prescriptive and +1 your comment and request is a very valid one

Project management and multiple master images

Anyone here making use of 2 or more projects with the same master image in each project?
scenario is:
project 1 "blah shoot" <-- contains all images from shoot
project 2 "portfolio" <-- will contain some of the images from the shoot
The problem im having at the moment is when i drag any master image from project 1 into project 2, it removes the master file from project 1
Surely i can have multiple images in multiple projects?

You can copy the master image to your portfolio by
clicking and dragging with the option key held down.
I don't know of a way to link these images so that
changes in one are carried over to the other though.
If someone does know, please let me know, it'd make
my life easier...
If you drag an image from one project into an album under another project, it will not move the master - it puts only that version in the album, linked back to changes made in the original project.
if you export that project, the master that version is based on will be copied at that time and pushed out into the exported project. So if you export a project and then re-import you will no longer have a link but a copied master. To get around that you can manually copy the project with the album holding links out of the Aperture library to elsewhere to make backups or move a set of projects together,

How to delete multiple images

Hello.
I am trying to delete multiple master images that are duplicates. I select all of the images that I want to trash, go to the file menu and click on 'delete master and all versions' but, only one of the selected images gets deleted. Why?? Why just the one?
AND....why does the "do not import duplicate images" work????
I have 2.1.4 installed

First question: Do you have Primary Only enabled? (turn it off if it is, then try again)
Second question: Perhaps the name or date of the images has changed and makes Aperture unable to determine duplicates.

Aperture 3- Calls Master image version 2 ????

Downloaded the trial of Aperture 3. Started playing around with it and noticed that the master image is being called version 2 and the actual adjusted version is not even labeled as a version. If I create multiple other versions of the image they are being labeled correctly as 3, 4 etc...
This is very odd to me. Possibly a BIG problem when deleting versions. Might end up trashing the master image since it's labeled as version-2.
Anyone else notice this?

Thank you both.
Of course I'm still confused though. Thought I knew Aperture, ha!
What I find in Aperture2 is that when I look at my viewer with all versions unstacked there always is one image in the stack that is indeed an image without any adjustments to it (what I thought to be my master). If I try to delete this image I get a warning that I am about to delete a master image.
In Aperture3 I do see what you are saying about them all being versions. I guess the question I have then is that when I do delete all the images in the stack where is my master image? When I turn off the "create new version" preference things seem more 'normal' to me as compared with Aperture2 but I still don't see an unadjusted 'version' of the image like I used to.
In Aperture2 when I had say 4 versions of an image and I didn't want or like any of them I could delete all the versions of an image in a stack and there was the unadjusted image there still viewable. I'd start adjusting away again and then my new version would be created.
There must be some preference somewhere that I'm not seeing to accomplish this all.
Thanks again! I think I've got too many versions of this question in my head.

Deleting A Version Without Deleting The Master

I'm still on 1.5.6 (sorry)...I open a version in my external editor and save back into Aperture.
I have created a few versions that I no longer want. When I select "file-delete version" I get a window asking me if I want to delete the master image and all versions. I only want to delete one version and keep my Master.

You are using the right option to get rid of the "version". The reason aperture is giving you this message is because the "version" that you are targeting has been edited in an external editor. These are a bit different that "versions" that are just created with new version from master or duplicate version. If you send an image to an external editor Aperture actually creates a new psd or tiff master from your original master plus any adjustments applied to the version that you are looking at. Aperture then sends this new psd/tiff master to the external editor. So, when you have a few "versions" of the same image that have been sent to an external editor you also have new masters associated with them. If you delete one of those Aperture is telling you that it is going to get rid of the PSD/Tiff with the modifications that you made in the external editor, it is not telling you that it is going to get rid of the original RAW master that you imported.
Was that clear?
RB

I'm trying to delete multiple pix in iPhoto that i stupidly made duplicates of without knowing, I've tried going into the applications folder and using image capture but i think I've missed a step , can anyone send the correct info / steps pls thanks

I'm trying to delete multiple pix in iPhoto that i stupidly made duplicates of without knowing, I've tried going into the applications folder and using image capture but i think I've missed a step , can anyone send the correct info / steps pls thanks

again image capture is not involved with deleting photos from iPhoto in any way ever
the paid version of iPhoto Library Manager is very good for finding duplicates as is Duplicate Annihilator
And I have no idea who told you this - or what it means - but re-read both of my opening statements
I was told I could delete multpiles thru image capture by transferring my iPhoto library etc
LN

Problem Rating / Deleting Multiple Images

I have a Problem Rating / Deleting Multiple Images at the same time. For the last 2 weeks I have been unable to select a group of images and rate them all - I have to select images indiviually for the rating to work. This also is the case when trying to delete images.
Anyone know if this is a bug?

Hit 'S' which toggles 'Primary Only' mode - this swaps between applying ratings,deletions to multiple images or just the one with the thicker selection border.
Ian

Deleting multiple images

I've accumulated so many photos that they're taking up too much space, and I don't use them. I'm trying to find a way to delete multiple images using Adobe Bridge CS5. I assumed it would be easiest through this program. Its taking too much time to delete them individually. Is there a more efficient way to delete photos? I thought of creating a folder and just putting the photos in there to delete but thats all I've come up with.

Its taking too much time to delete them individually.
No need for that, multiple options for you:
Selecting:
- use the mouse to hoover over the files you want to delete and select them all
- click on the first one and with shift click select the last in the series to select them all
- use the command key with click to select multiple files on different locations in the same folder.
Deleting:
With the files selected choose:
- the bin icon in the path bar (from CS4 and higher) top right of the Bridge Window
- hit command backspace
- Use right mouse click and choose 'move to trash' from the pop up menu
- Go to the menu 'File' and choose 'Move to trash"
There must be one amongst them that will suite you I would think...

Delete Multiple Records from Item Master

Hi,
We received wrong master data which has been uploaded and two groups have to be deleted. All the items in those particular groups have also to be deleted. Can anyone suggest how to delete multiple records from Item Master?
Currently I am navigating through each Item and doing a Right Click + Remove. It is very painful given the huge number of records.
Regards
Sudatt

Hi Sudatt.....
I recommend you not to run any kind of delete or update SQL query as it harms DB.
You can create your own front end application with the help of any technical consultant which can be
achieved very easily. Else such problems create a big problem during upgradation to next version.......
Regards,
Rahul

Deleting multiple images at once in Mues's Lightbox slideshow

I frequently need to delete 70 or 80 images from Muse's Lightbox slideshow before adding new images. Because you have to leave at least one image (at least that's my understanding) before adding new ones, I have to delete them one at a time. It's a real pain. It would be nice to be able to shift click or control click on the images I want to delete so I can do it in one move instead of eighty. Can this function be added or is there a work around or something I'm missing that would let me do this? I've tried selecting one, then clicking on 'select same' but there is no way to exclude one image so that I can leave one image behind.

Zak... Selecting one thumbnail > Select all > Delete worked just as you said; it leaves one image behind. I never would have tried that method because logically I would have thought that it would delete all the images since I chose 'Select all'. Thanks for the quick response and saving me a lot of work... Bill

Moving Master Images after Facebook Upload

I'm using a fully updated version of Aperture 3 and ran into a problem today moving master images that I have not experienced before. My normal workflow is to batch import images from my camera every few days in one large import, so I often have multiple subjects in every batch. For my 9 months with the program I have always downloaded everything into a temporary holding project I literally call "Hold". When I get the time to do a detailed review, I then delete what I don't want and move (drag) the master images I want to keep from "Hold" into other subject-matter-unique projects across the library. This works for me and has worked flawlessly until today when I downloaded about 20 images. What I did differently today was I took things out of my usual order and decided to quickly upload 3 of the images from the "Hold" folder to Facebook using the Aperture Uploader. The upload went fine, as it has in the past, but the problem surfaced when I then tried to move all the master images out of "Hold" to my permanent library file (project) structure. The 17 images (which were not uploaded to Facebook) moved out to their new projects just fine, as always, but the 3 masters which were the source for the Facebook upload will not allow themselves to be moved out of "Hold". When I drag them to the intended project, Aperture copies them into that project, but the original stays in "Hold." Of course, if I try to then delete what is in "Hold" (with a copy safely filed away elsewhere in the Library) I get the warning that I am attempting to delete a master upon which other versions are dependent (to include "Facebook albums" it says), and all will be deleted.
My take on this is the Facebook upload from "Hold", and the resulting versions created in the Facebook album (far bottom entries on the Library listing), now make "Hold" a permanent home for those associated master images. Is there some way to get around this and actually move the master images to where I want them to be AND to de-clutter the "Hold" folder? Or does this mean any use of Aperture's very handy (at least to date) Facebook uploader permanently glues a master to whatever project it was in when it was uploaded, never to fully and completely move again? Thanks.

I just made a test of this, and can confirm the apparent behavior. However, I examined the Masters folder in the Package of the Library (and I have a Managed Library) and I believe there may be some referencing between Projects taking place. The same appears to result where you have created a slideshow. In the Facebook album and in the Slideshow album, the file info reports the master file name -- in my case the xxxx.NEF file, which clearly none of them really are, but rather some version.
I will try to do a more precise test where I can measure the size of the Masters folder to see if the "Move" adds to its size by an amount equal to the size of the Master file.
Interesting!
Ernie
Message was edited by: Ernie Stamper

SCCM 2012 R2 Tasksequence for VDI Master Image

Hi
I'm currently building a ConfigMgr Tasksequence for a RDS VDI solution. At the end of the TS I have a PowerShell Script which prepares the SCCM Client for the master image (delete certs, remove provisioning mode). I would like to use the variable
SMSTSPostAction for doing the sysprep with a shutdown. But the machine hangs after rebooting out from the PS Script. Of course the Agent is no longer available but the SMSTSPost Action Variable should start.
Does anyone have an idea?
I need to use SCCM as MDT is not an option.

I fixed this by myself using powershell.
At the end of the TS I copy a PS Script to the sysprep folder. This script is running as SMSTSPostAction and does the following:
# Step 1 -Prepare SCCM Client for VDI Deployment
Get-Service -displayname "SMS Agent Host" | stop-service -Force
Remove-Item -Path C:\Windows\SMSCFG.INI -force
Get-childitem -Path cert:\localmachine\sms -DnsName *SMS* | Remove-Item
Invoke-WmiMethod -Namespace root\CCM -Class SMS_Client -Name SetClientProvisioningMode -ArgumentList $false
Clear-Host
Write-Host "Please do not use the VM. SMSTSPostAction is still running!" -foregroundcolor Green
Write-Host "Waiting several seconds until Sysprep..." -foregroundcolor Green
Start-Sleep -s 60
# Step 2 - Sysprep & Shutdown
C:\Windows\system32\sysprep\sysprep.exe /generalize /oobe /shutdown
The Maschine reboots at the end of the TS with a success code and runs then the SMSTSPostAction. The SCCM Agent is then well prepared for cloning. Make sure you have set your execution policy right.

I can't delete the master file, which is located on my external HD, through aperture

I import a folder to aperture which is stored on my external HD, and keep the originals on the HD. If I try to delete a master file with the option, file-delete master image and all versions, the photo deletes from Aperture, but not my hard drive. I have even tried to delete my trash, but no luck. Please help, otherwise I do not want to use aperture for file management, which was one of my major reasons for buying it.

After you've deleted a file it from the project it goes into Aperture Trash. When you empty Aperture Trash (Aperture>Empty Aperture Trash) you will get a dialogue box asking "Are you sure you want to permanently delete all items in the Trash?" Under this there is a checkbox giving you the option to "Move referenced files to System Trash". If you check this box it will move the master to the system trash, and from there you can permanently delete the file.
All this is to stop you from accidentally deleting work.

Delete multiple master images: hangs

Similar Messages

Maybe you are looking for