Displaying 7 results from an estimated 7 matches for "iamanidiot".
2004 Sep 10
2
beta 1.0.3 ERROR
The test script doesn't seem to stop on error. I noticed this
in the logs:
++++++ testing level 1 interface
simple iterator on read-only file
generating FLAC file for test
testing 'metadata.flac'... 0... 1... content... PASSED
is writable = 1
ERROR: iterator claims file is writable when it should not be
ERROR during test_libFLAC
FAIL: ./test_libFLAC.sh
Platform is a mobile
2004 Sep 10
1
beta 1.0.3 ERROR
--- David Willmore <davidwillmore@iamanidiot.com> wrote:
>
> The test script doesn't seem to stop on error. I noticed this
> in the logs:
>
> ++++++ testing level 1 interface
> simple iterator on read-only file
> generating FLAC file for test
> testing 'metadata.flac'... 0... 1... content... PASSED
&...
2004 Sep 10
0
beta 1.0.3 ERROR
--- David Willmore <davidwillmore@iamanidiot.com> wrote:
>
> The test script doesn't seem to stop on error. I noticed this
> in the logs:
>
> ++++++ testing level 1 interface
> simple iterator on read-only file
> generating FLAC file for test
> testing 'metadata.flac'... 0... 1... content... PASSED
&...
2004 Aug 06
2
--dtx alone does nothing?
> > So there should be some equivalency between --abr values and --quality
> > values? Or do they effect the rate in different ways.
>
> Actually, --abr adjusts the quality in real-time so that the average
> bit-rate meets a certain target. with just --quality, the final average
> bit-rate is dependent on the data, so that's why --abr is there.
Is there some time
2004 Aug 06
2
--dtx alone does nothing?
> > Is there some time window over which it tries to meet this average?
>
> Right now, it looks at what's the average bit-rate so far and does some
> adjustments to meet the target. There might be ways to improve, it's
> very rough right now. Also, note that you'll likely get better results
> by trying several --quality until you get the right bit-rate than with
2004 Aug 06
2
--dtx alone does nothing?
> All you say look normal to me.
Okay, clarification requires less code to be written than a bug. :)
> > Does that makes sense? I would have thought that --dtx alone would have =
> doen it,
> > but maybe it needs perfect digital silence to work? Or only uses the voi=
> ce activation
> > to know when there's silence?
>
> DTX requires the VAD to know when
2004 Aug 06
2
--dtx alone does nothing?
I'm running a:
for band in n w u
do
for quality in 0 1 2 3 4 5 6 7 8 9 10
do
for complexity in 3
do
for vad in "" "--vad"
do
for dtx in "" "--dtx"
do
echo speexenc -${band} --quality ${quality} --comp ${complexity} ${vad} ${dtx} input.${band}.wav