so ive been messing around with remote station control for a few months now and finally got a halfway decent setup going but im running into some weirdness with the RemoteHams client when i try to bridge it over to my IC-7300 at the other location. the SDR side of things works fine, like the websdr stuff is whatever, but when i actually want to key up through the remote link the latency is all over the place. sometimes its maybe 200ms which is tolerable for ssb if youre careful, and other times it spikes to like 800ms or more and then youre just talking over yourself constantly.

i did the obvious stuff, upgraded the router at the shack end, made sure the upload was decent (its about 15 up which should be enough), and the RemoteHams software shows good connection quality most of the time. but i wonder if the issue is more on the audio codec side - ive been running the default settings and never really dug into whether theres a lower latency option in there. anyone running a similar setup with the 7300 or even just any rig over RemoteHams and found a codec config that helps? also curious if anyone has tried to link a remote SDR receive-only node into a full duplex remote setup for like a panadapter over the internet, that seems like it would get complicated fast with timing.

yeah the latency thing with RemoteHams is real and it kind of depends on which server node youre routing through too, not just your own connection. i had similar issues with my FT-991A setup and what helped me the most was dropping to a lower audio quality setting in the client, i think i went down to like 8kHz sample rate instead of the default and it felt more responsive even if the audio wasnt quite as crisp. for SSB it honestly doesnt matter that much. also make sure youre not running anything else hammering your upload at the shack end, even a background windows update was enough to throw my latency through the roof one afternoon before i figured out what was happening.

the panadapter idea over the internet is doable but yeah its a headache. i tried piping SDRsharp output into virtual audio cable and then into the remote client and it sort of worked but the sync was always slightly off. if youre just using it for monitoring and not trying to sync RX to TX it probably doesnt matter much.

15 up should be way more than enough tbh. i ran a remote setup for about two years on like 5 up and it was fine once i got the codec sorted. the RemoteHams client has some options buried in the settings that arent super obvious, theres a jitter buffer setting that i found made a noticeable difference when i finally found it. too high and youre just adding artificial delay on top of whatever the network is doing, too low and you get those audio dropouts that sound like a broken record. i ended up somewhere in the middle and just left it.

one thing i dont see people talk about enough is what youre running on the computer at the shack end thats hosting the server side. if thats an older machine or youve got other stuff running on it the processing overhead can add latency that looks like a network problem but isnt. i had that exact issue, swapped to a dedicated little mini pc just for the remote server stuff and it got a lot better.