Aperture Map Is Suddenly Screwy

Hi all, I'm running Aperture 3.2.4 on OS X 10.6.8.
Recently, within the past couple of days, the map in the Places window has been going bonkers:
-> The zoom bar does not work.
-> My pins will be in the right place on the map until I double-click to zoom in; then they'll move hundreds of miles away.
-> Dragging the map will also move the pins incorrectly, and the map won't stay centered where I leave it - the center will "jump" when I release the mouse.
I can't find anything anywhere that mentions this problem, so I'm hoping someone here can help!

I've read that more recent versions of Aperture changed to Apple Maps over a year ago, but this problem just started happening this past week. So it might be some of the story, but perhaps not all of the story.
Be that as it may, if you're looking to geotag photos in Aperture, I've found an okay workaround, as long as you have Google Earth. This guy wrote a script that will set the location of any photos you have selected in Aperture to the center of the map window open in Google Earth: http://www.underdoug.ca/2012/08/13/geotagging-with-google-earth-and-aperture/
You'll need a crosshair to put at the center of the map window. The link to the one he suggests is broken. I found another one: http://regex.info/blog/2009-06-02/1225 - Just download the .kmz file and double-click it to import it into Google Earth (you might have to restart Google Earth to get it to show up).
It's unwieldy, but it'll have to do for now. Good luck.

Similar Messages

Aperture 2: Adjustments suddenly grayed out

Some help for an Aperture noob please. Subject line says it all about the symptoms so I guess I need to describe how I got myself into this fine mess:
1. Imported some photos (taken with an Olympus E-510), selecting to leave the photos where they are rather than physically importing them.
2. Played about with Apertures raw adjustment settings on some of these photos.
3. Exported the photos I'd played with to directory on my Mac.
4. Created a small .me gallery and published.
I think it was after step 4 that my problems started. All the adjustments (i.e. exposure, white balance, shadows/highlights and so on) are now grayed out, for all projects. Oddly, I can undo and redo all adjustments on a previously edited photo but I cannot select any individual adjustment.
Note: This is a trial copy of Aperture. Where did I go wrong?
Regards
J

I experience this, from time to time, and normally I only need to again click on the thumbnail in the Browser line to have the controls turn black again. I will have to better observe the sequence of actions, but I don't think my situation has anything to do with switching into Preview mode.
Ernie

Places: problem with the State field in Aperture 3.03

hi,
I live in Europe and I have some problems in handling the State field in Aperture 3.03, because this field isn't always relevant in non North-American Countries.
The Google suggestions in Places don't always include the 4 fields (Location/City/State/Country). I have a lot of pictures taken in the Azores islands (Portugal) which don't show up in my Aperture map because the marker somehow doesn't write Azores in the State field.
Question #1: is there a way to eliminate the State field from Aperture, or at least to render it optional?
Question #2: if I manually create a New Location, what is the proper syntax to separate Location/City/State/Country in a way that will be understood by the Aperture database? I tried putting commas as a separator, but it doesn't seem to be working.
Thanks for your help.

Yes, same here. I cannot complete my registration process due to the same error. My state is correct, which is RS (two letters only). I don't know what else to do. Refer to the image below. Thanks!

Obsticles moving within WCS MAP Editor

I have an issue whereby I import a floor plan into WCS and then open the map editor and draw over the map the wall obsticles so as to have the heat maps and RF predictions reflect the attenuation characteristics of the walls.
I save the map and at a later date reopen it only to find that the obsticle layer has moved or offset to the map. Considering that the floor layouts I have been editing are in some cases 40,000 sq meters in area, the number of walls to re draw constitutes major work.
I picked this problem up originally when my heat maps would suddenly be cut off mid room where the was no obvious obsticle. On opeing up the map editor I find that the overlay is offset by the same amout of the error in the heat maps.
The maps in question, beign floor layouts have nopt been moved in reference to their offset to their respective building plan.
The versions of code I am runnign is as follows:-
WCS: 7.0.164.0
MSE: 7.0.105.0
WLC: 7.0.98.0

No mention of the number of obstacles. I too am very detailed on my map layouts. The only thing they came back to me was that I may have been inaccurately drawing the obstacles by not magnifying the floor plan enough. This was a bit of an insult.
I have had situaltions whereby I can open a map one day and it is out of sync, and next it appears fine ( or almost).
I also have problems whereby i cannot get to the lower right portions of the floor plans when magnified as it is off the screen. I currently have 9 major hospital campuses with numerous buildings in each, some with up to 12 floors. Each floor layour is as detailed as I can possibly make it, and the thought of re doing these maps is somethign i just do not want to go to!
What the TAC finally got me to do was to tunr on logging and record when instances happened. The only problem here is that if you do not know or cannot repeat an instance of teh map going out of sync, how do you record the logging.
As I stated, I have basically given up on finding a resolution as I think it goot all too hard for Cisco to identify the actual issue.

