Feature Requests


You may post your feature requests here

Open next raw-file in folder with keyboard shortcut

Im just trying to follow the examples in "Calibrating the exposure meter" and "Determing pixel charge capacity..". A keyboard shortcut for "open ext raw file in folder" would ease the handling.

Right. Can you please use

Right. Can you please use drag&drop meanwhile?

Best regards,
Iliah Borg

In the samples window when

In the samples window when the Append button is pressed there is no confirmation that the sample data line was successfully appended. Multiple presses add multiple lines. Maybe a confirmation when the line is appended the first time? Thanks.

Thank you. Maybe a check that

Thank you. Maybe a check that the sample is already added, or a warning.

Best regards,
Iliah Borg

When a new sample is added,

When a new sample is added, an Asterisk (*) is added to the text of the Button "Save Samples"/"Append File". This Asterisk is cleared after a Save or Append. Maybe append only new samples to the file - now Append File appends all Samples to the file.

Can you add the Camera Model, the ISO, the shutter speed and the aperture to the saved File when saved in csv-Format?

Kind regards

Two requests :)

Two requests :)

A keyboard short-cut to convert selection to sample.
Ability to load samples locations from a previous saved *.csv.

Thank you,

Shortcut will be added to

Shortcut will be added to next minor release.

Save/Load sample locations requires sligtly more work, added to TODO list, thanks for suggestion.

usage for astronomical photography.

Having had a quick play with your program I can see that this would be a fantastic program for astronomical use,
The ability to see each of the RAW RGBG data is pretty useful.
Would it be possible to add to the program the following, Firstly a save as menu, giving options to save one of the RGBG images as any file format. raw, jpg, bmp, tiff, fit, ect.
Also a tick box so that each of the separate RGBG images can be saved at the same time,
Also if possible a batch option to do all of the above.
Normally we have between 10 & 500 images to process for one object.
To be able to strip every single raw image out in one hit and then process them after in the astronomical software programs would be

Excellent program.


For batch save you may use

For batch save you may use 'samples' (really, very useful programs) from LibRaw (Download page: http://www.libraw.org/download )

Precompiled versions for both Windows and Mac are available

The 4channels sample  converts RAW to 4 TIFF (or PGM) files, each for each color channel.

The unprocessed_raw sample saves 4 RAW channels into one TIFF file.

Source code for Library and samples is available, so you may adjust these simple utilities according to your needs.

Image File As-Shot Color Coefficient Data Display

This an excellent tool overall. However, it lacks the listing of the "raw" image-file's "as-shot color coefficients" that RAWnalyze's display data provides to the user. Adding that specific data to the RawDigger displayed data would be a very helpful feature for users who would like to use RawDigger in the process of evaluating and/or calibrating UniWB configurations. Is this something that could be added to RawDigger ?

Using RawDigger 0.9.9 Beta (EN)

Yes, WB on Raw Data is

Yes, WB on Raw Data is planned, but not on top of TODO list.

Blinking Over Threshold Highlight Display - Under Threshold Data

When I see specular highlights appearing in the "raw" image-file's histogram display above some particular level, it occurs to me that it would be very helpful and extremely useful for the user to be to set a threshold-level (in the Histogram window, or in the Main window) where all individual photo-site data (as viewed individually, or as viewed in 2x2 format) above that threshold-level would blink on and off in the Main window display of the image - in a manner similar to that provided in some digital camera preview/review displays. Such a feature is one thing that I find myself wanting to more easily determine.

Also, if such a user-settable threshold-level (only when set by the user) constituted the Maximum reported level in the displayed image statistics, and the Average and Standard Deviation reflected image statistics (only) below that threshold-level, the user would have useful data relating to the image statistics existing in image areas where individual photo-site data does not exceed such a user-settable threshold-level.

Yes, Over (and, Under-)

Yes, Over (and, Under-)-exposure warning is in TODO.

It it not very easy to do it both flexible and useful, so.. just wait several weeks :)

Retain Main and Histogram Window Size Data

I have a 1920x1200 pixel monitor display. Each time that I re-open RawDigger, I have to re-adjust the screen size of the Main window and the Histogram window (particularly the the Histogram window screen size). I also re-adjust the Histogram window for Linear X-Axis, and Log Scale in the Y-Axis controls.

How about if the last (most recent) screen-size of these windows (as well as the settings in general) were to be retained by RawDigger when the program is re-opened after being closed ? This would provide a very welcome convenience to the user, and it the implementation of such an approach would be no more complicated if the user were to choose to subsequently alter those particular program settings.

