Salve Francesco, It would be very useful to retain the functionality of the detectsilence filter -- 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.
Detecting whether a file is entirely silent is an easier problem, 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. Dave On Thu, 7 Jun 2007, Francesco Romani wrote: > On 5/30/07, Cyrus A <[EMAIL PROTECTED]> wrote: > > Thanks a million. That would be great. This would solve an issue that > > has caused me headaches for over a year now. > > Ok, here it is. It has took a bit longer than expected due to > ever-standing real life work issues and due to needed refactoring that > this task has pulled in. Anyway. > filter_astat in CVS HEAD (should) can now detect if an audio track is > silence only. > Just use > transcode -i file -a X -J astat > > Euhrystic implemented is a bit harsh, maybe it still needs some > extensions/tuning. Can't do it now, but It's planned before 1.1.0 > released. Feedback very-welcome. > > filter_detectsilence can do a stuff like that as well, but is > trickier. In practice, filter_detectsilence really detects the silence > *intervals* between audio chunks (useful to separate songs or track > parts, for example). Of course, if a silence interval is very long, > one can assume that the whole audio track is silence only, but isn't > so straightforward. > > I think the best way is to extend further filter_astat, and that's the > way I will go. > > None of those features will be backported to 1.0.x in any foreseable future. > I'm sorry for that, but that is due ever-standind time lacking. > Anyway, patches welcome. ;) > > > By the way, I'm using the freshrpms version of transcode. I couldn't get > > 1.0.3 to compile on my machine. > > It would nice to see the errors; start a new thread if you like. > > Bests, > >
