Tonal Photo

Tonal Photo Trying to make a business of my photos

Hasselblad pushed Phocus Mobile 2 v4.3.0 to the App Store this morning. The headline is automation: tap a portrait, and ...
05/29/2026

Hasselblad pushed Phocus Mobile 2 v4.3.0 to the App Store this morning. The headline is automation: tap a portrait, and the app builds the mask for you.

When v4.0 brought local adjustment masks to mobile, every selection was manual. You painted a brush mask, or dropped a linear or radial gradient, and cleaned up the edges by hand. v4.3.0 adds a Portrait Smart Mask that finds the person in the frame from a single tap, on both iPhone and iPad.

A note on support: This post represents my personal exploration and testing, not official technical support or guidance from Hasselblad. If you need assistance with your Hasselblad equipment, please contact Hasselblad directly: [email protected] for global support, [email protected] for the Americas, or visit hasselblad.com/support for regional options.

Key finding: Phocus Mobile 2 v4.3.0 adds a Portrait Smart Mask that auto-detects the subject from a single tap on iPhone and iPad. Invert it to edit the background independently, refine the edges with brush and eraser tools, and stack it with other masks. The update also adds an eraser to brush masks and improves EXIF retention on export.

What does the Portrait Smart Mask do?

It detects the portrait subject and generates a mask from one tap. From there you adjust the subject on its own, or invert the selection and work the background independently. Hasselblad's announcement lists exposure, highlights, saturation, color temperature, and tint as parameters you can push against the inverted mask.

The mask is not locked once it lands. Brush and eraser tools let you add or remove coverage, so you can fix the spots the auto-detection missed without starting over. Hasselblad calls it the Portrait Smart Mask, and it behaves like any other mask layer: it stacks with brush, linear, and radial masks, and supports duplication and deletion.

To reach it:

1. Open the editing interface.
2. Tap the mask icon in the toolbar.
3. Choose "Select Subject."

What changed for brush masks?

Brush masks picked up two refinements. There is now an eraser for quick corrections when you overpaint, and one-tap inversion to flip the selection after you have brushed it. Combined with the existing flow, size, and feathering controls, that closes the gap between a rough first pass and a clean final mask.

What else changed in v4.3.0?

Two more items, both about output rather than masking:

* Negative value adjustment on the highlight recovery and shadow fill sliders. The changelog states these sliders now accept negative values. I have not tested how that shifts their range in practice, so treat it as reported behavior until I confirm it.
* Improved EXIF retention for exported images. If you finish edits in the app and export from there rather than round-tripping to the desktop, more of the original capture metadata now survives the trip.

Should you update?

Yes. The portrait mask is the kind of feature that earns its keep on an iPad during a culling session, and the brush eraser is a quiet but real workflow improvement. The app sits at a 4.5 rating across 434 ratings on the App Store as of this release. Phocus Mobile 2 v4.3.0 is available now for iPhone and iPad; update through the App Store as usual.

References

1. Phocus Mobile 2 on the App Store
2. Hasselblad on Instagram: Phocus Mobile 2 v4.3.0 announcement

Phocus Mobile 2 v4.3.0 adds a one-tap Portrait Smart Mask on iPhone and iPad, plus a brush eraser and better EXIF retention on export.

You've probably noticed it. Open the same X2D II file on your iPhone and then on your iPad Pro and the iPad version look...
05/26/2026

You've probably noticed it. Open the same X2D II file on your iPhone and then on your iPad Pro and the iPad version looks meaningfully better. The tonal transitions are smoother, edge separation is cleaner, and the file feels three-dimensional in a way it didn't a moment ago on the smaller screen.

Most people chalk this up to screen size or display tech. The real explanation is mostly about your eye. The iPhone has higher pixel density than the iPad Pro. If raw resolution were the story, the iPhone would win.

💡A note on support: This post represents my personal exploration and testing, not official technical support or guidance from Hasselblad. If you need assistance with your Hasselblad equipment, please contact Hasselblad directly: [email protected] for global support, [email protected] for the Americas, or visit hasselblad.com/support for regional options.

