comparison .hgsubstate @ 1231:b4fd38b40712 spectrogram-minor-refactor

Fix threshold in spectrogram -- it wasn't working in the last release.
There is a new protocol for this. Formerly the threshold parameter had a
range from -50dB to 0 with the default at -50, and -50 treated internally
as "no threshold". However, there was a hardcoded, hidden internal threshold
for spectrogram colour mapping at -80dB with anything below this being rounded
to zero. Now the threshold parameter has range -81 to -1 with the default
at -80, -81 is treated internally as "no threshold", and there is no hidden
internal threshold. So the default behaviour is the same as before, an
effective -80dB threshold, but it is now possible to change this in both
directions. Sessions reloaded from prior versions may look slightly different
because, if the session says there should be no threshold, there will now
actually be no threshold instead of having the hidden internal one.

Still need to do something in the UI to make it apparent that the -81dB
setting removes the threshold entirely. This is at least no worse than the
previous, also obscured, magic -50dB setting.

 9f62684e1911c4184e7b97ba3a0673cb0464f3a2 checker
 896aefe629c85b05ae0880ec93a396b9e3a5a304 dataquay
 68ae618c6b0e442d08a71d39217784a08f2a8de3 icons/scalable
 1e4f338ae482429a7ab9bdd0825242042354152f sv-dependency-builds
 c3648c667a0bb9004c97f1997dca22b79c419e12 svapp
-c118d2022ffad04408e2b59891c209eacea983d9 svcore
-50324fca132875c354bd79047826f8ad7994231f svgui
+c7b9c902642f977f527c2b39bf48a30e6ef58e46 svcore
+9fb8dfd7ce4c3788e84d8ec28c683b53e0a5bfb1 svgui
 9a2998401bbe0a7b9e3233eeca5004542bc0014d vamp-plugin-sdk