CreativePro - Using Adobe Portfolio

Using Adobe Portfolio: article

If “build my website” is still on your To Do list, Adobe Portfolio is a quick and easy way to get a focused body of work online. Especially if you’re an Adobe Creative Cloud member, since Adobe Portfolio is available only as a benefit of an Creative Cloud membership (including the $9.99/month Photography Plan).

How does Adobe Portfolio compare to the long list of other and often more established web-browser-based site builders? How easy is it to learn and use Portfolio? Does it have the features that photographers and designers need to show their best work?

I try it out and then tell you what I think in my article for, which you can read at the following link:

Using Adobe Portfolio




macOS 10.12 Sierra image, courtesy Apple Inc.

macOS 10.12 Sierra: Will Adobe software work?

Now that macOS 10.12 Sierra is available from the Mac App Store, you’re probably wondering whether your Adobe software will work in the new Mac operating system.

With every Mac system upgrade, information about compatibility is often not available on the first day the new system is available, and emerges over time. If you use your Mac to run a business or as a serious hobby, do not upgrade to Sierra without thinking it through. (That applies to any operating system upgrade on any device.) Wait until there’s enough information about compatibility with all of your software and hardware.

Official statements

This section is updated as new information becomes available. A general Adobe statement about application compatibility has not been posted. (It took a while for an article to appear for OS X 10.11 El Capitan.) In the meantime, we rely on statements from individual product teams which usually appear on their official blogs, and those tend to emerge over time as issues become known.

While it’s frustrating when compatibility information isn’t available the day an OS upgrade becomes available, Adobe and many other companies prefer to wait until they’ve had sufficient time to test their software on the actual Mac App Store release version of macOS 10.12 Sierra, because Apple can be changing macOS code all the way up to that point.

Adobe Photoshop Lightroom

The Lightroom team has posted their Sierra statement (Lightroom and Sierra | macOS 10.12). It says “Adobe recommends that customers update Lightroom to the current version prior to updating macOS 10.12 (Sierra).”. It lists a number of compatibility issues, especially with Lightroom 5 and earlier, saying:

To avoid these compatibility issues on macOS 10.12 (Sierra):

  • Update to Lightroom 2015.7/Lightroom 6.7, or
  • Remain on your current Mac OS X version and do NOT update to macOS 10.12 (Sierra) if you are running Lightroom 5 or earlier.

Earlier, “Lightroom Queen” Victoria Bampton published a blog post with similar findings about Adobe Photoshop Lightroom in Sierra (Lightroom and macOS Sierra Compatibility).

Adobe Photoshop CC 2015

The Photoshop team posted a document (Photoshop and Sierra | macOS 10.12)  with a few known issues about Photoshop CC 2015.5, nothing major. As new issues turn up, they may add them to the document.

If you find a problem with Lightroom or Photoshop in Sierra, report it at the Photoshop Feedback site. If you run into a problem with other software such as Acrobat, Illustrator, InDesign, Premiere, or After Effects, try posting about it in the Adobe Forums. So far there aren’t many posts about Sierra in the Adobe Forums, so either “no news is good news” or everyone’s waiting to see what happens to the early adopters.

Adobe Premiere Pro CC

In response to a question on the Adobe Forums about Premiere Pro support for Sierra, Kevin Monahan of Adobe said “We haven’t announced support for this version of OS X yet to my knowledege. OS X 10.11 is the latest Mac OS that is recommended…It is not recommended that you install (Sierra) on a production machine at this time.” He’s not saying that Premiere Pro doesn’t work, because it does function in Sierra. He’s just saying it isn’t yet known whether there are any significant issues in a production workflow. For example, video and audio editing applications are particularly sensitive to whether third-party hardware drivers are compatible with a new OS.

Older versions of Adobe software (CS3–CS6)

