Displaying 8 results from an estimated 8 matches for "latticebuild".
2000 Dec 19
0
what script or command makes the codebooks? (fwd)
...2 3 5
0 1 2 3 5 8 11
0 1 2 3 5 8 11 14 17 20 24 28 31 35 39 43 47 51 56 61 66 71 72 78 84 90 96 102
0
0 1
0 1
0 1 3
0 1 3
0 1 3 5 8
0 1 3 5 8 11 14
0 1 3 5 8 11 14 17 20 24 28 31 35 39 43 47 51 56 61 66 71 72 78 84 90 96 102
huffbuild res0_96_128aux.vqd 0,4,2
huffbuild res0_96_1024aux.vqd 0,32,2
latticebuild res0_128_128_1.vql >! res0_96_128_1.vqh
latticehint res0_96_128_1.vqh >! temp.vqh
restune temp.vqh res0_96_128_1.vqd >! res0_96_128_1.vqh
latticehint res0_96_128_1.vqh >! temp.vqh
mv temp.vqh res0_96_128_1.vqh
latticebuild res0_128_128_2.vql >! res0_96_128_2.vqh
latticehint res0_96_...
2003 Aug 12
0
codebook
Hi all,
<p>I have read the the source code about codebook generation, but there are
some puzzles:
Where can I get a latticebuild description file?
How does one choose reasonable value0..value n on the second line of the
latticebuild description file(.ql) to latticebuild?
Does the output (xxx.vqi) of the resvqtrain have some relationships to the
latticebuild description file ?
Where can I get these information?
Thank you!...
2003 Aug 09
0
Date: Sat, 9 Aug 2003 09:40:10 +0800
Hi all,
I have read the the source code about codebook generation, but there are some puzzles:
Where can I get a latticebuild description file?
How does one choose reasonable value0..value n on the second line of the latticebuild description file(.ql) to latticebuild?
Does the output (xxx.vqi) of the resvqtrain have some relationships to the latticebuild description file ?
Thank you!
Aiming,Ji
<p>--- >8 --...
2003 Aug 11
0
lattice codebook
Hi all,
<p>I have read the the source code about codebook generation, but there are some
puzzles:
Where can I get a latticebuild description file?
How does one choose reasonable value0..value n on the second line of the
latticebuild description file(.ql) to latticebuild?
Does the output (xxx.vqi) of the resvqtrain have some relationships to the
latticebuild description file ?
Thank you!
Ji
<p><p><p><...
2000 Nov 10
1
cvs trunk vorbis/ compile patches
...g -O20 $(FLAGS)
-CC=gcc
-LD=gcc
-LDFLAGS=$(FLAGS)
-LIBS=-lm
-
-HFILES = ../lib/codebook.h vqgen.h vqext.h bookutil.h
-
-OFILES = vqgen.o vqsplit.o bookutil.o ../lib/sharedbook.o
-ALLOFILES = $(OFILES) lspdata.o genericdata.o train.o build.o run.o\
- cascade.o partition.o metrics.o residuedata.o latticebuild.o\
- latticepare.o latticehint.o latticetune.o
-
-all:
- $(MAKE) target CFLAGS="$(OPT)"
-
-debug:
- $(MAKE) target CFLAGS="$(DEBUG)"
-
-profile:
- $(MAKE) target CFLAGS="$(PROFILE)"
-
-target: lspvqtrain genericvqtrain residuevqtrain vqbuild vqcascade vqmetrics latt...
2000 Sep 21
0
.vqd example?
...train,
but can anyone supply hints for the rest of the procedure?
vqbuild will only produce a "cloud"-type quantlist, and
sequencep is pretty much ignored.
But if you use it anyway, you can go by hand through the xxx.vqh
file and guesstimate enough to make a bogus .vql file.
Then I ran latticebuild to get a first try .vqh file
Any comments about what's allowed and how to choose addmul?
Then I tried latticetune .vqh-file .vqd-file
ohoh tha name had to be precisely latticetune (or restune?)
ok I tried restune to read multiple cols. from lsp0coeff_0.vqd
still not a big difference. Tried...
2000 Nov 08
0
vq diffs
...gg
-HFILES = ../include/vorbis/codebook.h vqgen.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 @@...
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