American variant, and could seem to be using slang or imprecise phrases to a native of England. This has been a source of irritation to one of us, and if that is the case between two dialects on the universal language, it can be a larger problem for people from other language cultures. We have referred to this as the Globalisation versus Globalization problem.

In order to address this potential problem we have reconstructed Csound so all messages can be in a language of choice; within a single installation the user can chose between a selection of translations. At the time of writing we have American and English systems complete, and there is work on Japanese, French, Spanish, Italian and Swedish translations in progress.

Delivery

Although we have a global software culture, where using the InterNet our software can be obtained and customised to the local language, if we wish to distribute our music the large bandwidth requirements for audio demand some thought. While data compression techniques such as RealAudio and MP3 are one approach, for music teaching, and training composers and sound designers we need higher quality. Within the Csound community we have worked more to local delivery of the sounds, with distribution of the specification across the globe. An early example of that is NetSound⁹

but more recently a single file format for Csound has been developed, largely by Gogins¹⁰ , so a web link with the .csd extension can be sent directly to a local Csound synthesiser. A simple example is given below, incidentally using the Hammond B3 organ hybrid-model opcode

<CsoundSynthesizer

<CsInstruments

sr

=

44100

kr

=

441

ksmps

=

100

nchnls

=

1

instr 13

;; amp, freq, c1,c2,vDep,vRate, tables...

a1

fmb3

p4, cpspch(p5), 1, 1.2, 0.2, 8, 1, 1, 1, 1, 1

out

a1

endin

</CsInstruments

<CsOptions