Open Bug 1210479 Opened 10 years ago Updated 3 years ago

espeak speech service does not output audio

Categories

(Core :: Audio/Video: MediaStreamGraph, defect, P3)

defect

Tracking

()

People

(Reporter: eeejay, Unassigned)

Details

Attachments

(2 files)

I am working on an espeak speech service for b2g that is similar to the current pico service: It uses the MSG via nsSpeechTask by giving it samples, and expecting audio output. Both espeak and pico work almost in identical fashions, but one gives audio and the other does not. A few observations: 1. If I queue two utterances, pico and then espeak, both will be spoken. I assume this is because the first MSG did not go away yet, and it still has the correct driver set. 2. I can't reproduce this on Linux desktop. It only happens on my flame device. 3. After a while of debugging, it looks like pico transitions to the AudioCallbackDriver, while espeak stays in the SystemClockDriver. I suspect this is a timing issue, since espeak is much faster and provides the first audio samples in a much lower latency. 4. Pico gets to CreateOrDestroyAudioStreams a few times with aStream->mAudioOutputs.IsEmpty() being true and returning early. When CreateOrDestroyAudioStreams is first called with espeak, aStream->mAudioOutputs is not empty. Attached are two output from logcat of PRLog and MSG lifecycle prints. Hopefully, this is enough. My WIP espeak patch could be seen here: https://github.com/eeejay/gecko-dev/tree/espeak
Attached file pico_output.txt
This produces audio.
Attached file espeak_output.txt
This does not.
Hi Eitan -- Do you have a deadline for when you need this? Are you totally blocked? (I'm trying to determine the relative priority of this.) I'm currently thinking this is something we can look at in Q1 or early Q2, but I want to check you don't need it sooner. Thanks!
Rank: 25
Flags: needinfo?(eitan)
Priority: -- → P2
This is a legitimate bug, but it is not a high priority because of lack of clarity around b2g and the roadmap.
Flags: needinfo?(eitan)
Opps, pressed the button by mistake. Q2 would be fine.
Mass change P2->P3 to align with new Mozilla triage process.
Priority: P2 → P3
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: