so ive been messing around with setting up a remote station for a few months now and finally got the RCForb client talking to my IC-7300 at the home QTH which is great but the latency is driving me nuts on SSB. its like 300-400ms sometimes and i know thats partly just the internet connection but im wondering if anyone has tweaked the audio buffer settings in RemoteHams to get that down.

also the SDR side of things — i have an RTL-SDR dongle plugged into the same machine as the rig and i was thinking about running SDR# or SDRuno alongside it so i could have a panadapter view remotely too. not sure if thats even practical or if the bandwidth requirements just make it a nightmare. the upload at my home site is only like 6 Mbps which probably isnt great for streaming SDR data on top of everything else.

the other thing i wanted to ask about is linking this into the local repeater network via echolink or maybe wires-x. i know some guys do this but i dont really understand if youre supposed to bridge the audio from the remote session into the linking software or run them completely separate. seems like it could get messy with audio loops if you dont set it up right. anyway any pointers appreciated, been at this for a while and feel like im close but not quite there.

the latency thing on RemoteHams is mostly gonna come down to your buffer size in RCForb — theres a slider in the audio settings and most people set it way too high by default thinking it helps stability but it just adds delay. i run mine around 60-80ms buffer and yeah it drops out occasionally but SSB is actually usable. if you cant get the RTT under about 150ms to your home site though youre gonna have a bad time no matter what you tweak.

on the SDR panadapter idea over remote — ive tried this and honestly 6 up is probably workable if you throttle the sample rate on the dongle way down. like 250k samples/sec instead of the default 2.4M, and use something like OpenWebRX instead of SDR# because it handles the compression server-side and just sends you a rendered spectrum view in the browser. way less bandwidth than trying to pipe raw IQ data. its not as snappy as having it local but its functional enough to spot signals before you tune the main rig.

the echolink bridging question — yeah dont try to tie the audio from your remote session into echolink on the same machine without a virtual audio cable setup that youve really thought through. Ive seen guys create feedback loops that were just brutal. i would run the linking completely separate personally, like a dedicated node machine that doesnt touch the remote audio chain at all.

i had almost the exact same situation last year, was pulling my hair out over the audio delay. ended up switching from the default UDP mode to the lower latency option in RCForb and it helped a bit but honestly the biggest thing was just moving my remote machine to a wired connection instead of wifi. obvious in hindsight but wifi was adding like 80ms of jitter on its own and i hadnt even thought about it.

cant really help with the wires-x linking stuff, never messed with that system. echolink i know a little but not enough to say anything useful about bridging it with a remote session setup like yours.