Skip to content
View in the app

A better way to browse. Learn more.

Ham Radio Base

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.
Ham Radio Base — Education, Resources, Projects and Community
☀ Solar
SFI 99
SN 26
A 6
K 0 Quiet
X-Ray B2.3
Wind 384.8 km/s
Aurora 1
Updated 13:30 UTC HamQSL · N0NBH
Day 80/40m Good 30/20m Good 17/15m Fair 12/10m Poor
Night 80/40m Good 30/20m Good 17/15m Fair 12/10m Poor

Callsign Lookup
_
Vanity Call Signs Available
Enter filters above and click Search.
ⓘ Callsign lookups are in real time via the FCC database. Vanity callsign availability is refreshed daily at 6:00 AM CST. The vanity search may be unavailable for a few minutes during this update.
Live DX spots
Live DX Spots — 70cm via PSKReporter · scroll or pinch to zoom
Band
Mode
Time
Loading map data…
MHz DX Spotter Info
Recent spots —
Select a band above to load spots
Ready — select a band to fetch live spots

SSB audio checklist: mic gain, ALC, processor, EQ and bandwidth for clean signals and weak-signal work

ci_cover.jpg

A good SSB signal isn't the loudest one. It's the one that stays readable when the band is noisy, the path is marginal and the other operator is copying through QRM. Here is a working order of operations for setting up phone audio, with a few questions at the end that I'd like to hear other operators' views on.

Start with the microphone and the room. Most of what people call "bad audio" is mic placement, room reflections or RF in the shack, not the rig's settings. Keep the mic a few inches from your lips, slightly off-axis so plosives (p, b, t) don't hit the capsule directly, and keep that distance consistent. A foam windscreen helps. Hard walls and bare desks add a boxy, hollow sound, so soft furnishings or a mic positioned close to your mouth cut that down. If your audio changes when you touch the mic cable or key the transmitter, suspect RF feedback and look at ferrite chokes, grounding and antenna placement before touching any audio control.

Set mic gain by the ALC, not by ear. ALC (automatic level control) is a protection circuit that limits drive to the final stage. It is not a loudness control. On most rigs, set mic gain so that normal speech peaks just reach the ALC zone on the meter and never push far past it. Once you are deep into ALC action, the rig is flattening your peaks in a crude way, and the result is distortion and a wider signal. If you run an amplifier, this matters even more, because an overdriven exciter or amp produces splatter that other stations hear as splash on both sides of your frequency. Always check your manual, since ALC metering and the proper range differ from rig to rig.

Use the processor modestly. A speech processor or compressor reduces the gap between your loud and quiet syllables so the average power rises without raising peak power. That helps weak-signal work because a higher average level is easier to copy through noise. The cost is that room noise, breath sounds and sibilance come up with it, and heavy settings make the audio sound squashed and tiring. A sensible approach is to set mic gain first, then add compression until the compression meter shows a few dB of action on voice peaks, and stop there. If your signal gets harder to understand when you turn the processor up, you've gone too far, whatever the meter says.

Use the monitor, but know its limits. The TX monitor lets you hear your own audio in headphones while transmitting. Headphones prevent acoustic feedback. Depending on the rig, the monitor may sample the audio before or after processing, and it may not reflect what actually goes out over RF. It's useful for catching hum, popping, and over-compression, but it's not proof of what the other end hears. A second receiver or SDR tuned to your frequency, ideally with a waterfall or spectrum display, gives you a better view of bandwidth and splatter. Recording your own transmission and listening back is also a good way to catch problems you can't hear while speaking.

Shape the audio with the equalizer. Speech intelligibility sits mostly between roughly 300 Hz and 2.7 kHz. Low-frequency boom below about 200 to 300 Hz uses transmitter power without helping anyone copy you, so rolling it off is usually a win. A gentle lift in the 2 to 3 kHz range can add clarity on a dull mic, but too much sounds harsh and edgy. Make small changes, and always re-check ALC and compression after adjusting EQ, because boosting a band changes how hard the rig is being driven.

