Andreas Jansson wrote:
> Hi!
> 
> I'm an audio engineering student doing an essay on synthesiser design.
> I have not been using Csound for very long, but I want to submit a
> Csound instrument with my appendices. However I would rather not have
> to include the whole Csound library, in order to make it easier
> marked.
> 
> I have been reading about Csound VST and csLADSPA, but from what I
> understand, they also require the Csound library(?). Is there any way
> of "compiling" the .csd file as a VST-plugin, or a stand-alone
> solft-synth "application"?
> 
> I use an Intel Macbook, but I think could find me a PC if necessary.


The simplest way to get an independently-playable file, I think, would 
be to specify "-o filename" on the command line.  This causes Csound to 
generate a .WAV file that can be played by most systems' native 
music-player application.  You can transcode to some other format such 
as MP3, if desired.  I use a freeware program called Wav2MP3 on Windows 
to make MP3s from Csound's WAV files.

-- JK

-- 
I do not particularly want to go where the money is -
  it usually does not smell nice there. -- A. Stepanov

Dear Andreas, I am also a beginner, but is still seems to me that the other
answers to you are not clarifying things, probably because I'm not clear
about what you're asking.


Andreas Jansson wrote:
> 
> ...I want to submit a Csound instrument with my appendices. However I
> would rather not have
> to include the whole Csound library, in order to make it easier
> marked.
> 

First of all, I don't understand what you mean by "to make it easier
marked". But making some guesses: If you've created a Csound instrument, you
can simply present its listing in your appendix. This is actually one of the
things I like about it, in comparison to Max/MSP and GUI based sound tools.
Instruments and scores are simply text files.

I don't know why you are concerned about "including the whole Csound
library." Certainly, a person looking at your essay will need a running
Csound installation to duplicate your instrument, but this is the same as
including a C program in a paper: of course no one would assume that a C
compiler is somehow included.

Now if you mean you're submitting your paper electronically and want to
include the instrument as an executable: yes, that is a different issue.
Using the same analogy: you can provide a compiled and linked C program
without any need of a compiler, but it will only run on a computer of the
architecture for which it was compiled (except for meta architecture things
like Java, etc.) As far as I know, there is no corresponding level of
abstraction for a .csd file. Csound libraries will always be required.

Creating an audio file is relatively portable except of course that must
perforce be a fixed unchanging performance. But I'm not sure that's what you
want.

Is this any clearer? In fact, is it even correct?
-- 
View this message in context: http://www.nabble.com/Beginners-Question%2C-Csound-as-stand-alone-softsynth---plugin--tp18590748p18595357.html
Sent from the Csound - General mailing list archive at Nabble.com.