Key finding: An iPhone 17 Pro Max has higher pixel density (460 PPI) than the iPad Pro M4 (264 PPI), yet still loses for X2D II image review. Angular extent on your retina is the cause. The iPad places the image inside the peak of your contrast sensitivity curve, where micro-contrast and tonal gradations become perceptible. Display tech is secondary.

Why do X2D II files look better on iPad than iPhone?

Two reasons, in order of impact. First, the larger screen places the image at a higher angular size on your retina, hitting the peak of human contrast sensitivity around 3 to 5 cycles per degree, which is where micro-contrast and subtle tonal gradations become visible. Second, display differences like Reference Mode and HDR brightness add a smaller secondary effect.

That ordering is the part most coverage gets backwards. Display tech is the visible answer, so it gets the credit. Angular size is the invisible answer, so it doesn't. The X2D II's 100-megapixel files happen to live exactly where this matters: the small, soft, structured transitions that medium format renders so well.

Why doesn't the iPhone's higher pixel density help?

Because pixel density is the wrong bottleneck. The iPhone 17 Pro Max, for example, has a Super Retina XDR display at 460 PPI. The iPad Pro 11-inch (M4) by contrast has an Ultra Retina XDR display at 264 PPI. The iPhone is denser per inch by a wide margin. Both are 10-bit, both are P3 wide-gamut, both run through the same Core ImageIO decode and color management pipeline.

What changes is angular extent. Hold the iPhone 17 Pro Max in portrait at typical reading distance, around 25 to 30 centimeters, and its 73-millimeter screen width letterboxes a landscape X2D II file into roughly 14 to 17 degrees of horizontal visual field. Hold the iPad Pro 11-inch in landscape at maybe 35 to 45 centimeters and its 232-millimeter screen width shows the same file at roughly 29 to 37 degrees. The iPad puts the image across about twice the angular width on your retina, and that's with the smallest iPad Pro in the lineup paired against the largest iPhone in the lineup.

That difference matters more than the pixel count behind each device. PPI controls whether you can see individual pixels at a given distance. Angular extent controls whether you can see the patterns those pixels form.

Have you seen the guide? I've published Essential Phocus 4.x for Mac - 83 topics across 8 sections and 220 pages covering everything from HNCS color science to HDR workflows. It's the reference manual Hasselblad hasn't updated since 3.8. Pay-what-you-want starting at $24.

Get it here

How does contrast sensitivity decide what you actually see?

Your visual system is not equally sensitive to all spatial frequencies. The contrast sensitivity function (CSF), first measured by Campbell and Robson in 1968¹, peaks around 3 to 5 cycles per degree of visual angle for typical viewing luminance. Above and below that band, your ability to detect contrast falls off sharply.

This is the load-bearing fact for the iPad observation. When an image is small on your retina, the fine tonal transitions and micro-contrast in it sit at higher spatial frequencies, in the region where your CSF is already falling off. The information is on the screen. Your eye can't pull it back into perception. Make the same image larger on the retina and those same transitions shift into the CSF peak. Suddenly they read.

For an X2D II file with 100 megapixels of tonal information and the kind of slow gradient work medium format does best, this is the whole game. The file has the data. Your eye needs angular room to resolve it.

The same physics is why prints look the way they do, why darkroom contact prints from medium format negatives feel different from the same image on a phone, and why a 30-inch monitor at a desk feels different from a 65-inch TV in a living room. Distance and size together set angular extent. Angular extent sets which part of your CSF curve does the work.

Where do Reference Mode and XDR brightness fit in?

They help, but at a smaller magnitude than angular extent. The iPad Pro has a setting called Reference Mode (Settings → Display & Brightness → Advanced → Reference Mode) that locks the display to a calibrated reference color space with controlled gamma and a fixed brightness target. It tracks specifications like Rec. 709 SDR, Rec. 2100 HDR PQ, sRGB, and P3-D65. Turning it on disables True Tone, auto-brightness, and Night Shift while active. The iPhone has no equivalent toggle.

