Some of the loudest buzz to come out of the film photography community in 2017 was the announcement (in February) and subsequent limited release (in June) of FERRANIA P30® ALPHA, the new ISO 80 black and white negative film by FILM Ferrania – you can find further details right here.
The relatively short history of this new film stock has been well documented here, and FILM Ferrania’s Dave Bias talked a bit about P30® ALPHA and other future films we can expect in July 2017’s EMULSIVE x FILM Ferrania Community Interview.
To quote Dave:
“Our P30, for example, is derived directly from the original formula that was created for our Precision Coater. It performs almost exactly like its older cousin. But the “sameness” to the old P30 depends on your point of view. If you’re an emulsions scientist, our modern P30 is slightly different in very obscure technical details. If you’re a photographer, there is really no perceivable difference from the original.” ~ source
More from Dave a little bit later…
Before I jump into the review itself, let’s take a quick look at what you can expect from this and future parts in the series…
As with my Bergger Pancro 400 and other recent film coverage, this will be a long review and come together over several distinct parts.
Each part covers FERRANIA P30® ALPHA shot at a different speed with per meter, over exposed and under exposed examples. I will also be including the results of testing this film following a black and white reversal development process to produce slides (if you’re impatient, there’s a sneak peek here and a little further below).
Here’s an outline of the series as it stands at the time of writing:
- Part 1: 35mm FERRANIA P30® ALPHA at EI 80 with +/-1 stop exposure bracketing (Rodinal semi-stand)
- Part 2: 35mm FERRANIA P30® ALPHA at EI 640 with +/-1 stop exposure bracketing (Rodinal semi-stand)
- Part 3: 35mm FERRANIA P30® ALPHA at EI 80 with +/-1 stop exposure bracketing (reversal development)
It is highly likely that I will be repeating the bracketing / push processing in parts one and two using a different developer. More details on why at the end of this article.
Back to part one and here’s what’s covered: