similar to: Difficulties in add cover art to FLAC file

metaflac --import-vc-from ... used on flac file without vorbis comment destroys the file. This patch fix it. -- Miroslav Lichvar -------------- next part -------------- --- src/metaflac/main.c.orig 2002-09-28 14:45:49.000000000 +0200 +++ src/metaflac/main.c 2002-10-06 23:36:26.000000000 +0200 @@ -1754,20 +1754,24 @@ found_vc_block = true; } while(!found_vc_block &&

Hi, I think what happened is that you did not write the "message" length. With user-callbacks, you also need to say how large the message. The size is in bytes and encoded in 4 bits. Besides, you're probably the first one to use user-callbacks. BTW, why didn't you want to use Ogg. It's much simpler to use and overhead can be made minimal anyway. Jean-Marc Le ven

Hi, Sorry! Marc Gimpel. I wrote it in a false thread before. It was my first time. :-) I have to write a small programm which should be able to record speeches and in addition synchronize the recorded speeches with measuring data. My idea is to record the speech in the normal way with speex and without ogg. If a sync message was received, i write a custom in-band messages using mode 13

Hello, When I decode a recoded sound encoded by speex, it has too much noise. The noise is "slightly" reduced if I set the quality to 10. How do I get rid of this noise? The code is as follows. For encoding . state = speex_encoder_init ( &speex_nb_mode ); tmp = 7; speex_encoder_ctl ( state, SPEEX_SET_MODE, &tmp); // set quality tmp = 10; speex_encoder_ctl ( state,

Currently it's possible to corrupt FLAC file with flac and metaflac tools. If image filesize is just slightly less than 2^24 bytes then the size of PICTURE metadata block will be more that this limit. The first patch (fix1.patch) adds additional check in /share/grabbag/picture.c/read_file() and removes rather useless check from FLAC__metadata_object_picture_set_data(). It's enough to fix

Jean-Marc wrote: >I think what happened is that you did not write the "message" length. >With user-callbacks, you also need to say how large the message. The >size is in bytes and encoded in 4 bits. I wonder what is correct. Inside speex the documentation was written that the size in byte is encoded within 5 bit. I changed the code in both ways, but it doesn't work

hello, i switched to use the encoder.processData() and encoder.getProcessedData() of jspeex. however it looks to me like a memory leak ... memory usage is increasing very fast and there is no visible stop ... after about five minutes java.lang.OutOfMemory occurs. I think it must be the jspeex component, because before i added jspeex to my app usage was constant at about 5mb. is it possible