[email protected]
4bb5df9c87
feat(tracker): enum-style values and menus to choose one option
2026-01-31 13:57:09 +02:00
[email protected]
86ca3fb300
refactor(tracker): group Model methods, with each group in one source file
2026-01-27 22:16:14 +02:00
[email protected]
3a7010f897
feat(tracker): spectrum analyzer
...
Closes #67
2026-01-18 17:09:57 +02:00
[email protected]
bdfe2d37bf
feat(tracker): panic synth if Inf or NaN, and handle these in detectors
...
Closes #210 .
2025-10-08 08:53:46 +03:00
[email protected]
554a840982
refactor(tracker): new closing mechanism logic
2025-05-01 10:20:41 +03:00
[email protected]
9f89c37956
refactor(tracker): rename trySend to TrySend to make it public
2025-04-30 22:00:34 +03:00
[email protected]
0199658025
style(tracker): use for range loops everywhere in detector.go
2025-04-30 16:24:48 +03:00
[email protected]
3623bdf5b2
refactor(tracker): bake 1 kHz gain offset into filter coeffs
2025-04-29 20:45:14 +03:00
[email protected]
fe9daf7988
fix(tracker): loudness A- and C-weighting did not have proper scale
2025-04-29 15:12:57 +03:00
[email protected]
bf0d697b80
fix(tracker): reset also biquad filter states to avoid endless nans
2025-04-28 15:23:00 +03:00
[email protected]
5fd78d8362
feat(tracker): buttons for loudness weighting and peak oversampling
...
Closes #186
2025-04-27 21:30:10 +03:00
[email protected]
845f0119c8
fix(tracker): peak amplitude dBs should be 20*log10, not 10*log10
2025-04-27 19:55:25 +03:00
[email protected]
5a3c859a51
fix(tracker): also peak detector windows were in wrong order
2025-04-27 19:29:23 +03:00
[email protected]
5c0b86a0f0
fix(tracker): the peak detector result was in wrong layout
2025-04-27 14:13:31 +03:00
[email protected]
94058c2603
fix(tracker): do not close Broker but rather just close the detector
2024-11-02 20:45:10 +02:00
[email protected]
ec222bd67d
feat(tracker): oscilloscope and LUFS / true peak detection
...
In addition to the oscilloscope and loudness/peak detections, this
commit refactors all the channels between components (i.e.
ModelMessages and PlayerMessages) etc. into a new class Broker. This
was done because now we have one more goroutine running: a Detector,
where the loudness / true peak detection is done in another thread.
The different threads/components are only aware of the Broker and
communicate through it. Currently, it's just a collection of
channels, so it's many-to-one communication, but in the future,
we could change Broker to have many-to-one-to-many communication.
Related to #61
2024-11-02 15:08:09 +02:00
[email protected]