Difference between revisions of "Talk:LlSpeakText"

From Second Life Wiki
Jump to navigation Jump to search
 
(on the FURRY constants and function arguments)
Line 1: Line 1:
How will this handle unicode characters and languages other then english? [[User:Strife Onizuka|Strife Onizuka]] 11:38, 3 April 2007 (PDT)
How will this handle unicode characters and languages other then english? [[User:Strife Onizuka|Strife Onizuka]] 11:38, 3 April 2007 (PDT)
The furry variants are just weird. What exactly is a "furry" voice? Such a thing would have to vary depending on species. For instance, snakes and dragons can be considered to be in the furry (doesn't have to be literally furry) category, cats and mice shouldn't sound the same, etc. [[User:Dale Glass|Dale Glass]] 13:28, 5 April 2007 (PDT)
Also, I think the targets list is unnecessary. This would be a local text to speech converter on the user's computer, so a list of targets wouldn't be necessarily as voice wouldn't be streamed: it'd be a normal chat message that'd get converted at the destination. I'd do the function this way: llSpeakText(list params, string text). Besides the voice there are other things that could be interesting to have such as volume, intonation parameters such as speed and pitch, and anything else that might come up. [[User:Dale Glass|Dale Glass]] 13:28, 5 April 2007 (PDT)

Revision as of 13:28, 5 April 2007

How will this handle unicode characters and languages other then english? Strife Onizuka 11:38, 3 April 2007 (PDT)

The furry variants are just weird. What exactly is a "furry" voice? Such a thing would have to vary depending on species. For instance, snakes and dragons can be considered to be in the furry (doesn't have to be literally furry) category, cats and mice shouldn't sound the same, etc. Dale Glass 13:28, 5 April 2007 (PDT)

Also, I think the targets list is unnecessary. This would be a local text to speech converter on the user's computer, so a list of targets wouldn't be necessarily as voice wouldn't be streamed: it'd be a normal chat message that'd get converted at the destination. I'd do the function this way: llSpeakText(list params, string text). Besides the voice there are other things that could be interesting to have such as volume, intonation parameters such as speed and pitch, and anything else that might come up. Dale Glass 13:28, 5 April 2007 (PDT)