search for: 2chan

...-P 0 -b 4608 -m -l 8 -q 0 -r 3,3 -R 0 -V test: 101% complete, ratio=0.078 Which is clearly wrong (101%), and I think should probably trigger an error (but doesn't). Based on a few quick tests, this kind of problem seems to occur with any file smaller than 4k (at least when using 44100Hz/16bps/2chan). -- - mdz

...h original raw data thanks On Tue, Nov 13, 2001 at 02:38:32AM +0000, Adam M. Costello wrote: > Matt Zimmerman <mdz@debian.org> wrote: > > > Based on a few quick tests, this kind of problem seems to occur with > > any file smaller than 4k (at least when using 44100Hz/16bps/2chan). > > I don't think the problem is related to file size. The exact same > thing happens when I use a file over 700 MB. That's actually where I > discovered the problem, then I tried a small file to see if the behavior > was consistent. You are right; my test was flawed....

...Nov 13, 2001 at 02:38:32AM +0000, Adam M. Costello wrote: > > > Matt Zimmerman <mdz@debian.org> wrote: > > > > > Based on a few quick tests, this kind of problem seems to occur > with > > > any file smaller than 4k (at least when using > 44100Hz/16bps/2chan). > > > > I don't think the problem is related to file size. The exact same > > thing happens when I use a file over 700 MB. That's actually where > I > > discovered the problem, then I tried a small file to see if the > behavior > > was consistent. &g...

On Wed, Jun 4, 2014 at 4:31 PM, Timothy B. Terriberry <tterribe at xiph.org> wrote: > Alpha Thinktink wrote: >> max_data_bytes=-11 > > That value is passed in by you. I also don't think passing such a value > would have worked in earlier releases. It indicates the size of the > buffer you are passing to the encoder to receive the encoded output. Actually, I'm