similar to: question on usage of the libraries

> I'm not sure if I should post this question to this list. If not; please > tell me. > Ok, here it comes: > Is the following code correct for compressing audio? The output I get is so > extremely small, but what is more important: if I pass it through zlib, it > gets at least 50% smaller! On regular data, gzip might get a 5% reduction, so I doubt you can get 50% unless

> Ok, I forgot to mention that I want to incorporate speex into my own > program (which is for e.g. streaming audio and a couple of other > things). JM> One thing you'll need to decide: do you want to pack in into an Ogg JM> container or will you take care of handling the packets yourself? I take care of that myself. JM> If you JM> want to pack it in Ogg, I suggest you

In my app, the user can upload images. Rather than shoving the image data in the database, i want to put the filename and content type into the db, then rename the image with its record''s id number, and then save it into a local folder in my app folder. (hardcoded for now) All the details are being saved to the db ok, so as far as i know the "picture_file=" method is fine.

> Is the following code correct for compressing audio? The output I get is so > extremely small, but what is more important: if I pass it through zlib, it > gets at least 50% smaller! JM> On regular data, gzip might get a 5% reduction, so I doubt you can get JM> 50% unless you're encoding zeros or doing something wrong... I think I'm doing something wrong :o) Don't know

Hello, How would I go about updating 7000 or so rows of my database with unique values? (In other words, I''m not setting them all to NULL or incrementing or something... each row gets a new, special value.) But I can''t seem to get my rails app to do this in less than 7000 connections to the database! I''ve looked very hard (3 horus!), and can''t find anything

[ This patch depends on the cross-architecture ELF cleanup patch. ] This series updates the boot protocol to 2.07 and uses it to implement paravirtual booting. This allows the bootloader to tell the kernel what kind of hardware/pseudo-hardware environment it's coming up under, and the kernel can use the appropriate boot sequence code. Specifically: - Update the boot protocol to 2.07, which

[ This patch depends on the cross-architecture ELF cleanup patch. ] This series updates the boot protocol to 2.07 and uses it to implement paravirtual booting. This allows the bootloader to tell the kernel what kind of hardware/pseudo-hardware environment it's coming up under, and the kernel can use the appropriate boot sequence code. Specifically: - Update the boot protocol to 2.07, which

Hi. I've implemented "echo cancel" to voip project. But it doesn't work well . (I cannot feel the enhancement with activated AGC) My encode settings : 1. frame size : 320 bytes. 2. sampling rate : 16000 Hz (WB) 3. mono echo state initialized like this : echo_state = speex_echo_state_init(framesize, framesize*16); and befor encode : speex_echo_cancel(echo_state,

This series updates the boot protocol to 2.07 and uses it to implement paravirtual booting. This allows the bootloader to tell the kernel what kind of hardware/pseudo-hardware environment it's coming up under, and the kernel can use the appropriate boot sequence code. Specifically: - Update the boot protocol to 2.07, which adds fields to specify the hardware subarchitecture and some

This series updates the boot protocol to 2.07 and uses it to implement paravirtual booting. This allows the bootloader to tell the kernel what kind of hardware/pseudo-hardware environment it's coming up under, and the kernel can use the appropriate boot sequence code. Specifically: - Update the boot protocol to 2.07, which adds fields to specify the hardware subarchitecture and some

This series updates the boot protocol to 2.07 and uses it to implement paravirtual booting. This allows the bootloader to tell the kernel what kind of hardware/pseudo-hardware environment it's coming up under, and the kernel can use the appropriate boot sequence code. Specifically: - Update the boot protocol to 2.07, which adds fields to specify the hardware subarchitecture and some

This allows other boot loaders such as the Xen domain builder the opportunity to extract the ELF file. Signed-off-by: Ian Campbell <ijc@hellion.org.uk> Cc: Thomas Gleixner <tglx@linutronix.de> Cc: Ingo Molnar <mingo@redhat.com> Cc: H. Peter Anvin <hpa@zytor.com> Cc: Jeremy Fitzhardinge <jeremy@goop.org> Cc: virtualization@lists.linux-foundation.org ---

This allows other boot loaders such as the Xen domain builder the opportunity to extract the ELF file. Signed-off-by: Ian Campbell <ijc@hellion.org.uk> Cc: Thomas Gleixner <tglx@linutronix.de> Cc: Ingo Molnar <mingo@redhat.com> Cc: H. Peter Anvin <hpa@zytor.com> Cc: Jeremy Fitzhardinge <jeremy@goop.org> Cc: virtualization@lists.linux-foundation.org ---

This series: 1. Updates the boot protocol to version 2.07 2. Clean up the existing build process, to get rid of tools/build and make the linker do more heavy lifting 3. Make the bzImage payload an ELF file. The bootloader can extract this as a naked ELF file by skipping over boot_params.setup_sects worth of 16-bit setup code. 4. Update the boot_params to 2.07, and update the

This series: 1. Updates the boot protocol to version 2.07 2. Clean up the existing build process, to get rid of tools/build and make the linker do more heavy lifting 3. Make the bzImage payload an ELF file. The bootloader can extract this as a naked ELF file by skipping over boot_params.setup_sects worth of 16-bit setup code. 4. Update the boot_params to 2.07, and update the

input: http://pastebin.com/raw.php?i=MqPXZwc3 output: http://pastebin.com/raw.php?i=8QCkp4yv it will be a long day.. :D could someone please help with it? i have to make a "one liner" that get's the input, and gives the mentioned output.

>>That boot_params.hdr.code32_start field is probably either invalid (bad reloc or something else causing the bootloader to >>calculate the wrong address) or valid but the thing it thinks it is pointing to wasn't loaded (missing PT_LOAD etc.). >boot_params.hdr.code32_start field is valid :) It is 0x100000, like expected > >Then I suspect that that segment isn't being