[Speex-dev] version 1.0.1 X 1.1.4

[Jean-Marc Valin]

> I was aware of this change, but my question remains: Is version 1.1.4 
> incompatible with version 1.0.1 regards the changes in the API ?
> If I convert one frame using version 1.1.4 it should give exactly the 
> same output of converting this same frame using version 1.0.1, right ?
> In a more generic way: if I use the newer version, the frame encoded 
> with it can be decoded with the older versions ?

1.0.1 and 1.1.4 will give the same result only if you change your code
to account for the fact that the (float*) in 1.0.1 became (short*) in
1.1.4  (and got back to float after that). Otherwise, you'll likely to
simply get a segfault (or at least garbage). Note that the format itself
is the same, just the API that changed slightly (but not enough to
prevent it from compiling/linking unfortunately).

	Jean-Marc

> Flávio
> 
> Conrad Parker wrote:
> 
> >On Wed, Nov 17, 2004 at 09:05:05AM +0900, Jean-Marc Valin wrote:
> >  
> >
> >>Why do you want your app to with with 1.1.4 in the first place. It's a
> >>old unstable version and its API has been changed since then.
> >>
> >>    
> >>
> >
> >ie. Flavio, please upgrade to the recent 1.1.6 release. In your code,
> >you will need to change the follwing line (for the 1.1.x build only):
> >
> >  
> >
> >>>    /* Encode the frame */
> >>>    speex_encode( state, in, &bits );
> >>>      
> >>>
> >
> >becomes:
> >        speex_encode_int( state, in, &bits );
> >
> >Conrad.
> >
> >  
> >
> 
> _______________________________________________
> Speex-dev mailing list
> Speex-dev at xiph.org
> http://lists.xiph.org/mailman/listinfo/speex-dev