My Apeture library is suddenly empty. I think it happened when I was trying to use Prism to upload a video into my computer. My memory quantity is unchanged so can I hope that the over 7000 photos are still available- just missing? My imac is 5 yrs ol

My Aperture library is suddenly empty. I think it happened because I was attempting to import a video with Prism. I did not actually figure out how to complete that and gave up. The next time I opened my computer the library of over 7000 photos was completely empty. My memory quantity has not changed however,
could this mean that the photos are still in there somewhere? My imac is over 5 years old and I just don't know where to go for help.

Just to eliminate some possibilities, since you said that memory has not changed (and I'm assuming that you mean there is no more free space on your hard drive than you had before), have you looked to see if you have a filter activated?
Does your search field read "Unrated or better" or "Show All"? I'd check that first:

Is anyone else having problems with Apertures Date fields?

After experiencing a sysems failure I began restoring my images from backups. I have had no end of problems with Image dates. I have come to the determination that Aperture is NOT using either the "Create Date" or "DateTimeOriginal" as the image "Date" or "Date Created" data if other fields have other dates.
Here is a clip from my image metadata using exiftool:
File Modification Date/Time     : 2012:09:23 19:53:15-04:00
File Access Date/Time           : 2013:01:16 11:34:38-05:00
File Inode Change Date/Time     : 2013:01:16 11:31:32-05:00
Create Date                          : 2006:02:20 11:51:12.10
Date/Time Original              : 2006:02:20 16:51:12.10
Modify Date                          : 2006:02:20 11:51:12.10
And here is what Aperture utilized on import
Date:                               9/23/12 7:53:15 PM EDT
Date Created                         9/23/2012 7:53:15 PM
So Aperture utlized the File Modification Date/Time as the Create Date despite that the fact that the Create Date field is present and is properly formatted in the original image.
According to the Aperture mapping table, this shouldn't be happening.
Now, before someone recommends that I use Aperture's Date Adjust utility - I'm talking about slightly over 30,000 images. Editing images one at a time, or in blocks when you don't know what field Aperture is using as the Create Date would require individual inspection of each image followed by manual adjustment of each image. That approach isn't acceptable.

Hmm ok, let me restate the issue then, I thought I was clear. I could have pointed out in my original post however, that only the EXIF and IPTC date fields were displayed from the metadata dump.
The data set presented in my first post is the EXIF dataset from the file which clearly shows the image was captured by digital camera at
Create Date                          : 2006:02:20 11:51:12.10
Date/Time Original              : 2006:02:20 16:51:12.10
(The delta of 5 hours is the result of Zulu versus local time offset)
But, when I ingested it into Aperture, the import routine utilized the IPTC field
File Modification Date/Time     : 2012:09:23 19:53:15-04:00
which is updated by the OS whenever you move the file around outside of Aperture. (a number of image data fields are updated by the OS - filename for example is another.). This resulted in the image date fields being stamped in Aperture as:
Date:                               9/23/12 7:53:15 PM EDT
Date Created                         9/23/2012 7:53:15 PM
Which obviously came form the File Modification Date/Time field and not (either) the Create Date or Date/Time Original fields.

Google maps stopped working, & won't re-install

My Goolge maps app suddenly decided to not open up. After restarting etc, I uninstalled it & try to re-install but I just get 'Online Certificate Check Failed'
Any ideas please?
Nokia N8 on Belle

davej65 wrote:
try to re-install but I just get 'Online Certificate Check Failed'
Does this help?
davej65 wrote:
My Goolge maps app suddenly decided to not open up.
Make sure not to disable Wi-Fi. If you disable Wi-Fi via the notification bar, Google Maps opens for a seconds and closes rigth away again. Google Maps uses the Wi-Fi API for detecting your location faster. Obviously, Google does not expect the Wi-Fi to be turned off.

Aperture asks serial number on APP

Hello everybody, i just restarted my mac and try to open aperture. I have the Aperture App. Suddenly i have to enter user information:
First Name, Last name
Organization
Serial Number
Did i ever got a serial number when i bought the app? I do not think so. Who can help me?
Thnx
Marcel

" Aperture might have been bought through the App Store originally but at some point he attempted to upgrade by downloading the dmg file rather then going through the App Store."
That is exactly what I have been thinking, and also, I was not quite sure, if it was an Apple Store or App Store purchase, Frank; we will see, when we have the answer to your question, and know the Aperture version.
Added: Apple Store or App Store
Why is Apple so inapt at picking unique names?

IPhone and Aperture sync

Ok,
My iPhone 3G photos are no longer available. I tried Ap3, Ap2, iPhoto, Image Capture.... Nothing. Everything works under iTunes (even Internet Thetering) except the images. The iPhone no longer appear under import at Aperture. I did a Restore and everything worked untill I used the last iPhone back up.
Any suggestion ?

Same here. On the last Aperture sync, it suddenly popped up after a while. Thinking it might have had with space (I had 0k of space left, hence the need for a sync), I deleted all my music. Now the iPhone has 12Gb free, but still won't show up.

Airport Extreme or Droboshare to connect Drobo with Aperture wirelessly

I use a Drobo as my primary storage for referenced image files and use my Macbook Pro to store the library.
I'm frequently not able to work in my office and want to be able to put the Drobo on the network in my office (upstairs), connect it to my wireless network and continue to use Aperture anywhere in the house.
I have tried to connect my Drobo (and a normal USB2 hard disk) via my Airport Extreme base station (after installing all of the latest updates a couple of days ago) and Drobo does work with that - including Time Machine.
However, when I open Aperture when I'm using Drobo (or USB2 drive) as an airport disk, the referenced files on the Drobo (even though Drobo is mounted) all appear as off line. I am assuming this is because the reference to the files is slightly different (ie Airport Disk/Drobo/Images instead of /Drobo/Images).
So that rules out the AEBS?
Has anyone got experience with DroboShare to network a Drobo AND use an existing referenced file structure? I want to be able to use the Drobo connected when in the office, but switch to DroboShare when I'm not and therefore the Drobo must be treated as the same path. Because Drobo is on the network I can only assume that the path changes and therefore this wouldn't be possible?
Does anyone have any positive experience with getting an existing (without having to move all the masters to a new path) referenced library to work with either an AEBS or a Droboshare?
If I can't use Drobo in this way, Droboshare is a pointless exercise for me and I've tried my best to get the AEBS to work but the path change is screwing things up. If anyone has managed to get Aperture to work with the AEBS I'm all ears!
Thanks

Neither the DroboShare or the Airport Extreme will allow the Drobo to work with an existing referenced file structure unfortunately, as Aperture maps the path against each file as a fixed path rather than relative (IMO), so the inclusion of the network component places the Drobo on a different point in the path and Aperture simply looks at each path reference and says 'I can't find it' instead of being able to figure out that the drive is simply at a different point and find each file from there.
Looks like Apple fixed this issue with Time Machine as an existing time machine backup can now be referenced over a network when tied to an Airport Extreme. When you connect the drive for the first time it takes time machine a while to figure out where the backup is, but it does find it automatically eventually. So it is really just up to them whether they change the code or not in Aperture to allow users to switch from network to local connection.
The only option right now is to start from scratch with a referenced structure on a networked Drobo (or USB2 drive). That would of course work fine if you accessed the referenced files in Aperture over the network, but if you tried to access them with a direct connection you'd most likely run into the same difficulty.
In addition, there are no guarantees that when you are relocating masters or performing vault backups over a wireless connection or wired network that the files going across the network are actually being checked in at the other end. This was the same issue with Time Machine and that's why Apple locked USB2 drives out of Time Machine when you connected to an AEBS. Apple would have to ensure that the code not only referenced files correctly over a network but also ensure that files being written over the network (more specifically network packets) are checked in correctly at the other end.
Head over to http://apertureprofessional.com/showthread.php?t=13393 for this same topic (with more information)

IPhone suddenly closes applications!

Is it me, or is anybody else having similar issues?
See, I will be reading my e-mail, or navigating my google maps, when suddenly, the iPhone would kick me back to the "home" screen (as if I pressed the home button).
This was particularly annoying on a trip to Tampa, since I had to keep opening (and restarting the turn by turn trip directions) google maps over and over and the phone kept kicking me out.
It does the same while browsing pictures, email and it did it tonight while using Safari!
It does that while on EDGE and also while on WiFi...

Same here before 1.1.1 and after. It as happened mostly while doing what I would consider read/write centric activities: emptying lots of mai from trashl, surfing quickly with Safari, launching & stoping iPod videos. The application freezes or one of 3 things happens: 1) back to Home screen 2) screen goes black 3) screen goes white. Thus far pressing the Home button takes me Home after a brief delay for 5 to 15 seconds. Many times after the white or black screen goes away I emerge back at where everything locked up. Weird!
Message was edited by: XJ-linux

