thanks very much  Brady

also void then newline then pack
that explains why find in files didnt find it

need pack.h perhaps...

I'll add that to my list.

another question while you are still awake (!)
what's the story with the codebook for the mel_cb  lsps  ( amongst a couple of others) ?

the cmakefile refers to them like

    COMMAND generate_codebook mel_cb ${CODEBOOKSMEL} > ${CMAKE_CURRENT_BINARY_DIR}/codebookmel.c

is <
codebookmel.c> generated (IE and not in source distro ) ?


cheers



On 14/09/2016 4:25 PM, Brady O'Brien wrote:
Oh, no, I misread that. The return types are correct. They're still in pack.c.

73

On Wed, Sep 14, 2016 at 1:24 AM, Brady O'Brien <brady.obrien...@gmail.com> wrote:
Hi Glen,

They're under pack.c, as far as I can tell, although declared with different return types. There's something to add to the cleanup todo.

73

On Wed, Sep 14, 2016 at 1:12 AM, glen english <g...@cortexrf.com.au> wrote:
OK, 15 minutes into it...

where are: ?????
they are declared in quantise.h
but I cannot find any defition for them anywhere at all...
with thanks


void pack(unsigned char * bits, unsigned int *nbit, int index, unsigned
int index_bits);
void pack_natural_or_gray(unsigned char * bits, unsigned int *nbit, int
index, unsigned int index_bits, unsigned int gray);
int  unpack(const unsigned char * bits, unsigned int *nbit, unsigned int
index_bits);
int  unpack_natural_or_gray(const unsigned char * bits, unsigned int
*nbit, unsigned int index_bits, unsigned int gray);




On 14/09/2016 11:53 AM, David Rowe wrote:
> Hi Glen,
>
> Like a lot of open source, it's evolved organically over many years.
>
> If a re-org was to happen - the big question is who will take
> responsibility for it. If some one really wants to re-organise things,
> and is willing to carefully ensure nothing is broken (x86, Octave,
> embedded targets, Makefiles, unit tests, sort through/archive dead code)
> ... I'm happy for them to have a go.
>
> You didn't mention which part you wanted?  If it's the files reqd for
> FreeDV 1600 on an embedded platform, take a look in
> codec2-dev/stm/Makefile at the variable CODEC2_SRCS and SM1000_SRCS for
> what we use for the SM1000.
>
> Cheers,
>
> David
>
> On 14/09/16 11:00, glen english wrote:
>> Hi
>> I am now porting into a cortex M7, as we speak
>>
>>    wading through all the codec 2 sources, which I have only ever browsed
>> the encode and decode files
>>
>> I see the src folder has pretty much everything in it.....
>> and I just want a bit of it...
>>
>> is there any reason for everything  in one folder?
>> rather than
>> /demos
>> /tests
>> /codec2_core
>> /fmdv
>>
>> etc ?
>> would save me going through each file looking for dependencies.
>> or is there a list somewhere ?
>>
>> or " am I doing it wrong " ?
>>
>> 73
>>
>> glen
>>
>>
>>
>>
>>
>> ------------------------------------------------------------------------------
>> _______________________________________________
>> Freetel-codec2 mailing list
>> Freetel-codec2@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/freetel-codec2
>>
> ------------------------------------------------------------------------------
> _______________________________________________
> Freetel-codec2 mailing list
> Freetel-codec2@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/freetel-codec2
>



------------------------------------------------------------------------------
_______________________________________________
Freetel-codec2 mailing list
Freetel-codec2@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freetel-codec2




------------------------------------------------------------------------------


_______________________________________________
Freetel-codec2 mailing list
Freetel-codec2@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freetel-codec2




------------------------------------------------------------------------------
_______________________________________________
Freetel-codec2 mailing list
Freetel-codec2@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freetel-codec2

Reply via email to