Troubleshooting and Safety

No sound

Check the signal path in this order:

  1. the DAW track is receiving audio;
  2. Audio In modules use available host channels;
  3. the graph has a complete path to Audio Out;
  4. mixer/gain controls are not at zero;
  5. plugin Mix/Bypass are in the expected state;
  6. DSP has not been disabled by the panic/transport-stop controls.

Patch sounds different after switching Variants

Switch to Default and then back to the Variant. Deepfield restores Default before applying a Variant, so unrelated parameters should not leak from the previously active Variant. If they do, the likely problem is Variant membership or a parameter that is being captured when it should be driven/derived.

Tempo module does not follow the host

Confirm the patch uses TempoSelector, TimeInfo or TempoTrigger rather than a value that was calculated only once. Inside a submodule, timing modules should use the root graph's host time-information provider.

Modulation sounds stepped

Increase the patch's Modulation resolution or move the relevant path to an audio-rate design. If external audio is being used as modulation, try Force audio-rate modulation from Audio In nodes.

Very loud output / runaway feedback

Use Panic Mute Output first. If needed, use Disable DSP. Reduce the loop gain before unmuting.

Keep Safety output clamp enabled while building unfamiliar feedback patches. Remember that the clamp protects the final plugin output; internal graph values can still become very large.

Host channel layout does not change

Changing preferred Inputs/Outputs can require the DAW to reload the plugin instance or renegotiate its bus layout. The graph's Audio In/Out channel availability follows the layout actually supplied by the host.

Editor or graph problem

Use Export Diagnostic Bundle... when available. A useful report includes:

  • DAW and version;
  • operating system;
  • Deepfield version/build;
  • sample rate and buffer size;
  • the patch that reproduces the issue;
  • the exact action immediately before the problem;
  • whether it reproduces after reopening;
  • diagnostic bundle/crash report if available.

For UI issues, a screenshot or short screen recording is often more useful than a long description.