Kaine Avon

Basically my viewer doesn't even detect a headset it just detects the conexant built in mic on my computer. My computer doesn't even register a headet either, it is labled as conexant as well with my headset plugged in that's pretty much what i'm stuck with even with the headset plugged in. I have tried accessing the input and output devices in voice setup but unfortunately the viewer doesn't even access my microphones. It just tells me to please wait while it tries to connect to my microphones. I tried the most recent SL viewer and Firestorm with my built in microphone and my headset mic. Both voice boxes are greyed out I am unable to use them.

I have. Skype works just fine, and i'm not so sure if the newest build from sl will make a difference but I can give it a shot.

When I meant I had this problem before, it wasn't in reference to the voice morphing into distortion on its own. It was voice suddenly not deciding to work randomly for days at a time before. Now I did not say anywhere that this was a problem SL is causing, because if it was, several others would have my same exact issue and I haven't come across anyone that has. It is obviously something on my end that doesn't agree with the viewer but IF I KNEW how to fix it, I wouldn't be here asking for help. Yes I was initially irritated as any regular person can be, especially when they are not tech savy. I'm not making an excuse for how I came off, it was crappy. But all I want is help, please. When those problems happened I had a different PC AND headset. The computer I have now is a Toshiba Satellite. I did was you said and i'll update my computer information and paste if here for you. ------------------ Operating System: Windows 10 Home 64-bit (10.0, Build 10240) (10240.th1.150810-2333) Language: English (Regional Setting: English) System Manufacturer: TOSHIBA System Model: Satellite S55-B BIOS: 2.00 Processor: Intel® Core i7-4720HQ CPU @ 2.60GHz (8 CPUs), ~2.6GHz Memory: 12288MB RAM Available OS Memory: 12210MB RAM Page File: 4369MB used, 9696MB available Windows Dir: C:\WINDOWS DirectX Version: 12 DX Setup Parameters: Not found User DPI Setting: Using System DPI System DPI Setting: 120 DPI (125 percent) DWM DPI Scaling: UnKnown Miracast: Available, with HDCP Microsoft Graphics Hybrid: Not Supported DxDiag Version: 10.00.10240.16384 64bit Unicode ------------ DxDiag Notes ------------ Display Tab 1: No problems found. Sound Tab 1: No problems found. Sound Tab 2: The file xspltspk.sys is not digitally signed, which means that it has not been tested by Microsoft's Windows Hardware Quality Labs (WHQL). You may be able to get a WHQL logo'd driver from the hardware manufacturer. Input Tab: No problems found. -- I'll copy down the sound driver devices if that helps. Description: Microphone (Conexant SmartAudio HD) Default Sound Capture: Yes Default Voice Capture: Yes Driver Name: CHDRT64.sys Driver Version: 8.65.0036.0000 (English) Driver Attributes: Final Retail Date and Size: 3/24/2014 15:28:56, 1455808 bytes Cap Flags: 0x1 Format Flags: 0xFFFFF -- The headset I have is Sennheiser game ones. http://en-us.sennheiser.com/gaming-headset-game-one . The Mic plugin port is a regular headset plugin, not a usb at all. I have to use an audio/mic splitter cable to use this headset. I had windows 8 automatically installed on the pc when it was bought and this problem did not persist on Windows 8 at all. MY last topic was also in 2012 alittle over 3 YEARS AGO. Could you please cut me some slack, I get it I get frustrated with technology at times when I cannot seem to understand my problem. I'm sorry that I don't have too much patience with application issues when I have other priorities in my life to deal with. So how about I apologize for being impulsive, brash, and rude, and you can cut some slack please????

Could you not reply unless you have something helpful to actually say?

