MantisBT - opensim
View Issue Details
0008702opensim[REGION] OpenSim Corepublic2020-05-15 07:482020-05-17 02:44
paul_bacon 
 
normalfeaturealways
newopen 
Ubuntu20.04
0.9.1.0 
 
Standalone (1 Region)
BulletSim
XEngine
Mono / Linux64
6.x
Hippo
0008702: Add setting for voice chat distance
Using Vivox Voice on my server. Voice chat works but I want to be able to simulate an indoor environment where avatars can talk to each other without disturbing others in the same building.

The current voice chat distance is 60m (?), would like to be able to set this to a (much) lower distance, preferably using a setting in OpenSim.ini.
Use voice chat on a voice chat enabled server. Walk to 60 meters from other avatar.
Very new to OpenSim, could not find a way to do this, apologies if this is an existing feature or previously rejected.
No tags attached.
Issue History
2020-05-15 07:48paul_baconNew Issue
2020-05-16 05:41aiaustinNote Added: 0036474
2020-05-16 05:53tampaNote Added: 0036475
2020-05-16 07:37paul_baconNote Added: 0036476
2020-05-16 10:05danbannerNote Added: 0036477
2020-05-16 10:06danbannerNote Deleted: 0036477
2020-05-16 10:08danbannerNote Added: 0036478
2020-05-16 10:13danbannerNote Edited: 0036478bug_revision_view_page.php?bugnote_id=36478#r9041
2020-05-16 14:10paul_baconNote Added: 0036479
2020-05-17 02:44UbitUmarovNote Added: 0036481

Notes
(0036474)
aiaustin   
2020-05-16 05:41   
Hi Paul.. you can limit voice, and other sounds if you wish, to the current “parcel”. Look in the “About Land” tab in the viewer for the parcel you are on.

You can split up regions into any sized rectangular parcels you want to allow this. For example I have a meeting space with a central shared space surrounded by four corner breakout rooms into which sub-groups can go and have separate voice.

See https://community.secondlife.com/knowledgebase/english/managing-your-parcel-r49/#Section__10 [^]
(0036475)
tampa   
2020-05-16 05:53   
I think he is more asking in terms of distance because inside a building with multiple floors you generally can't hear folks talking two stories up. I don't recall there being a setting for voice distance and I suspect this would have to be set either on vivox end or through their service api. I would suggest sending them a mail, but they tend to just ignore them.
(0036476)
paul_bacon   
2020-05-16 07:37   
Ideally there would be a voice distance setting. OpenSim now sets the volume of voice inversely proportional to the distance, which is great and would work even better if the maximum distance could be set (or even configurable shout/talk/whisper distances as can be set for text chat).

@aiaustin: defining parcels is an excellent workaround for what I tried to achieve, thanks for that!
(0036478)
danbanner   
2020-05-16 10:08   
(edited on: 2020-05-16 10:13)
in the [VivoxVoice] section of the OpenSim.ini you can maybe adjust these values

    ; channel type: "channel" or "positional"
    ; - positional: spatial sound (default)
    ; - channel: normal "conference call", no spatial sound
    ;vivox_channel_type = positional

    ; channel characteristics (unless you know what you are doing, i'd
    ; leave them as they are --- now you WILL muck around with them,
    ; huh? sigh)

    ; channel distance model:
    ; 0 - no attenuation
    ; 1 - inverse distance attenuation
    ; 2 - linear attenuation (default)
    ; 3 - exponential attenuation
    ;vivox_channel_distance_model = 2

    ; channel mode:
    ; - "open" (default)
    ; - "lecture"
    ; - "presentation"
    ; - "auditorium"
    ;vivox_channel_mode = "open"

    ; channel roll off: rate of attenuation
    ; - a value between 1.0 and 4.0, default is 2.0
    ;vivox_channel_roll_off = 2.0

    ; channel max range: distance at which channel is silent
    ; - a value between 0 and 160, default is 80
    ;vivox_channel_max_range = 80

    ; channel clamping distance: distance before attenuation applies
    ; - a value between 0 and 160, default is 10
    ;vivox_channel_clamping_distance = 10

(0036479)
paul_bacon   
2020-05-16 14:10   
@danbanner: these look very promising. Changing the parameters however does not seem to have any effect. Using settings below max range remained 80 after a reboot of OpenSim.

Also tried setting vivox_channel_distance_model = 1, no change in behaviour. The settings don't seem to have any effect.


    ; channel type: "channel" or "positional"
    ; - positional: spatial sound (default)
    ; - channel: normal "conference call", no spatial sound
    vivox_channel_type = positional

    ; channel characteristics (unless you know what you are doing, i'd
    ; leave them as they are --- now you WILL muck around with them,
    ; huh? sigh)

    ; channel distance model:
    ; 0 - no attenuation
    ; 1 - inverse distance attenuation
    ; 2 - linear attenuation (default)
    ; 3 - exponential attenuation
    vivox_channel_distance_model = 2

    ; channel mode:
    ; - "open" (default)
    ; - positional: spatial sound (default)
    ; - channel: normal "conference call", no spatial sound
    vivox_channel_type = positional

    ; channel characteristics (unless you know what you are doing, i'd
    ; leave them as they are --- now you WILL muck around with them,
    ; huh? sigh)

    ; channel distance model:
    ; 0 - no attenuation
    ; 1 - inverse distance attenuation
    ; 2 - linear attenuation (default)
    ; 3 - exponential attenuation
    vivox_channel_distance_model = 2

    ; channel mode:
    ; - "open" (default)
    ; - "lecture"
    ; - "presentation"
    ; - "auditorium"
    vivox_channel_mode = "open"

    ; channel roll off: rate of attenuation
    ; - a value between 1.0 and 4.0, default is 2.0
    vivox_channel_roll_off = 2.0

    ; channel max range: distance at which channel is silent
    ; - a value between 0 and 160, default is 80
    vivox_channel_max_range = 10

    ; channel clamping distance: distance before attenuation applies
    ; - a value between 0 and 160, default is 10
    vivox_channel_clamping_distance = 5
(0036481)
UbitUmarov   
2020-05-17 02:44   
We do process those options like in past.
But those are options we just send to viewers and vivox servers.
 I asked Vivox information to review our code, and they refused to provide any. They kinda implied they don't have it, since the versions we use are obsolute and just happen to work on the servers they still provide.
They also refused to provide information about the new APIs
So we can not maintain that code. That code and references to Vivox, will be removed from opensimulator, as soon current solution stops working reliable, unless we get access to proper official documentation