> ..... I often use csound to
> generate individual sounds instead of entire pieces ....

I use a similar method. The whole system is complex (not only csound,
a lot of common lisp, various scripts, makefiles, ...)  but briefly:

- not csd file but orc+sco
  + orc directory
  + sco directory

- name of the score file:

    orcname_...[_usedscript].sco

- name of the wav file

  orcname_blabla.sco  ->  orcname_blabla.wav

  (in the whole system I use `cs_' prefix for csound, so `cs_orcname_blabla.wav')

- csound options managed by the makefile that sets `--omacro' and `--smacro'

    make SR=44100 FSIZE=8192
    make HQ=1
    ...

- every sco file can have two relative executable scripts

    pre_name
    name.sco
    post_name

  The makefile performs

    ./pre_name
    csound [options] name.orc name_....sco
    TARGET=... ./post_name

  For example, `post_name' can convert a soundfile and/or add
  a description in a text file in `org-mode' for emacs. From this
  text file I can get html, pdf, ... files

  The destinations are separate dirs, for example:

     |-- html
     |-- pdf
     |-- txt
     `-- wav
         |-- 44100
         |-- 48000
         |-- 88200
         `-- 96000

I create sounds in this way and I don't have problems.

tito

On Fri, Feb 24, 2012 at 11:57:32PM -0800, Alex Weiss wrote:
> Hi csounders
> 
> I have a general workflow question for all of you as well as a proposal for
> a potential solution to one of my workflow problems. I often use csound to
> generate individual sounds instead of entire pieces (which, as I
> understand, is how many users use csound). Consequently, I either have one
> .csd per sound or at least one instr for it (with similar instrs grouped
> into one .csd). As I work on the sounds I obviously keep making changes to
> the .csd files to generate multiple versions. However, no matter how hard I
> try that always leads to chaos in the end: I come back weeks (or even
> months) later, find a couple of great wave files with synthesized sounds
> together with .csd, but can't figure out which .csd file corresponds to
> which wave file, or which parameters I used to generate them. I tried
> various filename schemes as well as orchestra commenting schemes, but all
> to no avail. Has anybody else experienced this problem? What are your
> workflows? I'm curious to hear how other people deal with this, or if I'm
> the only one...
> 
> After much thought, I think I found a potential solution to the problem.
> What if, upon rendering, a host embedded the csd as a chunk in the
> resulting .wav? That way every sound would carry its own code within
> itself, putting an end to the chaos. I understand that creating custom
> chunks in a .wav is non-standard and should be avoided, but from what I
> know almost all players/DAWs/etc simply skip chunks they don't understand,
> so the file would play back perfectly fine. The only problem would be
> making changes to the file, as most applications will probably overwrite
> the header upon writing to disk. But at least it's something... Any
> opinions?
> 
> Thanks,
> Alex
> 
> Send bugs reports to the Sourceforge bug tracker
>             https://sourceforge.net/tracker/?group_id=81968&atid=564599
> Discussions of bugs and features can be posted here
> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
>