search for: celt_decoder_create

Displaying 4 results from an estimated 4 matches for "celt_decoder_create".

2009 Oct 16
3
API Change
...yone, I've just changed the API for CELT, but at least there's a good reason for that. It's now possible to use the same mode data for both mono and stereo. So here's the change: - The celt_mode_create() function has a "channels" parameter - The celt_encode_create() and celt_decoder_create() functions now have an additional "channels" parameter. - I also added an error parameter celt_encode_create() and celt_decoder_create() to return any error that occurs. Sorry about the inconvenience. You'll see, it's worth it. Please report any breakage. Cheers, Jean-Marc
2009 Jul 22
2
Allocating all memory up front
...t what sounds will be played. We would like to create all of our CELTDecode instances up front. Because celt_mode_create() requires a sample rate and number of channels passed in, this doesn't seem like it is currently possible. What I am thinking of doing is calling celt_mode_create() and celt_decoder_create() up front with the maximum values for sample rate and number of channels, this will allocate all the memory we need. Then when we actually go to play a sound and know the rate and number of channels, we can fix up the appropriate mode parameters before decoding. The only problem I can see is t...
2010 Mar 03
2
uint decode error on visual studio...
...if(mode2==NULL || error!=CELT_OK) { printf("ERROR: celt_mode_create 2 %s\n",celt_strerror(error)); return -1; } encodedfile=fopen(encodedfilename,"rb"); if(!encodedfile) { printf("ERROR opening %s for reading\n",encodedfilename); return -1; } CELTDecoder* decoder=celt_decoder_create(mode2,gNrChannels,&error); if(decoder==NULL || error!=CELT_OK) { printf("ERROR: celt_decoder_create %s\n",celt_strerror(error)); return -1; } fseek(encodedfile,0,2); int filesize=ftell(encodedfile); fseek(encodedfile,0,0); offset=0; while((res=fread(encodedbuffer,bytes_per_packe...
2009 May 20
2
Encoder crash in multithreading processing
Hi, I try to work with CELT encoder & decoder in 2 different threads at the same time. So I create/destroy encoder and encode in one thread and create/destroy decoder and decode in other thread. If I didn't protect celt_encoder_create, celt_encode_float and celt_decoder_create, celt_decode_float with CRITICAL_SECTION I get stable error in icwrs32 or ec_byte_write1 (more often) in encoder. What does it mean ? Is CELT not thread-safe ? Any way to avoid this error except CRITICAL_SECTION ? Sergei ps: I use last version from git repository, but I also checked with previou...