[arm-allstar] Couple quirks with Echolink
Mike Sullivan
kn4imu at gmail.com
Sat Mar 9 17:37:29 EST 2019
I'll have to do that then.. just curious why Echolink via the repeater
sounds so much worse than peer to peer connections. I was wondering if
there was perhaps a codec issue. I'll dig a little further and see what's
going on.
Mike
On Fri, Mar 8, 2019 at 11:39 PM "Doug Crompton via ARM-allstar" <
arm-allstar at hamvoip.org> wrote:
> Mike,
>
> There is no choice of codecs on Echolink and there is also no reason why
> it should sound different using windows vs. Allstar. The only thing
> different would be the interfacing and levels. You really need to setup
> Allstar itself and set the levels there to your repeater. Then if needed
> you can fine tune the Echolink levels in and out with the settings in
> rpt.conf.
>
> To my knowledge you are the first person to complain about the difference
> in Echolink voice quality between the platforms. Granted Echolink does not
> have the quality of Allstar but it is certainly a step above some of the
> digital FM modes. It is also is highly dependent on the source. Some of the
> smart phones using Echolink sound quite good while computer mics and levels
> are all over the place.
>
>
> *73 Doug*
>
> *WA3DSP*
>
> *http://www.crompton.com/hamradio <http://www.crompton.com/hamradio>*
>
> On Fri, Mar 8, 2019 at 9:51 PM "Mike Sullivan via ARM-allstar" <
> arm-allstar at hamvoip.org> wrote:
>
> > Update.. I had to work, sleep, and work agin but I ended up reinstalling
> > the image due to other problems. Couple updates.. I’ve been listening to
> > other users on Echolink and the audio quality is terrible compared to our
> > old PC based setup. When we go peer to peer it’s a lot better. Perhaps
> it’s
> > a codec issue? Is there any way to check/change it for Echolink?
> >
> > If anyone wants to check it out, it’s KG4DVE-R, 975506 on Echolink, 49608
> > on AllStar. All settings for Allstar are default currently, and I haven’t
> > had time to try settinf up
> >
> > I’m also still not able to get the connection messages working when a
> > client connects. I’ve checked the eann setting, it’s correct, but I’ve
> also
> > seen mention of additional settings in the conf files that may need
> added.
> >
> > Mike Sullivan
> >
> > On Wed, Mar 6, 2019 at 22:57 "Rick Harkins via ARM-allstar" <
> > arm-allstar at hamvoip.org> wrote:
> >
> > > I had a similar problem years ago on my first Echolink setup. Awful,
> > muddy
> > > audio. You need to make sure you are getting the proper audio source.
> It
> > > looks like the RIM-Lite is looking for discriminator audio. If you use
> > > speaker audio will not sound right.
> > >
> > > The interface I used had separate pins for discriminator audio and
> > speaker
> > > audio. Changing pins fixed the audio.
> > >
> > > Echolink audio can be as good as any other. There are a lot of nodes
> out
> > > there that don't seem to care about their audio quality, but that's not
> > > necessarily Echolink's problem.
> > >
> > > Rick WØYGH
> > >
> > > On Wed, Mar 6, 2019 at 7:38 PM "Doug Crompton via ARM-allstar" <
> > > arm-allstar at hamvoip.org> wrote:
> > >
> > > > It is eannmode - two n's.
> > > >
> > > > Echolink is certainly lower quality than Allstar but not as bad as
> you
> > > > describe. It should sound the same as it would between two echolink
> > > > clients connected together.
> > > >
> > > > I suspect a lot of your problems are with the controller and
> > interfacing.
> > > > If you connect to the node from another Allstar node and then listen
> to
> > > the
> > > > echolink how does it sound?
> > > >
> > > >
> > > > *73 Doug*
> > > >
> > > > *WA3DSP*
> > > >
> > > > *http://www.crompton.com/hamradio <http://www.crompton.com/hamradio
> >*
> > > >
> > > >
> > > > On Wed, Mar 6, 2019 at 8:34 PM "Mike Sullivan via ARM-allstar" <
> > > > arm-allstar at hamvoip.org> wrote:
> > > >
> > > > > Doug, I've checked the audio peer to peer from the same source and
> > it's
> > > > > fine.. I'm thinking it's just Echolink's poor audio quality period.
> > > > Haven't
> > > > > had a chance to do a single thing with Allstar yet, I wanted to get
> > > > > Echolink functioning since the majority of our users will be
> through
> > > > > Echolink.
> > > > >
> > > > > As far as the announcements, I have that set in the config, but it
> is
> > > > still
> > > > > not announcing for some reason. For clarification, is it
> "eannmode=2"
> > > or
> > > > > "eanmode=2" (one or two N's?)
> > > > >
> > > > > Mike
> > > > >
> > > > > On Wed, Mar 6, 2019 at 5:32 PM "Doug Crompton via ARM-allstar" <
> > > > > arm-allstar at hamvoip.org> wrote:
> > > > >
> > > > > > Mike,
> > > > > >
> > > > > > No idea on the echolink. Is an Allstar link doing the same
> thing?
> > > > > Muffled
> > > > > > audio might indicate you need to enable pre-emphasis or disable
> > > > > > de-emphasis. There is no reason you should have to use notch
> > > filters.
> > > > > You
> > > > > > should check the audio coming out with an amplifier to see what
> it
> > > > sounds
> > > > > > like. Also consider the source of the echolink signal. Is it
> from a
> > > > good
> > > > > > source?
> > > > > >
> > > > > > Echolink announcements are on the node that echolink is attached
> > to.
> > > It
> > > > > is
> > > > > > set by eanmode in the node section it is attached to in rpt.conf
> > > > > >
> > > > > > ;eannmode=1
> > > > > > ; Echolink announcement mode
> > > > > > ; Default: 1 = Say only node
> number
> > > on
> > > > > > echolink
> > > > > > ; connects. 2 = say phonetic call
> > > sign
> > > > > only
> > > > > > on
> > > > > > ; echolink connects. 3 = say
> > phonetic
> > > > > call
> > > > > > sign
> > > > > > ; and node number on echolink
> > > connects
> > > > > >
> > > > > > Remove the semicolon and set the mode.
> > > > > >
> > > > > >
> > > > > > *73 Doug*
> > > > > >
> > > > > > *WA3DSP*
> > > > > >
> > > > > > *http://www.crompton.com/hamradio <
> > http://www.crompton.com/hamradio
> > > >*
> > > > > >
> > > > > > On Wed, Mar 6, 2019 at 4:49 PM "Mike Sullivan via ARM-allstar" <
> > > > > > arm-allstar at hamvoip.org> wrote:
> > > > > >
> > > > > > > All, after a losing battle with using Verizon, we ended up
> > changing
> > > > to
> > > > > a
> > > > > > > cable landline at our tower site. With this, we have no more
> > > > > > > port/connection issues and our node is finally online. I still
> > have
> > > > to
> > > > > > fix
> > > > > > > a bunch of stuff, which is the reason I'm here. We're using a
> > RPi3
> > > > > > > connected to a RIM-Lite designed for the RC210, plugged into
> > Port 3
> > > > > with
> > > > > > > our repeater, a VXR-7000 in Port 1.
> > > > > > >
> > > > > > > First off, the audio coming from the interface is absolutely
> > > > horrible..
> > > > > > > really muffled when going from Echolink to repeater, but fine
> > radio
> > > > to
> > > > > > > radio and radio to Echolink. notch filters do not help. Any
> idea
> > > > what I
> > > > > > can
> > > > > > > do to improve it?
> > > > > > >
> > > > > > > Second.. we have had times where the node will be rebooted, and
> > > when
> > > > it
> > > > > > > reboots it dead keys the repeater for a few minutes until the
> > node
> > > > > > > announces the LAN IP, then after the controller times it out,
> and
> > > > > cancels
> > > > > > > the TO, it will stop.. hasn't done it the past few times, but
> not
> > > > sure
> > > > > > why
> > > > > > > yet.
> > > > > > >
> > > > > > > Also, even though the option is enabled in rpt.conf, the node
> is
> > > not
> > > > > > > announcing when a user connects/disconnects from Echolink.
> > > > > > >
> > > > > > > I'm sure there will be more things that I will find as we go
> > > along..
> > > > > I'm
> > > > > > at
> > > > > > > the tower site currently working on it, so any help is
> > appreciated.
> > > > > > >
> > > > > > > 73 KN4IMU
> > > > > > > Mike Sullivan
> > > > > > > _______________________________________________
> > > > > > >
> > > > > > > ARM-allstar mailing list
> > > > > > > ARM-allstar at hamvoip.org
> > > > > > > http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
> > > > > > >
> > > > > > > Visit the BBB and RPi2/3 web page - http://hamvoip.org
> > > > > > >
> > > > > > _______________________________________________
> > > > > >
> > > > > > ARM-allstar mailing list
> > > > > > ARM-allstar at hamvoip.org
> > > > > > http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
> > > > > >
> > > > > > Visit the BBB and RPi2/3 web page - http://hamvoip.org
> > > > > >
> > > > > _______________________________________________
> > > > >
> > > > > ARM-allstar mailing list
> > > > > ARM-allstar at hamvoip.org
> > > > > http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
> > > > >
> > > > > Visit the BBB and RPi2/3 web page - http://hamvoip.org
> > > > >
> > > > _______________________________________________
> > > >
> > > > ARM-allstar mailing list
> > > > ARM-allstar at hamvoip.org
> > > > http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
> > > >
> > > > Visit the BBB and RPi2/3 web page - http://hamvoip.org
> > > >
> > > _______________________________________________
> > >
> > > ARM-allstar mailing list
> > > ARM-allstar at hamvoip.org
> > > http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
> > >
> > > Visit the BBB and RPi2/3 web page - http://hamvoip.org
> > _______________________________________________
> >
> > ARM-allstar mailing list
> > ARM-allstar at hamvoip.org
> > http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
> >
> > Visit the BBB and RPi2/3 web page - http://hamvoip.org
> _______________________________________________
>
> ARM-allstar mailing list
> ARM-allstar at hamvoip.org
> http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
>
> Visit the BBB and RPi2/3 web page - http://hamvoip.org
More information about the ARM-allstar
mailing list