Reference Mode is available on the iPad Pro 12.9-inch starting with the M1 generation (2021) and on every iPad Pro M4 (2024 and later, both 11-inch and 13-inch sizes). Earlier 11-inch iPad Pros did not include it.

For HDR content from your X2D II, both displays publish the same headline HDR peak brightness of 1600 nits. The difference is in panel architecture and what each can hold across screen area. The iPad Pro M4's Ultra Retina XDR uses tandem OLED (two stacked OLED layers driven together) and is designed to sustain bright output across meaningfully large bright regions. The iPhone 17 Pro Max uses a conventional OLED panel and hits its peak on small bright zones but dims sooner when a luminous region grows to fill the frame. For an Ultra HDR JPEG with a sky occupying half the image, the iPad shows you the frame closer to how it was authored.

The Phocus Guide's Display Requirements for HDR Viewing topic covers the HDR-specific side of this in more detail, including which devices support full HDR rendering and which iOS conditions (Low Power Mode, thermal throttling) suppress it. The Hasselblad HDR guide covers how HNCS HDR encodes the wide dynamic range that benefits most from those displays.

What's the best way to review X2D II files in practice?

A few practical takeaways from how this physics plays out.

Match your viewing distance to your evaluation goal. Reviewing fine detail and edge work on a phone screen at 30 cm is a losing fight against the CSF. The same file on the same phone at 15 cm from your eye gives you back some angular extent at the cost of needing to scan around. Pick the geometry that matches what you're looking for.

Use Reference Mode for tonal evaluation if you're on a supported iPad. Your color and tonal calls will be more predictable. Brightness drops, which can feel like the image lost punch, but that's the calibrated reference appearance, not a problem with the file.

Don't cull final decisions on a phone. Phone screens work for rejecting obvious failures and triaging volume, where you only need to recognize broad properties. Final selections, where you're discriminating between two strong candidates on subtle differences, need angular room. A laptop screen is the practical minimum.

Prints still win for a reason. A 20x30-inch print at a reading distance of 50 cm covers a much larger fraction of your visual field than any practical screen. The CSF physics that explains the iPad versus iPhone observation explains why a print at proper viewing distance feels different from any display. The display you carry around is always making a compromise that the print doesn't have to.

Why medium format needs angular room to land

Photography has always been about deciding what your image is. Hasselblad's rendering decisions, applied through HNCS color science², the tonal curves in Phocus, and the way the X2D II sensor handles transitions in the deep end of its dynamic range, live in the file as a set of small, careful, structural choices. The renderer made them with the assumption that someone would eventually view the image at a size where those choices would register.

Shrink the result down to a phone screen at arm's length and you're filtering it through a perceptual aperture that throws away most of what the rendering is doing. The image still works. It still tells you whether the composition lands. But the part you paid for, the subtle tonal work and the medium-format sense of dimensional separation, doesn't get into your visual cortex at that scale.

The iPad gives the file an angular size where the rendering can be read by the only instrument that counts: the visual system of the person doing the looking.

References

1. Campbell, F. W., & Robson, J. G. (1968). Application of Fourier analysis to the visibility of gratings. The Journal of Physiology, 197(3), 551-566.
2. Michels, K. (2026). What Is HNCS HDR? Hasselblad's End-to-End HDR Explained. Tech Behind the Frame.

X2D II files look sharper on iPad than iPhone, despite the iPhone's higher PPI. Angular extent and contrast sensitivity drive the gap.

If you shoot Hasselblad and use Phocus 4.1.2 on Mac to export JPEGs, the file you get is not the size you asked for. Eve...
05/20/2026

If you shoot Hasselblad and use Phocus 4.1.2 on Mac to export JPEGs, the file you get is not the size you asked for. Every JPEG export from 4.1.2 comes out at 7000×5250 pixels regardless of whether your output preset specifies Full Size, Restrict Pixels 2000, Restrict Pixels 5000, or anything else.

