[Csnd] -L users and examples for the manual
Date | 2009-03-18 07:52 |
From | "Dr. Richard Boulanger" |
Subject | [Csnd] -L users and examples for the manual |
Dear Csounders, Are there any of you out there who use the *read line-oriented real-time score events from Device* features of Csound and could share some advice, and examples with us and for possible inclusion in the manual? This description in the manual has alway been pretty cryptic and in my opinion has always needed to be expanded in the expanded form, duplicated and re-located Read line-oriented real-time score events from device DEVICE. The name stdin will permit score events to be typed at your terminal, or piped from another process. Each line-event is terminated by a carriage-return. Events are coded just like those in a standard numeric score, except that an event with p2=0 will be performed immediately, and an event with p2=T will be performed T seconds after arrival. Events can arrive at any time, and in any order. The score carry feature is legal here, as are held notes (p3 negative) and string arguments, but ramps and pp or np references are not. -dr.B. Dr. Richard Boulanger Professor of Electronic Production and Design Music Technology Division Berklee College of Music 1140 Boylston Street Boston, MA 02135 617-747-2485 (office) |
Date | 2009-03-19 03:05 |
From | Tobiah |
Subject | [Csnd] Re: -L users and examples for the manual |
Dr. Richard Boulanger wrote: > Dear Csounders, > > Are there any of you out there who use the *read line-oriented real-time > score events from Device* features of Csound and could share some > advice, and examples > with us and for possible inclusion in the manual? Many years ago, I made use of this flag. This was long before FLTK widgets. I wrote a TCL/TK program that consisted of a bank of sliders. One would adjust the 'pfield' sliders, then hit a bang. The stdout would print a csound event, and, when piped to a csound -L process, would cause a csound event. I wrote this because the cycle of editing and running scores was too slow when what I needed was a usable value for some arbitrary orc parameter. I don't have the code any longer, but that was the one time that I found the -L flag to be of some use. Tobiah |