Main window position is

Main window position is already saved if you enable it (Preferences - Save Main window position).

For Histogram window(s) and Samples - it will be done in next beta. Thanks for suggestion.

Thank you. Good to hear that

Thank you. Good to hear that the Histogram window size (as well as the position) will (also) be saved upon exit. Also saving the (Main as well as Histogram) window specific settings last used would (also) be a valuable time saver. As I previously indicated, implementing this (from the user's standpoint) would often be more useful and efficient - and would not be any more laborious (from the user's standpoint) in the case that the user desired to change the settings (from the most recently used settings to any newer settings desired when re-opening the program).

This is TRUE dimensions of

This is TRUE dimensions of Fuji sensor (in pixels). The Fuji (not all cameras, but many) image should be stretched in one dimension to get true image proportion.

Save the decoded RAW file as TIFF

It would be great if rawdigger can save the resulted file as TIFF, based on the chosen options. This will be a wonderful feature.

I find rawdigger has the most robust decoding support.


So, you want to dump current

So, you want to dump current 'visible screen' to full-resolution TIFF, right?

This feature is already planned, expect it in 0.9.16 or 0.9.17

RAW dump

Yes. I think few choices would be great:
1. current visible screen area
2. full RAW resolution
3. user defined area (X1 - X2, Y1 - Y2)


Export Tiff

I think the data export ("Export Tiff") dialog should have the option to export Bayer RAW data as a grayscale 16-bit image when using "Raw composite" in the "data" section to match the interesting grayscale visualization available when the "Display RAW Composite in grayscale" options is selected on the "Display Options" tab.

opening other file types

When using a program to edit raw files (Lightroom, ACR, etc.) it is often desirable to view a histogram of the resulting image. While one can save such edits in a .dng file, when such a file is opened in RawDigger the edits are not reflected in the displayed image or histogram. Thus it would be of some value to be able to open e.g. a .tiff file with RawDigger. Is this request at all reasonable?

White/Saturation level in data processing tab

I think it could be useful to have in the "data processing" tab of the "Preferences" window a "White/Saturation Level Settings" in which you can set the saturation level (that is, the raw value at which the corresponding channel value is set to its maximum value) at least to:
"Auto" (similar to how the autoscale works now in RawDigger)
"Manual"(you set a single raw value for all channels, e.g. 4095 for 12-bit raw files)
"Per Channel"(same as manual but you can set the raw value at which saturation is reached for each channel, this is useful in Nikon cameras such as D3100 where the highest/clipping value for each channel is not always 4095)

Furthermore, these settings should also influence the image displayed in RawDigger main window and the exported TIFF images.

This could be useful, as an example, for assessing the actual exposure of the raw images captured by the camera.

P.S.: thanks for the implementation of the export of grayscale TIFF images!

Thank you for your suggestion

Thank you for your suggestion.
Added to TODO list (but no exact schedule, sometimes in future versions)

White Balance eyedropper will

White Balance eyedropper will do ... What?

Do you want to apply WB to Raw data for histogram display, statictics, export and so on?

White Balance

Yes, an eyedropper to calculate white balance by click-and-dragging an area on the image would be useful.

For instance when exporting TIFFs (In the Raw Processing Box add a tick box called 'Apply White Balance')

You want to export RAW+WB

You want to export RAW+WB TIFFs, right? No color conversion, no debayer, just black subtraction, WB (and scaling if set).
Interesting feature, added to TODO.

Right, thanks.

Right, thanks.

Live Metadata Update


I use Profile Edition and work on camera calibration. I was wondering if live metadata updates would be an eventual feature. Not necessarily writing to the file, but just in the UI. The ability to change color matrices, RGB neutral, white/black level, view of the current CCT/Tint according to the Robertson method (Adobe & BMD use these methods) or Ohno method which is the most accurate as of late. This would just make profiling/calibrating much easier.

And side question. How does RawDigger do linear scaling after linearization with black and white level. Does it just do black subtraction (lin - black) or does it do full scaling (lin - black)/(white - black)?


Dear Sir:

Dear Sir:

RawDigger's RGB rendering is just for reference, it is not targeted to be color precise. Meanwhile, we'll probably add user-defined color matrix and more flexible WB to future updates.

Color/Tint calculations depends on color matrix and camera calibration data used for calculation. So values calculated will not be compatible with other programs (and/or camera display). Again, we'll probable add this to TODO list.