I have upgraded my test Mac to the release version of Sierra. So far, various versions of Adobe Creative Suite (CS) applications I tried (the oldest being Photoshop CS3) are at least able to launch in the Sierra beta. As in El Capitan and earlier, older Adobe applications are able to launch after you run the Apple installer for Java for OS X 2015-001. If you see the alert below, clicking More Info takes you directly to the Apple download page for Java for OS X.

JavaScript requirement alert in macOS 10.12 Sierra.

Adobe software older than the Creative Cloud (CC) versions are not officially supported on macOS 10.12 Sierra. That doesn’t mean they won’t work; it just means that if those old versions have any new issues related to macOS 10.12 Sierra, there won’t be any updates to address them (that is, you’re on your own). From brief testing, Adobe application compatibility with Sierra appears to be comparable to their compatibility with OS X 10.11 El Capitan, with very similar limitations and conditions to those we’ve seen with the past few OS X releases. If Adobe does what they’ve done in the past, they will not be testing most older (pre-Creative Cloud) software at a level that can confirm which specific features do and don’t work; you’ll have to do that testing yourself (see “How to test macOS 10.12 Sierra yourself” below).

Photoshop CS3 working in macOS 10.12 Sierra.

Photoshop CS3 and up will run in macOS 10.12 Sierra after Java is installed.

With that in mind, here are a few things I’ve seen since trying out some older versions in Sierra.

Be prepared to uninstall and reinstall if needed. Adobe applications were already installed when I upgraded my test Mac to Sierra. After the upgrade, some older Adobe applications had licensing errors. I was able to fix these by uninstalling and reinstalling those applications, and the lesson here is to always make sure you have all of the information you need (such as license keys or registration numbers) to reinstall any of your key software.

“Installer Failed to Initialize” error. Some Adobe installers may fail to launch with the error “We’ve encountered the following issue. Installer failed to initialize. This could be due to a missing file. Please download Adobe Support Advisor to detect the problem.”

Installer Failed to Initialize” error.

Unfortunately, Adobe Support Advisor no longer exists, but there is an immediate workaround that should get the installer going:

  1. Right-click (or Control-click) the installer and choose Show Package Contents.
  2. In the Install window that opens in the Finder, go to the Contents/MacOS folder, and in there, double-click Install. That will open the Terminal application, some lines of code will automatically run, and the actual Installer should successfully launch.

Make a note of this workaround, because any pre-CC installers are unlikely to be updated.

[Update: A few days after I posted this, Adobe published a help document that confirms this workaround: Installing Creative Suite on macOS 10.12 (Sierra)]

Adobe Illustrator CS4. When starting the application, you may see an “Error loading plugins” alert which mentions PhotoshopExport.aip and PhotoshopImport.aip. This has been a problem for several OS X versions, and there is no fix that I know of. You can only work around it by clicking “Don’t show again” in the alert.

Adobe Illustrator CS5. Illustrator CS5 may crash on quit; this problem also existed in El Capitan so try the solution offered at the Adobe forums (Illustrator CS5 crashing on exit), specifically the part about renaming
/Library/Application Support/Adobe/CS5.5ServiceManager
/Library/Application Support/Adobe/CS5.5ServiceManager.bak

Registration servers, update servers, and activation servers. If you get a message saying that a registration or update server is not available in an old Adobe application, that won’t stop the application itself from working so it’s not much of a concern. A missing activation server may keep an application in trial mode, but I had no problems maintaining activation in the Adobe CS3 through CS6 applications I tried.

Adobe Creative Suite 2 (CS2) compatibility

This question comes up during every recent OS X upgrade: Some users moving up from older Macs running 10.6.8 or earlier to new Macs with the latest OS version may still be using the Creative Suite 2 (CS2) version of Adobe software, such as Adobe Photoshop CS2. As with the last several major Mac OS X upgrades, macOS 10.12 Sierra requires that software be written for the Intel processors that have been running Macs for over 10 years. CS2 applications were written for the PowerPC processors that ran older Macs. The last version of Mac OS X to run PowerPC software was OS X 10.6.8 Snow Leopard.

