A couple observations; I wonder if anyone else has noticed these, or if I'm forgetting something important. This is with app_rpt version 0.254:
ID's:
If someone is long-winded (I've noticed this only with incoming links on Echolink, so not sure if it can be generalized), the standard ID plays over whoever is talking, even if talkover ID is set. So, I have a sound file for my regular ID, and a morse string for talkover ID. If the voice ID starts and someone keys up, as expected, the morse ID takes over. However, if polite ID expires and some ratchet jaw is still ratchet jawing I guess, the regular ID, rather than the talkover ID, plays.
Macros:
Apparently, macros at least don't like having the digits A, B, C, or D in them, nor do they appear to like being started with a 0 digit. I just thought of this, does the leading 0 indicate a shortcut everywhere (i.e. "last connected node), or is that just for connect/disconnect?
Any light that might be shed on this stuff is much appreciated.
Thanks,
···
--
Buddy Brannan, KB5ELV - Erie, PA
Phone: (814) 860-3194 or 888-75-BUDDY
With 0.255 I have observed that the talk-over Morse ID is rarely
heard any more. This includes people talking on the local machine.
Back with 0.213 I remember we would hear the voice ID
only if there was no signal on the input.
Another oddball thing related to voce ID is that, if you have the
timeout timer disabled it still plays the voice timeout message and ID
(although it does not drop the PTT). This was in earlier versions too.
Ken
···
-----Original Message-----
From: app_rpt-users-bounces@qrvc.com [mailto:app_rpt-users-
bounces@qrvc.com] On Behalf Of Buddy Brannan
Sent: Tuesday, July 20, 2010 10:54 PM
To: App_Rpt Mailing List
Subject: [App_rpt-users] Macros and ID's
Hi,
A couple observations; I wonder if anyone else has noticed these, or if
I'm forgetting something important. This is with app_rpt version 0.254:
ID's:
If someone is long-winded (I've noticed this only with incoming links
on Echolink, so not sure if it can be generalized), the standard ID
plays over whoever is talking, even if talkover ID is set.
well, thats really strange. I just tested the polite id thing (on 0.255).
I start Asterisk. Ker-chunk the system (on the input freq) . It starts voice id.
I key up on the input freq and it goes to morse (polite) id. Whats the problem?
···
From: ke2n@cs.com
To: buddy@brannan.name
Date: Wed, 21 Jul 2010 04:45:45 -0400
CC: App_rpt-users@qrvc.com
Subject: Re: [App_rpt-users] Macros and ID’s
With 0.255 I have observed that the talk-over Morse ID is rarely
heard any more. This includes people talking on the local machine.
Back with 0.213 I remember we would hear the voice ID
only if there was no signal on the input.
Another oddball thing related to voce ID is that, if you have the
timeout timer disabled it still plays the voice timeout message and ID
(although it does not drop the PTT). This was in earlier versions too.
Ken
-----Original Message-----
From: app_rpt-users-bounces@qrvc.com [mailto:app_rpt-users- bounces@qrvc.com] On Behalf Of Buddy Brannan
Sent: Tuesday, July 20, 2010 10:54 PM
To: App_Rpt Mailing List
Subject: [App_rpt-users] Macros and ID’s
Hi,
A couple observations; I wonder if anyone else has noticed these, or if
I’m forgetting something important. This is with app_rpt version 0.254:
ID’s:
If someone is long-winded (I’ve noticed this only with incoming links
on Echolink, so not sure if it can be generalized), the standard ID
plays over whoever is talking, even if talkover ID is set.
okay… I set the idtime=1000 for testing purposes. I started Asterisk. Ker-chunked the input freq and heard the
normal voice id. After that was done, and the repeater Tx had stopped, I keyed-up on the input freq and kept
the signal there for a little while and then heard the morse ID, just like I would expect.
the part that does not seem to work, the same as before, is when somebody has the repeater already keyed up at the time an ID is needed. Instead of Morse, it talks all over the QSO in progress (impolitely). I had assumed I made some mistake somewhere when I heard this … The timeout message (with voice ) ID also talks on top; but that is probably OK - except when you have allegedly disabled the time out …
kinda noticing the same thing here.
I IAX into the site, and when I kerchunk, after a period of no activity, it runs the ID (voice or cw- I tried both to see what was up), then it runs it again. Have not put my finger on it yet, but it will run it
okay… I set the idtime=1000 for testing purposes. I started Asterisk. Ker-chunked the input freq and heard the
normal voice id. After that was done, and the repeater Tx had stopped, I keyed-up on the input freq and kept
the signal there for a little while and then heard the morse ID, just like I would expect.
the part that does not seem to work, the same as before, is when somebody has the repeater already keyed up at the time an ID is needed. Instead of Morse, it talks all over the QSO in progress (impolitely). I had assumed I made some mistake somewhere when I heard this … The timeout message (with voice ) ID also talks on top; but that is probably OK - except when you have allegedly disabled the time out …
well, thats really strange. I just tested the polite id thing (on 0.255).
I start Asterisk. Ker-chunk the system (on the input freq) . It starts voice id.
I key up on the input freq and it goes to morse (polite) id. Whats the problem?
No, that's correct behavior, as I stated, and mine acts like that as well. The problem is if a transmission (at least, from the Echolink side, I suspect it doesn't matter) is ongoing, the polite ID timer expires, i.e. the time after the regular ID, and an ID triggers while a transmission is ongoing, the regular, rather than the talkover ID plays. In other words the transmission has to be occurring when the ID triggers, not picking up in the middle of an ID.
···
On Jul 21, 2010, at 10:59 AM, Jim Duuuude wrote:
--
Buddy Brannan, KB5ELV - Erie, PA
Phone: (814) 860-3194 or 888-75-BUDDY
> From: ke2n@cs.com
> To: buddy@brannan.name
> Date: Wed, 21 Jul 2010 04:45:45 -0400
> CC: App_rpt-users@qrvc.com
> Subject: Re: [App_rpt-users] Macros and ID's
>
> With 0.255 I have observed that the talk-over Morse ID is rarely
> heard any more. This includes people talking on the local machine.
> Back with 0.213 I remember we would hear the voice ID
> only if there was no signal on the input.
>
> Another oddball thing related to voce ID is that, if you have the
> timeout timer disabled it still plays the voice timeout message and ID
> (although it does not drop the PTT). This was in earlier versions too.
>
> Ken
>
>
>
> > -----Original Message-----
> > From: app_rpt-users-bounces@qrvc.com [mailto:app_rpt-users-
> > bounces@qrvc.com] On Behalf Of Buddy Brannan
> > Sent: Tuesday, July 20, 2010 10:54 PM
> > To: App_Rpt Mailing List
> > Subject: [App_rpt-users] Macros and ID's
> >
> > Hi,
> >
> > A couple observations; I wonder if anyone else has noticed these, or if
> > I'm forgetting something important. This is with app_rpt version 0.254:
> >
> > ID's:
> >
> > If someone is long-winded (I've noticed this only with incoming links
> > on Echolink, so not sure if it can be generalized), the standard ID
> > plays over whoever is talking, even if talkover ID is set.
>
> _______________________________________________
> App_rpt-users mailing list
> App_rpt-users@qrvc.com
> http://qrvc.com/mailman/listinfo/app_rpt-users