I'm going to scream!

[JulietAlpha]

Not that anyone would hear it. My comms are "extremely broken and unreadable"

I've tried three headsets, built in mic, external boom mic, resetting the router, rebooting x-plane, rebooting VSPro, rebooting my computer, yelling at the moon and animal cruelty...and nothing has worked, every time I hit PTT I get "aircraft calling you're extremely broken and unreadable"

Does ANYONE have any suggestions?

[Keith Smith]

I can do a screen share with you later next week after I return from a trip.

we only require a little upstream bandwidth, doubt that is the issue.

Will be curious to see what the cause is.

[Andrew Doubleday]

I'm wondering if maybe it could be a directsound vs wave thing possibly?

[Ryan Geckler]

I was the one today telling you that... I'd literally hear about two garbled words before it became silence. Could be a bandwidth issue, or potentially a firewall issue (Keith)?

[Alex Stjepanovic]

If you were N45XS at SNA yesterday, then yes, you were broken on about 4-5 instances that you tried.

[Keith Smith]

Try installing TeamSpeak 3 and connecting to our server (pilotedge.net), I don't think a password is required. PM one of the controllers in the controlling rooms and ask if they can come up for a quick voice check. Let me know the result.

[JulietAlpha]

I tried a few times with different aircraft. I've noticed the PA-24-250 for whatever reason does not receive ATIS or transmit comm 1. Kind of strange, something I'll check into on the backside after I get this first issue worked out.

I do know for a fact that bandwidth isn't the issue with 15Mbps down/2Mbps up 50ms to a cross-country server, 0 packet loss and low jitter.

My guess is firewall, because as you know I had no comm issues when I first started out and worked through I-10 but I now have a new OS that may have a back end issue with VSPro.

[JulietAlpha]

Ok, I got on TS and with Alex's help, we checked comms on TS and in game. TS was just fine, however I did get this warning while online:8/26/12 12:58 PM Core Audio Warning RenderGetData::getData called while it had no data (sound buffer underrun)

In game, same issue, chop then silence.

I checked, all firewalls are off. There's no security protocols in place.

[Ryan B]

What about recording a simple .wav file within Windows Sound Recorder? Can you do it successfully?

START button ->Run->SoundRecorder.exe

Are you running onboard sound?
If so what motherboard? - >Do you have latest drivers?
If not what card and same question as above...

What about your OS, which version? What are you firewall settings? Do you happen to have an anti virus program like crappy Norton Security Suite (which also runs a firewall)?

Go to Control Panel\All Control Panel Items\Sound -> Recording tab: Does it light up when you talk into it?

I'm wondering if maybe it could be a directsound vs wave thing possibly?

This is also what I'm thinking. However, in PE software the options are disabled afaik... at least mine are blank. In SB4 for vatsim I've had to switch mine around to get it work. Also I recently setup a friends' comms in SB4 and it was a nightmare like this poor animal cruelty guy is dealing with, and I ended up changing those settings. Mine is set up INPUT: Direct Sound, OUTPUT: Wave

[JulietAlpha]

Ryan pointed out that everyone assumed I was on a Windows PC. Just thought I'd mention I'm on a mac running OS X 10.8 Mountain Lion.

I have used PE before, and after the update I haven't been able to use it. I'm not sure if my OS upgrade is the difference.