There is no way to run Adobe CS2 software on macOS 10.12 Sierra. The only option is to use a newer version of the software.

How to test macOS 10.12 Sierra yourself

Since Apple made macOS 10.12 Sierra available as a public beta on on July 7, 2016 it’s been possible for you to test your own workflows with Sierra and report bugs back to Apple. Of course, you can now test with the final release version.

As with any new operating system, it’s best to install Sierra on a separate test volume (such as a spare external drive), and test your mission-critical applications and workflows on that before you upgrade the system you use for daily work. Don’t rush to upgrade to a new operating system until you are confident that there are no remaining issues with every application, utility, and device you depend on, such as displays, printers, cameras, mass storage, network storage, and color calibration devices. OS X 10.11 El Capitan was released in September 2015, but I chose to migrate my production Macs to El Capitan only after its fifth update (OS X 10.11.5) was released in May 2016.

How to manage Adobe license limits when you test a new OS version

When you test your Adobe Creative Cloud/Creative Suite workflow compatibility with a new OS version installed on a separate test volume or drive, you have to keep Adobe licensing in mind. For a single-user license you get two activations. If you’ve currently activated the software on one computer, no problem…you still have one unused activation to use on your test system. If you’re already using both of your activations because, for example, you use Adobe software on both a desktop and a laptop computer, you can still test on a third volume but you may need to do a few more steps.

For Adobe Creative Cloud (CC) software, it’s not a big deal. After you install macOS 10.12 Sierra on your test volume, you can install the Adobe Creative Cloud desktop application on it and then use that to install and run Photoshop CC and other Adobe CC desktop software. If this will be your third activation, Adobe may have you sign you out of one of your first two activations automatically so that you don’t exceed two. You can also manually sign out of one of your first two activations yourself.

When you’re done testing and want to go back to using your two production Macs, it’s a good idea to sign out of the Creative Cloud desktop application on the test volume to leave two activations available for your two production Macs. If you forget to sign out, don’t worry, Adobe will probably just ask you to sign into the Creative Cloud application on one of your production Macs and deactivate Creative Cloud on your test volume until you sign in there again. Remember, you don’t have to uninstall any Adobe software to switch activation away from the test volume; you can leave the software installed and only sign out. That makes it easy to come back later for more testing, because all you have to do is sign in again to reactivate.

For the older Adobe Creative Suite (CS) software, the process is manual. If you need to free one of your two activations For each Adobe Creative Suite application you want to test, such as Photoshop CS6, choose Help > Deactivate on one of your production Macs. With that activation now made available, you can now reboot into your macOS 10.12 Sierra test volume, install the CS software you want to use and activate it there. Activation should happen at the end of installation, but you can always do it by choosing Help > Activate.

When you’re done testing and need to return to your production Macs, you should now choose Help > Deactivate in those same applications before you shut down macOS 10.12 Sierra on your test volume so that Adobe activation instance is made available to the production Mac where you need to work.

Other aspects of Sierra that may affect Adobe software


One upcoming change affecting Adobe software is that Safari 10 will disable the Adobe Flash plug-in by default. You can still enable it if you want.


Sierra will be able to use the newly announced Apple File System (APFS), which is being designed around security, reliability, and the ability to work across macOS, iOS, tvOS and watchOS. APFS will replace HFS+. From an Adobe user point of view, an interesting thing about APFS is that it is case-sensitive only. Currently, Adobe Creative Cloud applications cannot be installed on case-sensitive file systems on the Mac. It’s not yet clear how much of an issue this will be, because APFS cannot be used on the startup disk in the currently available build of Sierra. Apple says APFS will not become the default for Apple products until some time in 2017. Presumably, by the time APFS becomes the standard, Adobe will have ensured compatibility…at least for the latest versions of its installers. Whether older versions of Adobe software can be installed on an APFS volume will be a question until it can be tested.

Wondering what Sierra is all about?

