Tuesday, April 14, 2015

Apple's Photos App is Disappointing

I had high hopes for the new Photos app on OS X that was intended to replace both iPhoto and Aperture.  I spent quite a few weeks processing my large Aperture libraries, with the intent to convert them all to Photos.  I have about 100,000 photos split over two large libraries, plus a couple of smaller ones.

With libraries this large, I have always had speed issues.  To get around it, I have kept an 'Active' library that only contained my most frequently used images plus the current year.  When Photos was released just in the past week or so, I converted 'Active' to Photos and allowed it to migrate to the iCloud library.  It seems quick enough, with only a thousand photos.

It finally came time to see if I could process my 'Recent' library, which was about 40,000 pictures, spread over several years.  Starting Photos up, pointing to the Aperture library, it spend overnight converting the library, and then crashing.  I tried it again, on the converted library, and with a long, long startup, it also crashed before being usable for anything.

At least I could still use the original Aperture library, after some of the program's automated cleanup. It seems like I'll be keeping Aperture around for a while, if my libraries are unusable under Photos.  I may export photos and import them into Photos that way, but that will be huge, time-consuming process, but given that Aperture is not being updated and will die before too long, I'll need to do some kind of migration.

But if the problem is Photos' inability to handle large libraries, I'll have to find some other technique for handling my historical archives.  I'll keep an eye out for other people with large libraries and see how they handle it.

Wednesday, March 25, 2015

Internet Frustrations

I have several websites, some of them blogs like this one. Yes, I know, I should have only one and concentrate on that.  But things change.  I've been blogging since before the name was invented, and much of it is still on this site, even though I've been pouring more of my writing-focused content into henrymelton.com and my Facebook fan page lately.  Still, I'm not going to abandon Idle Thoughts anytime soon, since it's my primary repository for non-writing content.

And so, when google alerts flagged me that for a couple of days running, I had a spike in readership here, I rushed to see what had happened.  After all, the most recent posting was a couple of months old.  If I had a new flux of readers, I wanted to know where they came from and why.  At best, I could then find some way to reward them by providing more of what they came to see.  At the least, I could become more aware of the site that referred them, visit there and see if we had common ground.

But it was a frustration.  As you probably know, websites get a little snip of information that tells where a new arrival came from.  I looked, and what I found was this:
From this, I can see that the number one source of referrals lately was from social-buttons.  This is frustrating. It tells me nothing about where the site was, or the topic of conversation. It's just the site that manages the link button.  It's like asking "where did the click come from?" and getting the answer "From the mouse button."  No useful information at all.

You see, they might not even have wanted to come here.  Maybe the link was in error, or they were looking for the football player with my same name.  I can't tell.  

If YOU came here looking for something, I would be overjoyed if you left me a comment or an email. Seriously, sometimes even the spam is entertaining.  And if you were looking for something that you didn't find, let me know and maybe I can help.

See you next time.