Carl-Erik Kopseng wrote: integer used to be computationally more effective. (although i've heard people who should know it say it's no longer an issue on modern cpus. still, if you are targetting embedded systems, be sure to check out their floating point performance.) float has the very big advantage that it will always give you optimum resolution (i.e. use all vailable bits) regardless of your level, and that you don't have to worry about overflow. only in the last step before the DAC do you need to clamp it between 0 and 1.0. when reducing bit depth, be sure to understand about dither. wikipedia should have something, steve harris explained it in a joint paper we did some years ago at a LAC (http://spunk.dnsalias.org/public_stuff/linux_audio/audio_engineering_in_a_n…), and there is an excellent chapter in bob katz' book on mastering audio. both come with example programs. bit-shift and dither. in the open source world, every app is a howto :-D the easiest and most rewarding API is probably JACK. check out the example programs. apart from hiding the gruesome details of audio hardware, it will make your application part of the most versatile and creative free infrastructure existing today. -- jörn nettingsmeier home://germany/45128 essen/lortzingstr. 11/ http://spunk.dnsalias.org phone://+49/201/491621 Kurt is up in Heaven now.

Thanks for the tips, everyone. I guess I will just have to dig through the example programs. Reading code is supposed to make you a better programmer, so I hope it’s worth it J Btw. The example code on that blog helped ;) Last infamous words: I’ll be back. (Probably) Regards, Carl-Erik