I think I solved it. I set the colorspace on the underlying CAMetalLayer of the MTKView (iOS/Catalyst does not let you set this directly on MTKView): Add the following code at the end of the init method in MTKImageView.swift: if let taggedColorSpace = image.colorSpace, let metalLayer = self.layer as? CAMetalLayer { metalLayer.colorspace = taggedColorSpace } All three images now properly display for me:

Update: If the colorspace supports wideGamut, then I set the colorspace in the CAMetalLayer to extendedSRGB, instead of the tagged colorspace: if let taggedColorSpace = image.colorSpace, let metalLayer = self.layer as? CAMetalLayer { metalLayer.colorspace = isWideGamutRGB ? CGColorSpace(name: CGColorSpace.extendedSRGB) : taggedColorSpace }

This seems to be related to layout constraints on the map view in the storyboard. If I remove the layout constraints on the map view, then I get a different error: -[MKMapView _recursiveClearViewWillDidDisappearOnMoveToWindow]: unrecognized selector sent to instance 0x12b92dc00

I have the same issue. Any chance you could post some sample working code, either here or in a DropBox folder? Thanks!

Regarding the "SupportingHDRImagesInYourApp" sample app from Apple: If I load a RAW image file, then it initially looks correct in the UIImageView class, but it doesn't seem to have enough dynamic range in Edit Mode when the adjustment sliders are displayed (colors seems slightly darker).

Do either of you have sample code showing how to properly expand the Laplacian Pyramid with the x2 logic? Thanks, Rick