For the most in-depth Sierra review you’ll probably find anywhere, read the macOS 10.12 Sierra review at Ars Technica. As with every major release of the Mac operating system, the Ars Technica review not only evaluates the visible features that Apple promotes, but goes under the surface to explain changes to some of the underlying technologies in macOS and how they affect your Mac experience.

This article was originally posted on June 16, 2016 but has been updated throughout the macOS 10.12 Sierra public beta and final release.

InDesign Mag 86 Self Published Photo Books

Exploring self-published photo books: InDesign Magazine article

My friends at InDesign Magazine asked me to explore self-published photography books for the June 2016 issue. In my article Manual Exposure: Eye-Opening Self-Published Photography Books I write about photography books from four countries, focusing on the book designers and their creative approaches.

Each book had its own interesting design features such as multiple page sizes and paper stocks, loose inserts, innovative binding, or no binding at all. As I write in the article, the book designers “found ways to enhance their narratives through thoughtful and sometimes unorthodox design choices, and by close collaboration with book designers and writers.”

To read the article, click the link or image below to download the article as a PDF excerpt from the issue. (InDesign Magazine is published only in Portable Document Format.)

Manual Exposure: Eye-Opening Self-Published Photography Books (PDF)

First page of article Manual Exposure: Eye-Opening Self-Published Photography Books

Want to read the rest of the issue? You can buy it as a single issue or as a benefit of a paid InDesign Secrets premium membership, which may interest you if you want to advance your InDesign skills with the help of some of the most knowledgeable InDesign users in the industry.

InDesign Magazine is a bimonthly periodical devoted entirely to Adobe InDesign and to the thriving community of InDesign professionals. With editorial direction by page-layout guru and author David Blatner and editor in chief Mike Rankin, InDesign Magazine brings you the in-depth features, reviews, and tutorials you need to master Adobe InDesign. You can download a free trial issue.

Conrad Chavez - City Panorama 2016 selections

Two photographs selected for City Panorama 2016

I’m honored and pleased that two of my panoramic photographs have been selected for the City Panorama 2016 public arts program. One of the images is a panorama of a sunset at Haystack Rock in Cannon Beach, Oregon; and the other is of Dusty Lake in eastern Washington state.

City Panorama is an annual project that displays inspirational panoramic format art on Metro bus shelters throughout Seattle and King County. The art will appear on 8-foot-wide wood panels, and may be displayed for up to ten years. The process of printing, mounting, and siting all selected works takes several months so I don’t yet know where the images will be installed, but I’ll post the locations when I find out.

I shot the Dusty Lake photo from a high point on a ridge above the lake. Dusty Lake sits in a depression gouged out by Ice Age floods, about 200 feet below the top of the ridge. To get a sense of the field of view for this image, the lake is over half a mile long, and the far end of the ridge in the distance on the right is about a mile and a half away.

Both of my images are multiple-frame panoramas photographed in camera raw format, then merged and processed in Adobe Lightroom, with some additional edits in Adobe Photoshop as needed.

Thank you to Photographic Center Northwest, King County Metro, and Youth in Focus as well as the panel of jurors from those organizations who selected the images. Thanks also to 4Culture who fund the program through a grant.

For more information and to see the complete list of photographers and artists whose work was selected, visit City Panorama 2016 (Photo Center Northwest).

9.7-inch iPad Pro

iPad Pro 9.7 inch and iOS 9.3: Color management progress

The 9.7-inch iPad Pro and iOS 9.3 demonstrate that Apple is gradually implementing color management in iOS. While the presence of color management isn’t obvious on the surface, Apple has added multiple new features that would typically depend on color management. And Apple has now made iOS color management available to developers.

Night Shift

Based on the findings of sleep studies, the new Night Shift feature in iOS 9.3 tries to make it easier for you to sleep after using an iOS device late at night by reducing the amount of blue light emitted from the display. Night Shift does this by changing the white point of the screen away from blue and toward yellow.

