On Thu, 2007-06-07 at 10:12 -0700, David Liontooth wrote: > Salve Francesco, > > It would be very useful to retain the functionality of the detectsilence > filter --
I 100% agree, so filter_detectsilence was untouched on CVS HEAD, just updated and ported to our new plugin infrastructure. Except for obvious bugs pushed into by this process, the filter is expected to work like before. > what I need is getting a detailed readout of the beginning and > end (in seconds) of sequences in an audio file that are silent. Of course > this could be done with the astat filter if that's an easier starting > point. For this specific task detectsilence looks best suited. It's matter to do a bit more tuning for this. > Detecting whether a file is entirely silent is an easier problem, Definitively it is, this is the main reason because I've choosed to extend the astat filter. > though it would be good to have a filter that does it fast -- cutmp3 takes a > long > time to search through a whole file looking for sound, and I use the > shortcut I posted earlier of compressing a file and comparing to expected > file size. OK, so detectsilence needs a bit extra care. No problem for this (except, of course, time). I'll see what I can do this weekend or ASAP. Bests, -- Francesco Romani