Fed up with "Unsupported File format" crashes!

I really like Aperture - but, I am totally fed up with only being able to edit a few photos before I get the dreaded red/brown screen and the message of 'Unsupported file format' This cannot be the case as they are all .tifs and I have just edited several OK. My whole day is now one of 'stop/start' and either quit or sometimes 'Force quit'. Then Aperture works fine for another short series of edits - before the same problem recurs. It wastes a lot of valuable editing time - and completely spoils the otherwise pleasurable experience of using Aperture!
I have made a lot of scans from original slides via a Nikon Coolscan 5000 - using Silverfast I have converted these from 48 bit to 24 bit. However, the file size is still large at 100MB - to get the best from the slides. I then import these .tifs into Aperture 2.1. I am using a MacBook Pro, 2.4 Ghz Intel Core 2 Duo with 4 MB RAM. I have an external 24 inch monitor. The .tif files are on an external firewire hard drive - 500 GB LaCie. My Aperture library is in my pictures folder on my MacBook Pro.
Can someone PLEASE explain how and why I can make a series of edits fine in Aperture and then suddenly I get the red/brown screen and this unsupported file format message?
Is it a memory problem? Given that I need to edit such large files is it a problem for my (powerful) MacBook Pro? Or, is it a more general problem with Aperure 2.1?
Any advice - or solutions - PLEASE