This is the second confirmed regression in Phocus 4.1.2's core functionality. The first, a critical color preview bug that makes every Hasselblad raw render flat and desaturated by default, is honestly the worse of the two. The export bug here gives you a wrong-sized JPEG, which is recoverable: re-export from 4.1.1 and you have the right file. The color bug means every editing decision you have made in 4.1.2 was made against a wrong reference image. Between the broken preview pipeline and the broken JPEG export pipeline, 4.1.2 is not a usable version of Phocus for any photographer who cares about color accuracy or output dimensions.

Two Hasselblad shooters from different communities reached out to me about this export bug in the last five days. Both were on 4.1.2. Both were hitting the same silent downsize. The Dimensions field in your Output Preset is not being honored.

A note on support: This post represents my personal exploration and testing, not official technical support or guidance from Hasselblad. If you need assistance with your Hasselblad equipment, please contact Hasselblad directly: [email protected] for global support, [email protected] for the Americas, or visit hasselblad.com/support for regional options.

Key finding: Phocus 4.1.2 silently caps every JPEG export at 7000×5250 regardless of preset settings. This is the second confirmed 4.1.2 regression in core functionality, alongside the critical color preview bug that breaks default raw rendering. 4.1.2 is not a usable version of Phocus. Downgrade to 4.1.1.

How can you tell if you're affected?

The fastest check: open any X2D II 100C raw file in Phocus 4.1.2, set your output preset Dimensions to "Full Size," and export a JPEG. The native sensor resolution on the X2D II 100C is 11656×8742 pixels. If your exported JPEG comes out at 7000×5250 instead of 11656×8742, you're hit.

The same check works for Restrict Pixels. Configure a preset for Restrict Pixels 2000×2000 (which should produce a 2000×1500 JPEG on a 4:3 source) or 5000×5000 (which should produce 5000×3750), export, and check the file's actual dimensions. Every output comes out at 7000×5250 regardless of which Restrict value you set.

I tested on an X2D II 100C, where native 11656×8742 raw files come out at 7000×5250 JPEGs. The bug lives in Phocus's JPEG export pipeline rather than in any camera-specific code, so the other 100MP bodies that share these source dimensions (X2D 100C, H6D-100c) would likely show the same 7000×5250 output. 50MP bodies (X1D II 50C, H6D-50c) would presumably hit the same code path with a different fixed output dimension. I have not tested any of those bodies directly.

I only tested JPEG exports. TIFF, DNG, and HEIF behavior is untested.

Have you seen the guide? I've published Essential Phocus 4.x for Mac - 83 topics across 8 sections and 220 pages covering everything from HNCS color science to HDR workflows. It's the reference manual Hasselblad hasn't updated since 3.8. Pay-what-you-want starting at $24.

Get it here

What is actually happening?

Other preset settings still work correctly in 4.1.2. JPEG quality, color profile (Adobe RGB versus sRGB), chroma subsampling, all reflect the active preset. Only the Dimensions code path is broken. The scale factor is uniform across every test: 0.6005 in each direction, regardless of which Dimensions option you select.

Phocus also writes no log entries for the export operation itself. The Phocus.log captures preview generation for the source raw file but is silent during the actual JPEG export, so there is no diagnostic trail to follow.

The same JPEG export operations work correctly under Phocus 4.1.1 on the same hardware. Full Size produces native 11656×8742, and Restrict Pixels caps are honored. This is a regression introduced specifically in the 4.1.1 to 4.1.2 update.

The only confirmed fix: downgrade to 4.1.1

There is no in-app workaround. Restarting Phocus, rebuilding presets, switching to the built-in canned JPEG preset, none of those change the output. The only thing that produces correct JPEG export sizes is dropping back to Phocus 4.1.1.

