Csound Csound-dev Csound-tekno Search About

Re: csound processor optimizations?

Date1999-05-06 03:47
FromMichael Gogins
SubjectRe: csound processor optimizations?
Since we have access to the source code, it is easy to recompile it with
optimizations for our own particular platform. I find that, with Visual C++
5 and 6, "blend" code generation optimized for "fastest code" with inlining
"any suitable" functions produces the fastest code for Pentium or Pentium
II. The inlining of everything possible produces a modest but real
performance gain.

Further optimization would involve resorting to something like the Intel
performance library, which replaces select parts of the Microsoft runtime
library, not to mention monkeying with the Csound algorithms.

-----Original Message-----
From: Josh Whiting 
To: csound@maths.ex.ac.uk 
Date: Wednesday, May 05, 1999 8:45 PM
Subject: csound processor optimizations?


>I am wondering if any versions of csound are available that are optimized
>for certain processors, i.e. P2 or P3, or other processors.  I am not
really
>technically knowledgeable enough to know what optimizations that might
>include or how to implement them by modifying the source code, but i am at
>least aware that the P3 has a new instruction set that provides a
>significant increase in FPU operations per cycle, and software such as Seer
>System's Reality is optimized to take advantage of it.
>
>The reason I ask is because I need to use csound in real time.  I don't
>really need any of the advanced synthesis opcodes, just basics and the midi
>features.  I have been using a digital synthesizer (the roland jx-305,
which
>is sample-based) and a software sequencer to make my music but I am
>frustrated by the synthesizer's limitations (especially because it isn't
>expandable - i cannot use my own samples).  I see csound as having strong
>potential as a substitute (and its free!).
>
>so, any help in finding an optimized csound or anything else that would
help
>me get it going in real time would be greatly appreciated.
>
>thanks
>josh whiting
>jwhiting@hampshire.edu
>