On Sun, Aug 21, 2011 at 3:14 PM, Peter Retep <[email protected]> wrote: > i have updated our production system with using the %wav parameter with > duration=3600.0 . > When I checked recorded WAV files , I found out that duration is 40 or 80 > milliseconds longer than expected:
Hi Peter, Unfortunately, this was to be expected... I was surprised in the first place that such a simple solution was sufficient. I suggest we start thinking about a more robust solution, like finding a clean way to call an external program to write the duration of the recorded WAV. An obvious possibility is to add an on_close param to output.file(). I'd like to avoid it if existing mechanisms allow it already. It seems that on_start/stop won't be enough here... Anybody sees the beginning of another solution? I don't have time to code right now, but let's try to get this moving. Cheers, -- David ------------------------------------------------------------------------------ Get a FREE DOWNLOAD! and learn more about uberSVN rich system, user administration capabilities and model configuration. Take the hassle out of deploying and managing Subversion and the tools developers use with it. http://p.sf.net/sfu/wandisco-d2d-2 _______________________________________________ Savonet-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/savonet-users
