so ive been messing around with RemoteHams for the past few weeks trying to get my home station accessible from work and honestly its going better than expected but i still have a few things driving me nuts

the latency on the audio path is workable, maybe 200-250ms which is fine for SSB but trying to do any CW above like 15wpm is pretty rough, i keep getting jumbled characters because the timing just isnt consistent. i know thats kind of expected but wondering if anyone has found a way to tune the buffer settings to help with that. im running the server software on a dedicated machine with a pretty solid upstream connection, like 50mbps up so i dont think its a bandwidth issue

the other thing is the SDR side of it — ive got an RTL-SDR hanging off the same machine doing panadapter duty and it works but its kind of clunky how the two interfaces interact. has anyone integrated something like SDR# or HDSDR into the RemoteHams setup cleanly, or are people mostly just using whatever comes built in

also curious if anybody is running internet linking alongside this for local club repeater stuff, like IRLP or AllStar running on the same box. wondering if there'd be resource conflicts or if thats just not something people do

the CW latency thing is just kind of a reality with any IP-based control setup, doesnt matter how fat your pipe is, jitter is the killer not raw bandwidth. what codec are you using for the audio path? if youre on something like OPUS try bumping the bitrate and lowering the frame size, smaller frames means less buffering and the jitter gets a bit more predictable. some guys also just use a keyer at the remote end and send timing data instead of actual audio which helps a lot but thats more complicated to set up

on the SDR integration question i got HDSDR working alongside RemoteHams on my station using virtual audio cable to pipe the IQ stream around but honestly its a bit of a house of cards, if one thing crashes it tends to take everything with it. the built in waterfall in RemoteHams isnt amazing but its stable and for remote ops i kinda value stable over pretty

yeah i run AllStar on the same physical machine as my remote HF setup and it mostly works fine, the CPU load from AllStar node is pretty minimal as long as youre not running a busy repeater link. the thing to watch out for is making sure your port forwarding doesnt get messy — AllStar wants its UDP ports and RemoteHams has its own set and if your router firmware is doing anything weird with NAT timeouts you'll get dropouts on one or both. i had an issue for months that turned out to be my ISP modem going into some kind of low power state and killing UDP sessions after like 90 seconds of inactivity, drove me absolutely crazy before i figured it out