Choose bandwidth to suit conditions. A 2.4 kHz transmit and receive filter is a common starting point, and many rigs let you set the TX bandwidth anywhere from about 2.4 to 3.0 kHz or wider. Wider can sound more natural for ragchews on a quiet band. Narrower settings, around 2.1 to 2.4 kHz, put more energy in the speech band and take up less space on a crowded band. On receive, narrowing the filter or using passband shift can cut adjacent-signal QRM, but go too narrow and the voice turns muffled, so back off until the speech is just comfortable.

Sideband selection. By long-standing convention, amateurs use LSB on 160, 80 and 40 meters, and USB on 20 meters and above. On 60 meters in the US, channelized operation is USB. These are conventions, not universal rules, and some regions and band plans differ, so check the band plan where you operate. Using the wrong sideband doesn't just sound odd. The other station has to retune to the opposite sideband, and your signal won't be where listeners expect it.

Working weak stations and DX. Clean, moderate audio usually beats an aggressive setting. Speak slightly slower than normal conversation, use standard phonetics for callsigns, and keep exchanges short and clear. Give your callsign cleanly and at a steady pace rather than shouting. In a pileup, a modest processor setting can raise your average level, but distortion and splatter make you harder to copy and annoy neighbors. For reference, doubling power is only about 3 dB, so audio quality and antenna improvements often do more than another round of tweaking.

Where do you land on a few things? What ALC reading do you aim for? Do you leave the processor on for casual contacts, or only when conditions are tough? And what TX bandwidth do you use on a quiet band compared with a contest weekend?

  • Replies 2
  • Views 14
  • Created
  • Last Reply

Top Posters In This Topic

Featured Replies

  • Moderators

On the ALC point, I'd add that the meter only tells you part of the story, because different rigs scale it differently. Some show ALC as a bar that should barely flicker, others have a defined zone that's supposed to be hit on peaks. The manual's recommended setting is the starting point, but you still need to verify it by looking at the signal on a second receiver or SDR. If the bandwidth looks wider than expected or there are hard skirts on the spectrum display, drop the mic gain or processor level, even if the ALC meter looks acceptable.

It's also worth remembering that mic gain and processor level interact. If you turn up the processor without backing off the mic gain, you can push the ALC hard and not realize it. A clean sequence is to set mic gain with the processor off, then switch it on and re-check the ALC and output power. The processor should raise average level, not make the ALC meter hit the end stop.

On EQ, I'd say cutting is safer than boosting. Roll off lows and any boomy resonance first. Boosting highs on a mic that's already bright can make sibilance worse once the compressor kicks in.

  • Moderators

For DX, I'd split the problem into the transmit side and the receive side. On receive, the 2.4 kHz filter is a good default, but the useful trick is shifting the passband and narrowing only as much as the QRM requires. Many operators go straight to a very narrow filter, then find they can't tell sibilants apart and end up asking for repeats, which costs more time than the QRM did. Try 2.4 first, then step down to about 2.1 or 1.8 kHz if you need to, and see whether the callsign still comes through clearly. A noise reduction setting that's too aggressive can have the same effect and leave the voice sounding watery.

On transmit, the DX operator has to copy you through fading and noise, so consistency matters more than loudness. Speak at a steady level with the mic at the same distance, and avoid trailing off at the end of your callsign. If you're running a processor, use only enough to even out the peaks. Keep the exchange short: callsign, report, and any information required. Longer transmissions leave more room for fading to swallow part of your call.

Finally, check which split rules and calling frequencies the DX station is using before you call. A perfect signal on the wrong frequency, or on the wrong sideband for the band, doesn't get you into the log.

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

Affiliate Disclosure: As an Amazon Associate, Ham Radio Base earns from qualifying purchases. Some links throughout this website may be affiliate links. If you purchase a product through one of these links, we may earn a commission at no additional cost to you. Your support helps us continue creating free articles, tutorials, reviews, and resources for the amateur radio community. N0TLB © Ham Radio Base - Powered by the Ham CQ DX Community. All rights reserved.

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.