Your message dated Mon, 23 Sep 2013 05:59:13 +0200 with message-id <20130923035913.GB7700@mraw.org> and subject line Re: Bug#712725: pu: package espeak/1.43.03-2 has caused the Debian Bug report #712725, regarding pu: package espeak/1.43.03-2 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact owner@bugs.debian.org immediately.) -- 712725: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=712725 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: Debian Bug Tracking System <submit@bugs.debian.org>
- Subject: pu: package espeak/1.43.03-2
- From: Samuel Thibault <sthibault@debian.org>
- Date: Tue, 18 Jun 2013 22:30:04 +0200
- Message-id: <20130618203004.GA23978@type.youpi.perso.aquilenet.fr>
Package: release.debian.org Severity: normal User: release.debian.org@packages.debian.org Usertags: pu Hello, A user reported that “using espeak as an emacspeak speech server is basically unusable if you're using pulse, which is kind of the default configuration in wheezy.” (Bug#712629). This happens because the last chunk of the synthesized sample gets lost. A simple solution was found by forcing a flush, see patch below. Would it be OK to upload to wheezy? Samuel Description: Trigger speech start on final chunk of write When espeak is used with pulseaudio, the last part of a line or other chunk is not spoken because pa_stream_trigger needs to get called to start speech. This is called if the buffer is full and writes are not progressing. However nothing calls this for the last part of what's being spoken. The contract for wave_write on the portaudio side seems to start the stream, so do the same on pulse. This patch takes advantage of the fact that calling pulse_free twice in a row with no write causes a trigger. An alternative but larger change would be to refactor that code out of pulse_free. Author: Sam hartman <hartmans@debian.org> --- The information above should follow the Patch Tagging Guidelines, please checkout http://dep.debian.net/deps/dep3/ to learn about the format. Here are templates for supplementary fields that you might want to add: --- espeak-1.46.02.orig/src/wave_pulse.cpp +++ espeak-1.46.02/src/wave_pulse.cpp @@ -731,6 +731,9 @@ size_t wave_write(void* theHandler, char } pulse_write(aBuffer, bytes_to_write); + //trigger + aTotalFreeMem = pulse_free(); + aTotalFreeMem = pulse_free(); terminate: pthread_mutex_unlock(&pulse_mutex);
--- End Message ---
--- Begin Message ---
- To: 712725-done@bugs.debian.org
- Cc: Samuel Thibault <sthibault@debian.org>
- Subject: Re: Bug#712725: pu: package espeak/1.43.03-2
- From: Cyril Brulebois <kibi@debian.org>
- Date: Mon, 23 Sep 2013 05:59:13 +0200
- Message-id: <20130923035913.GB7700@mraw.org>
- In-reply-to: <1376943629.16804.16.camel@jacala.jungle.funky-badger.org>
- References: <20130618203004.GA23978@type.youpi.perso.aquilenet.fr> <20130619084249.GA22077@mraw.org> <1372503365.25916.17.camel@jacala.jungle.funky-badger.org> <1376943629.16804.16.camel@jacala.jungle.funky-badger.org>
Adam D. Barratt <adam@adam-barratt.org.uk> (2013-08-19): > On Sat, 2013-06-29 at 11:56 +0100, Adam D. Barratt wrote: > > Reading through the log for #712629, it appears that the submitter > > no longer believes the patch should be applied. > > Is anything happening with this? Not that I can see. Closing the pu request for now. Mraw, KiBi.Attachment: signature.asc
Description: Digital signature
--- End Message ---