기술 자료

​
​

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
법률 정보개인정보 처리방침쿠키Documentation Terms of Use개인 정보 판매 또는 공유 금지개인정보 보호 선택(쿠키 설정)

'Unity', Unity 로고 및 기타 Unity 상표는 미국 및 기타 지역 내 Unity Technologies 또는 그 계열사의 상표 또는 등록상표입니다(자세한 내용은 여기에서 확인하세요). 기타 명칭 또는 브랜드는 해당 소유자의 상표입니다.

일부 페이지는 편의를 위해 기계 번역되었으며 부정확한 내용이 있을 수 있습니다. 정보가 상충되는 경우, 영어 버전을 우선으로 참조하세요.


    이 페이지의 문제 보고