Nerius Landys, le Sun 12 Dec 2010 23:01:39 -0800, a écrit : > Keep in mind also that there is probably a buffer of sound data that > is a few millisecond "delayed".
> So the logic you found senses > silence, it might stop the output altogether, and in reality it's that > few milliseconds that is lost (the milliseconds of the buffer). > Checking silence in delayed buffer and chopping output in real-time > audio. I know I'm not making much sense, and I'm just guessing. Well, I understand the kind of reason that can lead to wanting what flite_strip_silence(), but that's not a reason for letting that function do so much black magic which reveals being wrong and dropping actually more than just silence. I'm actually wondering whether the function couldn't check that what it drops is actually silence (0s). Samuel -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