RawDigger subtracts black level (if enabled in settings) from values decoded from raw. Subtracted values are used for all calculations and numeric value display (no scaling)

For Raw Composite/Channel display (and TIFF export) values are scaled to full scale (again, if enabled in settings) and 2.2. gamma correction applied (again, if enabled).

Thank you for the quick reply

Thank you for the quick reply!

That's good to hear that you're considering adding these as features. I use RawDigger extensively for doing color work before sending the metadata to firmware or directly to DNGs, so these features will be a great help.

Would it be possible to add full scale values as an option for full scale calculations? This helps in determining the linear values (18% grey, 19.8% grey, 90% white) that apps use before applying scene linear adjustments (baseline exposure).

The problem is full-scale

The problem is full-scale range definition. In display/export case we use real data maximum from real frame. Some data formats reports data maximum, but some are not. So, for precise work this scaling does not looks reliable.

How about another option: display values in percent, relative to user-specified 100%  level?

Apologies for the late reply.

Apologies for the late reply. So would that mean the percentage would be based on scaled data from the user-entered white level? If so, that works perfect!

And thank you for being so responsive!

But you said relative to the

But you said relative to the user defined white level. I think I'm misunderstanding then. So you mean the percentage would just be 100 * value / user-defined white?

I see it as two separate

I see it as two separate things:

1) Display values as percentage of maximum value (and, also, in EV, relative to histogram EV0).

2) Ability to specify user own 100% level

I do not see any need to data scaling here.


Then that's less helpful

Then that's less helpful since it doesn't reflect how the scaling is done in the most used raw converters. Since most applications deal with scaled data, it helps us to know how the raw unscaled data relates to the scaled data, and it would be much quicker to view scaled data in RawDigger.

For those cameras that don't provide a white level, the programs will usually default to some integer representation of 1.f. Maybe have an option in 'Data Processing' for white level like you do for black level (auto, manual, per channel) and do all scaling based on that? That would give a more realistic relation of camera raw data to intermediate scaled to linear color output than scaling based on the image max.

Relative value (current value

Relative value (current value divided by maximum) is the same regardless of (linear) scaling.

In second sentence you note 'linear color output', so camera color profile and some color engine (and some gamut mapping) are in mind?


Relative value (current value

Relative value (current value divided by maximum) is the same regardless of (linear) scaling.
That's mathematically impossible since you're effectively changing the slope of the line? So an unscaled value relative to an arbitrary 100% of 3800 will not yield the same multiplier as the scaled value relative to 4095. Maybe I'm over thinking it and missing something?

In second sentence you note 'linear color output', so camera color profile and some color engine (and some gamut mapping) are in mind?
By 'linear color output' I just meant demosaicked RGB, not necessarily color transformed. Sorry, should've been clearer there.

Linear scaling is

Linear scaling is multiplication by (some) constant.   So a/b == (a*const)/(b*const).

Indeed, relatve to different max values without scaling will result in different results :)

No plans for demosaic in RawDigger (except 'for reference only' rgb render).

Linear scaling is

Linear scaling is multiplication by (some) constant. So a/b == (a*const)/(b*const).

Indeed, relatve to different max values without scaling will result in different results :)

Well that's the point though. It's supposed to be a different slope so it clips at the correct values. Scaling in some other fashion than the earlier described black/white y=mx + b won't yield the correct black and white points. Which will mean for someone who has to determine metadata values, there's more work in determining the values that create a mathematically and visually correct image (avoid magenta highlights and shadows, get correct middle gray). That's why having the ability to view both unscaled and b/w scaled values is so convenient. It'll also help those of us that work on the in-camera pipeline as well.

No plans for demosaic in RawDigger (except 'for reference only' rgb render).

Yeah, that's all that's really needed. I didn't mean to imply adding a more advanced or new demosaic.

Scaling, indeed, is performed

Scaling, indeed, is performed after black level subtraction. Unsubtracted values are non-linear (not proportional to amount of light received) and mostly useless.

So are you subtracting black

So are you subtracting black from the user defined white level as well like:
scale = 100 / (white - black)
subtracted = (unsubtracted - black)
percent = subtracted * scale

or do you just do 100 * (unsubtracted - black) / white?

Because if you're subtracting black from the white value as well, then the scale is correct and there are no mathematical discrepancies. In which case I apologize for misunderstanding your original statement haha

This feature (user defined

This feature (user defined maximum) is not yet implemented.

Indeed, we need to add option [ ] Black value already subtracted for this used-specified 'white level'


Add new comment