Help

Support

One address, read by the person who wrote the app: support@amphoarder.com.

AmpHoarder is still in development and has no public release. If you are testing a pre-release build, this is the right place to send anything that went wrong.

What to include

Audio problems are hard to reproduce from a description alone. The more of this you can include, the faster it gets fixed — and for audio faults, the DSP and latency readings at the time of the fault are worth more than any description of the sound:

• Device and OS version — the exact model, not just the brand.

• Audio interface, if you are using one, and how it is connected.

• Buffer size and sample rate from the app’s audio settings.

• What you heard — silence, crackle, a dropout at a specific moment, latency that felt wrong.

• What you were doing when it happened, in enough detail to repeat it.

• The model or IR file involved, if it only happens with one.

• The build number shown in the app’s settings, if you are on a test build.

Common things first

No sound at all

Check input gain on the interface before anything else, then check that the amp stage in the chain is actually enabled — a chain with the amp stage bypassed is silent by design.

Crackle or dropouts under load

Usually the buffer is too small for the chain you are running. Raise the buffer size in audio settings and see whether it clears before changing anything else.

Two signals slightly out of time

Turn off direct monitoring on your interface and any system-level input passthrough. Two copies of the same signal at slightly different delays sounds thin and hollow, and it is easy to blame on the capture.

What to expect back

Reports are answered within three working days. Defect reports that include the readings above are fixed faster than those that do not.

Privacy

Anything you send to that address is used only to answer you. See the privacy policy for what the app itself does and does not collect, and the terms of use for the licence.