Aperture's unsupported image message - a false alarm but a real problem

(see Updates. I've left this post roughly as it unfolded, but this wasn't an Aperture bug.)

The latest incarnation of an old Aperture bug is particularly nasty.

You get a project where only outlines of images can be seen. Click on them and you get a red square with white text saying "unsupported image format'. Restart doesn't fix this, there's no known fix. It's what you get with unsupported RAW images, but it occurs with old RAW images.

Here's one threat on the topic: Apple - Support - Discussions - Unsupported Image Format ...

There's a new release of Aperture, but no news if it has a fix. It's too big for me to download over a lousy hotel connection.

Aperture is a pro project. You can imagine how happy Aperture pro users must be to lose their work this way.

Update: The "unsupported image format" error is a red herring. I experimented with dragging the project out of Aperture, then inspecting the contents (right click, open package). It contains metadata, but no images. The images appear to have been lost by Aperture, leaving only misleading metadata. I suspect there's an image loss bug that can be triggered by moving images between projects contained in different folders.

Update 2: I'm going to run the consistency check described in Apple's Aperture troubleshooting page. I'd moved this Library from another machine, and I think that's an unsupported action. I see now I have 'read only' permissions for the Package -- I'm surprised it works at all. I have changed Package Permissions to read/write. I'm going to save a copy before I do this however.

Update 3: After I changed package permissions I ran the consistency check (Command-opt click on Aperture, hold cmd-opt until get dialog) to fix other permissions. That concluded without a message. I then restarted Aperture and this time ran the database repair. That found the images that had vanished earlier and restored the project with correct values.

So this problem began with my copying a library to a new machine, which is not entirely kosher. Then I failed to check permissions on the library/package. That meant Aperture could do some things, but other things would fail (no permissions). This particularly impacted copies on folders -- so when I tried to copy images into a project in a certain folder only some of the data was copied -- the pictures were orphaned. (This is arguably a bug, Aperture should detect the copy failure.)

The unsupported image message was a red herring.

Google Reader messes up the shared tag feed - includes items shared by those I follow

Something odd his happening with my Google Reader - "MacOSX" shared posts. I'm seeing posts I know I didn't share - including posts I've not yet read!

They are OS X related and they're mostly interesting. So is it due to some corruption with the (increasingly buggy) Byline iPhone app I use? Some mixture of what I share and what those I follow share? Google Reader bugs?

Weird. I'll have to track this ...

Update: I think it's a Google issue. The items showing in the public feed don't match what GR shows in its shared items list.

Update 2: My tag-specific shared item feed obtained from my "manage subscriptions" "folder and tag" list includes not only my shared items, but also items from blogs I follow that have been independently shared by people I follow! This is interesting, but, Google, so very, very wrong. Please don't make me explain why this is wrong, just think about it for a moment.

OS X Preview PDF display - it has limits

Montreal offers a detailed PDF map of the island ..

montreal.com - general tourist info

... See this Google map of the metropolitan area or download the incredibly detailed city map (pdf format) from the Montreal transit site ...

It's a richly detailed 4.4 MB pure vector PDF.

I tried viewing it in OS X Preview.app. Not such a good idea. Preview pegged my MacBook at 98% CPU and a GB or so of memory.

This is the first time OS X Preview has disappointed me. I hadn't realized it was such a light duty application. I'm contemplating installing Adobe's product, something I try very hard to avoid given Adobe's astounding record of installer dysfunction.

Using Google Voice when traveling internationally

When we visit the old country (Canada) I put my AT&T iPhone in airport mode. So no cell services and no data services. It will work in Canada, but even the voice charges are prohibitive.

So what do I do about for people calling my cell phone while I'm away? How should people from work get in touch with me?

Enter Google Voice.

