[Csnd-dev] Documenting new opcodes
Date | 2017-01-24 14:26 |
From | jpff |
Subject | [Csnd-dev] Documenting new opcodes |
i see new opcodes checked in but no documentation. I mean: linlin, xyscale, mtof, ftom, pchtom, bpf, ntom, mton, sc_lag, sc_lagud, sc_trig, sc_phasor |
Date | 2017-01-24 14:49 |
From | Rory Walsh |
Subject | Re: [Csnd-dev] Documenting new opcodes |
You could probably reach out through github: On 24 January 2017 at 14:26, jpff <jpff@codemist.co.uk> wrote: i see new opcodes checked in but no documentation. |
Date | 2017-01-24 15:04 |
From | jpff |
Subject | Re: [Csnd-dev] Documenting new opcodes |
I am standing by the protocol -- you write it, you document it. So clearly the author knows what they do while i do not! On Tue, 24 Jan 2017, Rory Walsh wrote: > You could probably reach out through > github:https://github.com/csound/csound/pull/751 > > > On 24 January 2017 at 14:26, jpff |
Date | 2017-01-24 15:21 |
From | Rory Walsh |
Subject | Re: [Csnd-dev] Documenting new opcodes |
Perhaps Eduardo is not aware of this protocol. I'm sure a gentle reminder would do the trick ;) On 24 January 2017 at 15:04, jpff <jpff@codemist.co.uk> wrote: I am standing by the protocol -- you write it, you document it. So clearly the author knows what they do while i do not! |