Displaying 4 results from an estimated 4 matches for "residuesplit".
2000 Nov 10
1
cvs trunk vorbis/ compile patches
...:
- $(MAKE) target CFLAGS="$(OPT)"
-
-debug:
- $(MAKE) target CFLAGS="$(DEBUG)"
-
-profile:
- $(MAKE) target CFLAGS="$(PROFILE)"
-
-target: lspvqtrain genericvqtrain residuevqtrain vqbuild vqcascade vqmetrics latticebuild latticepare latticehint latticetune huffbuild residuesplit
-
-lspvqtrain: $(OFILES) lspdata.o train.o
- $(CC) $(CFLAGS) $(LDFLAGS) $^ -o $@ $(LIBS)
-
-residuevqtrain: $(OFILES) residuedata.o train.o
- $(CC) $(CFLAGS) $(LDFLAGS) $^ -o $@ $(LIBS)
-
-genericvqtrain: $(OFILES) genericdata.o train.o
- $(CC) $(CFLAGS) $(LDFLAGS) $^ -o $@ $(LIBS)
-
-vqbuild: $(OF...
2000 Dec 19
0
what script or command makes the codebooks? (fwd)
..._sequencep treatment was a bit off, and you don't
interleave that data).
>
> Regenerate training data with LSP books because residue is affected by LSP
> books.
Here I mucked with vorbisenc.c to add a new mode with a certain
bit-rate window.
>
> Run residue training data into residuesplit (parms in mode_*.h but not
> stated in an obvious way), which splits the residue into partitions.
Do this on a LARGE partition with many gigs of free space, to get a feel
for how big those intermediate files will be.
>
> Lattice build each partition (parms can be extracted from the vqhes...
2000 Nov 08
0
vq diffs
....h vqext.h bookutil.h
+HFILES = ../lib/codebook.h vqgen.h vqext.h bookutil.h
OFILES = vqgen.o vqsplit.o bookutil.o ../lib/sharedbook.o
@@ -85,5 +85,5 @@
lspvqtrain genericvqtrain residuevqtrain\
vqbuild vqmetrics latticebuild vqcascade latticepare\
- huffbuild residuesplit
+ huffbuild residuesplit latticehint latticetune
distclean: clean
diff -bBu2r vorbis/vq/bookutil.c vorbis-ejk/vq/bookutil.c
--- vorbis/vq/bookutil.c Sat Nov 4 01:43:55 2000
+++ vorbis-ejk/vq/bookutil.c Wed Nov 8 14:00:20 2000
@@ -22,7 +22,7 @@
#include <string.h>
#include <errno.h&...
2001 May 01
1
encoder observation
Hello!
First of all a question:
When you make the encoder tables (ie: mode_e.h)
do you use the mapping0_forward function?
Because you made the encoder tables, and after this
you did a minor correction in the final beta4 ...
(this correction was:
additional[0]=fabs(additional[0]*scale);
in the mapping0_forward function)
(I see this was a bug, and the modification
was correct, but this correction