Analysis systems that only show critical issues miss important secondary improvements that contribute to a professional-sounding mix. Priority fixes address the most urgent problems, but they don't tell the complete story. Minor adjustments address these secondary issues with the same rigor as priority fixes, ensuring comprehensive guidance for mix engineers.
What minor-adjustments reveals (and why it matters)
Minor adjustments are 3–5 lower-priority fixes generated alongside the five priority fixes by the AI coaching engine (Source: inputs/articles/minor-adjustments/brief.md#Core message). They address real problems worth fixing but are secondary in impact, urgency, or dependency. The system doesn't classify problems as "critical" versus "ignorable". Instead, it separates fixes into two tiers: issues that must be addressed first and issues that matter but can be tackled second.
This two-tier structure solves a fundamental problem in automated mix analysis. If a system reports only the top issues, important secondary problems get lost. If it reports everything with equal weight, critical issues don't stand out. Minor adjustments provide the middle ground. They give mix engineers a complete picture without overwhelming them with undifferentiated feedback.
Despite the "minor" label, these fixes are not optional. They still require specific numbers in their fixes and provide concrete actions (Source: inputs/articles/minor-adjustments/brief.md#Core message). The distinction is purely one of relative priority. Priority fixes are critical first steps. Minor adjustments are important follow-ups or secondary issues that may depend on priority fixes being resolved first.
For mix engineers working toward a professional sound, minor adjustments represent the polish layer. They catch issues that aren't show-stoppers but still detract from the final result. A vocal with slightly harsh sibilance, cymbals with excessive high-end, or a snare that sits 1 dB too loud—these problems won't ruin a mix, but fixing them contributes to the professional finish that separates good mixes from great ones.
How minor-adjustments works: technical methodology
Minor adjustments are generated in the same Stage 2 AI prescription call as priority fixes. Both are returned together in the same JSON response (Source: inputs/articles/minor-adjustments/brief.md#Page structure sections). This technical integration ensures that both fix categories draw from the same diagnostic analysis and maintain consistent quality standards.
The generation process begins with Stage 1 diagnostic ranking, which identifies and prioritizes all detected issues in the mix. The AI prescription system then determines which issues belong in the priority fixes list and which belong in minor adjustments based on relative severity, impact on the overall mix, and dependency relationships between problems.
Both fix categories use the same strict formatting rules. Each minor adjustment follows a four-field structure identical to priority fixes: issue (short label, maximum six words), description (one sentence explaining the problem and its impact), fix (precise action with specific numbers), and ear_training (what the listener will hear after applying the fix) (Source: inputs/articles/minor-adjustments/brief.md#Key accuracy requirements).
The fix field requires the same level of specificity as priority fixes. A minor adjustment for harsh cymbals might specify "Apply a narrow cut of 2.5 dB at 8.2 kHz with Q of 3.0 on the overhead bus", not vague guidance like "reduce high frequencies slightly". This precision ensures that minor adjustments provide actionable instructions, not interpretable suggestions.
The AI determines the exact number of minor adjustments based on identified issues. While priority fixes are always exactly five items, minor adjustments can range from three to five. This flexibility allows the system to report all secondary issues without padding the list with manufactured problems.
Interpreting minor-adjustments values and outputs
Reading minor adjustments requires understanding the distinction between priority levels and fix quality. The minor adjustments section appears below the priority fixes table in the UI, with visually lighter styling to distinguish priority levels (Source: inputs/articles/minor-adjustments/brief.md#Page structure sections). This visual hierarchy reinforces the workflow sequence: address priority fixes first, then move to minor adjustments.
Each minor adjustment contains the same four fields as priority fixes, but the problems they address have lower relative urgency. A priority fix might address a vocal that's 4 dB too quiet and unintelligible, while a minor adjustment might address the same vocal's sibilance that's slightly harsh at 8 kHz. Both are real problems. Both need specific fixes. The difference is impact and urgency.
The description field provides context for prioritization. Descriptions often include language about dependencies, such as "After reducing the overall bass level, the kick drum may need slight reinforcement at 60 Hz". This signals that the minor adjustment depends on a priority fix being resolved first. Other descriptions emphasize polish rather than correction: "High-end slightly harsh on cymbals" indicates an issue that affects tone but doesn't compromise intelligibility or balance.
Some minor adjustments may be absent entirely if the analysis detects fewer than three secondary issues. Priority fixes are always exactly five items (enforced by the prompt), but minor adjustments adapt to the actual problems found (Source: inputs/articles/minor-adjustments/brief.md#Key accuracy requirements). An empty minor adjustments section doesn't indicate a parsing error. It means the AI identified five critical problems but fewer than three secondary issues worth reporting.
Parsing issues can occasionally truncate the minor adjustments list. If the JSON response is incomplete or malformed, the minor adjustments section may contain fewer than three items or be empty entirely. This differs from a deliberate decision to report fewer items. Checking the response logs can distinguish between these scenarios.
How minor-adjustments integrates with other systems
Minor adjustments feed into the same coaching pipeline as priority fixes. Both categories appear in the prescription display, both can be marked complete by the user, and both contribute to the overall mix improvement workflow (Source: inputs/articles/minor-adjustments/brief.md#Page structure sections). The system treats them as complementary layers of guidance, not as separate tracks.
The visual presentation reinforces this integration. Minor adjustments use the same four-field row layout as priority fixes, maintaining consistent formatting for familiarity. The only visual difference is the lighter styling, which provides clear hierarchy without breaking the pattern. A user who understands how to read and apply priority fixes already knows how to work with minor adjustments.
Downstream tracking systems can optionally separate priority fixes from minor adjustments when analyzing completion rates or user behavior. An engineer might complete all five priority fixes but skip the minor adjustments, or they might tackle priority fixes immediately and return to minor adjustments in a later session. The structured format allows analytics systems to measure these patterns.
Internal linking opportunities connect minor adjustments to related features in the AI coaching system. Articles about priority fixes, diagnostic ranking, or the AI prescription process can reference minor adjustments as part of the comprehensive guidance model. Each mention reinforces the positioning: MixCoach.ai provides layered recommendations that address both critical and secondary issues.
Practical application and workflow
The recommended workflow treats priority fixes and minor adjustments as sequential phases. Address priority fixes first. These represent the most urgent problems and often create prerequisites for secondary fixes. Once priority fixes are complete, revisit the mix and assess whether the minor adjustments still apply.
Some minor adjustments depend explicitly on priority fixes being resolved first. If a priority fix reduces overall bass levels, a minor adjustment might suggest reinforcing the kick drum slightly to maintain its presence. Applying the minor adjustment before the priority fix would produce incorrect results. The description field often signals these dependencies with phrases like "After addressing the priority fix for bass reduction" or "Once the vocal level is corrected".
Other minor adjustments address independent problems that simply have lower urgency. A slight harshness on cymbals at 8 kHz doesn't depend on any other fix—it just matters less than a vocal that's 4 dB too quiet. These adjustments can be applied in any order after priority fixes are complete.
Don't ignore minor adjustments entirely. Professional mixes often need these secondary fixes to achieve the final polish (Source: inputs/articles/minor-adjustments/brief.md#Core message). An engineer who completes only priority fixes will have a mix that's balanced and intelligible but may still have rough edges or tonal imbalances that detract from the professional result.
Consider minor adjustments as the "phase two" improvement process. Priority fixes correct critical problems. Minor adjustments refine the result. Both contribute to the final quality, but the sequence matters. Attempting to polish a mix before correcting its critical issues wastes time and produces inconsistent results.
What are minor-adjustments? Minor adjustments are 3–5 lower-priority fixes generated by the AI coaching engine alongside priority fixes. They address secondary issues with the same specificity and actionable format as priority fixes, but with lower relative urgency.
How do minor-adjustments work? Minor adjustments are generated in the same Stage 2 AI prescription call as priority fixes, based on Stage 1 diagnostic ranking. The AI determines which issues belong in each category based on impact, urgency, and dependency relationships.
How to interpret minor-adjustments outputs? Read the description field to understand the problem's context and any dependencies on priority fixes. Apply the fix exactly as specified, using the provided numbers for frequency, gain, Q, and other parameters. Check the ear_training field to verify the expected result.
Summary and key takeaways
Minor adjustments complete the picture by addressing important secondary issues that complement priority fixes. They use the same four-field structure, the same specificity requirements, and the same rigorous formatting as priority fixes. The only difference is relative priority.
The system generates 3–5 minor adjustments alongside the five priority fixes, with the exact number determined by the AI based on identified issues. These fixes address real technical problems with actionable guidance and specific numbers. The "minor" label refers to urgency, not importance.
Integrate minor adjustments into your workflow by treating them as phase two of the improvement process. Complete priority fixes first, then revisit the mix and apply minor adjustments to achieve professional polish. Don't skip them—secondary improvements contribute meaningfully to the final sound quality.
Minor Adjustments are 3–5 lower-priority fixes generated alongside priority fixes by the AI coaching engine. They address real problems worth fixing but are secondary in impact, urgency, or dependency. Despite the "minor" label, these are not optional—they still require specific numbers and provide concrete actions (Source: inputs/articles/minor-adjustments/brief.md#Core message).