文档

​
​

Development

User Acquisition

Monetization

工业

Vivox Core SDK

Vivox Core SDK

此页面不支持所选语言。
Vivox
​
​
Vivox Core SDK
  • Overview
  • Before you begin
  • Get started
  • Release notes
  • Developer Guide
    • Client SDK basics
    • Channels
    • Presence management
    • Messaging
    • Manage audio
    • Couch co-op
      • Couch co-op configuration
      • Couch co-op example workflow
    • Android app development
    • iOS app development
    • macOS app development
    • Windows app development
    • Real-time recording
    • Speech-to-text audio transcription
    • Text-to-speech
    • Troubleshooting
  • Reference
  • Privacy overview
  1. Vivox Core SDK documentation

Couch co-op configuration

Configure couch co-op for local multiplayer.
阅读时间2 分钟
最后更新于 8 个月前

Many Vivox API request and event types include an additional
account_handle
field that identifies a particular user on a device. In those request types, this field is optional; if left unset, the first user who signs in is the default.
注意
No changes are required in the Vivox SDK initialization workflow for the
vx_initialize3()
or the
vx_req_connector_create
request.
To begin a multi-user voice play session, simultaneously sign in multiple users by using the
vx_req_account_anonymous_login
request, with different
account_handle
values specified for each of the different users.
注意
For couch co-op implementations, you receive a unique set of events for each user who is signed in. Use the
account_handle
attribute to differentiate the events for each user. For more information, refer to Network connection state events.
After multiple users are signed in, you must assign them separate render and capture devices. You can design your game to automatically select these devices, or the game can present a UI to allow users to select their specific devices.
  • To enumerate the list of valid devices, use the
    vx_req_aux_get_render_devices
    and
    vx_req_aux_get_capture_devices
    requests.
  • To set the capture and render devices for each user, you must call
    vx_req_aux_set_render_device
    and
    vx_req_aux_set_capture_device
    with each user's account handle to assign specific devices to specific users.
    注意
    This request is required because audio devices are not automatically associated with each user.
Set other device attributes on a per-user basis, such as the mute status, volume, and voice activity detector (VAD) properties, by supplying the corresponding user's
account_handle
in the request type.
You can also add users to their own independent sets of session groups and sessions, or add them to the same sessions. If you add multiple users on the same device to the same session, then use the
vx_req_session_set_participant_mute_for_me
request to locally mute those users to each other so they do not hear an in-channel echo of anyone who is speaking that is physically nearby to them.

Copyright © 2026 Unity Technologies
法律信息隐私政策CookiesDocumentation Terms of Use请勿出售或分享我的个人信息您的隐私选择(Cookie 设置)

“Unity”、Unity 徽标及其他 Unity 商标是 Unity Technologies 或其附属公司在美国和其他地方的商标或注册商标(此处查看更多信息)。其他名称或品牌是其各自所有者的商标。

为方便起见,一些页面是机器翻译的,可能包含不准确的内容。如有信息不一致的情况,以英文版本为准。


    报告此页面的问题