Ulrich Klauer <ulr...@chirlu.de> wrote: > Eric Wong <normalper...@yhbt.net>: > > > In any case, do we agree "soxi -b" showing "0" is incorrect? > > Not necessarily, for codecs using compression, it may be impossible to > say how much space one sample takes, as this may change, or the term > may be inapplicable (e.g., for frequency-domain expression).
For compression, then shouldn't -b be the maximum bits-per-sample decoding the file will give? (which should match precision, I think?) Perhaps there should there be a '-p' flag for show precision in soxi? That would match the "Precision" field when soxi is called without switches... > Regarding the LADSPA patches, I put the memory-leak fixes into dot and > everything into master, except that I distributed some SOX_EFF_* flags > to the commits that require them (*_MCHAN, *_CHAN) and discarded > others (*_RATE, *_LENGTH). From the LADSPA documentation, it seems to > me that there is no way for a plugin to indicate a changed sample > rate, nor to make any changes to the number of samples. Its run() > function is called with a certain number of input samples, and it is > expected to output the same number; there is no possibility to tell > the host of a different number of output samples. I don't think I was 100% sure about those flags, either, but I figured they were harmless (other than performance). It's been a while since I did that, I'll try to give everything in master a spin, soon. Thanks for looking at these! ------------------------------------------------------------------------------ Master SQL Server Development, Administration, T-SQL, SSAS, SSIS, SSRS and more. Get SQL Server skills now (including 2012) with LearnDevNow - 200+ hours of step-by-step video tutorials by Microsoft MVPs and experts. SALE $99.99 this month only - learn more at: http://p.sf.net/sfu/learnmore_122512 _______________________________________________ SoX-devel mailing list SoX-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sox-devel
