Skip to content

Clarifying the goals of cubeb-rs #47

@mitchmindtree

Description

@mitchmindtree

Hi folks! I was made aware of the cubeb and cubeb-rs projects by @padenot after his excellent WebAudio talk at Native Instruments last night. It's exciting to see the Mozilla cross platform audio backend peeking into Rust, I only wish I came across the project sooner.

I am currently one of the main maintainers/developers of the CPAL project, a project that seems to have very similar goals to cubeb though is far less mature and less battle-tested. I am also one of the founders of nannou, a creative coding framework for Rust. We recently received a grant to work on CPAL and improve the state of cross-platform audio in Rust. We've made a few improvements already over the past month or two, but even after the rest of the work we currently have planned we would still be a long way from the exhaustive set of features and backends that cubeb currently supports.

While I think CPAL is making decent progress, cubeb with its experienced team and Mozilla backing has piqued my interest, and I wonder if our efforts would be better combined in cubeb-rs.

This brings me to some questions:

  • Is the ideal goal for cubeb-rs to eventually become a pure-Rust (down to the platform API) port and replacement to the cubeb C++ library for eventual use within gecko? Or is the intention for cubeb-rs to remain as a set of bindings to the C++ cubeb library?
  • Are you interested in seeing cubeb-rs used in projects unrelated to the rest of the Mozilla ecosystem? E.g. as the audio backend for a creative coding framework like nannou? Do you have any interest in non-Mozilla devs contributing?

Thanks for your time!

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions