brailcom/speechd

Get sound as a binary, not output it to speakers

Open

#348 opened on Jun 11, 2020

View on GitHub
 (1 comment) (1 reaction) (0 assignees)C (86 forks)auto 404
enhancementhelp wantedpriority

Repository metrics

Stars
 (325 stars)
PR merge metrics
 (PR metrics pending)

Description

Hi. I use speech dispatcher as a tts server middleware. I mean I give it text, and it creates sound. Its main part is interfaces: one interface to the client and another one to modules. But as I understand, currently there is no interface for getting sound by a client. I mean I give it text, but the sound created should go not to ALSA/PulseAudio, but to one of codecs installed on a host (i.e flac, but a dummy "codec" returning input should be also present) and the result should be returned to the client that has requested the synthesis. It is useful if we wanna use the sound in other way than directly output it to speakers, i.e. we may send it into a browser (it's my use case), or we may record it into a file.

Contributor guide

Research direction
Explore the speech dispatcher architecture, specifically the output module interface. Look at existing modules (e.g., ALSA, PulseAudio) to understand how to create a new module that returns audio data as binary instead of sending to speakers. Consider using codecs like FLAC or a pass through mode. Then implement the module and add a client API to request binary output.
Tech stack
c
Domain
backendapi
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
Caudio programming
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40