What does a synchronization unit become when it no longer has its own audio segment?

Abierto
#327 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
48/100
Tipo de issue
Documentación
Claridad
Bien especificado
Estado de actividad
Activo

Línea de trabajo

Read the glossary and docs/architecture/conversion.md, then compare the current model with ADR 0022 and the other relevant ADRs. Produce a sized list of terminology, timing, failure/retry, saved-position, and ADR impacts for the go/no-go; do not design the build. The issue identifies this as part of issue #320.

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

Descripción

wayfinder:grilling

Question

What does a synchronization unit become when it no longer has its own audio segment, and how big is that change?

Today each synchronization unit has its own narration chunk and audio segment and starts in the narration track at the sum of the preceding segments' durations; the audio segment is the unit of synthesis, storage, settlement and duration reservation (ADR 0022); a listening position is a unit and an offset within its audio; a finally failed segment has no audio and is marked in the text. Decoupling makes a narration chunk span several synchronization units. Walk the glossary and Conversion and decide, without designing the build:

  • what the glossary terms become (narration chunk, audio segment, synchronization unit, segment, narration track, listening position, duration reservation), and whether any new term is needed or avoidable;
  • where unit start times would live and who computes them;
  • what failed-segment marking and retries mean when one audio segment carries several segments;
  • whether listening positions saved under the current model stay valid;
  • which ADRs it would contradict or supersede.

The answer is a sized list of what would change, as input to the go/no-go, not a spec.

Part of Map: decouple speech synthesis from synchronization units.

Lenguaje dominante
TypeScript
Estrellas
1
Forks
0
Métricas de merge de PR
Sin PR fusionados en 30 d

Preparar el entorno

Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.

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 patricktree/cup

Todos los issues de patricktree/cup

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.