Hi all , How do you turn off the announcements in allstar? Is there a way to turn their volume down? 73's Harry KC4RPP
How do you turn off the announcements in allstar?
http://ohnosec.org/drupal/node/102
Is there a way to turn their volume down?
When you set the TX and RX levels per instructions the announcements will be the correct level. Please (again) see http://ohnosec.org/drupal/node/48 for all the gory details of setup with chan_usbradio. If you use chan_simpleusb the RX procedure is a bit different: Generate (with a service monitor) a full quieting 1kHz tone at 3kHz dev with no CTCSS. At the OS CLI type radio_tune_menu, adjust the reading for 3kHz. With a RTCM the procedure is pretty much the same except you have nice indicator LEDs right on the RTCM. Transmit is pretty much the same regardless of the interface. Turn of any TX CTCSS. Press *989 to generate the reference test level tone. Then measuring with your service monitor set the dev to 3 kHz. -- Tim :wq On Sep 7, 2013, at 11:19 PM, Harry Romano <hromano@earthlink.net> wrote:
Is there a way to turn their volume down?
On 9/8/2013 1:23 PM, Tim Sawyer wrote:
When you set the TX and RX levels per instructions the announcements will be the correct level.
With all due respect, what is a "correct announcement level" level is up for debate. (I'm not bringing this up to change or start a thread on why one distro is better than another - and I'd appreciate if no one else did either). When I got into this technology, one of my biggest gripes, along with many users, was the level of the telemetry. Allison just stepped on folks, especially if they were a little soft spoken. Of course, this IS with the levels set properly. This is one area where XIPAR has an advantage. In zipper, we can set the Nominal Telemetry Level and the Duck Level. I run -10 dB nominal, and -15 dB duck. With these levels, Allison doesn't blast you out of the water, and if someone (somewhere) has the mic keyed, she's ducked out an additional amount, BUT you can still hear what she is saying - even along with a loud mouth (such as myself). While I refer to "she" (Allison) all telemetry, including CWID's and whatever is controlled by these settings. Thanks, Kevin
I agree that this is a great feature that Xipar has. Also subjective, and I don’t know what they’re doing differently, but I have an easier time with level adjustments with Xipar (the automatic level setting for rxnoise seems to work a bit better), and at least on my radios, audio “sounds” better, better being kind of relative, yes, I understand that. However, it looks like xipar is missing a couple things that main line acide distro has, I mean besides that acid works with Allstar’s autopatch and dial-in service without additional fiddling. Doesn’t appear Xipar has the provision for recording or streaming from app_rpt. Also, it looks like ID pitch and volume are fixed (and a bit lo of my taste), and the echo link channel driver didn’t compile last time I tried a beta of it several months ago. And i at least don’t really need or want Freepbx. So, until or unless Echolink gets worked out along with streaming/recording, I’m sticking with acid, even in spite of some of xipar’s real advantages. -- Buddy Brannan, KB5ELV - Erie, PA Phone: (814) 860-3194 or 888-75-BUDDY On Sep 8, 2013, at 3:40 PM, Kevin Custer <kuggie@kuggie.com> wrote:
On 9/8/2013 1:23 PM, Tim Sawyer wrote:
When you set the TX and RX levels per instructions the announcements will be the correct level.
With all due respect, what is a "correct announcement level" level is up for debate. (I'm not bringing this up to change or start a thread on why one distro is better than another - and I'd appreciate if no one else did either).
When I got into this technology, one of my biggest gripes, along with many users, was the level of the telemetry. Allison just stepped on folks, especially if they were a little soft spoken. Of course, this IS with the levels set properly.
This is one area where XIPAR has an advantage.
In zipper, we can set the Nominal Telemetry Level and the Duck Level. I run -10 dB nominal, and -15 dB duck. With these levels, Allison doesn't blast you out of the water, and if someone (somewhere) has the mic keyed, she's ducked out an additional amount, BUT you can still hear what she is saying - even along with a loud mouth (such as myself). While I refer to "she" (Allison) all telemetry, including CWID's and whatever is controlled by these settings.
Thanks, Kevin
_______________________________________________ App_rpt-users mailing list App_rpt-users@ohnosec.org http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users
On 9/8/2013 4:38 PM, Buddy Brannan wrote:
I agree that this is a great feature that Xipar has. Also subjective, and I don’t know what they’re doing differently, but I have an easier time with level adjustments with Xipar (the automatic level setting for rxnoise seems to work a bit better), and at least on my radios, audio “sounds” better, better being kind of relative, yes, I understand that. However, it looks like xipar is missing a couple things that main line acide distro has, I mean besides that acid works with Allstar’s autopatch and dial-in service without additional fiddling. Doesn’t appear Xipar has the provision for recording or streaming from app_rpt. Also, it looks like ID pitch and volume are fixed (and a bit lo of my taste), and the echo link channel driver didn’t compile last time I tried a beta of it several months ago. And i at least don’t really need or want Freepbx. So, until or unless Echolink gets worked out along with streaming/recording, I’m sticking with acid, even in spite of some of xipar’s real a dvantages. --
You know, what's interesting, is the different focus of the two and how they've developed on parallel, but, in some respects, divergent paths: open source is like that. I think a couple things, from my standpoint, that I'd like to see in acid would be including DCS as an option for coded squelch. IIRC, XIPAR has it. That, and the variable audio level features Kevin described. Other than that? Both are viable, excellent programs that address a need...you pays your money, you takes your chances. So, they're both good; guess it just comes down to what you need to do, how you addressed it with what tools you had at the time, and how much pain it would be to migrate (though, to tell the truth, I'd like to try WN3A's rewrite of one of the codecs...I hear the quality is superb...) Bryan
Rewrite of a codec? Hmm, I’m intrigued. -- Buddy Brannan, KB5ELV - Erie, PA Phone: (814) 860-3194 or 888-75-BUDDY On Sep 8, 2013, at 8:16 PM, Bryan D. Boyle <bdboyle@bdboyle.com> wrote:
On 9/8/2013 4:38 PM, Buddy Brannan wrote:
I agree that this is a great feature that Xipar has. Also subjective, and I don’t know what they’re doing differently, but I have an easier time with level adjustments with Xipar (the automatic level setting for rxnoise seems to work a bit better), and at least on my radios, audio “sounds” better, better being kind of relative, yes, I understand that. However, it looks like xipar is missing a couple things that main line acide distro has, I mean besides that acid works with Allstar’s autopatch and dial-in service without additional fiddling. Doesn’t appear Xipar has the provision for recording or streaming from app_rpt. Also, it looks like ID pitch and volume are fixed (and a bit lo of my taste), and the echo link channel driver didn’t compile last time I tried a beta of it several months ago. And i at least don’t really need or want Freepbx. So, until or unless Echolink gets worked out along with streaming/recording, I’m sticking with acid, even in spite of some of xipar’s real a dvantages. --
You know, what's interesting, is the different focus of the two and how they've developed on parallel, but, in some respects, divergent paths: open source is like that.
I think a couple things, from my standpoint, that I'd like to see in acid would be including DCS as an option for coded squelch. IIRC, XIPAR has it. That, and the variable audio level features Kevin described. Other than that? Both are viable, excellent programs that address a need...you pays your money, you takes your chances.
So, they're both good; guess it just comes down to what you need to do, how you addressed it with what tools you had at the time, and how much pain it would be to migrate (though, to tell the truth, I'd like to try WN3A's rewrite of one of the codecs...I hear the quality is superb...)
Bryan
_______________________________________________ App_rpt-users mailing list App_rpt-users@ohnosec.org http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users
On 9/8/2013 8:37 PM, Buddy Brannan wrote:
Rewrite of a codec? Hmm, I’m intrigued.
Should have said rewrite of tx/rx bandpass filtering rules...We talked about it a little bit while I was working for him a month ago while on the bench. My bad, and fingers worked ahead of my brain, listening to 2 sunday night nets and typing mail messages...sorry... BB
On 9/8/2013 8:37 PM, Buddy Brannan wrote:
Rewrite of a codec? Hmm, I'm intrigued. On 9/8/2013 8:47 PM, Bryan D. Boyle wrote:
Should have said rewrite of tx/rx bandpass filtering rules...We talked about it a little bit while I was working for him a month ago while on the bench.
Actually - you are correct Bryan..... When Jeff DePolo was first getting into this technology, he discovered problems with the receiver input filter. Jeff is a perfectionist, and like me is an audio purist. There is a brief reference to his work (detailed below) in the link I shared: http://www.wanrepeater.com/xipar_urd_filters.doc Here is an email Jeff wrote while testing: /I spent most of today on a hair-pulling excursion to try to find the cause of some really hellacious aliasing distortion through the repeater. I could give you the long story some other time, but the short version is that I found a bug in the rx frontend FIR code where the history buffer is shifted to add a new sample. The line: memmove(x+1, x, nx-1) should be memmove(x+1, x, (nx-1)*2) Gotta move 16-bit ints not bytes. With that corrected, the aliasing distortion dropped immensely as you might imagine. Aliasing-related distortion products are now below -40 dBr as compared to as little as -6 dBr previously! However, I'm still not happy with the audio. I'm seeing 1-2% THD through Asterisk from dongle Rx port to Tx port. That led me down yet another path to quantify the performance of the hardware (DMK Engineering dongle) via my Audio Precision test set, analysis software in Windows (had the dongle connected to an XP machine for testing), etc.. For the most part, it passes, with the basic specs coming fairly close to the specs for the CM108. It still has other issues, but none that would account for the THD that I'm seeing. There's also a problem somewhere that manifests as excruciatingly high distortion below about 450 Hz when the input amplitude is over maybe -6 dBFS (I haven't dug into that deeply yet, but I'm guessing it's an overflow/underflow problem in 16 bit integer math somewhere). That's where I'm stopping for the night. Anyway, thought you'd want to know about the FIR bug if nothing else. Please keep in mind that I'm NOT trying to find faults in your code. I have some perfectionist tendencies, and they really come through when it comes to audio. If you're open to constructive criticism I'll pass along whatever else I find. If not, just tell me to go away and I will. --- Jeff/ Jeff also wrote a followup: /I re-did all of the FIR filters, found a few other bugs along the way, etc. There is still a problem in the preemphasis/deemphasis routines that can result in integer overflows under certain conditions, and I have some other things I want to fix, but I'm going to stop for now until I have some more time to spend on it.// / Ultimately, Jeff went through everything and got it to a state where he was satisfied. I'm fairly sure all of these improvements exist in ACID as well as XIPAR, maybe Dude can verify? Thanks, Kevin
On 9/8/2013 4:38 PM, Buddy Brannan wrote:
I agree that this is a great feature that Xipar has. Also subjective, and I don't know what they're doing differently, but I have an easier time with level adjustments with Xipar (the automatic level setting for rxnoise seems to work a bit better), and at least on my radios, audio "sounds" better, better being kind of relative, yes, I understand that.
I guess it depends on if you are using the audio w-i-d-e-n-i-n-g filter rules. If you are - then they are not relative, but real improvements in audio quality. In zipper, the following apply: rxlpf=x txlpf=x txhpf=x txlpf=x x can be 0, 1 or 2. More info here: http://www.wanrepeater.com/xipar_urd_filters.doc
However, it looks like xipar is missing a couple things that main line acide distro has, I mean besides that acid works with Allstar's autopatch and dial-in service without additional fiddling. Doesn't appear Xipar has the provision for recording or streaming from app_rpt.
Recording and Streaming - sure it does. We record everything and it is streamed on Radio Reference. Contact Brian Burton - KB3ORS for details on this.
Also, it looks like ID pitch and volume are fixed (and a bit lo of my taste),
You have to put in the following in rpt.conf then you can set it however you like. morse = morse Then, adjust the settings in the [morse] stanza.
and the echo link channel driver didn't compile last time I tried a beta of it several months ago.
Not sure - I personally don't do Echolink, but it worked the last time someone else did a new install and connected to WAN.
And i at least don't really need or want Freepbx. So, until or unless Echolink gets worked out along with streaming/recording, I'm sticking with acid, even in spite of some of xipar's real advantages.
That's why there are several distros. IMHO there are two BIG disadvantages currently with XIPAR - No WebTransceiver and no AllMon. So, I run two servers with ACID - all fixed... Kevin
Kevin, Do you mean WAV file recording like ACID does? Recording and Streaming - sure it does. We record everything and it is streamed on Radio Reference. Contact Brian Burton - KB3ORS for details on this. Tony ________________________________ From: Kevin Custer <kuggie@kuggie.com> To: Buddy Brannan <buddy@brannan.name>; app_rpt-users@ohnosec.org Sent: Sunday, September 8, 2013 7:21 PM Subject: Re: [App_rpt-users] announcements On 9/8/2013 4:38 PM, Buddy Brannan wrote: I agree that this is a great feature that Xipar has. Also subjective, and I don’t know what they’re doing differently, but I have an easier time with level adjustments with Xipar (the automatic level setting for rxnoise seems to work a bit better), and at least on my radios, audio “sounds” better, better being kind of relative, yes, I understand that. I guess it depends on if you are using the audio w-i-d-e-n-i-n-g filter rules. If you are - then they are not relative, but real improvements in audio quality. In zipper, the following apply: rxlpf=x txlpf=x txhpf=x txlpf=x x can be 0, 1 or 2. More info here: http://www.wanrepeater.com/xipar_urd_filters.doc However, it looks like xipar is missing a couple things that main line acide distro has, I mean besides that acid works with Allstar’s autopatch and dial-in service without additional fiddling. Doesn’t appear Xipar has the provision for recording or streaming from app_rpt. Recording and Streaming - sure it does. We record everything and it is streamed on Radio Reference. Contact Brian Burton - KB3ORS for details on this. Also, it looks like ID pitch and volume are fixed (and a bit lo of my taste), You have to put in the following in rpt.conf then you can set it however you like. morse = morse Then, adjust the settings in the [morse] stanza. and the echo link channel driver didn’t compile last time I tried a beta of it several months ago. Not sure - I personally don't do Echolink, but it worked the last time someone else did a new install and connected to WAN. And i at least don’t really need or want Freepbx. So, until or unless Echolink gets worked out along with streaming/recording, I’m sticking with acid, even in spite of some of xipar’s real advantages. That's why there are several distros. IMHO there are two BIG disadvantages currently with XIPAR - No WebTransceiver and no AllMon. So, I run two servers with ACID - all fixed... Kevin _______________________________________________ App_rpt-users mailing list App_rpt-users@ohnosec.org http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users
Well we can agree to disagree on Allison's level. I don't find her too loud and none of our group has complained. We do have do have the telemdefault=2 because all the connects and disconnects are annoying at any level. Having said that, I wish ACID had audio ducking not so much for Allison but for links on monitor. It's nice to monitor a link (my two meter repeater from UHF for example) and be able to talk over it and have the link audio duck a few dB. -- Tim :wq On Sep 8, 2013, at 12:40 PM, Kevin Custer <kuggie@kuggie.com> wrote:
In zipper, we can set the Nominal Telemetry Level and the Duck Level. I run -10 dB nominal, and -15 dB duck. With these levels, Allison doesn't blast you out of the water, and if someone (somewhere) has the mic keyed, she's ducked out an additional amount, BUT you can still hear what she is saying - even along with a loud mouth (such as myself). While I refer to "she" (Allison) all telemetry, including CWID's and whatever is controlled by these settings.
participants (7)
-
Brett Friermood -
Bryan D. Boyle -
Buddy Brannan -
Harry Romano -
Kevin Custer -
Tim Sawyer -
Tony KT9AC