No Whistle Sound in Edge: Check the Output and App State

For a silent whistle in Edge, stop playback before checking which audio output the system is using. Keep system volume low, return to the visible app page, and start a short steady tone with a direct click. Use a lower frequency and nonzero software gain. Silence at a high preset alone does not show that Edge audio is broken.

Check the output before starting again

If silence began after connecting headphones, a display, or another audio device, stop the whistle first. Check the output selected in your system sound controls. Return to the Edge page only after choosing the intended device and setting a low system volume. Keep speakers away from ears. The app responds to a devicechange signal by stopping, but that signal has browser limits. Some route changes may not be reported. A missing automatic stop therefore does not prove the output stayed the same. Make each comparison with a fresh, brief press after checking the route yourself.

Avoid swapping audio devices while a tone is playing.
Check system volume again after selecting a different output.
Stop immediately if the resulting sound causes discomfort.

Read the gain and playback mode together

Software gain and system volume are separate controls. The app starts with 10% software gain, allows zero, and caps its gain at 25%. Check for zero before changing anything else. Then select steady mode so the first comparison has no deliberate pulse gaps. Use hold mode if you want release to end the sound. Toggle mode keeps playback active until stopped or interrupted. Press the page control directly because browser audio may need a user action. Keep Edge in front: hiding the tab ends playback, and returning to it calls for another start action.

Use one short activation instead of leaving toggle playback running.
Try the visible controls before relying on keyboard shortcuts.
Outside typing fields, Space toggles and Escape stops.

Separate frequency limits from speaker limits

Begin the frequency check at 440 Hz. Read the current value on the page, then use the 100 Hz coarse controls only if another comparison is needed. Presets request 4, 8, 12, 16, or 18 kHz. The app clamps them to its available cap, calculated as floor(actual AudioContext.sampleRate × 0.45). That calculation limits the digital signal. It says nothing about verified speaker response. Phone and laptop speakers often cannot reproduce ultrasonic frequencies. If lower tones work, a silent higher selection may reflect that physical limit. Do not increase volume to chase an inaudible preset or treat this as a hearing check.

Compare frequencies while leaving both volume controls unchanged.
Read the displayed value after selecting a preset.
Do not interpret a dog's response as a frequency measurement.

Use a simple comparison before trying timed features

With the whistle stopped, play one classic or soft clicker marker if you need a second app sound to compare. Quick yap also produces a synthetic marker. Hearing that marker confirms only that this sound reached the output at that moment. It does not certify high-frequency playback. Leave preset drills aside during troubleshooting. Their programmed gaps can resemble missing audio, and the app allows three total drill runs per UTC day. Likewise, the four-second reaction burst serves a different purpose. Its reacted or noReaction entry is a local observation, not a sound check. The last three dated outcomes can be cleared.

Return to the same steady setting after a marker comparison.
After an interruption, inspect the page before starting another tone.
If an offline page loads poorly, retry online; cached operation requires an earlier successful cache.

Stop the app, check the system's chosen output, and set a low volume.
Bring Edge forward, choose steady playback, and confirm nonzero app gain.
Set 440 Hz, press the playback control directly, and release after a brief check.
Compare one marker if necessary, then stop before changing devices or settings.

Can the displayed maximum prove my speaker plays that frequency?

No. The maximum comes from the audio context's sample rate. Speaker response is a separate physical limit.

Why is a preset drill a poor first silence check?

Drills contain fixed sound periods and gaps. A steady tone gives a clearer first comparison without using a daily drill run.

Will the installed app always work without internet in Edge?

Offline use depends on an initial successful cache. Installation alone does not promise sound and page access under every offline condition.

Online Dog Whistle and Whistle Tone Generator