Hello Gabriel and the Team,

Some questions, suggestions and my preferences:-

>Where possible, use tables generated inside the orchestra (by means of
>ftgen opcode).


?? Is it ok to use the .csd format and generate tables in the score section?
I also prefer .csd because the flags are evident.

>At this point we have to divide the work of coding the examples.

?? Which version/variant of csound do we use?

>Choose some opcodes you want to test, and let know them to the list.


I, Richard Bowers, shall attempt the following, if that's ok. The platform
shall be exclusively Cyrix 'Pentium' processor (233Mhz) PC under Win95 (DOS
window):-

1) MIDI Convertors (excluding sliders)
2) Input and Output (but not above 2 channels)
3) Sensing and Control

(BTW I would love to know who would be doing the Spectral Operators because
I've had no joy whatsoever from them.)

For the record I shall only be testing at 44100 Hz, mono and stereo which,
with the 4 suggested k-rates, produces eight seperate passes of each test.

Incidentally, it may be better to seperate mono orchs from stereo orchs
because many opcodes have different numbers of outputs according to nchnls
(ie. involves careful rewriting) - which hampers their long-term usefulness
as test orchs. May I suggest that we 'mirror' the mono tests with the stereo
(and higher) tests in seperate files.

The sr/kr variants do not, I imagine, present the need to rewrite parts of
the orchestra (except where analysis files are used and input audio files -
anything else?)

I shall test the MIDI opcodes using a prepared MIDI file as input. Maybe
Gabriel could supply this for consistency's sake - or is that not too
important?

All the best,
Richard.


--