so ive been running a remote station for about 8 months now using a mix of stuff - the actual radio side is handled through RemoteHams RCForb client talking to a node at my QTH, and for the SDR piece im using their SDR remote which honestly works better than i expected for monitoring the band before i key up. the latency is acceptable on my 50/10 connection, not great but workable for SSB, CW is a different story and i basically gave up trying to do serious CW work over it.

what i cant figure out is the internet linking side when i want to tie this into my local repeater network. ive got EchoLink running on a separate box and bridging audio between the two systems has been kind of a nightmare. the timing is just off enough that it sounds terrible on the repeater end. somebody told me IRLP would be better for this use case but i dont have an IRLP node anywhere near me to test with.

anyone actually using RemoteHams SDR remote in a setup like this on a daily basis? curious if the newer versions fixed any of the audio sync issues because mine is still running whatever version came out maybe spring of last year and i keep forgetting to update it

yeah the audio sync thing with EchoLink bridging is a known headache, its not really a RemoteHams problem specifically its just what happens when you stack two separate VoIP-ish systems that both have their own jitter buffers doing their own thing. you end up with like 400-600ms of combined latency and the AGC on the repeater just hates it.

what worked for me was ditching EchoLink entirely for that use case and just setting up a dedicated Allstar node with app_rpt - the timing is way more consistent because you have actual control over the buffer sizes. took me a weekend to set up on a Pi 4 but its been rock solid since. the RemoteHams SDR piece i actually use independently just for bandscoping, i leave it open in the background and its pretty decent for that, not as good as a proper panadapter obviously but when youre remote you work with what you got.

what radio are you running on the home end btw? some of the CI-V controlled rigs play nicer with RCForb than others in my experience

CW over any remote setup with real latency is rough, i gave up on that too. some guys swear by the low-latency mode in RCForb but even then you need sub-100ms round trip to make it feel anything close to normal and thats hard to guarantee over the internet unless both ends have really good connections with low jitter. i just use remote for phone and digital now, JS8Call actually works surprisingly well because it doesnt care about a few hundred ms here and there.