Dave's query points out a weakness in the Csound help/documentation that
needs addressing. I have experienced the same problem many times. As Csound
grows, the problem just gets worse.

In a nutshell the problem is: it's difficult to find what you are looking
for.

In Dave's case, there is no Help entry for "file output" for example. There
need to be general and commonly understood headings for opcode groupings,
with links.

I know it's possible to search, but doing so is cumbersome and imprecise,
especially for multiword phrases (even in quotes).

For example, hilbert. I had no idea this was a kind of filter and can be
used for frequency shifting. A listing of hilbert under "filters" as well as
"frequency shifter" would be most helpful.

May I stress the importance of using common words and phrases. "IIR",
"Butterworth" and "second order" mean almost nothing to me, but "filter"
does. I've nothing against the former (indeed they are technically crucial),
but "filter" is what is I need to find my way around Csound.

Art Hunkins

----- Original Message -----
From: "Dave Seidel" 
To: 
Sent: Thursday, March 16, 2006 10:59 AM
Subject: Re: [Cs-dev] questions on soundout opcode


> Thanks, Istvan, that's very helpful.  I hadn't noticed fout before, but
> it does just what I want.
>
> - Dave
>
>
> Istvan Varga wrote:
> > On Thursday 16 March 2006 15:55, Dave Seidel wrote:
> >
> >> If I clear out the  section, I get no output at all, and
the
> >> console states:
> >>
> >>      winmm: opening output device 0 (SB Audigy 2 [FEC0])
> >>      winmm: error: failed to open device
> >>      Failed to initialise real time audio output
> >
> > This simply means that your sound card (at least when using MME) does
> > not support the sample rate, buffer sizes, sample format, or number of
> > channels you want to use, and has nothing to do with the soundout
opcode.
> > Without an -o option, real time output is used instead (probably set as
> > default in .csoundrc).
> >
> >> If I put back my previous options (-g -W -o foo.wav), I get an empty
> >> foo.wav
> >
> > Which is not very surprising without any 'out' opcodes.
> >
> >> and I get the four output files specific in the soundout calls,
> >> but they are apparently raw files (this actually makes sense, but seems
> >> like it should be called out explicitly in the docs).
> >
> > soundout and soundouts always write raw (headerless) files, although
> > only the newer soundouts has correct documentation.
> >
> >> 1. Should a "-o ..." argument be necessary for soundout to work?  Am I
> >> missing some other (undocumented) prerequisite setting for soundout?
> >
> > No, see above why you get the error without -o.
> >
> >> 2. Is there any way for soundout to output anything other than a raw
> >> file?  If not, no problem, I'm just wondering.
> >
> > Well, it is possible, just not with soundout, but rather with fout.
> > For a floating point WAV file, use a format code of 16 (i.e. 10 for WAV
> > + 6 for floats); note that this is not supported by old 4.xx versions.
>
>
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by xPML, a groundbreaking scripting
language
> that extends applications into web and mobile media. Attend the live
webcast
> and join the prime developer group breaking into this new coding
territory!
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel



-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net