Hi Jan,
There should be the following codebook files once generated:
codebook.c
codebookd.c
codebookjmv.c
codebookge.c
codebooknewamp1.c
codebooknewamp1_energy.c
codebooknewamp2.c
codebooknewamp2_energy.c
generate_codebook expects one or more .txt files and outputs the resulting
.c file on stand
Hi,
My attempts at generating a codebook :-). I downloaded the entire Codec2
repo, turned generate_codebook.c into generate_codebook.exe which I tried
to run in the command line, but that's where I got stuck.
1) Is this approach even correct? Or do I need to do it through the
mentioned CMakeLists?
Hi Jan,
In the STM32 CMake code, there's logic to generate the codebook files by
calling the generate_codebook application in
https://github.com/drowe67/codec2/blob/main/stm32/cmake/gencodebooks.cmake.
In that file, there should be the command lines you should use to generate
the needed files. I'd
Hi David, Mooneer, and everyone,
It seems that I have made some progress with the implementation into the
STM32 project. However, I have encountered an error: int lsp_bits(int i) {
return lsp_cb[i].log2m; }. Does this mean that I might need to generate
something with the codebook? I have installed
Hi Jan,
Please feel free to ask any question.
There's a list of files for the vocoder in the codec2.pdf doc I posted
a link to earlier today, well most of them anyway. One trick is that
some of the tables are generated as part of the build process, so best
to follow the standard build process on
Hi Jan,
The CODEC2_SRCS variable in
https://github.com/drowe67/codec2/blob/main/stm32/CMakeLists.txt#L150 is
probably a good starting point for anything STM32-based. You'll also want
to define some build variables (at minimum the first line of below minus
"add_definitions", but depending on what C
