|
|
|
I am having the same problem in the new release also. Several times a day. Clear cache , relogg, clear cache again, restart computer and sometimes helps. but please resolve
Same thing is happening to me when I cross regions around my estate, I've noticed that it happens less when you teleport between regions.
I've been without voice for several weeks, apparently coinciding with the 1.22 viewer release. I just went back to 1.21.6, and voice is working with that viewer. This is happening on both a MacBook Pro and a Mac Pro (both recent machines). I've tried all the recommended fixes, but nothing works. When I tried running SL on my Mac Pro, voice worked for about a minute, then stopped. It's not worked since. I'm assuming that since voice works with 1.21, this is due to a bug in 1.22, rather than something in my configuration or network. I'm running OS X 10.5.6. The symptom is that the Device Settings dialog just says "Please wait", I never get an input level display. There is no dot over my head, and the Talk button is disabled. I can't hear anyone else either, and see no one as voice-enabled.
(later) I spoke too soon. Now voice is failing in the 1.21 viewer. Unlike the 1.22 viewer, the Device Settings works, but it can't connect to in-world voice chat. I updated to the new viewer and I lost my voice. After years of it working fine, now it won't work at all. I have windows xp and windows vista and it is happening on both, even on my desktop and laptops.. My settings say I have voice enabled. I cannot talk in-world or in the private chat.
I have voice problems for weeks now. I cannot record voice anymore with fraps.
Only solution so far (after submitting a ticket I got this tip, and it works till the next log off/on):
Only problem left now is that I cant record voice in fraps, still, even after the described prodedure. Making machinima is seriously limited down for me. Please LL, help.... Ok, i have noticed other possible link of folder for voice dump file in Windows Xp:
I don't know why but i thin this folder is created for vivox log. Hello
i have the same problem i cant voice, Mine happend yesterday after haveing a voice chat with friends i tped home and it just stoped working. i have reinstalled sl many times cleaning cach and registry if i run debug i see this error LLVoiceCient. loginResoinse: Account.Login response failure (401) Account is misconfigerd mismatch web and ser credntials. Please see your customer rep Same here on Gentoo
[16:58] Connecting to in-world Voice Chat... ----------- You are at 249620.2, 246939.9, 558.1 in Stockbridge located at sim377.agni.lindenlab.com (216.82.9.63:13000) CPU: Intel(R) Core(TM)2 Duo CPU E8400 @ 3.00GHz libcurl Version: libcurl/7.16.4 OpenSSL/0.9.7c zlib/1.2.3 c-ares/1.4.0 and the RC too ----------- Built with GCC version 40102 You are at 249633.6, 246944.3, 535.0 in Stockbridge located at sim377.agni.lindenlab.com (216.82.9.63:13000) CPU: Intel(R) Core(TM)2 Duo CPU E8400 @ 3.00GHz libcurl Version: libcurl/7.16.4 OpenSSL/0.9.7c zlib/1.2.3 c-ares/1.4.0 I am behind a NAT, but have other Windows Clients here where SL Voice works fine. So I guess that is not an network problem. The reason this is not reproducible consistently, spread across so many different yet connected problems, and the reason this appears to be occurring for many since the release of the 1.25 and 1.26 server rollouts is because it appears to be a server issue. For the sake of time and completeness of method used to reach this conclusion I shall redirect those having these specific issues to the posts made at the following Jira Entry: http://jira.secondlife.com/browse/VWR-12476
This appears not to be a client side bug, it is one that many across many different OS, viewer, and hardware types are experiencing. I don't think encouraging users to install a Release Candidate viewer as a fix for this issue is the proper solution, however I will not dispute that the issue may be rectifiable client side should the server environment for the Vivox connections had to have been retooled in anticipation of future changes to the client. If this is the case then I would have to say shame on LL for allowing such a bug to begin with, any time they have to change interfaces between client and server side functions they have been very good at making sure that all changes match up. I doubt there is any such retooling here as there would have been need to notify users of the older client that the upgraded viewer would have to be downloaded to retain voice functions and of course LL has made no such claim or notice. It should be noted that RC viewers are not guaranteed to be as stable as the main viewer, nor are the features in them finalized and guaranteed to remain functional or in place by official release time. Downloading the RC viewer is for the purpose of testing and bug reporting prior to the official release of the viewer. It is not meant to be a method of fixing bugs which are in current incarnations of the viewer or server software. I appreciate the effort to collect these issues into a central location Ella but this is not fixable with the blanket approach this particular entry seems to take. In this case it seems that the wide range of voice issues recently and the variety of the steps taken to attempt to fix or reproduce these issues points more to a server issue than anything else. That having been said I am sure LL knows of the issue and is attempting some sort of fix for users affected by it, at least one can hope that this is the case. I would not claim that the new RC will fix the issue, and after having read your suggestions and having already performed the very same actions more than once or twice since server 1.25 and 1.26 rollouts as well as using the newest viewers and even going so far as to test third party viewers which were previously fine I have simply been unable to fix the issue with any kind of consistency. Submitting tickets in this case will most likely not resolve the issue, however adding things to this Jira can help as it is used by Linden Labs Quality Assurance to help identify, locate, and rectify major issues. I am going to say with the number of issues regarding voice it is well likely that Linden Labs QA is already taking a look at these entries and trying to track it down. After having tried several fixes, including one proposed by yourself Ella, I have come to the conclusion that until the server side is again updated this intermittent and seemingly random problem will continue. Best course of action is to post the about SecondLife data and client log files in Jira under your appropriate issue or even one such as this in order to obtain data which may be used to more effectively pinpoint the problem(s). It's not a viewer problem - I get the same with the RC viewer, all the recent SL official ones, and the Emerald viewer. Is it related to FMOD by any chance? World of Warcraft forums are also reporting this problem, and they also use FMOD. Would LL recompiling using the latest FMOD library solve the problem?
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
 |
|
Meta Issue
Open
Major
Meta-Issue: Voice Issues with Viewer 1.22
EDIT Second Life 1.23.0 (118378) Apr 24 2009 14:24:08 (Second Life Release Candidate) has been released.
There have been a number of fixes for Voice issues in the 1.23 Release Candidate. If you would like to try the Test Viewer, it can be downloaded from here Test Viewers Release Candidate
Please see Release Notes/Second Life Release Candidate/1.23
and pJIRA Issue Navigator Search "1.23 Release Candidate" for Known Issues. [ Please note Issues
VWR-12962,VWR-13051&VWR-12899]------------------------------------------------------------------------------------------------------------------------
EDIT from Release Notes/Second Life Release Candidate/1.22
Known Issues
Occasional reports of problems with SL Voice on Mac and Windows
We're still tracking these issues, but continue to have difficulty consistently reproducing them. If you happen to experience any of the following problems, we would appreciate your help in documenting the circumstances in which they occur:
1.
VWR-12010[c]: Spatial Voice Chat remains in the previous region after a TeleportIf you experience this problem, please add a comment to
VWR-12010describing your in-world location and details about how long you were in-world.2. VWR-12023[c]: After a viewer crash, Voice options and Talk button stay disabled on next relog
We only have anecdotal reports of this occurring from our early Resident testers. Please add your comments if it happens to you.
3. VWR-12024[c]: On some SL accounts, your first login takes 2-3 minutes to connect to Voice
We only have anecdotal reports of this occurring from our early Resident testers. Please leave your comments if it happens to you.
4. VWR-12025[c]: If you reset Voice during a 1-on-1 Voice call, the viewer may show you "stuck" in the call even if you return to spatial Local chat
We have improved this behavior, but still observe some reports on Mac and Linux. Please leave your comments in the JIRA if it happens to you.
Possible continued problems with Audio and Voice on Linux (introduced in RC8):
3. VWR-12136[c]: Voice quality on Linux can be poor (a pulse of crackly noise) with Intel Audio chips, such as Intel ICH7 and ICH8.
We are investigating bugs in the voice SDK which degrade the quality of voice on some systems
For reporters with this issue please make sure you have
How to Use Voice
Voice FAQ
Can I use voice from behind a firewall?
If you still have an issue, please add your comments and vote on an existing issue or create a new issue and comment on
Your comments will help the LL Developers investigate this issue
Thank you : )