there are opcodes in the manual that are missing good, simple and/or complete examples. Sometimes there are just plain bugs and the opcodes do not work as they should. This makes that these opcodes like black boxes and make them unusable.
I think an example should clarify immediately why at the time it was necessary to create this particular opcode. Without this, the knowledge can get lost.
If someone knows of an example for an opcode that has been placed in the list below, please let me know.

These are the guidelines for the examples in the manual:

1. work right-out-of-the-box
2. run in realtime if possible
3. sr = 44100 (or 48000 using jack)
4. ksmps = 32
5. nchnls = 2
6. use the "modern" 0dbfs = 1 if possible
7. be simple and clear in the purpose of that particular opcode

I'm testing with Ubuntu11.10 and WinXound/CsoundQt.
I work my way through the manual from A -Z and hope that soon this blog can be deleted because all opcodes will have their examples in the manual and my work is done :)

This is the list with unsolved problems with examples
================================================

These are simple drone-like pieces generated algorithmically using only a basic sine-wave instrument. The csd files are created by analyzing PGN (Portable Game Notation) files, which are standard format files used to store chess games. The program was written in C++.

Game # 1 - Standard tuning pentatonic in A major
Game # 2 - 5-TET
Game # 3 - Just Intonation pentatonic
Game # 4 - 11-TET pentatonic
FourGames - 3h8TET - This piece was generated from a multiple game PGN file which includes all four of the other games.

The source chess games used are classics from the 1800's.

I have been playing around with building vst code generators and I also grabbed all the vst parameters so they can be edited in a spreadsheet. The blog doesn't seem to allow .zip files so I have them uploaded over here.

http://dexrowem.blogspot.com/2011/06/csound-vst-generater-pack.html

I've added a few more features to the (ruby script) midi2sco app that I wrote a while back (http://www.csounds.com/node/87), that I hope may make it a little more versatile.

It now (by default) separates instrument parameters in the file it generates with tabs rather than spaces. This doesn't hurt the output as a Score file at all, but makes it also acceptable to a spreadsheet program, so you can conveniently tweak parameters further if you wish.

http://www.csounds.com/matt/d+d.html

+ now supports latest CsoundLib Universal Binary

+ fixed crashing bugs when rendering to file and other problems

+ updated opcode color syntax library

+ added new opcode "soundinmac"
FEATURES (benefits over existing soundin/diskins)
:: automatic sample rate and channel conversion (# of outputs can be DIFFERENT than # of soundfile channels)

:: higher quality (k-rate) pitch shifting than diskin2's sinc interpolation

It is very common for ide's for programming languages to have menu's that are definable, This is the feature I am waiting for because there are a number of utilities that are available (I could make a python version of freq to sco) outside the gui that would be helpful to have. I.E. read from a file that the user can change. It is probably outside the possibility for the editor but I think that there is a 2 controller (I forget the name) that if the highlighting routines where written from scratch would provide highlighting for the table numbers although it is best to use constants.

FMbot-00 is an constrained-random algorithmic just intonation composition, using a retriggering synth I call FMbot. The FMbot synth contains some simple constrained-random orchestra code and takes only the basic three pfields, instrument, note start time, and duration, making it a very easy synth to use and compose with. The results will be quite a bit different each time the song is played. I hope you find it interesting and/or amusing.

BW

Three tempered tritave tunings take turns.

http://bwong.ca/template1.php?sub=11

I have posted two minor software tools on my website at http://www.bwong.ca

etrcalc.pd is a Pure Data patch that calculates the closest match to an interval within any equal temperament tuning.

ethan-00.zip is a Windows only executable file that displays tuning data in cents and frequency ratio for any equal temperament tuning.

Obviously these have nothing specifically to do with Csound, they are just my learning tutorials for a couple of new programming languages, but perhaps someone might find them useful utilities for composition or synth design, as I do.

Installing of CsoundQt

CsoundQt - formerly know as Qutecsound - is developing fast.
This is how i got CsoundQt from SVN installed - with help from Andrés Cabrera **thanks**

1. download CsoundQt from Sourceforge: svn co https://qutecsound.svn.sourceforge.net/svnroot/qutecsound qutecsound
2. i already have built and installed Csound Double Precision - see another blog entry; http://www.csounds.com/node/1373
3. install qt4-qmake and libqt4-dev
4. go to qutecsound/trunk/qutecsound
5. For Csound double precision use: qmake-qt4 qcs.pro CONFIG+=build64 LIBSNDFILE_LIBRARY_DIR="/usr/lib/x86_64-linux-gnu"
6. stay at qutecsound/trunk/qutecsound
7. make

This will produce a working CsoundQt in qutecsound/trunk/qutecsound. Doublclick on "qutecsound" in the qutecsound/trunk/qutecsound/bin and CsoundQt opens.

Installing of Loris

For the Loris opcodes to work in Csound, i've used these instructions:

1. go to http://sourceforge.net/projects/loris/files/ and get Loris version 1.8.