|
1 | 1 | { |
| 2 | + "date": "2026-06-05", |
| 3 | + "author": "Antigravity / USER", |
2 | 4 | "topic": "Mixer Peak Measurement", |
3 | 5 | "affected_api": ["levels.measure_track_level", "CMD_MIXER_GET_TRACK"], |
| 6 | + "context": "Automatic threshold calculation for dynamics processors needs a pre-fader signal estimate, but the measured level path is affected by mixer fader position.", |
| 7 | + "observation": "The peak level returned through levels.measure_track_level is post-fader. The raw incoming pre-fader estimate is obtained by subtracting the current mixer track fader dB value from the measured peak dB value.", |
| 8 | + "tested_values": [ |
| 9 | + "Measure a track peak with the fader at 0 dB.", |
| 10 | + "Lower the same track fader and observe the measured peak drop by the same amount.", |
| 11 | + "Subtract track_info['vol_db'] from measured['peak_db'] to recover the pre-fader estimate." |
| 12 | + ], |
| 13 | + "result": "Pre-fader peak estimate should be calculated as measured['peak_db'] - track_info['vol_db'] for tools that need raw signal level rather than post-fader output level.", |
| 14 | + "confidence_level": "implementation_verified", |
| 15 | + "source_method": "User-provided patch in src/fl_studio_mcp/tools/mixing.py plus paired Markdown knowledgebase note.", |
| 16 | + "open_questions": "None.", |
| 17 | + "next_recommended_action": "Ensure future tools that derive thresholds or raw signal levels account for the post-fader nature of the level measurement API.", |
4 | 18 | "behavior": "post_fader", |
5 | 19 | "conversion": { |
6 | 20 | "to_pre_fader": "measured['peak_db'] - track_info['vol_db']" |
7 | | - }, |
8 | | - "confidence": "implementation_verified", |
9 | | - "date": "2026-06-05", |
10 | | - "source": "user_patch_mixing_py" |
| 21 | + } |
11 | 22 | } |
0 commit comments