<div dir="ltr">Thank you all for the suggestions. I'll try these and let you know!<div><br></div><div>Thanks again to the group for you knowledge!</div><div><br></div><div>de K0JSC</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Fri, May 8, 2015 at 5:56 PM, kk6ecm <span dir="ltr"><<a href="mailto:kk6ecm@gmail.com" target="_blank">kk6ecm@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Our MASTR II on Allstar had audio issues... powersupply and bad connections seemed to make it quite acceptable.<br>
<br>
Bob<br>
kk6ecm<br>
<br>
-----Original Message-----<br>
From: <a href="mailto:app_rpt-users-bounces@ohnosec.org">app_rpt-users-bounces@ohnosec.org</a> [mailto:<a href="mailto:app_rpt-users-bounces@ohnosec.org">app_rpt-users-bounces@ohnosec.org</a>] On Behalf Of David McGough<br>
Sent: Friday, May 08, 2015 4:49 PM<br>
To: Tim Sawyer<br>
Cc: app_rpt mailing list<br>
Subject: Re: [App_rpt-users] MASTR III<br>
<br>
<br>
Hi,<br>
<br>
I 2nd Tim's comments that GE hardware generally has very good audio. I've<br>
used Mastr II's, III's and Rangr's with no complaints.<br>
<br>
>From what your describing, I suspect you've got flat audio IN/OUT from the<br>
repeater. As Tim mentioned, check the pre-emphasis and de-emphasis<br>
setting.... And, look out for possible ground loops in the audio chain if<br>
you've got buzzes or low-level distortion.<br>
<br>
<br>
73, David KB4FXC<br>
<br>
<br>
<br>
<br>
On Fri, 8 May 2015, Tim Sawyer wrote:<br>
<br>
> It's been a long time ago but I had a MSTR II base connected to IRLP<br>
which really sounded good. GE generally has good audio so it should work<br>
well if nothing is wrong with the radio.<br>
><br>
> Of course you have to match the filtering to your radio. If using<br>
discriminator audio then deemphasis must be enabled. This could likely be<br>
your missing low end on RX. Sometimes you can tell if the RX filtering is<br>
correct just by making sure all the touch tones decode properly. Bring up<br>
the *CLI> with verbose 3 and play each tone to see if it’s decoded. Be<br>
sure you have good CTCSS filtering (in your radio or voter.conf or even<br>
both) because that will cause TT decode problems without.<br>
><br>
> For TX feeding to a non-mic type input will require preemphasis. If<br>
you are using a mic input, which I recommend, make sure there is not a DC<br>
bias on the mic. An easy way to tell if the TX filter is right is to<br>
connect to a known correctly setup node and listen to the squelch tail<br>
and user audio. The squelch tail will be obviously high frequency<br>
sounding if doubled preemphasized or muddy if emphasis is needed.<br>
><br>
> Okay, so much for general audio filtering information. Now on to RTCM<br>
specifics.<br>
><br>
> The filter settings in the RTCM are a bit obscure. It tries to<br>
automatically do the right thing but it isn’t always what you want. The<br>
RX filter is controlled by the COR Type (menu 13). 13 = 0 assumes<br>
discriminator and thus deemphasizes. 13 = 1 assumes non-discriminator and<br>
thus has no deempahis. There is also a nodeemp setting in voter.conf<br>
which may be needed in unusual situations.<br>
><br>
> The hidden filter trick on TX is setting a CTCSS tone. If you set a TX<br>
tone the RTCM assumes a CTCSS input and thus will preemphasize. With no<br>
CTCSS tone there will be no preempashis. Generally I think the radio<br>
should do the preempashis (and tone encoding) as the manufacture knows<br>
best what their radio should do. But for simulcast or if you just want<br>
AllStar to sent the CTCSS tone then you must feed the radio at a point<br>
where it will not emphasis. You can fake it out if you want emphasis<br>
without a CTCSS tone by setting the txctcsslevel=1 (or other very low<br>
level) in voter.conf.<br>
><br>
> Hope that helps.<br>
> --<br>
> Tim<br>
> :wq<br>
><br>
> > On May 8, 2015, at 10:44 AM, Jeff Carrier <<a href="mailto:k0jsc.jeff@gmail.com">k0jsc.jeff@gmail.com</a>> wrote:<br>
> ><br>
> > Both TX and RX more or less. The RX path lacks a lot of the low end<br>
but is clean. I'm having more trouble with the TX path. I tried DPLX<br>
Line A/B as indicated in the how to but the transmitted audio lacks<br>
fidelity and is missing the low end (both from local and network audio).<br>
It's also slightly raspy and seems to distort if the remote user has a<br>
hotter mic and the deviation exceeds 3 kHz. I know the RTCM can sound<br>
really nice I've got a few paired with motorolas. I had this same issue<br>
with the MASTR II and I would up giving up on that.<br>
> ><br>
> > On Fri, May 8, 2015 at 10:14 AM, Tim Sawyer <<a href="mailto:tim.sawyer@mac.com">tim.sawyer@mac.com</a> <mailto:<a href="mailto:tim.sawyer@mac.com">tim.sawyer@mac.com</a>>> wrote:<br>
> > Please elaborate on ‘really nasty’. Is it the RX side or the TX side?<br>
> > --<br>
> > Tim<br>
> > :wq<br>
> ><br>
> >> On May 7, 2015, at 8:42 PM, Jeff Carrier <<a href="mailto:k0jsc.jeff@gmail.com">k0jsc.jeff@gmail.com</a> <mailto:<a href="mailto:k0jsc.jeff@gmail.com">k0jsc.jeff@gmail.com</a>>> wrote:<br>
> >><br>
> >> I don't want this to sound like a dumb question and I've searched all over with really no luck. I've also tried several things but I'm looking for "clean" audio. I've done this a million times on Motorolas so why doesn't this work on a GE? Does anyone have experience with an RTCM and a MASTR III? I have tried to inject audio into every point I can find in the manual and can't make it sound "right." There is a good write up on repeater builder about interfacing a controller with an M III but when I follow that it sound REAL NASTY. Any tips would be greatly appreciated.<br>
> >> _______________________________________________<br>
> >> App_rpt-users mailing list<br>
> >> <a href="mailto:App_rpt-users@ohnosec.org">App_rpt-users@ohnosec.org</a> <mailto:<a href="mailto:App_rpt-users@ohnosec.org">App_rpt-users@ohnosec.org</a>><br>
> >> <a href="http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users" target="_blank">http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users</a> <<a href="http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users" target="_blank">http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users</a>><br>
> >><br>
> >> To unsubscribe from this list please visit <a href="http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users" target="_blank">http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users</a> <<a href="http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users" target="_blank">http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users</a>> and scroll down to the bottom of the page. Enter your email address and press the "Unsubscribe or edit options button"<br>
> >> You do not need a password to unsubscribe, you can do it via email confirmation. If you have trouble unsubscribing, please send a message to the list detailing the problem.<br>
> ><br>
> ><br>
> > _______________________________________________<br>
> > App_rpt-users mailing list<br>
> > <a href="mailto:App_rpt-users@ohnosec.org">App_rpt-users@ohnosec.org</a><br>
> > <a href="http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users" target="_blank">http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users</a><br>
> ><br>
> > To unsubscribe from this list please visit <a href="http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users" target="_blank">http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users</a> and scroll down to the bottom of the page. Enter your email address and press the "Unsubscribe or edit options button"<br>
> > You do not need a password to unsubscribe, you can do it via email confirmation. If you have trouble unsubscribing, please send a message to the list detailing the problem.<br>
><br>
><br>
<br>
_______________________________________________<br>
App_rpt-users mailing list<br>
<a href="mailto:App_rpt-users@ohnosec.org">App_rpt-users@ohnosec.org</a><br>
<a href="http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users" target="_blank">http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users</a><br>
<br>
To unsubscribe from this list please visit <a href="http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users" target="_blank">http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users</a> and scroll down to the bottom of the page. Enter your email address and press the "Unsubscribe or edit options button"<br>
You do not need a password to unsubscribe, you can do it via email confirmation. If you have trouble unsubscribing, please send a message to the list detailing the problem.<br>
<br>
_______________________________________________<br>
App_rpt-users mailing list<br>
<a href="mailto:App_rpt-users@ohnosec.org">App_rpt-users@ohnosec.org</a><br>
<a href="http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users" target="_blank">http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users</a><br>
<br>
To unsubscribe from this list please visit <a href="http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users" target="_blank">http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users</a> and scroll down to the bottom of the page. Enter your email address and press the "Unsubscribe or edit options button"<br>
You do not need a password to unsubscribe, you can do it via email confirmation. If you have trouble unsubscribing, please send a message to the list detailing the problem. </blockquote></div><br></div>