I've seen the message (letters are big enough

), but as there was neither an update here or there I did not think more closely about it.

Back on topic of thermal cameras:
I really like the offline mode very much - you can go back to whatever snapshot one has taken and work with it as if it were live. Also the locking is very useful for various reasons. IMHO it is not stated clear enough, that in this mode the thermal image itself is used for generating the main image. I would not be able to recognize as (except for the colors) it looks so similar to the original output of the camera.
In offline mode I can even produce a side by side comparison of what I found as erroneous earlier:

I took my old raw image fro offline mode, locked it and applied "Map 1" which is according to console output "Mapping filter: LINEAR".
On the left side there is the original camera image with added "Inv HSV" mapping, where the scale labels do not fit with labelled temps. Applying some color map to the obviously already mapped image fails - especially obvious if the range is large. On the right side the colors match the scale given for the left image: Power supply and lamp head with some blueish color indicating 30 °C and not in the mid of the images total temp range.
The left image definitely gives more visual guidance because there are more objects/contours visible, but I think no information in the image should be contradicting each other. According to screenshots of the original app it only labels the extremes of the scale with temperature, but nothing in between - to avoid the problem of non-linearity? As stated earlier I'm not too much into resource effectiveness in the first line in my current use case, but definitely not when content is wrong because of that.
So easiest way to solve this with minimal impact to current functionality and optimization for low-power platforms IMHO would be:
- do not display intermediate temperature labels next to the scale if we are not sure about its calculation
- as this is seems to always be the case with post-processing the 1st camera sub-stream, indicate the stream used for generation of the (sub-)window somewhere (as it is has already been started by "Img" and "Therm" indicators)
- add a scale bar (like it is now with intermediate labels) to the self-produced image with known mapping if it is present (generated from 2nd sub-stream because of locking and such)
Another track would be to fiddle out how the camera transforms the scale and reverse that processing to end up with something that we know. But I assume that also is computationally intensive like "forward processing" the raw temperature image due to the fact we need to apply some transformation function to all pixels present?
BTW: In offline mode there is no display change between "Clip" and "Grow" (obviously because it makes no sense with static information), but I still need to press "l" two times to get back to default, while nothing changes in display with the second key press. Perhaps it cycles through both modes in the background?