It's a bug in Aperture 2.x with large files and/or large pixel dimensions on images (not clear which). I have submitted a bug report, as should anyone who is seeing this. You'll find quite a few threads on this if you search back. The error message is frustratingly incorrect: there is nothing whatsoever unsupported or wrong with the file format, it just leads you down some dead ends in trying to find a solution while you figure that out.
I could sometimes not even work on one image before it would do this. I went from 6GB to 10GB in my Mac Pro, and now I can pretty reliably work on two images before having to restart. So that to me smells like a memory leak or memory mismanagement of some sort is at the root of this, but who knows. We're all just waiting for each next release, hoping Apple has finally found and fixed this, because as you know they don't spend a lot of time discussing what bugs they're addressing; they just show up fixed eventually (one hopes!)
If anyone chimes in here to tell you it's your fault for working with such large images, just ignore them. There were releases of 1.5 that handled these images just fine, as Aperture should. It broke with 2.x.
Duncan

My location is 105 miles out

'My location' in Maps has suddenly changed to another location 105 miles away

Report it to Apple. Tap the bottom, right flap on the map then "report a problem" (above "Print)

Dodge and burn tool

Well I have used the tool a couple of times and I just opened my aperture, and its suddenly gone...any reason why? Thats kind of weird

Never heard that one before. The dodge and burn plugin is actually part of the package in the applications folder so it's kind of hard to nuke it w/o blowing away aperture itself.
Hmmm, that is weird. I'll take a poke around and see if I can break it on purpose and get back.
RB

Fibre Link Down

We have been using an Apple RAID with 8 disk (4 in each controller side) for almost 6 months, each controller in the raid is conected to a Qlogic 5600 and from there to 3 IBM servers using slicing and LUN mapping.
Suddenly since two weeks ago we have been receiving this logs AT IRREGULAR intervals:
Upper Controller 04/01/08 08:51:09 PM RAID Controller 1 Fibre Link Up
Warning Upper Controller 04/01/08 08:51:08 PM RAID Controller 1 Fibre LIP
Warning Upper Controller 04/01/08 08:48:48 PM RAID Controller 1 Fibre Link Down
And the windows server report that the SCSI disk have been disconnected, when we stop all the servers and reboot the raidfabricsservers works for 2 to 5 days and again the same messages.
Any idea of what is happenning and how to handle this ?
Humberto

+ the ports on the fibre switch should be configured right for storage/hosts:
RSCN suppression on / device scan off for hosts
and vice versa for storage
+ the logs from the FC are hidden, you can access them following the next procedure. (As explained in the [qlogic event manual|http://www.servants.co.jp/qlogic/pdf/2-259060-00_A-QLogicFCSwitchEventMassageGuideFW40.pdf]
Archiving and Downloading the Event Log
You can use the command line interface to create a file on the switch that contains
the most recent 200 entries plus the previous 1000 entries. This file can then be
downloaded to the workstation using FTP. To create and download a log file, do
the following:
1. Log into the switch through Telnet and create an archive of the event log.
The Set Log Archive command creates a file on the switch named logfile.
QLogic #> admin start
QLogic (admin) #> set log archive
2. Open an FTP session on the switch and login with the account name images
and password images. Transfer the file logfile in binary mode with the Get
command.
ftp ip_address
user:images
password: images
ftp>bin
ftp>get logfile
xxxxx bytes sent in xx secs.
ftp>quit

Aperture Map Is Suddenly Screwy

Similar Messages

Maybe you are looking for