[sldev] VWR-10311 Enabling lip sync by default

[Jamey Fletcher]

Joshua Bell wrote:

> Only if this is critical should this feature be added. IMHO, the 
> discussion on this list has not provided sufficient evidence that adding 
> the "disable lip-sync" feature is warranted. (I'm not saying it isn't 
> warranted, just that I haven't seen the evidence. It's also unclear that 
>   a "don't show lip-sync for anyone I'm looking at" is the desired 
> anti-feature, vs. "don't show anyone lip-sync for my mouthless avatar".)

> FWIW, I'd vote for shoving a checkbox in the Voice Prefs tab, because 
> it's not that cluttered and once a user has fallen into Preferences 
> we've lost the "keep it simple and discoverable" game anyway. :( Like 
> any UI, Preferences will continue to evolve with periodic 
> reorganizations of the content. No app (that I'm aware of) that caters 
> to non-engineers has ever had a stable preferences UI over several 
> iterations.


Well, for preferences UI - I rather like xine's.

However - What would be sufficient evidence that adding the "disable 
lip-sync" feature is warranted?  A vote of users?  I'll add mine in 
here.  A vote on the JIRA?  I need to go look at that - but the JIRA 
only allows votes for, not against.  That's why the Mesh Import topic 
has two JIRA entries.  (I voted against, wanting improved tools to 
manipulate content *in world*, rather than taking yet one more step 
towards pushing the newbie *out* of content creation.  It's bad enough 
that you're stuck working out of the world for texture and audio work - 
once meshes become importable, you can kiss prims goodbye completely.

A proposal for the Linden feature-putting-in team.  You know that poll 
that pops up from time to time on log in?  How about this - any new 
feature suggestion gets put into those polls.  A log of which AV is 
asked (as in who logs in right afterwards) is maintained, and AVs only 
get counted once (maybe by IP, instead of who logs in right 
afterwards?).  After 500, or a 1000 responses to that feature are 
gathered, the summarized response (x said yes, y said no, z didn't 
answer when presented the option) would be posted somewhere - not 
before, to help limit ballot stuffing.  This would give the team basic 
feedback to decide whether to take the next step: actually posting 
information on what the feature/decision is all about, and opening forum 
discussions on it.  *ONLY* after this takes place, does anyone bother 
actually coding it and starting integrating it into the RCs.  That might 
help silence some of the complaints, such as the big foo-rah about 
openspace/homestead SIMs, or the bug-a-boo about the Adults Only areas 
(which topic I'd *REALLY* like to see some data on how much demand for 
it there really was... 1 request each from 50,000 AVs, or 5000 requests 
from 10 AVs?)

Seriously, though - I don't mind a lot of options in the Preferences - 
but I do think it would make it easier to manage for most people if 
there were levels - Beginner, Intermediate, Master, "I know more about 
SL than the Lindens Do"...  The higher you pick, the more options become 
available.  At the highest level, the debug options from the Advanced 
menu (and most of the Advanced menu, in fact) becomes available in 
appropriate sections.  Maybe make them tabs across the top, of the tabs 
along the side windows.  This makes them fairly discoverable, while 
leaving the messy ones out of the way of the people who don't want to 
play with them.