Don't know for sure what the problem is, but the last 2 -3 times I've used P2ATC I have to repeat 95% of my calls at least 2-3 times and sometimes I just can't get thru.  I keep getting "aircraft calling (whoever) please repeat with your call sign."  I can make the call with my call sign and make what ever statement I need to make and then I go thru it all over again.  Thought it was maybe a mic problem, so I went thru setting up my mic again.  Didn't work.  So I went thru the speech recognition, still same problem.  I'm really frustrated now.  Never had this problem before.  Can someone give me a clue as to what I'm doing wrong?  BTW, I know it's there but I hate using "say it".  I have reviewed the calls in the "say it" program I have been having problems with to correct my speech, but it still isn't helping.  Any help would be greatly appreciated.  I've grown so used to using P2ATC that I really don't enjoy flying much w/o using it anymore.  Thanks for the help.

Rodger
 

Rodger,

Two possible  causes come to mind.  The first, as you suspected is the mic or the quality of the sound coming from the mic.  To ensure a clear signal is coming through, go to the Grammar Help screen an say a practice phrase.  Then press the "Replay" button and see if your voice is loud and clear.  If not, then go back to checking the mic settings.

If the Replay is clear, then it could be a faulty CallSign that the program is not interpreting correctly.  If you email me a screenshot of your Config screen where the call sign is set, I'll have a look.   Email to me at [email protected].

Dave

I am having exactly the same issue. It did work for me then recently just would not recognise my call sign. It initially was an airline call sign Skyways 174 (Our VA callsign). I tried changing it to a GA aircraft: - Cessna GJMM, but it still asks me to use a proper call sign. Have this evening done a re-install of P2A - same result! All I can do at the moment is to use sayIT. This however is not conducive to doing circuits. Not sure what I can do. Nothing wrong with my mike - works fine for Skype. I am using the most recent version of P2A. Really want to get this sorted but just not sure what I can change. My call signs must be OK because SayIt recognises it.

John

After more research, I think it is the mike. Going into settings the mike volume was very high. When I reduced it to 50%, P2A suddenly started to recognise the call sign. And I am sure I know what has happened! I think it was the Win 10 update that happened a couple of weeks ago. Win 10 updates have screwed up my settings before, changing default speakers to the monitor's etc. I haven't touched mike settings but I am sure that it is connected with an update altering settings. Anyway it seems to have sorted for me so C130FE check if something like this has happened to your system. I think it is the curse of Win 10 updates!!!

15 hours ago, John_Metcalfe said:

After more research, I think it is the mike. Going into settings the mike volume was very high. When I reduced it to 50%, P2A suddenly started to recognise the call sign. And I am sure I know what has happened! I think it was the Win 10 update that happened a couple of weeks ago. Win 10 updates have screwed up my settings before, changing default speakers to the monitor's etc. I haven't touched mike settings but I am sure that it is connected with an update altering settings. Anyway it seems to have sorted for me so C130FE check if something like this has happened to your system. I think it is the curse of Win 10 updates!!!

Thanks for the information John.  I'm having the opposite problem.  My mic on my headset when I try to set it up is so low that it barely registers.    I'm pretty sure that the volume is so low P2ATC isn't recognizing it.  However, the program says my mic is set up and good to go.  Got the mic problem fixed, now to check it out in P2ATC.  Hopefully it'll work now.

Edited August 29, 20196 yr by C130FE

Still have to repeat almost every call.  Been using the same call sign for a long time with no problem before, so maybe I'll try changing my call sign again.  Running out of ideas.

Sorry to hear the (bad) news. Did Dave come up with any ideas. Although you and I have had a similar issue, it doesn't seem to be coming up as a mainstream issue judging by the posts. 

Be sure that "Do Nothing" is checked on the Sound Communications tab so that the P2A mic is not being muted or reduced in volume when you use other programs for communications.

Also, Windows may recognize your mic as part of a Headset rather than as a mic and separate speakers.  If so, check the Headset levels and be sure they are set correctly.  Also, be sure that if you have a head set mic set as the default Recording/audio input device, you also have the same Headset as the default playback audio device.  Some users have had their mic not work because they had their Speakers set as the playback device.

Dave