I forwarded my iPhone number to my local Google Voice number (it's in iPhone settings under phone). In Google Voice turn off forwarding to the iPhone [1] and all other numbers.

Now calls to my mobile to go my GV voice mail. All messages are transcribed, and an email is sent to my Gmail account with the transcription and a link to the audio (which plays, interestingly, in the iPhone's video player -- weird, but it works).

So when I travel voice messages will reach me whenever my iPhone has WiFi services, which is usually a few times a day. Not bad.

When I cross into the US I just turn on the iPhone and turn off forwarding.

Now to see what happens if I try to may a GV call from Canada (I think it won't let me do this, but I'll give it a try).

[1] If you forget to do this, you can set up an infinite loop. GV forwards to the phone which forwards to GV. Ok, so I forgot. Turns out the phone rings for a while but GV eventually goes to voice mail (because you're not picking up the forwarding). If you turn off forwarding to the phone GV picks up incoming calls immediately.

Update 8/26/2013: A more sophisticated version of this.

iPhone notifications – two services that create notifications for email

In the past week or so I’ve come across two different services that create iPhone notifications upon email receipt. One here:

macosxhints.com - Push any email to the iPhone via third-party app

There have been several hints in the past, including these two of mine, with regards to using push email on the iPhone, or using MobileMe with custom reply-to entries, etc. A new application called PushMail ($5; App Store link) seems to me to be the ideal way of using push email (or any mail) on the iPhone…

… Essentially, PushMail gives you your own new email address, something like a@dopushmail.com. Everything that gets sent to that address has a push notification displayed on your phone. The notification displays the sender, the subject, and as much of the email as can fit in a notification. So, you can configure your regular email addresses to all forward a copy of your email to that new address, and you will have your email pushed to you.

This is an option in the settings for most webmail email services such as Gmail, or you can configure procmail to forward a copy, if you've got control of your email server. ..

..You can to the same for free using text free lite - lookup in appstore textfree, they will give you a push enabled smth@textfree.us address, then just forward to that address…

and another:

TUAW: Apple approved Gmail app for iPhone. Has hell frozen over?

TechCrunch is reporting today that an iPhone App that utilizes the Apple Push Notification system to let you know you have new Gmail is about to hit the app store. The app, called GPush, is developed by Tiverias Apps, and gives Gmail users an instant notification that new mail has arrived. iPhone users will still have to read their mail, either in a browser or the Apple Mail client, but the notifications will be essentially instant.

GPush will be US$0.99 for a week, then will be sold for $1.99 after.

The Tiverias sight has more on GPush including an FAQ. It does work with Google Apps.

That means I could create an email account on one of our family Google Apps domains just for push email. Then I could use that whenever I have something I want to be notified of, like an email notification related to a Google Calendar event. Using an account like this has a very important advantage – the way GPush works their server has to hold your account un/pw:

Should I be concerned about providing my password to GPush?

When we created the app, we committed first and foremost to security. We are using multiple levels of encryption including SSL and obfuscation. We had a penetration testing team run their analysis on the server and passed their certification.

Briefly, HELL YES you should be concerned. My Gmail credentials are among the most valuable “things” I own. Steal my car please – at least that’s insured! (It’s also very crummy.) I’m not giving the keys to the empire to any vendor. A purpose build Google Apps account though – that I could do.

I’ll provide an update on how well this works.

We can now tweet from Google Reader

When you click the Twitter link Google Reader opens Twitter with a URL shortened link to the post ..

A flurry of features for feed readers

We've made it easier to share posts you like to Blogger, Twitter, Facebook, and more, with our new 'Send to' feature...

Just head over to the settings page, and enable the services you want to use.... you can create your own 'Send to' link with a URL template...

To share an item on one of your sites, simply click the 'Send to' button and choose your service. If you're into keyboard shortcuts, 'shift-t' will do the same.

It's a lesser version of what I wanted Byline to do. It's interesting, but, darn it, they got it wrong! I want a single button that would let me write a comment for sharing in Google Reader, and have that comment (length limited) go to Twitter. Also there's no option to send a post to multiple sites at the same time.

You can also send to Blogger, but it sends the entire page to the editor. I don't know if I'll find it very useful for blogging.

Overall, it's a step in the right direction, but only a smallish step.

Update 4/25/10: This is still not a part of the mobile reader UI. I think it's a dead end.

Verizon's WiFi service doesn't support OS X

This surprised me ...

Macintouch - Mac Marginalization:

... the rumor is that Verizon intends to support Mac users on its WiFi service in October, about 4 months after making the service available to Windows users. Such a delay could have been avoided by simply using platform agnostic user-verification methods....

Verizon chose to use some proprietary logon app?! That's such a peculiar choice it casts doubt on all of Verizon's technical judgment.