Dog WhistleHow to Check Whistle Audio Output on Windows
Stop the whistle before selecting another Windows output. Check the selected device and browser volume in Windows sound settings, then return to onlinedogwhistle.com. Start with low system volume and a short press in hold mode. The displayed frequency describes the generated signal; it does not confirm what your speakers reproduce.
Choose the Windows output before playing
Begin with the whistle stopped. Open the sound output controls available in your Windows installation. Read the device name before making a selection. A monitor, USB speaker, Bluetooth device, or built-in speaker may have a separate entry. Choose the device you intend to use, then lower system volume. Keep the sound source away from ears. If anything feels uncomfortable, stop immediately. Do not hold a speaker near your head to check a quiet tone.
- Check the selected output again after connecting or removing audio hardware.
- Keep other audio quiet while checking which speaker receives playback.
Check browser volume and start from the page
If the page appears active but produces no sound, inspect Windows volume controls for the browser and the selected output. Look for a muted browser entry or a low application level. Also check whether the browser tab is muted. Return to the whistle page and start playback with its control. Browsers can require a user action before audio starts. A silent page immediately after loading is therefore not enough to identify an output fault. Make one short attempt, stop, and inspect the controls again.
- Use hold mode for a brief first check; release the control to end playback.
- In toggle mode, activate the control again when you want playback to stop.
Read the frequency without treating it as a measurement
The current frequency remains visible. Coarse adjustments move in 100 Hz steps, starting from a minimum of 440 Hz. Five presets request 4, 8, 12, 16, or 18 kHz. Each preset is clamped to the current generation cap. That cap equals the actual AudioContext sample rate multiplied by 0.45, rounded down to a whole number of hertz. This is a digital generation limit. It is not a verified speaker specification. Many laptop and phone speakers cannot reproduce ultrasonic frequencies. Silence at a high setting does not justify raising volume.
- Read the displayed setting after choosing a preset, especially when checking a different output.
- Use steady mode first so pulse or warble does not complicate an initial output check.
Handle an output change as a fresh check
Before switching to another device, end playback and lower its volume. Do this even when the app has stopped automatically. The browser may report some hardware changes through devicechange, but that signal does not cover every route change. Returning from another tab also calls for a deliberate start, because hiding the whistle tab stops it. The tone uses a 10 ms cosine fade. That fade does not replace careful volume control. Software gain ranges from 0% to 25%; its percentage is not a measurement of sound at the speaker.
- Press Escape to stop when you are not typing in a field.
- Space toggles playback outside text entry, so keep keyboard focus in mind.
- End any active tone, open Windows sound controls, and select the intended output device.
- Lower system volume, inspect the browser volume entry, and check the tab for muting.
- Return to the page, select steady mode, read the frequency, and make a short hold-mode check.
- Release the control before changing hardware; repeat the output and volume checks after each switch.
Does choosing 18 kHz prove that my Windows speakers reproduce it?
No. The setting specifies the generated tone, subject to the app's cap. Speaker response is unverified, and a high-frequency silence cannot establish what the hardware emits.
Why did the whistle stop when I opened another tab?
Check both the chosen output and browser volume in Windows sound settings.. Return to the page and start it deliberately after checking the output. Do not expect background playback while adjusting settings elsewhere.
Can a saved reaction identify an output problem?
No. The four-second reaction burst ends with reacted or noReaction choices. Only the last three dated outcomes are stored locally, with a clear action. Dogs vary; those entries do not verify speaker output or promise training results.