Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

add port name to StreamConfig

Abierto
#557 4 comentarios 3 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
42/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Estancado
Stack tecnológico
rust

Línea de trabajo

Start by reading the StreamConfig definition and the stream creation paths for the JACK and PipeWire backends. Check how those backends name ports and how other backends handle configuration; the issue proposes accepting a caller supplied name and ignoring it elsewhere. Done when applications can choose port names on JACK and PipeWire and existing backends continue to work.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

host - jack host-specific feature

For usability with JACK and PipeWire routing applications like Catia or QJackCtl as well as session managers, it is important that applications can choose their port names. I think this could easily fit into the API of StreamConfig. For backends besides JACK and PipeWire the name would simply be ignored.

As far as I can tell CPAL is the only crossplatform audio library in any language that could do this well because Stream creation is decoupled from stream usage, so the application can create all its ports for other applications to connect to without the CPAL application needing to use every port at the time of creating them. As a comparison refer to this Mixxx bug report about the problems using JACK through the limitations of PortAudio's API. RtAudio has an API to set the JACK port name but it couples port creation with port usage.

Lenguaje dominante
Rust
Estrellas
4k
Forks
554
Merge medio
3 d 3 h
PR fusionados (30 d)
4

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de RustAudio/cpal

Todos los issues de RustAudio/cpal

Issues similares

Más issues de Rust

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.