Dirk,

Quite the contrary, the Linden Lab / Vivox relationship is very healthy and we have some interesting new features ready to roll shortly.  There were a few issues in the SDK shipped with the 1.22 viewer that have caused problems for some folks.  One in particular was triggered by very large Friends Lists (800+ calling cards in inventory) so it would likely affect long-term residents like yourself.  That problem (and others mentioned in the Jira you referenced below) should be fixed now in the 1.23RC nightly, soon to be RC0.  If you have questions around functionality or problems with voice in SL, you'll have better luck seeking answers here or at Linden than expecting Vivox to respond.  Please feel free to hit me with an IM or email if you have specific issues or questions you're having trouble getting answers to.  I'll get you the answers.

-- Joe

Black Hat Design wrote:
I agree that Lip Sync be moved out of Beta. It does a fairly decent job when
voice actually works. Unfortunately residents are suffering many voice
issues now (http://jira.secondlife.com/browse/VWR-12487) and these are no
longer triaged as they appear to be third party issues. I have not had much
luck in getting answers from Vivox on the issues currently plaguing SL
residents. I am led to believe that the issue is arising out of a conflict
with the new SDK which was introduced in RC9 of the current release running
alongside the old SDK which many residents are still running since there is
no mandatory update to the viewer at this time.

Currently, if you want stable voice, you can run the old client and suffer
through many of the bugs that are fixed in the current version, or you can
run the new client and go back to using Skype and a stream for inworld
conferences.

Being that Vivox has not been responsive to inquiries, I am curious as to
whether there has been some deterioration in the relationship between Linden
Lab and Vivox.

Dirk Talamasca
[email protected]

Skype: Dirk Talamasca
Yahoo: blackhat
AIM: Black Hat Design
Google: [email protected]

Edited subject.

There's enough information to display green waves of appropriate
intensity above each speaking avatar. That same information can't be
used to control which avatars move their mouths?

On Mon, Apr 20, 2009 at 11:01 AM, Kakurady Drakenar <[email protected]>
wrote:
  
It doesn't do what it's supposed to do, that is accurate lip-synching for
all avatars. All it does is babbling for your own avatar, and all other
avatars at the same time when even only one of them talks, because of the
limitations of Vivox's voice architecture.

Now, if there's a way to have user aware of that caveat, I have nothing
    
else
  
to worry on this issue.

GCat/Kakur

(To Moriz: Sorry for the duplicate, I forgot to choose "reply to all".)

On Mon, Apr 20, 2009 at 11:40 AM, Moriz Gupte <[email protected]>
    
wrote:
  
I also vote for taking lipsynch out of beta. I use it all the time but
have to waste some time telling new users how to enable it. extremely low
client side CPU footprint + does what it is supposed to, no reason not to
move it out of beta IMHO.
R

On Mon, Apr 20, 2009 at 9:24 AM, Mike Monkowski <[email protected]>
wrote:
      
I'd like to see http://jira.secondlife.com/browse/VWR-10311 implemented.
 It's a trivial change. If it requires any shepherding, I'll do it.  I
think it would be appropriate for an "open source" viewer.

Mike
Mm Alder

Rob Lanphier wrote:
        
So, are there other patches in JIRA that seem worthy of making it in
before the first merge window, and are there volunteers to shepherd
those patches through?
          
_______________________________________________
        


_______________________________________________
Policies and (un)subscribe information available here:
http://wiki.secondlife.com/wiki/SLDev
Please read the policies before posting to keep unmoderated posting privileges
  
_______________________________________________
Policies and (un)subscribe information available here:
http://wiki.secondlife.com/wiki/SLDev
Please read the policies before posting to keep unmoderated posting privileges

Reply via email to