This was an early clue for me that iOS was implementing color management. In OS X, the software f.lux can already perform the same kind of display white point adjustment that’s based on the time of day. f.lux does it by applying a custom display profile — you can see this in the Displays system preference in OS X. If Apple implemented Night Shift on iOS the same way f.lux does it on OS X, that suggests iOS 9.3 has some level of support for a display profile that can be manipulated.

f.lux software works by manipulating the display profile.

In OS X, f.lux software works by manipulating the display profile. Night Shift may work in a similar way.

True Tone display

The 9.7-inch iPad Pro includes a new feature that Apple calls the True Tone display. Apple says it uses “advanced four-channel ambient light sensors to automatically adapt the color and intensity of the display to match the light in your environment.” The point is to reproduce what happens when you carry a piece of white paper around all day long: Whether you notice or not, the apparent color of the paper constantly shifts to reflect the color and brightness of the ambient light, from normal daylight to relatively yellowish or greenish artificial light.

True Tone display images from Apple Inc.

This Apple graphic illustrates how the True Tone display adapts to match ambient lighting conditions.

Because an iPad screen works by emitting its own light, it can’t reflect ambient light like a piece of paper can. What the True Tone display does instead is use the iPad light sensors to make the color and brightness of the iPad display’s emitted light match the ambient light. It’s a curiously elaborate way to reproduce what happens in the natural world with no batteries.

The white point change of the True Tone display appears to be conceptually similar to how the Night Shift feature works, and that’s why I’ve assumed the True Tone display came into existence in part because there is now a foundation for color management in iOS 9.3.

DCI-P3 display

Another new feature of the 9.7-inch iPad Pro is that its display is claimed to cover the DCI-P3 color gamut. In terms of color gamut size, that display puts the 9.7-inch iPad Pro in a class above most other mobile devices and all other iOS devices. As I noted in my article A Look At The P3 Color Gamut Of The iMac Display (Retina, Late 2015), DCI-P3 is so much larger than the conventional sRGB color space that color management is essentially required to maintain color consistency for objects that have always assumed a display would be close to sRGB, as well as for objects tagged with other color spaces. Using a DCI-P3 display was another clue that iOS now contains a standard color management infrastructure.

Developer notes emerge

Up to this point I was only guessing that there was a color management system in place in iOS. Then Jeff Carlson reported on Twitter:

The tweet links to a post on Jeff’s blog, which refers to a Twitter conversation that confirmed color management is in place in iOS 9.3.

It’s official, and I don’t have to wonder any more: Apple has in fact added support for color management in iOS 9.

[Update: Craig Hockenberry has now written a very interesting and more technically grounded article about iOS color management: Looking at the Future]

Almost there…

If you consciously use color management on your OS X or Windows computer, the current implementation in iOS 9 may not yet meet all of your expectations or needs. While there are now iOS 9.3 features that use color management and Craig Hockenberry’s tweet says that color management is “completely open to other apps,” as far as I know you can’t yet do things like install your own ICC profiles, connect and run a display profiler, soft-proof, or use the equivalent of the Assign Profile or Convert to Profile commands in the desktop version of Photoshop. Right now it isn’t clear how quickly Apple plans to have iOS support the same level of color management as OS X and Windows, or even if Apple intends to support color management that far on iOS.

But the appearance of color management in iOS is still a welcome development. At the very least, it provides a way for color reproduction on iOS devices to be potentially more reliable than on devices running other mobile operating systems.

Many may not accept this until it’s possible to create a custom display profile in iOS, but displays have matured. LED-backlit displays don’t drift as quickly as CRT or CCFL-backlit displays used to, and iOS devices may be using display circuitry that compensates for age (some desktop displays have this feature). Apple may feel that they can keep the iPad Pro display stable enough so that the factory-installed display profile, together with a color management system, provides color rendering that’s reliable enough for most purposes and acceptable for photo editing.

It will be interesting to see how quickly iOS apps take advantage of the color management foundation that Apple has added to iOS.