Lou,

I was quoting a message from John ff, indicating which opcodes were omitted 
from *OLPCsound*. The statement about using these opcodes was made by John.

Except for those listed by John, all other opcodes should be included in 
OLPCsound ("event" - I surely hope so).

Perhaps John could clarify which opcodes are the "control" opcodes.

At any rate, I remain hopeful that the OLPCsound manual can be checked 
against the actual opcode list - and that, for example, bformdec and 
bformenc can be eliminated from the manual.

Art Hunkins

----- Original Message ----- 
From: "Lou Cohen" 
To: 
Sent: Tuesday, December 23, 2008 12:24 PM
Subject: [Csnd] Re: OLPCsound/Manual - control opocdes


Art, I just noticed your comment below that the ³control² opcodes, possibly
only used by you, should be removed or changed.

If by ³control² opcodes, you mean ³event², ³active² and ³mute² among others,
you are not alone. I depend heavily on these opcodes and my code would be
broken if they were removed or changed. Perhaps you are only referring their
occurrence in the OLPC; in which case this would not affect me, but I wasn't
sure from your note.

If you mean other opcodes, then I¹m curious... which?

regards and happy holidays,

Lou Cohen


On 12/10/08 16:15, "Art Hunkins     "  wrote:

> I understood from jpff that bformenc and bformdec were not included in
> OLPCsound. (Or babo.)
>
> They are, however, included in the OLPC user manual.
>
> According to John:
>
> The opcode components missing (from OLPCsound) are:
>
> Loris, STK, spat3d, ambisonics, scanned synthesis, the "control"
> opcodes (which I suspect are only used by me and should be removed or
> changed anyway), babo and the ATS opcodes; also no fluidsynth.
>
>
> Could someone (maybe Andres or John) go through the manual to check for 
> any
> other inconsistencies?
>
> Art Hunkins
>
>



Send bugs reports to this list.
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe 
csound"=