so ive been messing with RemoteHams for a few months now and overall its decent but the latency on SSB is just brutal sometimes. like 400-600ms on a good day and it makes actual two-way contacts feel really awkward. im running it into my IC-7300 at the remote site with a pretty solid fiber connection on that end, something like 150 down 20 up. the client side is just my laptop on regular cable internet, maybe 60-70 down.

the weird part is that the SDR waterfall display actually seems fine and updates reasonably fast, its really the audio path that gets gummy. ive tried messing with the audio buffer settings in the client software but havent found a sweet spot. has anyone actually gotten this usable for like casual ragchewing or is it really more of a DX/digital mode thing at this point

also curious if anyone has experimented with using something like EchoLink or AllStarLink alongside a remote setup like this for any kind of internet linking. half formed idea i had was setting up a node at the remote site so local club guys could at least get on HF through the link somehow. not sure if that even makes practical sense

the audio latency thing with RemoteHams is real and it kind of depends a lot on what codec settings youre using. if youre on the default settings it tends to buffer more than it needs to. i dropped my buffer down pretty aggressively and it helped but you do get some occasional glitching when the connection hiccups. for ragchewing its workable but you have to kind of mentally adjust — i tell people im on a remote and most of them get it.

the 20 up on the remote end might actually be your bottleneck depending on how many audio channels and how much of the SDR spectrum youre trying to push back. if youre pulling a wide SDR slice across the link that eats bandwidth fast. try narrowing your SDR display width and see if the audio path gets any cleaner, worked for me when i was on a similar setup with a 7610 remote.

the AllStar idea at the remote site is interesting but you'd basically be relaying HF through VoIP through AllStar which is kinda a mess of latency stacked on latency. i mean it CAN work, ive seen club setups where they do something like this for nets but the audio quality ends up being pretty rough by the time it gets through all those hops. echolink might actually be simpler if the goal is just occasional access for club members who dont want to deal with the RemoteHams client.

honestly though for the latency problem on your SSB — what router are you running at the remote site, and have you done any QoS config to prioritize the audio packets. that made a bigger difference for me than any software setting.