Ever since Windows updated to Windows 10 I have had a ridiculous problem with voice. My voice was distorted and sounded like a low demonic voice, which annoyed me, and users around me. Now the suggestion made by a user here was that SecondLife had a bitrate compatibility issue with windows if the Microphone is set to Channel 2 48000 HZ which is the default for most users. The fix was to change it to bitrate Channel 2 44100 HZ and problem solved. This didn't do anything but grey voice out. Now I tried several clean re-installs, turning off and turning back on voice and nothing. My pc then notified me days later of an update for my sound drivers. So I accepted and downloaded them. I logged back onto Secondlife and nothing worked, not changing bitrates, not restarting my pc, nothing. My viewer was Firestorm latest release 4-7-3-47323. My computer Specs are Operating System: Windows 10 Home 64-bit (10.0, Build 10240) (10240.th1.150810-2333) Language: English (Regional Setting: English) System Manufacturer: TOSHIBA System Model: Satellite S55-B BIOS: 2.00 Processor: Intel(R) Core(TM) i7-4720HQ CPU @ 2.60GHz (8 CPUs), ~2.6GHz Memory: 12288MB RAM Available OS Memory: 12210MB RAM Page File: 4369MB used, 9696MB available Windows Dir: C:\WINDOWS DirectX Version: 12 DX Setup Parameters: Not found User DPI Setting: Using System DPI System DPI Setting: 120 DPI (125 percent) DWM DPI Scaling: UnKnown Miracast: Available, with HDCP Microsoft Graphics Hybrid: Not Supported DxDiag Version: 10.00.10240.16384 64bit Unicode ------------ DxDiag Notes ------------ Display Tab 1: No problems found. Sound Tab 1: No problems found. Sound Tab 2: The file xspltspk.sys is not digitally signed, which means that it has not been tested by Microsoft's Windows Hardware Quality Labs (WHQL). You may be able to get a WHQL logo'd driver from the hardware manufacturer. Input Tab: No problems found. -- Here's my sounddrivers if that helps. Description: Microphone (Conexant SmartAudio HD) Default Sound Capture: Yes Default Voice Capture: Yes Driver Name: CHDRT64.sys Driver Version: 8.65.0036.0000 (English) Driver Attributes: Final Retail Date and Size: 3/24/2014 15:28:56, 1455808 bytes Cap Flags: 0x1 Format Flags: 0xFFFFF The system upgraded to Windows 10. I see other users using 10 without problems. I have had problems like this with voice in the past when it randomly started working again, right now I do not have any patience to deal with this. I'm extremely displeased that I cannot access the same features offered to all users of SL that have an equal right to use. I would really appreciate a fix if someone has one to offer. ---- Edit: I understand that I come off as un-warrantingly irritated. But a majority of whom I communicate with on Secondlife use voice. I'd say 95% of my friends do. To not be able to hear them at all is extremely frustrating. I also have to speak up on voice to get their attention, if I just IM them i'll be ignored unless I actually say something to them. But now I cannot hear anyone. I have sat down, filed out this to Jira and everything. I don't know if this is Vivox's problem or Linden Labs but I really just want help. That's all I'm asking for .... :<

I have a windows 7 home premium 64 edition Samsung Netbook labtop. I have used SL for a while now and had gotten tired of how badly it lagged. Now voice had worked JUST FINE when I used it on SL viewer. Now I switched yesteray to Phoenix and voice has not worked for 1 second. The voice chat button is greyed out even though it's enabled and the white voice indication dot is missing! I have voice enabled in my preferences and used the debug settings for Cmdlinedisablevoice and set it to false to enable voice. I even checked this page http://wiki.phoenixviewer.com/doku.php?id=voice and tried several solutions on it. EVERY ONE who has had voice issues has been sent to that page and had their problems resolved yet no one points out what is specifically WRONG. I checked bandwith and compatablility! I don't know if I did the directions right but I tried several times. I have relogged, rebooted, but I have not reinstalled. I seriously need some help with this, for 2 days now this has not been fixed! Someone help me please!!! DO NOT REFER ME TO THE PHOENIX VOICE HELP PAGE SINCE I ALREADY TRIED OPTIONS THERE. IT would only cause me a GREATER HEADACHE to be pointed there without a SPECIFIC SOLUTION.