so ive been messing with RemoteHams for about three months now and overall its been pretty solid but i keep running into this annoying audio desync issue when im connected over my home broadband from work. the setup is a IC-7300 at the home QTH with a raspberry pi handling the server side and everything looks fine on the waterfall but the audio just drifts after like 20-30 minutes and i have to reconnect to get it back in sync. latency is showing around 80-90ms which shouldnt be that bad i think

the other thing im wondering about is whether anyone has actually used the SDR remote features alongside something like EchoLink or AllStar for internet linking because i had this half-baked idea of tying them together so club members could use the linked repeater system remotely through the SDR interface but i honestly dont know if that even makes sense architecturally or if theres a cleaner way to do it. im not a network engineer just a guy who likes tinkering

anyone run into the audio drift thing specifically with the 7300? or is this more of a generic RTP buffer problem because i see references to that in the RemoteHams docs but the explanation is pretty thin

the audio drift on RemoteHams with the 7300 — yeah been there. what fixed it for me was adjusting the jitter buffer size in the client settings, there's a slider thats kind of buried in the audio config tab. i pushed mine up to around 150ms and the drifting basically stopped. you lose a tiny bit of responsiveness but for casual operating it's totally fine. 80-90ms latency is actually pretty decent, i was running on a rural connection at like 180ms for a while and it was still workable just felt a bit like talking through a satellite phone

on the EchoLink/AllStar question honestly i'd think twice about that combo. AllStar with app_rpt can already do remote base linking through its own architecture and adding RemoteHams into that chain feels like you're introducing a lot of extra failure points. might be cleaner to just set up a separate remote base node on AllStar and let the club members connect that way. but if you specifically want the SDR waterfall visibility for users that changes the calculus a bit i guess

not sure about the specific audio drift thing you're describing but just wanted to say ive been running a remote station for our club through wfview instead of RemoteHams and it handles the 7300 really well, might be worth a look if you keep having headaches. wfview has gotten a lot better in the last year or so with the network audio stuff

the internet linking idea sounds interesting though. we did something vaguely similar tying a remote rx site into our linked repeater system but we used a dedicated URIxB interface and just treated it as another node. wasnt exactly elegant but it worked for what we needed during a couple of ARES exercises