Skip to content

Web support #21

Description

@SolarLiner

Problem Statement

Add support for Web Audio.

Proposed Solution

It's unclear what the solution should be.

There are two approaches:

  1. Create a separate module for running in a Web Audio node. This is the better performance option, separates concerns and does not block the main thread (nor competes with it for timeslices).
    However, SharedArrayBuffers are not available unless a specific security context is active; in practice, unless the user can configure the headers the HTTP server sends with the payload that will instanciate the module, this is not available to us.
  2. Schedule the audio callbacks on the main thread at regular intervals, and use a ring buffer to pop audio data from the Web Audio node.
    This approach is available everywhere, and has been used in other projects, but is the cause of performance issues on the web.

Checklist

  • I have searched for existing issues that may be similar
  • I have explained the feature's value proposition
  • I have provided concrete examples

Metadata

Metadata

Assignees

No one assigned

    Labels

    B-WASMIssues regarding the WASM backendP-WebIssues and PRs targetting the WebfeatureNew feature or requesthelp wantedExtra attention is needed

    Projects

    Status
    Todo

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions