Speex dev - Aug 2004 - API changes for Speex 1.2

Hi,

Speex is progressing and I've started thinking about the next 1.2
release (don't hold your breath). Though the bit-stream won't change,
the API likely will. The API for 1.1.x already differs from 1.0.x
because the speex_encode and speex_decode now use shorts instead of
floats. Now, since I'm changing the API anyway, I thought I might as
well fix things that might be annoying with the current API.

So, I'm open to suggestions from people who have used Speex before and
think some things should be changed. These are a couple things I'm
already considering:
- allow the user to provide his own buffer for the *init() functions
(instead of having Speex itself call malloc) 
- allow the user to override the internal stack used by the encoder and
decoder (saves memory when using a large number of encoder/decoder
states)

        Jean-Marc


-- 
Jean-Marc Valin, M.Sc.A., ing. jr.
LABORIUS (http://www.gel.usherb.ca/laborius)
Université de Sherbrooke, Québec, Canada


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 190 bytes
Desc: Ceci est une partie de message numériquement signée.
Url :
http://lists.xiph.org/pipermail/speex-dev/attachments/20040317/2ba7726a/signature-0001.pgp

Hi,

Maybe a review of the configuration options would be interesting?
Make all options like
SPEEX_SET_VBR_QUALITY

So you would have
SPEEX_SET_ABR_BITRATE
SPEEX_SET_CBR_BITRATE
SPEEX_SET_CBR_MODE
SPEEX_SET_CBR_QUALITY
SPEEX_SET_VBR_QUALITY

and then
e.g. SPEEX_SET_VBR_BITRATE, ...
would also make sense: e.g. set vbr_quality so that the average bitrate
is as specified.

Now it is easy to make a mistake when configuring the encoder (because
now abr/cbr/vbr is sometimes set separately from bitrate/mode/quality).

It would also be nice if there is a intuitive mapping between the RFC
options and
the encoder configuration. Examples:
- how to configure encoder when SDP specifies: b=AS:10 and vbr
- how to configure encoder when SDP specifies: cng

Best regards,
Chris
> ----- Original Message ----- 
> From: "Jean-Marc Valin" <Jean-Marc.Valin@USherbrooke.ca>
> To: "speex" <speex-dev@xiph.org>
> Sent: Wednesday, March 17, 2004 9:23 AM
> Subject: [speex-dev] API changes for Speex 1.2
>
> Hi,
>
> Speex is progressing and I've started thinking about the next 1.2
> release (don't hold your breath). Though the bit-stream won't
change,
> the API likely will. The API for 1.1.x already differs from 1.0.x
> because the speex_encode and speex_decode now use shorts instead of
> floats. Now, since I'm changing the API anyway, I thought I might as
> well fix things that might be annoying with the current API.
>
> So, I'm open to suggestions from people who have used Speex before and
> think some things should be changed. These are a couple things I'm
> already considering:
> - allow the user to provide his own buffer for the *init() functions
> (instead of having Speex itself call malloc)
> - allow the user to override the internal stack used by the encoder and
> decoder (saves memory when using a large number of encoder/decoder
> states)
>
>         Jean-Marc
>
> -- 
> Jean-Marc Valin, M.Sc.A., ing. jr.
> LABORIUS (http://www.gel.usherb.ca/laborius)
> Université de Sherbrooke, Québec, Canada
>
--- >8 ----
List archives:  http://www.xiph.org/archives/
Ogg project homepage: http://www.xiph.org/ogg/
To unsubscribe from this list, send a message to
'speex-dev-request@xiph.org'
containing only the word 'unsubscribe' in the body.  No subject is
needed.
Unsubscribe messages sent to the list will be ignored/filtered.