Aaargh! To IEEE FLOAT limits! I've spent a lot of time this morning working on my volume trackers. I use a few in Prometheus, but realised (I probably knew this once but had forgotten) that these don't track volumes over 1... as these climb and fall equally/exponentially, rather than grow slowly (value=value/climb) and fall quickly (value=value*climb). An equal rise/fall is most useful.
I couldn't get the inverse of "value=value/climb" to work today; this is: "value=1-(1-value)/climb" - but at values near to 1, (like 0.9999) it did nothing at all because of float resolution. Low numbers (0.0001) are much better represented. This probably means that many of my volume tracking plugins are bugged.
