* Visualizer: use log scale
- log scale frequency and gain
- Hamming windowing
- improve reading from fifo
* Fix Visualizer memory leaks
* Visualizer: use Blackman window
* Visualizer: support DFT zero padding
* Visualizer: support fractional height bars, fix fifo read
* Revert "Fix Visualizer memory leaks"
This reverts commit 5c6509d2b8ed985a4928f681217dc8616d053ace.
* Visualizer: fix fifo read again
* Visualizer: add cubic interpolation option
* Visualizer: Expose more config options, add docs for config options
* Visualizer: Use reverse video text for stereo visualizer smooth look
* Visualizer: use FormattedColor to for reverse-video
* Visualizer: change some config options for spectrum
* Fix build fftw disabled
* Visualizer: use [0,5] interval for dft_size config option
On DirectColor-capable terminals with the proper terminfo
database in use, COLORS is 2^24. Since the color map is
only 64k entries, this resulted in a segfault. I've
introduced NC::colorCount(), which bounds it by the
previously assumed maximum (and usable range) of 256.
taglib deprecated removeField internally in [1], but did not add the
deprecation warning until about four years later. The original bug
report [2] and pull request commit both mention not wanting to change
the original method's behaviour, but this was done anyway (perhaps by
mistake) in [3].
With that change, removeField(type) will not remove all tags of the
given type anymore, as the default for value has changed from
String::null to String().
This commit replaces explicit calls to removeField(type) with
removeFields(type), which has the correct behaviour. In writeXiph,
removeField is removed entirely, as addField(key, value) will replace
the tag by default.
[1] https://github.com/taglib/taglib/pull/681
[2] https://github.com/taglib/taglib/issues/651
[3] https://github.com/taglib/taglib/commit/c05fa78406fd8ce7382a11c1f63a17c4bfbe83fa
Andrzej Rybczak