FileZilla 3.x Sound Alerts: Moving to a Failure-Only Setup

The goal is an alert setup where a sound always means a transfer failed, while successes stay silent because the queue panel already shows their status. FileZilla Client documents a Sounds page in its settings dialog (Edit > Settings > Sounds in common builds) with toggles for events such as successful transfers, failed transfers, and connection events, which appears to support this failure-only arrangement.

Two constraints complicate the decision. Sound events, their labels, and default states have shifted across the 3.x line, so older writeups may not match a current install; the page should be checked against the version in use. The client also offers no native conditional alerting — no built-in filter by server, transfer size, or repeated failures — so finer-grained alerting would require external log parsing or scripting.

A product boundary matters too: FileZilla Server's logging is configured separately from the client's sound settings, and server 1.x replaced the 0.9.x administration interface, so guidance does not transfer between the two products.

• Can success and failure transfer sounds be toggled independently in current 3.x builds, or do they share a single event?
• When a multi-file queue partially fails, does the failure alert fire once per failed file or once for the whole queue?
• Is there any documented hook for conditional alerting, or is external log parsing the only route?