Between this bug and the Phocus 4.1.2 critical color preview regression that affects every Hasselblad raw file's default rendering, 4.1.2 has shipped with two material regressions in core functionality at the same time. The export bug is the milder of the two. A wrong-sized JPEG is recoverable. The color preview bug means every editing decision you have made against the 4.1.2 default preview has been made against a wrong reference image. Both bugs share a fix: downgrade. Hasselblad publishes the 4.1.1 installer on their support site.

Status with Hasselblad

I filed a detailed bug report with Hasselblad support on 2026-05-20. The report includes full reproduction steps and a 4.1.1 versus 4.1.2 control test. The evidence package contains the source raw file, four mis-sized JPEG exports demonstrating the bug across different preset configurations, four screenshots of the Output Preset dialog at each configuration, a screen recording of the full export sequence, and the Phocus.log. Hasselblad's support system acknowledged the ticket within seconds. The customer-facing case number arrives with the first human triage response, typically within one business day.

This is now the second 4.1.2 regression I've reported. The first, the color preview bug, has already been reproduced by Hasselblad engineering with a fix committed for a future release. I will update this post when a fixed version of Phocus ships.

What you should do now

If you shoot Hasselblad and edit in Phocus 4.1.2 on Mac:

1. Downgrade to Phocus 4.1.1. Between the JPEG export size bug and the critical color preview regression, 4.1.2 is not a usable version of Phocus for any photographer who cares about color accuracy or output dimensions. Hasselblad's support site has the 4.1.1 installer.
2. Check the dimensions of any JPEGs you've already exported from 4.1.2 before delivering them to a client or uploading them anywhere with strict size limits.
3. If you have done any color or tone work in 4.1.2 against the default preview, treat it as suspect. The preview was not showing you your actual file's colors. See the color preview regression post for the impact.
4. Consider filing your own ticket with Hasselblad support. Reference "Phocus 4.1.2 JPEG export ignores configured Dimensions" so they can match it to the existing report.

For a running list of other Phocus 4.x bugs and their current status, see Phocus 4.x for Mac: Known Issues and Bug Reports.

References

1. Phocus 4.1.2 Has a Critical Color Preview Regression
2. Phocus 4.x for Mac: Known Issues and Bug Reports
3. Hasselblad Phocus download page
4. Hasselblad customer support

[BUY ME A COFFEE - replace with HTML card]

[SIGNUP BLOCK - add manually]

Phocus 4.1.2 on Mac caps every JPEG export at 7000×5250 regardless of preset settings. Only confirmed fix is to downgrade to 4.1.1.

05/19/2026

Short answer: no. If you are shooting just RAW, the X2D II captures the full dynamic range in every frame, and Phocus can render that data as HDR after the fact. You only need RAW+JPG or RAW+HEIF if you want the camera itself to embed an HDR JPEG or HEIF at capture time.

That said, the camera's HDR menu makes it sound like the answer is yes. The in-camera HDR toggle is the source of the confusion. Most X2D II shooters can ignore it without giving anything up.

💡A note on support: This post represents my personal exploration and testing, not official technical support or guidance from Hasselblad. If you need assistance with your Hasselblad equipment, please contact Hasselblad directly: [email protected] for global support, [email protected] for the Americas, or visit hasselblad.com/support for regional options.

Key finding: The X2D II HDR toggle only controls whether the camera writes an HDR JPEG or HEIF at capture. The RAW captures the full 15.3 stops of dynamic range regardless of toggle state. Any 3FR or FFF can be rendered as HDR in Phocus or Phocus Mobile 2, no JPEG sidecar required.

What does the in-camera HDR toggle actually do?

The HDR toggle on the X2D II is an output-format setting. When it is on, two things happen at capture: the camera locks metering to Smart Metering and pulls exposure back to protect highlights from clipping, and it renders an HDR-encoded JPEG or HEIF alongside (or instead of) the RAW. That HDR JPEG carries the SDR base image plus a gain map that HDR-capable displays read to extend the luminance range. The HEIF version does the same thing with PQ encoding.

What the toggle does not do is change what the sensor records. The X2D II captures the same data either way: a single RAW frame with roughly 15.3 stops of dynamic range, ready for whatever processing decision you want to make later.

