Skip to content
View in the app

A better way to browse. Learn more.

Ham Radio Base -Powered By Ham CQ DX

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.
Solar
SFI 203
SN 101
A 5
K 0 Quiet
X-Ray C5.0
Wind 319.6 km/s
Aurora 1
Updated 22:00 UTC HamQSL · N0NBH
Day 80/40m Poor 30/20m Good 17/15m Good 12/10m Good
Night 80/40m Good 30/20m Good 17/15m Good 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

RemoteHams SDR setup - audio latency is driving me nuts

 Loading...

so ive been messing with RemoteHams for about three weeks now trying to get my IC-7300 set up as a proper remote station and honestly the RF side of things went smoother than i expected but the audio is just killing me. im getting somewhere between 400-600ms of delay on the receive side which makes SSB basically unusable, CW is tolerable but still annoying. running the RCForb client on a windows 10 machine at the remote end, server is sitting on a raspberry pi 4 at the shack.

my upload at the shack is only about 12Mbps which i know isnt great but it should be enough right? ive tried dropping the audio sample rate down to 8kHz and messing with the buffer settings in the server config but nothing seems to move the needle much. the SDR part of it actually works decent, the waterfall updates are reasonably snappy, its just the audio pipeline that seems to be the bottleneck or maybe its the pi struggling with the codec? not sure. anyone else run into this with the pi specifically

  • Replies 1
  • Views 11
  • Created
  • Last Reply

Featured Replies

had almost the exact same issue when i first set mine up. the pi 4 should handle it no problem, that wasnt my problem anyway. turned out my router at the shack was doing some kind of traffic shaping on UDP packets and it was causing jitter more than actual latency. the latency number looked okay in the logs but the variance was terrible. worth checking if you have QoS enabled on the router, try disabling it completely just to test. also what codec are you using, if its opus try switching to pcm just temporarily to rule out decode overhead on the client side.

honestly 12 up should be fine for this, ive run remotehams over way worse connections. one thing i dont see you mention is where the bottleneck actually is - have you checked the ping time and jitter between the two endpoints specifically, not just a general speedtest. i use mtr for that. also if your shack is on a residential ISP some of them throttle or deprioritize certain port ranges which can mess with the realtime audio even when raw bandwidth looks ok. the internet linking side of things is really sensitive to jitter, like way more than bandwidth.

Guest
Reply to this topic...

Account

Navigation

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.