I've been looking to get a second 24 inch LCD monitor to connect up to my main Mac system as a secondary screen in a dual monitor setup. While my HP LP2475W will remain the my primary screen, but I wanted to be able to get reference material (manuals, documents that I responding to by e-mail, etc) up on a separate screen. It would also allow using Lightroom in dual screen mode, although I've never really felt the need.

It so happens that I found a very good deal on a Samsung BX2450 from an on-line store, with free next-day delivery. The Samsung BX2450 is a new-generation "green" display with an LED backlight. A quick internet search revealed that the BX2450 got high marks from almost all owners. The only negatives I found was fiddly touch sensitive buttons, and that there is a known incompatibility between the BX25450 and the ATI (now AMD) graphics driver on Windows if you connect the BX2450 up with a HDMI to HDMI cable (the BX2450 doesn't have any DVI inputs, just HDMI). Apparent if you use a DVI to HDMI cable, there isn't a problem. But, for my purposes that was fine - mostly I work on a Mac anyway, and if I do need to connect to one of my Windows boxes, using a DVI cable is fine. So I went ahead and bought the BX2450.

The rest of this post is my experiences in using and calibrating the BX2475. It's written very much from an imaging and photographic perspective. Those interested in gaming performance - response times and the like - should look elsewhere.

First impressions and construction


First impressions were positive - the BX2475 looks good, and has a stand that, while it looks a bit fragile, actually seems to support the display as well as as my (much) more expensive HP unit. The BX2450 also appears to to live up to its green credentials - the power supply is external, and about the size of an iPhone. In fact, the whole display is light in weight - it was easy to carry around, and get in position on the desk.

Initial power up was fine; the BX2450 immediately showed as a second screen under OS X, with the correct resolution, etc.

The bad news: you can't adjust the height of the display. At all. There however is a tilt function.

The second piece of bad news is that all the software is Windows only. Not a single piece of Mac software - not even a display profile.

The "just be aware of" news - the BX2450 appears to essentially be an HDMI TV, rather than a computer monitor, even if you set it to "PC" mode. Now that doesn't make a lot of difference but be aware that there are some funnies: you will see the resolution listed as 1080p, rather than 1920x1080, and the display seems to identify itself as a HDMI TV rather than anything else. So you will see an "Overscan" checkbox in the Mac Display preferences which you won't for a normal monitor. Don't try to switch that off, btw - the display will no longer show a picture(!) This identification issue probably also explains the Windows HDMI issues that others have found.


Calibrating the display

Although the default setting on the display were ok, certainly better than some other displays I've seen, the first thing I looked at was how to calibrate the display. Now I didn't buy the BX2450 to display images; that's what the wide gamut LP2475 is there for. But as a I spend a lot of time looking at images, and specifically looking at the color rendition of images, bad color bothers me. I was also interested in how accurate a display I could get from a low-cost LCD display with LED backlighting. So I got out my trusty X-Rite Eye-One calibration device, and set to work. Here's the quick summary of my experiences:

  • First thing that I had forgotten was the X-Rite's Eye-One Match 3 software doesn't actually support calibrating to two monitors. Now you'll see a lot a stuff written on the internet that this is because "you can't have two calibrated displays on one display board because there's only one LUT in hardware", etc. Nonsense. Any modern OS will happily let you run two different calibrated displays from one video board. This is just a limitation of the Match 3 software. Solution: temporarily disconnect the primary monitor, and use the secondary as the primary while you calibrate. OS X will automatically keep track of which profile applies to which monitor, btw.
  • Second thing that I found out was that the touch sensitive buttons on the BX2450 really are as fiddly as claimed.
  • Third thing I found is that the BX2450 (or maybe the combination of the BX2450 and the Eye-One puck) doesn't like to be calibrated to a D55 (5500K) white point. While you can calibrate to that, the resulting display is truly horrible; the brighter parts of the image are ok, but the darker parts get a massive red color cast - totally unusable. So I ended up calibrating to a D65 white point. 
  • Fourth thing I found out was that setting any of the Red, Green or Blue controls to more than 50 is not a good idea; when you generate a profile you get nasty discontinuities in the gamma curves, indicating that the display becomes non-linear. The process I followed was firstly to set the BX2450 to what Samsung call a "Cool" color tone, which was close to D65. Then I manually adjusted to D65 as measured by the Eye-One using the RGB sliders, taking care that no color control went above 50. For reference, the settings I ended up with were Red:20 Green:20 Blue:50 
  • As with most displays, the default brightness was way to high; I set it to 34 on the slider, which corresponds to a 110 cd/m² setting, my preferred LCD value.
The end result of this was pretty good. It's almost impossible to give any idea of color rendition on the web, but visually comparing the BX2450 to my LP2475, the BX2450 stood up pretty well for images with relatively small color gamuts. Specifically, for sRGB images, which are what almost all JPEG files use for a color space, the calibrated BX2450 looked nearly as good as the LP2475. Interestingly, to my eyes, the difference was more a slight lack of contrast in the shadows, than any major difference in color rendition.

The BX2450's gamut

The problem for the BX2450 of course, and the reason why the LP2475 costs several times more, is gamut - how broad a spectrum of colors can be displayed. A quick look at some raw images rather than JPEGs from my Nikon and Sony cameras showed a very different story; the LP2475 was able to display better reds and greens.

Here are the gamuts of the LP2475, the Samsung BX2475, and the sRGB gamut for reference. 


Bottom line - the BX2450 doesn't come anywhere near the gamut of the LP2475, especially as regards greens, but also in reds. Compared to the sRGB gamut, the BX2450 is actually pretty close, but is just a bit less capable on both the greens and reds. Which is consistent with what I found looking at actual images - sRGB images are ok, raw images that have wide color gamuts, not so ok.

Conclusion

The bottom line is the following: if your imaging needs are limited to looking at JPEG images, or web surfing, the BX2450 will serve you fine, and if you have a hardware calibration device, you can get quite acceptable color if you stick to a D65 white point. Also, the BX2450 will be a good choice for those that create websites, or artwork that will primarily be seen on the web - in that case the similarity of the BX2450's gamut to sRGB is actually an advantage.

In the role that I'm using the BX2450, and given what I paid for it, I've very happy - it does exactly what I bought it for, and does better than I had anticipated in terms of color accuracy.

However, if you're a serious photographer that deals with raw images, the BX2450 is not for you, at least as a primary monitor. Firstly, the color gamut isn't wide enough. But the real show stopper is the issues I had trying to calibrate the BX2450 to a non-D65 white point. That may not be the fault of the BX2450 - it may be that my Eye-One calibration device isn't up to dealing with LED backlights. But for whatever reason, if you're serious out photography, you need a monitor that will calibrate reliably with current calibration devices.
4

View comments

  1. Good news in a difficult year - all the macOS apps that I support - AccuRaw EXR, AccuRaw Monochrome, pcdMagic, CornerFix, dcpTool (both the GUI and command line version), DNG cleaner and pcdtojpeg - now are all available with native Apple Silicon versions for blazing fast performance on Apple's new "M1" processor. Download are in all the usual places.

    Enjoy.

    0

    Add a comment

  2. There's a whole slew of new camera support, including for Canon's new CR3 format.

    Updates of AccuRaw EXR, AccuRaw Monochrome, PhotoRaw are now available on the Apple App Store. These updates add support for these new cameras: Canon EOS-1D X Mark III, Canon EOS 90D, Canon EOS M50, Canon EOS M6 Mark II, Canon EOS Rebel SL3 (EOS 250D), Canon EOS R, Canon EOS RP, Canon EOS R5, Canon EOS R6, Canon PowerShot G5 X Mark II, Fujifilm XF10, Fujifilm GFX 50R, Fujifilm GFX 100, Fujifilm X-100V, Fujifilm X-A7, Fujifilm X-Pro3, Fujifilm X-T30, Fujifilm X-T4, Fujifilm X-T200, Leica Q2, Leica SL2, Nikon Coolpix P950, Nikon Coolpix P1000, Nikon D780, Nikon Z 6, Nikon Z 7, Nikon Z50, Panasonic DC-G90, Panasonic DC-G100, Panasonic DC-G110, Panasonic Lumix DC-G95, Panasonic DC-LX100 M2, Panasonic DC-S1, Panasonic DC-S1R, Panasonic DC-S5, Panasonic Lumix DC-FZ1000 II, Olympus OM-D E-M1X, Olympus OM-D E-M1 Mark III, Olympus E-PL10, Olympus OM-D E-M5, Olympus OM-D E-M10 Mark IV, Olympus TG-6, Pentax K1 II, Ricoh GR III, Sony DSC-RX100 VII, Sony A7 III (ILCE-7M3), Sony A7C (ILCE-7C), Sony A7R Mark IV (ILCE-7RM4), Sony A7S III (ILCE-7SM3), Sony a6100 (ILCE-6100), Sony a6400 (ILCE-6400), Sony a6600 (ILCE-6600),Sony HX99. 

    0

    Add a comment

  3. pcdMagic for Windows - the only currently available app that can convert Kodak Photo CD images with correct color and at full resolution - is now available on the Microsoft Windows Store.

    This great news for users:

    • The Windows Store version has a free trial mode that allows the app to be tested without any commitment.
    • The Windows store handles all updates automatically.
    • There's no need to keep track of license codes.
    The Windows store only supports the latest versions of Windows 10. However, for users of earlier versions of Windows, you can still purchase pcdMagic from the FastSpring webstore.
    2

    View comments

  4. As usual when new Leica cameras come out, I took a quick look inside a DNG from one of Leica's new Leica CL  cameras:

    1. The camera name shows as "LEICA CL"
    2. The image data is 14-bit. There is no compression used in the DNG I looked at. 
    3. The DNG version is 1.4, with a "backward version" of 1.3. There is a reason for this - DNG 1.3 allows for opcodes, which Leica use for lens correction.
    4. In the DNG I looked at, which was shot with a "Summicron TL 1:2 23 ASPH." lens, lens correction is done by a single "WarpRectilinear" operation in the DNG. 
    5. In addition to the lens correction op code, there is also a "FixBadPixelsConstant" opcode, whose function is exactly as the name states. This is the same as in the Leica Q, SL, etc.
    6. Unusually, the DNGs all contain 2 different JPEG preview images in addition to the main raw image, one of 1620x1080, and finally a full sized preview of 6000x4000. Having the full sized preview is particularly odd, as it takes up a lot of space. In the approximately 45 MB files I've seen, the full size preview typically takes up about 1.8 MB. 
    So in summary, the DNGs appear to be a bit of a hybrid of the "SL", "Q", etc style of DNG, with a single lens correction opcode, and a bad pixels correction opcode, and of the "M10" style of DNG, with a full sized preview. As I noted in my analysis of the M10 DNG, the full size preview is probably there to support viewing on mobile devices that often don't have raw decoding capability built in. 

    Finally, it's notable that the DNGs don't contain the bizarre Lightroom XMP metadata that the M10 DNGs have embedded in them. 
    2

    View comments

  5. So finally, after many years of searching, I have an answer to the question that torments all who go down the digital color rabbit hole.

    This is from XKCD, brought to my attention via an article on the Digital Transitions website about the Phase One IQ3 100mp Trichromatic.



    0

    Add a comment

  6. Back in January, when the new Leica M10 was introduced, there were claims that the improvement in dynamic range from the Leica M240 to the M10 was of the order of 1.5 to 2 stops.  At the time, I wrote that just by eyeballing the published images, I believed the improvement to be "closer to 0.5 stops than 1.5-2".

    Much to my surprise, given what I had thought to be just a basic explanation of why dynamic range is a tricky concept, the post generated a lot of push-back. And I mean a LOT.

    Well, now there is actually an independent third-party measurement available, from photonstophotos.net:


    And....(drum roll)....the improvement in DR between the M240 and the M10 is 0.55 stops. As I predicted back in January.

    You can a find whole lot more information, including a useful interactive graphing tool that allows you to compare cameras, on the photonstophotos.net site.
    0

    Add a comment

  7. dcpTool has been available for quite a while as a command line application for Windows and the Mac. But now it available in the form of an easy to use Mac app, with powerful batch processing capabilities. dcpTool for the Mac is available from the App Store.

    dcpTool allows you to:

    1. Decompile DNG Camera Profile (DCP) files in XML. The XML can then be read and edited with a simple text editor.
    2. Recompile edited XML into DCP files
    3. Remove "Hue twists" from camera profiles. 
    For more information on hue twists, see these posts:
    11

    View comments

  8. Many cameras embed lens corrections into raw the raw files that they produce. Generally, that's a good thing - straight lines stay straight, etc. For an example of lens corrections in practice, take a look at this post about the Leica SL.

    But, as the saying goes, "there is no free lunch". Lens corrections also have some downsides:

    • Lens corrections result in a small reduction in sharpness. Sean Reid, at Reid Reviews has done extensive testing on this as part of his various lens reviews, and his conclusions are clear - there is a measurable loss in sharpness.
    • Lens corrections result in some reduction in image size - the corrections inevitably result in the edges of the image curving, and the curved parts need to be trimmed off to get back to a straight edge.
    So sometimes, it's useful to be able to get an uncorrected image. Now there are some raw developer apps that allow you get to uncorrected images (AccuRaw EXR is one of them), but most mainstream apps such as Lightroom and Photoshop don't allow correction to be disabled.

    Fortunately though, there is a "simple trick" that will allow you to disable lens corrections for nearly any camera that produces raw images. What you need to do is a simple two step process:
    1. Firstly, convert the raw image to a DNG image, using Adobe's DNG converter.
    2. Then use DNG Cleaner (macOS only) to remove any opcodes.
    The resulting DNG will not have any lens correction, and you can load it into Lightroom, Photoshop, or any other app that supports DNGs.

    Why does this work? This works because whenever DNG Converter converts an image that needs lens correction, it embeds the required correction as an "opcode" into the DNG image. Lens correction opcodes as usually things like "WarpRectilinear". DNG Cleaner knows where to find these opcodes, and simply removes them, as long as you have the "Remove opcodes" checkbox selected:


    Note that in order for this to work, you need DNG converter to be using it's default settings. Specifically, Compatibility should be set to the most recent version of Camera Raw. You should definitely not be using Custom Settings with the "Linear" checkbox selected. "Linear", otherwise known as LinearRaw, bakes any corrections into the actual data in the DNG, making it impossible to remove.

    There's more information on the DNG Cleaner website.
    0

    Add a comment

  9. Those of you that have read the Leica M10 raw file analysis post will know that M10 DNGs have more baggage in them that is typically the case for a Leica DNG. I've put together a little app to clean them up, called DNG Cleaner (Mac only for the moment). For M10 DNGs this will remove:

    1. The full size image preview - that will save about 3MB
    2. The various Lightroom/Photoshop adjustments embedded in the XMP portion of the DNG - ISO dependent noise reduction settings, lens profiles, etc

    DNG cleaner will also optionally remove opcodes, and apply lossless compression. This isn't relevant to the M10, but in many other Leica cameras, e.g., the Q, the SL, etc, opcodes are used for lens correction. For an example of the SL's with and without lens correction, see my post on the subject. DNG Cleaner is what Sean Reid used to remove opcodes for his SL 50 review, which some of you will have seen.

    As ever, back up your files before using any app that is designed to modify them.

    For more information on DNG Cleaner, see the website.
    0

    Add a comment

  10. AccuRaw users might have gotten a bit of a surprise recently - AccuRaw has turned into AccuRaw EXR, and is now at version 3.

    The reason for the name change is that the focus of the AccuRaw product has changed a bit, based on what users were actually doing with it. AccuRaw has always been focussed on having highly linear color response, with no "hue twists" or other surprises in the color rendering. As it turns out, that is a very useful feature to have if you're composting stills into video - it reduces the amount of work required for color matching.

    In the world of video, especially in the professional cinematography world, the "gold standard" is to use a format such as EXR, which is a floating point format. That allows huge flexibility in the way that post processing is done. So the new version of AccuRaw, now named AccuRaw EXR, supports EXR output.

    However, it's more than just a name change. In order to really support EXR output, AccuRaw has seen major changes internally - it now has a fully floating point, non-clipping workflow. For more on why that is important, see this post.

    1

    View comments

Popular Posts
Blog Archive
About Me
About Me
My Photo
Author of AccuRaw, PhotoRaw, CornerFix, pcdMagic, pcdtojpeg, dcpTool, WinDat Opener and occasional photographer....
Loading