HNCS HDR is a single-exposure technique. The whole pipeline is about encoding the dynamic range that the sensor already captured, not about combining multiple frames the way traditional bracketed HDR works on other camera systems. I covered the mechanics in What Is HNCS HDR and Why Should RAW Shooters Care?. The RAW file is complete on its own.

What about RAW files when the toggle is off or grayed out?

Phocus renders them as HDR anyway. The camera-side toggle has nothing to do with whether Phocus can apply HDR to a RAW file. The image format on the camera (RAW only, RAW+JPG, JPG only) controls what files the camera writes to the card. Phocus only needs the RAW. For the full picture of in-camera HDR limitations across every shooting scenario, see Part 4 of the HDR Demystified series, which is the closest companion to this post.

Open any X2D II 3FR in Phocus 4.x, check the HDR checkbox in the Adjustments panel, and the histogram expands to show the extended HDR luminance range. The same is true in Phocus Mobile 2: tap the HDR toggle on a RAW you imported, and the app renders it with HDR.

HDR off. The histogram and the file render inside the standard SDR luminance range, even though the underlying RAW carries more than that.

HDR on, same RAW. The histogram opens up to show the extended luminance range the file always contained. The camera-side toggle has no input over any of this.

The toggle on the camera grays out in a number of shooting modes. The grayed-out toggle is sometimes read as "HDR is unavailable for this shot." It is not. What is unavailable is the camera generating an HDR JPEG or HEIF at the moment of capture. The RAW still records the full dynamic range, and Phocus can render it with HDR at any point afterward.

Shooting Mode
In-camera HDR toggle
RAW HDR in Phocus

Single shot, Auto / Av / Tv / P
Available
Yes

Manual exposure (M)
Grayed out
Yes

Continuous drive
Grayed out
Yes

Exposure bracketing
Grayed out
Yes

Focus bracketing
Grayed out
Yes

Nikon-compatible flash attached
Grayed out
Yes

RAW-only image format
Grayed out
Yes

The right-hand column is the load-bearing one. Whatever the camera-side toggle is doing, Phocus can render the RAW with HDR.

Why is there a misconception that RAW+JPG is mandatory?

The camera's HDR menu only shows the toggle when an image format with a JPEG or HEIF component is selected. Switch to RAW only and the option disappears. The natural reading is "HDR requires JPEG or HEIF," and most people stop there. That reading is true for in-camera HDR output, but the inference that follows ("therefore I must shoot RAW+JPG to have HDR") is not.

Sony, Canon, and Fuji all have in-camera HDR modes that genuinely require multiple exposures and produce a merged output. Anyone bringing that mental model to the X2D II reasonably assumes "HDR mode" means the same thing, and that of course you need an output format that can carry the merged image. HNCS HDR is structurally different. It is single-exposure, and the output encoding is about luminance range, not about combining frames. For the longer treatment of how Hasselblad's render-time pipeline works, see What You Keep (and Lose) When You Skip Phocus.

Have you seen the guide? I've published Essential Phocus 4.x for Mac - 83 topics across 8 sections and 220 pages covering everything from HNCS color science to HDR workflows. It's the reference manual Hasselblad hasn't updated since 3.8. Pay-what-you-want starting at $24.

Get it here

When do you actually want RAW+JPG capture?

There are real reasons to enable RAW+JPG with HDR on the camera. Three come up regularly.

You want HDR-rendered output immediately, in the field. With the toggle on and RAW+JPG enabled, the camera produces an HDR JPEG (or HEIF) right alongside the RAW. Phocus Mobile 2 or any device that reads Ultra HDR JPEG can display that file with HDR luminance on a capable screen. Useful if you are reviewing or sharing on-location.

