The snapshot, a combination of nearly 7,500 separate Hubble exposures, represents 16 years’ worth of observations. The ambitious endeavor is called the Hubble Legacy Field. The new view contains about 30 times as many galaxies as in the HUDF. The wavelength range stretches from ultraviolet to near-infrared light, capturing all the features of galaxy assembly over time.
The image mosaic presents a wide portrait of the distant universe and contains roughly 265,000 galaxies. They stretch back through 13.3 billion years of time to just 500 million years after the universe’s birth in the big bang.
Despite those staggering figures, this image still represents only a tiny portion of the sky, covering roughly the area taken up by the Moon in the night sky.
I downloaded the 700MB 25,500×25,500 PNG version of the image, and set to work making some new 5120×2880 desktop images. You can read more about the process in an upcoming post, but for now, here are the resulting images…
While working on some photos this weekend, I noticed that I’d taken two nearly-identical photos of the Enola Gay at the Steven F. Udvar-Hazy Center—nearly identical, but separated by four years:
Click once for larger, then click the icon in the upper right of the pop-up for largest vesrion.
The left image was taken in 2014 with a 2011 Pansonic Lumix DMC-ZS10 pocket camera (specifications); the right image was taken in 2018 with my 2017 iPhone 8 Plus. (Interesting to note that I didn’t bring my DSLR on either trip…the best camera is the one you have with you, right?)
Neither of the above images has been edited, beyond whatever algorithms the cameras use when saving the photo. Frankly, I was amazed at just how much better the iPhone 8 Plus photo is compared to the one from the Lumix: The Lumix photo is skewed heavily blue, edges aren’t well defined, and detail in shadow areas is obscured. The iPhone’s image is perhaps just a bit towards the yellow end of the spectrum, but it’s miles better than that of the Lumix.
I’ve been away from home for nearly a month—first a couple weeks in DC to visit family, then off to Las Vegas with our APA 8-ball pool team for the World Championships. We did reasonably well, winning four matches and finishing in the 65th to 128th place bucket. (It’s a huge tournament, with 713 teams this year, so not every place is played out.)
Because of the uncertainty of when we’d be finished in the tournament—it’s a modified double-elimination, so you’re guaranteed two matches, but nothing more—I chose to drive, so I could leave as soon as we were finished. (Also playing into my decision was the fact that I was leaving from south of Bend, Oregon, which isn’t really convenient to flying to Las Vegas—I’d either have a one-hour drive to an airport followed by a flight to Seattle and a layover, or a four-hour drive to Portland for a direct flight.)
I’ll have more to say on the road trip in a future write up, but thought I’d take a minute to share some photos I snapped during the journey. None of these are edited at all; I haven’t had the time; they’re all direct from the camera, my Nikon D5500 (though there is one iPhone panorama).
First, in Reno, I stumbled across this fantastic exhibition of classic cars. Although it was really warm out, it was well worth walking through this collection of gorgeous cars. There was a bit of everything there—true classics, kit cars, semi-modern cars, and even a few race cars.
Once in Vegas, on our one day off, we drove out to Hoover Dam, drove across (which I didn’t think was allowed any more, after the opening of the Hoover Dam Bypass, but it was), then parked and explored for a bit. I snapped a bunch of pictures, none of which reveal just how mind-numbingly hot it was outside. They also, as always, fail to capture the sheer size of the dam and the vertigo you experience when peering over the edge. It really is worth the visit if you’re in the area. (The tour is highly recommended, too; we just didn’t have enough time.)
In all, it was a great trip, and hopefully we do well in league this year and get to go back again next year!
A friend asked if there was a way in Photos to see which albums a selected photo had been added to. This is one of those things that would be incredibly easy for Apple to provide: Select a photo, press Command-I, and in the info window, you could see a list of all albums containing the selected photo.
Unfortunately, Apple doesn’t seem to think people might care about what albums a photo is in, so this feature exists only in my mind. Thankfully, Mac users Jacques Rious and léonie wrote an AppleScript to solve the problem. I used the first instance (version 4) of the script in that post and it worked fine in High Sierra. (In case Apple ever decides to remove its forums, I’ve recreated the script below.)
To use the script, paste it all into AppleScript Editor and save it as an application (or you can just run it in AppleScript Editor). In Photos, create a top-level album (I named mine Find Albums Photo Is In), and place the photo you want to know about into that album. Leave it selected, then run the AppleScript. You’ll see one dialog stating what photo is being used, then after a bit, you should see a results dialog, like this:
As you can see, the album used for the search is included in the results; someone with better AppleScript skills than I could probably modify the script to exclude that album (any takers?). While I’d much prefer Apple include this feature directly in Photos, at least there’s an alternative when you need this information.
Last fall, I finally made the move from iPhoto to Photos…months later, I still find myself frustrated by many things in the Photos’ user interface.
Today’s aggravation dealt with cleaning up a bunch of older photo albums—some I just wanted to delete, others I wanted to convert from Smart Albums into normal albums (because I wouldn’t be adding any more photos that used the keywords in the Smart Album). That meant I wanted to delete a bunch of albums—well over 100.
Deleting an album in Photos can only be done from either the My Albums overview, where you can select more than one (though not across folders), or via the contextual menu in the sidebar.
The My Albums view wasn’t going to work for me, as I needed to look at and work with many of the albums, across many folders. But after the sixth time of doing the “right click, select Delete Album, tab to Delete in the confirmation dialog, press Return” dance, I was sick of it. Time for another Keyboard Maestro macro.
This one is very simple—it just replicates the actions required to delete an album. With it in place, I click on the album I wish to delete, then press Control-D. It’s still more mouse interaction than I’d prefer—why can’t I select albums via the keyboard?—but it’s oh so much faster than using the contextual menu.
I find slow-motion video of falling snow oddly compelling, and was looking forward to filming some snow with my new iPhone 8 this winter. Little did I know that winter would arrive this morning, at least briefly in central Oregon (where I am for a few days).
It was too warm to stick, but we had a good 30 minutes of these huge, fluffy flakes falling early this morning. Here’s a decent-quality brief snippet in slow-mo (240fps at 1080p)…
I uploaded the original version (1:13, 122MB) if you’d like to watch a longer version—though I don’t know that anyone else finds this as visually interesting as I do.
As noted in priorposts, I’ve recently moved to Photos from iPhoto. So far, it’s been a mixed experience. There are some elements of Photos I like, but as of today, those things are outweighed by the things I don’t like.
I’ve vented on a number of the things I dislike on Twitter, but wanted to expand on both the positives and the negatives in more detail. Hence, this “one week in” review (of sorts) of Photos, from the perspective of an experienced iPhoto user.
I’ve also included some tips for working with and migrating to Photos for those who haven’t yet made the move from iPhoto. Finally, if you’re still reading, I’ve listed the key features I’d really like to see come to Photos in a future update.
Note that I am not a great photographer, but I do take a lot of photos—I have over 40,000 photos and a couple thousand video clips in my database. To keep things organized, I use lots of keywords and Smart Albums, so much of my feedback on Photos is concerned with those areas of the program.
First off, my time with Photos hasn’t all been bad; there are some things that I really like in Photos…
As a recent somewhat-forced convert to Photos, I’m struggling with a number of things—more on that coming in a future post. But one of the tougher adjustments for me is that Photos uses a floating Info window, whereas iPhoto had an embedded info panel.
I keep the Info window open all the time, because I do a lot of work with keywords and location. (I also like to keep the Keywords window open, though this one was also floating in iPhoto.) I resize the iPhoto/Photos window quite often, depending on what I’m doing with other apps—sometimes I want my photos covering the screen, sometimes I don’t.
In iPhoto, this isn’t an issue (left GIF), as the info panel is attached to the main window. In Photos, though, resizing the main window leaves the Info window floating in space (right GIF).
I don’t like the big gap, either visually or operationally, so I wind up moving the Info window next to the newly-resized main window.
There are a few solutions to this problem, the best of which only Apple could provide. They could make the Info window a panel below the photos, or they could make it magnetic so that it would stick to the edge of the Photos window, even as it resizes. I don’t suspect we’ll see either solution coming from Apple, though.
Instead of waiting for Apple, I used one of Many Tricks’ own apps, Moom, which (among its other tricks) has the ability to save window layouts, either within an app or across many apps.
I know that’s a shocking headline, but that certainly seems to what they’re saying for a certain group of users (red emphasis added):
By default, your System Photo Library is stored in the Pictures folder on your Mac, but you can move it to another location on your Mac or store it on an external storage device. WARNING: If a Photos library is located on an external drive, don’t back up the drive using Time Machine. The permissions for your Photos library may conflict with those for the Time Machine backup
Jan 23 2018 update: Thanks to reader Brian for commenting below that Apple has updated this page with much clearer wording. It now reads (emphasis added):
If a Photos library is located on an external drive, don’t use Time Machine to store a backup on that external drive. The permissions for your Photos library may conflict with those for the Time Machine backup.
That just means you shouldn’t use the same external drive for both your Photos library and as a destination drive in Time Machine. This makes much more sense; continue reading only if you care about my feelings on the original incorrect wording.
Here are my quick thoughts on each, and my buying plans…
Apple Watch Series 3
This is a nice evolution of the watch. The LTE doesn’t really interest me, as I’m sure it’ll require another $5 or $10 a month to my wireless carrier, and I almost always want my phone with me. (If I swam regularly, I might feel differently about that.) The much-faster CPU would be a nice upgrade over my original-generation watch, but the Series 3 is nearly a full millimeter thicker than the original…and honestly, I think the first version was already borderline too thick.
Will I buy? At this time, the outlook is doubtful; my watch is working fine, and a faster CPU isn’t worth the added thickness and $359 of my money.
Apple TV 4K HDR
Support for 4K is welcome, and long overdue. I’m not so sure about HDR; sometimes I find HDR images tend to look artificial, and I don’t know if I’d find the same issue in moving images. A real added bonus was Apple’s decision to provide the 4K version of movies you’ve purchased for free—this from a company that charged us to upgrade the quality of our music files a few years back.
I wish Apple wasn’t so damn set on streaming everything, though—I would much prefer to store movies directly on the device, to make it more portable and not subject to the vagaries of wifi, device positioning, and network load. Those times are gone, though, so now the only choice is whether or not to spend $20 more for the 64GB version.
Will I buy? Yes, and I’ll spend the extra $20 for the extra 32GB. I’ve been moving an Xbox One back and forth from the game TV to our 4K TV to watch 4K content, so this will be a simpler solution.
iPhone 8 and 8 Plus and iPhone X
Let me get this out of the way: I do not like the iPhone X. Well, that’s not true. I think almost all of it is absolutely stunning, and I really want one. Unfortunately, that’s “almost all,” and there are two things that aren’t perfect that will keep me from buying this phone…
The Notch. I absolutely, positively hate the cutout at the top of the phone for the sensors. In case you (somehow) missed it, this is the notch…
I would have much preferred if Apple just blacked out that entire region, giving up that marginally-usable pixel space for a cleaner appearance. I understand that videos can play cropped, so as to not be “notched,” but it’s the presence of the notch in other normal views that really gets to me. It’s everywhere.
Many people won’t notice, or won’t care about the notch. I wish I could be one of those people, but I can’t. During the keynote, all I could focus on whenever the phone appeared was the stupid notch. It simply grabs my eye, and I cannot unsee it when it’s there. (Maybe a future software update will stop drawing the desktop up there, which would make it look much nicer to my eye.)
Face ID. Apple has told us facial recognition is more secure, and I have no reason to doubt them. They also told us it’s fast, and it seemed to be in the demo. But secure and fast can’t override the absolute convenience of Touch ID. I can use Touch ID as I remove my phone from my pocket (press plus press-click), and it’s ready to go as soon as it’s out of my pocket. I don’t have to look at my phone unless I want to; if I have to look at my phone every time I want to unlock it, that’s going to get annoying. Very quickly.
Apple Pay is even worse. Today’s system is as near-magic as any tech I’ve ever used: Hold the phone near the register, rest finger on the home button, and you’re done. With Face ID, it appears (based on the demo in the keynote), I’ll have to both double-tap the side button and look at the phone to use Apple Pay. Ugh.
There are also some security considerations with Face ID, as pointed out by Ian Schray. The police cannot compel you to put your finger on your phone without a warrant…but can they compel you to simply look at your phone?
Other than these two no-go items, I really like everything else about the iPhone X. It’s only marginally larger (.20 inches taller, .15 inches wider) than an iPhone 7, yet has a screen that’s 30% larger and has more pixels than the gigantic Plus model phones. It also has the double cameras, which I would love to have on my next phone.
While you may not consider the notch and Face ID as deal breakers, they really are for me. I’ll go look at one in person, of course, but I simply cannot unsee the notch, and I hate the idea of having to look at my phone to unlock it, and taking more steps (and time) for Apple Pay.
So that leaves me with the 8/8 Plus versus my current 7. I think the new CPU, faster Apple-developed GPU, better cameras and sensors, 240fps slow-mo 1080p video, wireless charging, and the glass design make the iPhone 8 a compelling upgrade. As noted, I’d love to have the dual cameras to work with, but I think the Plus-size phone is just too big for daily use, so I think that’s out of the question. (I will visit the Apple Store again to see the 7 Plus before I decide for sure.)
Will I buy? As of now, yes, I plan on buying an iPhone 8, and hoping that…somehow…Touch ID survives for a long time to come, lest that iPhone 8 be my last new iPhone.