I think I’ve found a weird bug (unless it’s somehow intended behaviour and I don’t understand the logic). Basically, if you have the 16-bit range set to something that is not “Automatic”, you can get odd behaviour where the min and max settings are reset when you move the channel slider.
The background of this is a lot of our users use μManager to capture their images. If you open an ome.tiff made in μManager in FIJI while on “Automatic” the appearance is set so that the min and max will go to the minimum and maximum value found in the image. This means our users then open their positive and negative images and are immediately worried because they look the same (what they are missing is min/max are 100-12000 and 50-200 respectively).
To get round this we tend to tell to first go to Edit>Option>Appearance and set the bit range to the bit-depth of the camera they use (usually 14-bit or 16-bit) and then find and set suitable min/max values for their images.
I’ve put a little macro that shows the problem although it does need the user to move the slider before the problem is revealed (as indicated by the print to the log). An additional extra fun thing is that this only happens IF the brightness/contrast window is open so in the below macro if you remove the line
run("Brightness/Contrast..."); then this doesn’t happen.
run("HeLa Cells (1.3M, 48-bit RGB)"); call("ij.ImagePlus.setDefault16bitRange", 16); run("Brightness/Contrast..."); Stack.setChannel(1); run("Enhance Contrast", "saturated=0.35"); Stack.setChannel(2); run("Enhance Contrast", "saturated=0.35"); Stack.setChannel(3); run("Enhance Contrast", "saturated=0.35"); print("Click slider to move channel to see loss of min/max settings");
Edit to add version details: