udio from echolink was fine before the last batch of updates 3.4.4 and 3.4.5 , seems as though its clipping I've been changing settings to see if I could resolve it to the extent of a fresh install on a different Pi , allstar audio is fine.
The 3.5.5 release fixes this.
I am still noticing slightly choppy audio with Echolink connections, even running the latest version app_rpt 3.5.5. It is much improved, but after closely monitoring my system, which receives a lot of Echolink activity, when stations connect inbound directly to the Echolink node hosted on the ASL node, the audio is not great.
If I use a Windows-based Echolink node as the “hub” for all users to connect to, then have one outbound connection from the ASL based Echolink node to this so-called Windows “hub”, the audio on the ASL node, and anything connected to it, is very good. If the Echolink users connect inbound directly to the ASL-based Echolink node, the audio does not sound as good, almost like the old days of frame slippage on T1 circuits (the best way I can describe it).
I’d really like to get rid of the main Echolink hub pc, which a club member is hosting, and just have the ASL-based Echolink node, but the audio quality is not there yet. Anyone know of a cheap Windows VM hosting service, similar to the <$20/yr Debian offerings, so I can build a hosted Windows PC for the Echolink hub, and just link it back to the ASL VM node?
Eric
K2CB
the last update fixed this issue for us, but here is an interesting question when you set the audio levels did you do it with a service monitor, or just by ear. The issue may be that your main output is overmodulating, but you dont notice because the input level from anyone local is set low. Just a thought.