You want the metering bias the HDR mode forces. When HDR output is on, the camera locks to Smart Metering and pulls exposure back by up to about 2.5 stops to keep highlights clean. The X2D II sensor has enough dynamic range that shadow recovery is essentially free in post, but clipped highlights are gone for good. An automatic highlight-protective bias produces a safer RAW than neutral metering would in scenes with bright sky, specular highlights, or strong window light. If you are not someone who manages your own exposure for highlights, this is a useful safety net. Experienced shooters in Manual mode metering for highlights themselves get the same RAW outcome without needing the toggle.

You want the camera's 1400-nit display to show you the HDR rendering for review. With HDR off or grayed out, the LCD shows the SDR-rendered embedded preview from the RAW file. With HDR on, the JPEG sidecar carries the HDR luminance and the screen will display it. This is a preview behavior only. It does not affect what Phocus can do with the RAW later.

None of these mean RAW+JPG is mandatory. They are reasons you might choose it.

The cleaner workflow for most X2D II shooters

If your finishing pipeline goes through Phocus on a Mac, shoot RAW only and ignore the camera-side HDR toggle entirely. Bring the 3FR (or FFF) into Phocus, enable HDR in the Adjustments panel when you want it, and export as Ultra HDR JPEG for delivery or as a 16-bit TIFF with BT.2100 PQ encoding when you want to take the image into a third-party HDR-aware editor like Photoshop or Affinity Photo. The complete step-by-step workflow, including the hidden histogram Levels tool, is in Part 3 of the HDR Demystified series.

If your finishing pipeline is iPad-first, Phocus Mobile 2 works the same way. Import the RAW, toggle HDR, export Ultra HDR JPEG. Same result; the camera-side toggle isn't part of the workflow.

The one workflow where the camera-side toggle is the cleanest tool is on-location delivery: shooting tethered to a phone or iPad and handing off HDR JPEGs right out of the camera. Even then, RAW+JPG (not JPG only) is the right choice because you keep the RAW for any future re-rendering.

Common mistakes

Switching the camera to RAW+JPG just to make the HDR toggle available. If your finishing pipeline is in Phocus, you are doubling your storage and adding files you will probably discard. Shoot RAW only unless you have a specific reason for the JPEG sidecar. The three real ones are in the section above.

Reading the grayed-out HDR toggle as "this shot cannot be HDR." It cannot be HDR in-camera. It can still be HDR in Phocus.

Thinking HDR means multi-frame. HNCS HDR is single-exposure. One RAW carries the data; Phocus reads it.

Worrying that Manual exposure mode disables HDR. Manual mode disables the in-camera HDR JPEG generation because the camera can't apply its intelligent metering bias when you're setting exposure yourself. The RAW is fine. If you're protecting your own highlights, your Phocus HDR render will be no worse than what HDR-mode-on Auto would have produced.

Related: the HDR Demystified series

If you want the full picture rather than just the RAW+JPG question this post answers, the longer five-part series covers the wider territory:

* Part 1: What Is HNCS HDR and Why Should RAW Shooters Care?
* Part 2: Output Formats and the Trilemma Every Shooter Faces
* Part 3: The Complete Phocus 4.x Workflow
* Part 4: Displays, In-Camera Limitations, and Platform Support (the closest companion to this post)
* Part 5: Print, Archival, and Practical Recommendations

The complete topic-by-topic Phocus 4.x reference, including the full mechanism behind every grayed-out state in the table above, is in the paid Essential Phocus 4.x for Mac guide.

References

1. What You Keep (and Lose) When You Skip Phocus: Why HNCS is render-time, not RAW-baked, and what that means for third-party editors.
2. Hasselblad X2D II 100C User Manual v1.0, Section 2.7 "HDR Function": the manufacturer's own description of when the in-camera HDR toggle is available.

Address

San Acacia, NM

Website

https://payhip.com/b/6pqAt, https://www.lulu.com/shop/konrad-michels/essential-phocus-4x-f

Alerts

Be the first to know and let us send you an email when Tonal Photo posts news and promotions. Your email address will not be used for any other purpose, and you can unsubscribe at any time.

Contact The Business

Send a message to Tonal Photo:

Share

Category